TL;DR: Intent data tells you someone at a company might be interested. Intent-based prospecting tells you who, why and when to reach out. This guide walks you through the full migration in six steps: audit your current intent stack, map intent categories to concrete signals, build a scoring model, connect your CRM, run both systems in parallel, then cut over. Teams that complete the switch typically see reply rates jump 2-3x while cutting prospecting tool spend by 30-50%.
What is the difference between intent data and intent-based prospecting?
Intent data aggregates anonymous browsing behaviour across third-party publisher networks. A provider might tell you that employees at Acme Corp have been reading articles about “CRM migration” over the last two weeks. The data is probabilistic, usually company-level, and delayed by days.
Intent-based prospecting takes a different approach. Instead of inferring interest from anonymous page views, it monitors concrete, verifiable business events: a company just raised a Series B, a VP of Sales was hired last Tuesday, a competitor’s contract was renewed, a new job posting appeared for “Revenue Operations Manager.” Each of these is a discrete signal with a timestamp, a source and, in most cases, an identifiable person attached.
The practical consequence is straightforward. Intent data gives you a list of accounts that might be in-market. Signals give you a reason to start a conversation.
Prerequisites
Before you begin the migration, make sure the following pieces are in place:
- Access to a signal API. This guide uses the Rodz API. If you do not have an API key yet, create one from your dashboard under Settings > API Keys and review the API Reference for endpoint details and rate limits.
- A CRM with open API access. HubSpot, Salesforce or Pipedrive all work. You need the ability to create custom properties and trigger workflows from external events.
- A documented ICP (Ideal Customer Profile). You should know your target company size, industry, geography and the personas you sell to.
- Historical performance data. Export the last 6-12 months of won and lost opportunities from your CRM. You will need this for the scoring calibration step.
- A workflow automation tool. Make, n8n or Zapier, whichever your team already uses.
Intent data vs. intent-based prospecting: a comparison
The table below highlights the structural differences between the two approaches.
| Dimension | Intent Data | Intent-Based Prospecting |
|---|---|---|
| Granularity | Company-level (anonymous) | Contact- and company-level (identified) |
| Freshness | Aggregated weekly or bi-weekly | Real-time or near-real-time |
| Source transparency | Opaque publisher networks | Verifiable public sources (registries, job boards, press, social) |
| Signal types | Topic-keyword clusters | Discrete events: funding, hiring, contract, tech change, social mention |
| Actionability | ”Acme is surging on CRM topics" | "Acme just posted a RevOps Manager role and raised 12M EUR” |
| False-positive rate | High (30-60% of flagged accounts show no real buying activity) | Low (events are factual, not inferred) |
| Personalisation potential | Generic topic mention | Specific event reference in outreach |
| Integration model | CSV export or flat API | Webhooks, streaming, REST with filtering |
| Typical cost | 20-60k EUR/year for mid-market | Pay-per-signal or tiered API plans, often 40-70% less |
| Measurement | Hard to attribute (company-level match) | Direct attribution (signal-to-meeting-to-deal) |
If most of your outbound pipeline already comes from referrals, inbound leads or manual research, the jump to signals will feel natural. If you rely heavily on intent-data-driven BDR sequences today, the migration requires more planning, but the payoff is larger.
The 6-step migration roadmap
Step 1: Audit your current intent stack
Start by cataloguing every intent data source your team uses. For each source, record:
- Provider name and annual cost.
- Topic clusters being tracked (e.g., “ERP migration”, “sales automation”).
- Volume: how many accounts are flagged per week?
- Conversion rate: of flagged accounts, how many turned into qualified opportunities in the last two quarters?
- Workflow: where does the data land (CRM, spreadsheet, Slack)?
Most teams discover that only 2-3 of their 8-12 tracked topics generate meaningful pipeline. The rest produce noise. This audit gives you a clear picture of what the intent data is actually doing versus what you are paying for.
Create a simple scorecard:
Topic Cluster | Accounts/Week | Opps Created | Cost Share
--------------+---------------+--------------+-----------
CRM migration | 42 | 3 | 22%
Sales tools | 67 | 1 | 18%
HR software | 38 | 0 | 15%
...Topics with zero or near-zero opportunity creation are candidates for immediate removal.
Step 2: Map intent categories to concrete signals
For every intent topic that does generate pipeline, identify the real-world events that would indicate the same buying context. This is the core intellectual work of the migration.
| Intent Topic | Mapped Signals |
|---|---|
| ”CRM migration” | Job posting for CRM Admin or RevOps; mention of CRM vendor on company blog; tech stack change detected on website |
| ”Sales hiring” | New VP Sales or CRO appointment; 3+ SDR/BDR job postings in 30 days; funding round (often precedes sales hiring) |
| “Data privacy” | DPO role posted; CNIL registration (France); public mention of GDPR audit |
| ”Office expansion” | New office address registered; commercial lease filing; job postings in a new city |
The Rodz API exposes signal categories that cover most of these scenarios: financial events (fundraising, M&A, company registrations), HR signals (job postings, executive changes), competitive and market signals (public tenders, competitor relationships) and digital-presence signals (tech stack changes, content publishing, social mentions). Review the full list in the API Reference.
Step 3: Build a signal scoring model
Not every signal deserves the same response. A Series B fundraise is a stronger buying indicator than a single blog mention. You need a scoring model that ranks signals by relevance to your ICP.
A good starting point is the Balance scoring framework, which weights signals across three dimensions:
- Fit: Does the company match your ICP on firmographics?
- Timing: How recent is the signal? Signals decay. A job posting from yesterday is worth more than one from six weeks ago.
- Intensity: How many correlated signals has this account triggered in a rolling 30-day window?
For a detailed walkthrough of building a scoring model on top of the Rodz API, see the Balance scoring guide.
Here is a simplified scoring table to start with:
| Signal Type | Base Score | Decay (per week) |
|---|---|---|
| Fundraising round | 40 | -5 |
| Executive hire (VP+) | 35 | -5 |
| 3+ job postings (same department) | 30 | -4 |
| Tech stack change | 25 | -3 |
| Public tender published | 25 | -5 |
| Social mention of pain point | 20 | -4 |
| New office/registration | 15 | -2 |
| Single job posting | 10 | -3 |
An account becomes “signal-qualified” when its composite score crosses a threshold you define, for instance 50 points within a 30-day window. Calibrate this threshold against your historical CRM data: take the won deals from the last six months, retroactively score them and find the threshold that captures 80%+ of winners without flooding your team with false positives.
Step 4: Connect your CRM and routing
Signals are only useful if they reach the right rep at the right time. Set up the data flow:
- Configure webhooks in the Rodz API to push matching signals to your automation tool (Make, n8n or Zapier).
- Enrich the signal payload. When a signal fires, call the company enrichment and contact enrichment endpoints to attach firmographic data and contact details.
- Write to CRM. Create or update the company record, attach the signal as a timeline event, and assign a score.
- Route to a rep. Use your CRM’s assignment rules (territory, round-robin, named accounts) to notify the right person.
- Trigger a sequence. If the score crosses your threshold, auto-enrol the contact in a personalised outbound sequence that references the signal.
The entire pipeline, from signal firing to sequence enrolment, should take less than five minutes. That speed is what makes intent-based prospecting fundamentally different from weekly intent data dumps.
Step 5: Run both systems in parallel
Do not cut off your intent data on day one. Run both systems side by side for 4-6 weeks and compare:
- Volume: How many accounts does each system flag per week?
- Overlap: What percentage of signal-qualified accounts were also flagged by intent data?
- Conversion: Of the accounts flagged by each system, how many progressed to a qualified meeting within 30 days?
- Speed to action: How quickly did a rep reach out after the flag?
Track these metrics in a shared dashboard. Most teams find that the overlap is smaller than expected (typically 15-25%), which means intent data was surfacing a largely different, and usually less actionable, set of accounts.
During this phase, run A/B tests on outbound sequences: one version uses generic intent-based messaging (“We noticed your company is exploring CRM solutions”), the other references a specific signal (“Congrats on the Series A. Scaling the sales team after a raise often surfaces CRM pain points. Here is how we help.”). Measure reply rates, positive reply rates and meetings booked.
Step 6: Cut over and optimise
Once the parallel run confirms that intent-based prospecting outperforms intent data on your key metrics, begin the transition:
- Cancel or downgrade intent data contracts. Keep one provider on a minimal plan if your team still values the coverage as a secondary input.
- Redirect budget. Reinvest savings into signal API credits, sequence tooling or additional SDR capacity.
- Refine scoring monthly. Every month, pull the deals that closed and the signals that preceded them. Adjust base scores and decay rates based on actual outcomes.
- Expand signal coverage. Start with 3-4 signal types, then add more as your team builds confidence. Financial signals are the easiest starting point. HR and competitive signals add depth over time.
- Document playbooks. For each high-value signal type, write a one-page playbook: what the signal means, how to personalise the outreach, what the first message should reference and what the follow-up cadence looks like. Tools like Claap can help here by recording sales calls triggered by specific signals, so your team can review what messaging works best for each signal type.
Case study scenario: SaaS mid-market team migration
Consider a 12-person sales team at a B2B SaaS company selling a project management tool to mid-market companies (100-2,000 employees) in France and the Benelux region.
Before (intent data):
- The team subscribed to a major intent data provider at 38,000 EUR per year.
- They tracked 10 topic clusters including “project management”, “agile transformation”, “remote work tools” and “digital workplace”.
- The platform flagged an average of 280 accounts per week.
- BDRs worked these lists sequentially, sending a generic multi-touch sequence.
- Conversion from flagged account to qualified meeting: 1.2%.
- Average cost per qualified meeting from intent-sourced outbound: 310 EUR.
After (intent-based prospecting):
- The team configured the Rodz API to monitor five signal types: fundraising rounds, VP/Director-level hires in product or operations, 3+ job postings in project management or PMO roles, tech stack changes (removal of competitor tools) and public tenders mentioning project management.
- Signals were pushed via webhook to Make, enriched with contact data, scored and routed to HubSpot.
- Average of 85 signal-qualified accounts per week (70% fewer, but higher quality).
- BDRs sent sequences that referenced the specific signal in the opening line.
- Conversion from signal-qualified account to qualified meeting: 4.1%.
- Average cost per qualified meeting from signal-sourced outbound: 95 EUR.
- Annual spend on signal tooling: 14,400 EUR (API plan + Make subscription).
Net result: 3.4x higher conversion rate, 69% lower cost per meeting and 23,600 EUR in annual tool savings.
This scenario is not unusual. The mechanics are simple: fewer, higher-quality targets plus personalised outreach equals better outcomes.
ROI framework: how to calculate the business case
Before pitching the migration internally, build a simple ROI model. Here are the inputs you need:
Cost side
| Line Item | Intent Data (Current) | Intent-Based (Projected) |
|---|---|---|
| Platform/API subscription | A | B |
| Enrichment tools | C | D (often included in signal API) |
| BDR hours spent on list review and cleanup | E | F (reduced, signals are pre-qualified) |
| Sequence/automation tooling | G | G (unchanged) |
| Total cost | A+C+E+G | B+D+F+G |
Performance side
| Metric | Intent Data (Current) | Intent-Based (Projected) |
|---|---|---|
| Accounts flagged/week | X | Y |
| Conversion to qualified meeting | R1 | R2 |
| Meetings/week | X * R1 | Y * R2 |
| Average deal value | V | V |
| Win rate from meeting | W | W (conservative: keep constant) |
| Pipeline generated/week | X _ R1 _ V / W | Y _ R2 _ V / W |
ROI calculation
Annual Savings = (Intent Cost) - (Signal Cost)
Pipeline Uplift = (Signal Pipeline/week - Intent Pipeline/week) * 52
ROI = (Annual Savings + Pipeline Uplift * Win Rate * Avg Deal Value)
/ Signal CostEven with conservative assumptions (same win rate, same deal size), most teams see a positive ROI within the first quarter because the cost savings alone offset the signal API spend, and the conversion improvement is pure upside.
To refine these projections with real scoring data, integrate the Balance scoring model and measure actual signal-to-meeting conversion rates during your parallel run phase.
Frequently asked questions
Can I use intent data and signals together instead of migrating fully?
Yes, and many teams do during the transition. Intent data can serve as a secondary layer that confirms signal-qualified accounts. If an account triggers both a concrete signal (fundraise, executive hire) and an intent surge on a relevant topic, you can boost its priority score. However, most teams find that once signal workflows are mature, the marginal value of intent data drops sharply. The intent subscription becomes hard to justify on a cost-per-insight basis.
How long does a full migration take?
Plan for 8-12 weeks end to end. The first two weeks cover the audit and signal mapping. Weeks 3-4 are spent building the scoring model and CRM integration. Weeks 5-10 are the parallel run. Weeks 11-12 are the cut-over and documentation phase. Smaller teams with fewer legacy workflows can move faster. Enterprise organisations with multiple intent data contracts and complex CRM environments may need 16 weeks.
What if my intent data provider also offers “signals” or “buying triggers”?
Some intent providers have started labelling features as signals. Look under the hood. If the “signal” is derived from the same anonymous browsing data (topic surges, keyword clusters), it is still intent data with a new label. True signals come from verifiable, public sources: government registries, job boards, press releases, social platforms, DNS records. Ask your provider for source transparency. If they cannot tell you exactly where a data point came from, it is intent data.
Do I need a data engineer to set this up?
Not necessarily. If you are comfortable with a workflow automation tool like Make or n8n and your CRM’s API, you can handle the integration yourself. The Rodz API uses standard REST conventions with JSON payloads and webhook delivery. For a production-grade setup with custom scoring, historical backfills and multi-CRM routing, a data engineer or a RevOps specialist will accelerate the work. Consult the API documentation for endpoint specifications and code examples.
How do I handle signal volume as my monitored account list grows?
Signal volume scales linearly with the number of accounts and signal types you monitor. Two strategies keep it manageable. First, use filters at the API level: only subscribe to signal categories that map to your validated use cases. Second, let the scoring model do the prioritisation. Your team should only see accounts that cross the qualification threshold. Everything else stays in the system but does not generate a notification. The API’s rate limits and pagination are designed for high-volume usage. Refer to the API Reference for details on bulk endpoints and rate-limit headers.
What metrics should I track to prove the migration is working?
Focus on five metrics during and after the migration:
- Signal-to-meeting conversion rate: percentage of signal-qualified accounts that become a qualified meeting within 30 days.
- Time-to-action: average hours between signal firing and first rep outreach.
- Positive reply rate: percentage of outbound messages that receive a non-negative response.
- Cost per qualified meeting: total signal tooling spend divided by meetings generated.
- Pipeline velocity: average days from signal-qualified to closed-won.
Track these weekly during the parallel run and monthly after cut-over.
What signal types should I start with?
Start with the signals that are easiest to act on and have the highest correlation with your past wins. For most B2B teams, that means:
- Fundraising and M&A events. Companies that just raised money are actively investing. They have budget and urgency.
- Executive and leadership changes. A new VP typically brings new tools and vendors within the first 90 days.
- Job postings in your buyer’s department. If a company is hiring three sales ops people, they are probably scaling, and scaling creates tool needs.
Once these are working, layer in tech stack changes, public tenders and social signals for additional coverage.
How does intent-based prospecting affect messaging and copywriting?
It transforms it. With intent data, the best you can do is reference a broad topic: “I noticed your team is exploring data analytics solutions.” With signals, you can write: “I saw you just opened a Head of Data role in Lyon. Teams hiring at that level usually need infrastructure in place before the new hire arrives. Here is how we help.” The specificity increases reply rates because it demonstrates genuine awareness of the prospect’s situation. Every signal type should have a corresponding messaging template that your team customises per prospect.
Next steps
The migration from intent data to intent-based prospecting is not a technology swap. It is a shift in how your team identifies, prioritises and engages potential customers. The technology is the enabler, but the real change is operational: fewer accounts, better research, more relevant outreach.
To get started:
- Run the intent audit from Step 1 this week.
- Create your Rodz API key and explore the signal categories available for your market.
- Map your top three intent topics to concrete signals using the framework in Step 2.
- Build your first scoring model following the Balance scoring guide.
The teams that move first will have a structural advantage. Signals are still underused in most markets, which means your outreach will stand out. That window will not stay open forever.