Finding the customers you already know how to sell to

There is a gap between the strategist who sells a framework and hands it off, and the agency that supplies volume but needs the thinking done for it. What is missing is the person making strategic decisions inside the execution: which trigger actually means a buying window opened, which person inside the account, and what language makes a technical capability legible as their problem. Those decisions only get made well by someone who understands the buyer’s world, and they get made one account at a time.

This is not demand generation

The two get used interchangeably and they are different jobs. Demand generation creates awareness of a problem in a market that has not decided it matters yet — content, category language, committee scoring, programs measured over quarters. Demand capture assumes the problem is already real to a defined set of accounts and goes to get the conversation.

Different time horizons, different proof, different failure modes. Demand generation fails when the market never adopts the framing. Demand capture fails when the triggers are thin or the message does not land, and you know within weeks.

Where the strategy actually sits

Two decisions carry almost all the outcome, and both are upstream of any send.

1. Trigger selection. Which observable events in a market indicate a real buying window — a new obligation, a leadership change, a funding round, an incident, a published commitment — and which ones only look like signal.
2. The message. Translating a technical capability into something a specific person recognizes as their own problem, in their vocabulary, at the moment the trigger makes it urgent.

Everything downstream — list building, sequencing, sending, following up — is execution that a good delivery team does better than we would. What they cannot source on their own, in a technical market, is the judgment about which trigger and what to say.

A worked example

A company selling vector surveillance — biological threat detection, effectively situational intelligence with a different threat model.

1. Trigger: a public health agency or large employer publishes an updated communicable-disease or continuity plan naming early detection as a gap. Observable, dated, and specific to one accountable owner.
2. Message: not “vector surveillance platform.” The message is about the interval between an outbreak starting and anyone knowing — the same decision-under-uncertainty problem the plan just admitted to, in the language the plan itself used.
3. Meeting: with the person who owns that plan, about a gap they wrote down themselves, within weeks of writing it.

The trigger made the timing right. The message made the capability legible. Neither came from a list.

Feasibility comes before a number

Before anyone commits to anything, the delivery team assesses the market: trigger density, list availability, reply likelihood, and whether the ICP is defined tightly enough to write to. Out of that assessment comes a meeting number they commit to and have to hit.

That sequence matters. The number comes from the team that has to deliver it, not from us, and not before the market has been looked at. If the assessment comes back thin, we say so before anyone signs — a market with weak triggers or a vague ICP produces meetings nobody wants, and booking them anyway is how outbound earned its reputation.

It doubles as message testing

Outbound is the fastest honest read on a message. A positioning statement can survive a workshop indefinitely; it cannot survive two hundred sends to the right people without producing a signal. Reply rate, which trigger pulled, which segment answered and which stayed silent — that is market evidence, and it arrives in weeks rather than quarters.

So this is useful earlier than a booked-meeting goal suggests. A company still resolving product-market fit can run the same motion as a test: several triggers, several framings, several segments, and a read-out on which combination earned a conversation. The meetings are the outcome either way, but what you learn about which description of the work lands is often the more durable result — and it feeds directly back into messaging and positioning.

What it requires from you

Demand capture assumes three things already exist: a defined ideal customer profile, a sales process that can handle the meetings, and a product whose value is real to that buyer. If those are not in place, this is the wrong order of operations — that is a positioning project first, because outbound at scale only amplifies whatever clarity you already have.

It works in any technical market with a defined ICP. Security, risk, and resilience is where we have the deepest buyer knowledge, which shortens the trigger and message work considerably.

How it fits with everything else

This is a named add-on rather than a standalone retainer. It sits on top of existing work — a fractional CMO engagement, a positioning project, a go-to-market build — because the trigger and message work draws directly on the positioning decisions made there. Added to an engagement where that thinking already exists, it starts producing in weeks.

Related reading

1. Automating outbound without automating yourself into the spam folder
2. Start with 40 names.
3. The lead machine myth
4. You can run two channels. Not six.
5. Fractional CMO vs agency

What people ask