Two companies launched from zero
Both founders wanted leads first. Neither company had written down who the product was for, so we did that before building any outbound.
- Role
- Independent GTM consulting
- Clients
- Startup Support · Catalyst Holdings
- Order
- Positioning, then outbound, then paid
- Sectors
- SaaS and architecture auditing
Both of them asked for leads
Two early-stage companies, a year apart, in unrelated markets: one a SaaS product, one an architecture-auditing practice. Both arrived with the same request, phrased almost identically: they needed more leads, and they wanted outbound built.
Neither of them could finish this sentence: we help ___ do ___, instead of ___.
Every downstream decision depends on that sentence. Who to contact, what to open with, which objection to pre-empt, what the first thirty seconds of a call sounds like, what counts as a qualified lead at all. Building outbound before it exists means building a machine that sends a guess to a list, measuring the result, and learning nothing from it, because when it fails you cannot tell whether the list, the message or the premise was wrong.
The order
Same sequence both times: positioning, then a repeatable outbound motion, then paid. Each stage is only affordable because the one before it has already narrowed what you are spending on.
Positioning, by subtraction
Both engagements started by removing customers rather than finding them. Who has this problem badly enough to pay this year, what are they doing about it today, and what would have to be true for them to switch. The SaaS product could plausibly serve six segments and was therefore compelling to none; the auditing practice was selling on credentials into a market that assumes credentials and buys on turnaround time.
The output is a one-paragraph claim, a named segment narrow enough to build a list from, and a written note on which objection kills the deal. Outbound tests all three as soon as it starts, which is why they come first.
Outbound as an instrument
Then the acquisition infrastructure: sending domains and authentication, a list built against the segment rather than bought, sequences written to the named objection, a dialer motion behind the email, and a CRM configured so that what happened is recoverable a month later. These are the same components described in the other projects.
What is different at this stage is the purpose. Early outbound is a measuring instrument that occasionally produces revenue. A hundred contacts against a sharp segment answers questions no amount of internal discussion will: which title replies, which objection arrives first, whether the problem is urgent or merely acknowledged.
Paid last, deliberately
Paid acquisition is an amplifier and amplifiers are indifferent to what you feed them. Running ads before there is evidence of what converts buys traffic against an untested claim at a price per click. Both companies got to paid, and both got there with a landing page and an angle that outbound had already proven, which is the difference between a budget and a donation.
The part you’d be right to argue with
A founder with twelve months of runway hears “spend the first six weeks on positioning” as a consultant delaying the part they are paying for. That suspicion is reasonable and I have seen it be correct about other people.
- Six weeks is wrong. It is a fortnight, and outbound infrastructure gets built during it. Domains have to warm for weeks regardless, so the calendar does the overlap for free. Nothing about this sequence requires sitting still.
- The positioning is a working draft. The first two hundred contacts test it, and it gets rewritten. What I won’t do is skip writing one.
What I haven’t solved
Knowing when to stop narrowing. Both times I could have cut the segment further and both times I stopped on instinct rather than on evidence, because the cost of being too narrow shows up as silence and the cost of being too broad shows up as noise, and from inside week three those look identical.