A lead is not a pursuit

Here's a test worth running on your own business. Walk over to whoever owns outbound and ask them how many companies you're currently pursuing. Not how many leads are in the database, and not how many emails went out last week. How many live pursuits exist right now, and which of them are owed something today.

In most businesses they'll go and look in three places and then give you a number they don't fully believe. That isn't a failure of the person. Nothing they own was built to answer it.

Five tools, five wrong units

A typical outbound stack has four or five products in it, and each one is genuinely good at its job. The problem is that none of their jobs is the actual job.

A lead database counts records. It'll tell you there are eleven thousand companies matching your filter. It has no opinion about which of them are worth your time, because it has never met your business and doesn't know what you sell.

An enrichment tool counts fields. It fills in headcount, funding, tech stack. Useful, and still not judgement. Knowing a company has ninety employees doesn't tell you whether ninety is the right size for what you do.

A sequencer counts messages delivered. This is the one that looks most like it's doing the work, and it's the one that stops soonest. It sends on a schedule and then, the instant a human replies, it hands the entire thing back to a person and goes quiet. The moment the interesting part begins is the moment it stops participating.

A CRM counts stages. And specifically, stages that somebody remembered to update. Your CRM's picture of reality is exactly as good as your team's discipline on a busy Thursday, which is to say it's a lagging, optimistic, partial account of what happened.

An agency counts activity. They'll report sends, opens, replies and meetings, and some of them are very good. But the pursuit lives in their heads and their spreadsheets, which means the day the relationship ends, so does every piece of context about who you were chasing and why.

What a pursuit actually is

The unit of outbound work isn't a lead and it isn't a message. It's a company you've decided to chase, held in a specific state, with something owed on it.

That definition has three parts and each one is doing work. Decided to chase means it passed a judgement, so it isn't just a row that matched a filter. Held in a state means the system knows where this one has got to without anyone typing it in. Something owed means there's a next action with a clock on it, and the clock is the part everything else misses.

Once you hold that, the questions you can ask change completely. Not how many emails went out, but how many pursuits are waiting on us rather than on them. Not what the reply rate was, but which pursuits have been sitting in the same state for longer than they should. Not how many leads are in the list, but how many we've decided are genuinely not worth continuing, which is a number almost nobody tracks and which tells you more about your targeting than any open rate.

Sent is not an outcome

Watch the language a sequencer uses and you'll notice it reports on itself rather than on the world. Delivered. Opened. Clicked. Every one of those describes something that happened to a message, not something that happened to a relationship.

A pursuit has real endings, and there are more of them than people expect. It can end because someone said yes and a conversation is booked. It can end because someone said no. It can end because they never replied and you've decided, deliberately, to stop. And it can end because you learned something halfway through that disqualifies them, which is the most useful ending of all and the one that no stack records.

And a pursuit needs to be allowed to end. This sounds obvious and it's routinely violated: systems that can't close a pursuit keep nudging forever, and that's how a company acquires a reputation in its own market that nobody in the building chose. The ability to stop is a feature.

The clock is the whole thing

If you had to pick one part of this that a person is worst at, it's the waiting.

Everything else in outbound has a natural trigger. A reply arrives and you answer it. A meeting is booked and you prepare. But a pursuit sitting in "waiting, follow up due in three days" has no trigger at all. Nothing arrives. Nobody chases you. The only thing standing between that pursuit and silence is a person remembering, on the right day, among forty other things.

This is why outbound is inconsistent in almost every business that does it in house, and why it's inconsistent in a very particular pattern: strong for three weeks after someone decides to focus on it, then quietly decaying. Nobody stops doing outbound. The follow ups just stop landing on the day they were due, and then stop landing at all.

What changes when the unit is right

Hold pursuits rather than messages and the whole activity becomes answerable. You can say, at any moment, how many companies you're chasing, which are owed something today, which have gone quiet past the point where quiet means no, and which you've decided against and why. None of that requires anyone to have updated anything.

It also becomes improvable, because now you have something to learn from. Which kinds of company reach a conversation and which never do. Which angle moved things. Where pursuits reliably die. A system counting sends can only ever tell you to send more.

The uncomfortable version of this argument is that most outbound problems aren't effort problems. Businesses that feel like their outbound isn't working are usually doing plenty of it. What they don't have is anything holding the state of it, so the work gets done in bursts by whoever has capacity, and the compounding never starts.