Inbound led outbound
Intent based outbound for B2B
Inbound led outbound targets accounts already showing buying signal, such as content engagement, pricing page visits, hiring patterns or intent data, then routes them into personalised outreach within a set window. It replaces the cold, purchased list with a list the account itself built through its own behaviour.
- Signal sources
- Site behaviour, intent data, hiring, content engagement
- Routing window
- Same day to 48 hours from signal
- List source
- Behaviour, never a purchased database
What this covers
Cold outbound built on a purchased list has a low hit rate because the account has given no indication it has a problem right now. Inbound led outbound inverts the order: signal comes first, list comes second. An account visits a pricing page, downloads a specific guide, or shows up in intent data against a defined topic, and that behaviour is what puts them on the list, not a firmographic filter alone.
This exists to fix the two failure modes of most outbound programmes: reps burning time on accounts that show no sign of a problem, and real signal sitting unrouted in a marketing tool for two weeks before anyone acts on it.
- A contact fills out a form or downloads a guide and does not hear from anyone for ten days
- Reps work a purchased list with a 1 to 2 percent reply rate because nothing on it indicates intent
- Intent data is bought and reviewed monthly instead of routed the day it fires
- The same account gets touched by three different sequences because nobody owns the routing rule
This is for you if
- You already have some inbound volume: content, webinars, a free tool, or paid traffic worth acting on
- You have sales capacity that is currently under-fed rather than overloaded
- You can agree a routing rule and stick to it without every deal becoming an exception
This is not for you if
- You have no inbound signal at all yet and need demand created before it can be captured
- Sales is already at full capacity and cannot absorb faster-routed leads
- You want a one-off list to run once rather than an ongoing routing process
Verdict: With no inbound volume to route against, the right service is demand generation first, this second.
How the engagement runs
Signal to outreach flow
Signal capture
Site, product, intent and hiring data pulled into one view
Scoring
Signals weighted so noise does not swamp real intent
Routing
Qualifying accounts assigned within the agreed window
Outreach
Personalised sequence referencing the actual signal, not a template
Feedback loop
Reply and meeting outcomes fed back to re-weight scoring
- 1
Days 1 to 30
Map every signal source already available: web analytics, product usage if there is a free tier, intent data if it is licensed, hiring signals, content downloads. Agree which signals actually correlate with a real opportunity by checking them against closed-won history. Build the scoring rule and the routing window.
- 2
Days 31 to 60
Turn on routing for the highest confidence signals first. Write outreach that references the specific signal, not a generic opener, and get sales sign-off on the first sequences. Track reply rate and meeting rate by signal type so weak signals get demoted quickly.
- 3
Days 61 to 90
Expand to the next tier of signals once the first tier is proven. Tighten the routing window if speed is the bottleneck, or the scoring rule if volume is too high for sales to work. Document the full routing logic so it does not live only in one person's head.
What you get
Artefacts and rhythm
- ✓A documented signal map: what counts as intent and where it comes from
- ✓A written routing rule with the response window sales has agreed to
- ✓Outreach sequences built per signal type, not one generic template
- ✓A weekly reply and meeting rate report broken out by signal source
- ✓A monthly review to retire signals that are not converting
How it is measured
Signal to meeting rate
Meeting rate = Meetings booked / Accounts routed on that signal
- Meetings booked counts only meetings that hold, not scheduled and no-showed
- Accounts routed is the count that passed the scoring threshold for that signal type
- Rate is tracked per signal source so weak signals can be identified and dropped
Example: If pricing page visits route 40 accounts and produce 6 held meetings, that signal runs at a 15% meeting rate, which can then be compared against intent data or content download signals.
| Signal type | Accounts routed | Held meetings | Meeting rate |
|---|---|---|---|
| Pricing page visit | 40 | 6 | 15% |
| Third party intent data | 120 | 9 | 7.5% |
| Content download | 80 | 4 | 5% |
What we will not do
- Buy or use a purchased cold list and call it inbound led outbound
- Route every signal at the same priority; weak signals get demoted, not treated equally
- Promise a specific reply rate before signal quality has been checked against your own closed-won data
- Build sequences that hide the fact a signal triggered the outreach; the message names it
Objections, answered
The strongest case against this
This sounds like it needs a big martech stack we do not have.
It needs whatever signal already exists in your analytics, CRM and any intent tool you license, connected into one routing rule. Most teams already have more usable signal than they think, sitting unrouted. The first 30 days is finding out what you actually have before recommending anything to buy.
The strongest case against this
Won't this just mean fewer accounts get worked overall?
Yes, and that is the point. A rep working 40 accounts with real signal against them will book more meetings than a rep working 400 cold accounts with none. The trade is volume for hit rate, and it is a trade sales capacity data almost always supports given how tight quota attainment already is.
The strongest case against this
Intent data is unreliable. Why build a process around it?
Intent data alone, unchecked against your own outcomes, is unreliable. That is why the first 30 days checks every signal source against closed-won history before it earns a place in the routing rule. Signals that do not correlate with real pipeline get dropped, whatever the vendor promised when it was sold.
Common questions
- What counts as a buying signal here?
- Anything the account does that correlates with a real opportunity in your own closed-won history: pricing page visits, specific content downloads, product trial usage, licensed intent data against defined topics, or hiring patterns for roles tied to your product. What counts gets checked against your data, not assumed from a vendor pitch.
- How is this different from lead scoring in marketing automation?
- Lead scoring usually sits inside one tool and scores individual contacts on form fills and email opens. This works at the account level across every signal source available, including ones outside the marketing automation platform, and it is tied directly to a routing rule sales has agreed to.
- Do we need to buy intent data to do this?
- No. Licensed intent data can be one input if you already have it or want to add it, but plenty of usable signal exists in web analytics, product usage and CRM history first. The signal map in the first 30 days will show what is already available before recommending a purchase.
- How fast does routing actually need to happen?
- Fast enough that the signal is still live when the rep reaches out, typically same day to 48 hours. The exact window depends on the signal type; a pricing page visit decays faster than a hiring signal, so the routing rule sets different windows per source.
- What if sales does not have capacity to work more accounts?
- Then the fix is not more accounts, it is fewer, higher confidence ones. This service is built to reduce volume and raise hit rate, which fits a capacity constrained team better than a cold outbound programme that adds volume with no signal behind it.
- Does this replace our existing outbound sequences?
- It replaces the list logic behind them, not necessarily the sequence copy itself, though the copy usually changes too since it needs to reference the actual signal. Existing sequences aimed at a purchased list get retired in favour of ones triggered by routing rules.
- How do you know a signal is actually working?
- Each signal source is tracked separately for reply rate and held meeting rate, not blended into one outbound number. A signal that is not producing meetings gets demoted or dropped within a review cycle rather than kept because it is easy to collect.
- Can this work for a company with very low inbound volume?
- It works better with some existing inbound volume to route against. With very little signal, the honest recommendation is to build demand generation activity first so there is something worth routing, rather than forcing outbound onto a thin signal base.
- How does this fit with the rest of a demand programme?
- It sits downstream of demand generation, which is what produces the signal in the first place, and it works alongside predictive LTV scoring to decide which signals are worth prioritising when routing capacity is limited.
Read the thinking behind it
Want this run for you?
Tell us what you are spending and where the pipeline stalls. If this is not the right first step for you, we will say so.