To move from your first 10 beta users to predictable outbound, test your message on strangers before you scale anything. Your first customers prove that people who trust you will buy. They do not prove that people who have never heard of you will. Run three small cold cohorts in adjacent segments, and promote the one where the same pain repeats.
Key takeaways
- Network wins prove access. Cold replies from strangers prove demand.
- Pick test segments by trigger and job to be done, not by industry label. The best segment is often one your network never pointed you to.
- Run three cohorts of 20 to 50 named accounts and compare them. Do not blend them into one list.
- Write the promotion gate before you send: the same pain and the same message, across two cycles in a row.
- Automate research and follow-ups first. Keep the choice of segment, the message and the first calls with you until the pattern is teachable.
Why your first 10 customers do not predict customer 11
Early customers buy a person as much as a product. Geoffrey Moore's Crossing the Chasm describes the gap this creates. Early adopters buy into the founder's vision and accept rough edges. Pragmatists want proof in use cases like their own, from customers they know.
Moore warns that the two groups can look the same on a customer list, while the basis for the sale is very different. A founder's network fills the first list. Strangers fill the second, and they need a different reason to say yes.
Sales hiring advice repeats the same warning. In a survey of 41 founding account executives, Dan Oakes quotes one respondent who says founders should close 10 or more strangers from cold outbound first, because closing only your network "can fill you with false confidence." Forum Ventures says the same: build a process for generating leads outside your team's network before you hire anyone to run it.
What changes when the buyer does not know you
| Question | Founder network | Cold market |
|---|---|---|
| Why does the buyer reply? | They know and trust you | The message names a problem they have right now |
| How do you pick the account? | Who you know | A trigger you can name and check |
| What do you learn from a no? | Little. The no is polite | A lot. The no shows the weak point in the message or the segment |
| Who can run it? | Only you | Anyone who has the list, the message and the rules |
| What does the result prove? | Access | Demand |
The last row is the point. A cold motion that works is one you can write down. That is why it can leave your calendar.
Choose segments by trigger, not by industry label
Your network points you at the obvious buyer: the industry you came from, or the one your first beta users work in. That list is easy to build, and it is also the list that stops growing.
Describe the buyer by what is happening at the account instead. Ask three questions:
- What event makes your product urgent? Examples are a new hire, a failed hire, a launch or a rule change.
- Which job does the buyer hire your product to do? Write it as a sentence without your product's name in it.
- Which industries have that event and that job, and are not in your network?
The answer is a short list of non-obvious segments. Pick three. Each one should have a trigger you can verify from public information before you write the first email.
Blesso's own work shows the pattern at small scale. For HappierHire, an AI hiring platform, Blesso sent signal-led outreach to talent leaders, triggered by hiring signals at the account. HappierHire reports 3.1x pipeline in one quarter and a shelved SDR hiring plan. That is one customer's result, with no published baseline. It is not an average, and it does not promise the same for your product.
The cold cohort test: three segments, three cohorts
The test has one purpose: find out which segment buys from a stranger, and why. Unify GTM's early-stage outbound framework gives the working numbers: 20 to 50 named accounts at the start, and 10 to 20 real conversations before the pattern shows. This is a framework, not a measured benchmark, so treat the numbers as a starting point.
- Name the cohorts. Choose three segments from the section above. List 20 to 50 accounts in each, with the trigger written beside every account.
- Use one message frame per cohort. Write the problem in the buyer's words, not yours. Keep the offer and the ask the same across cohorts, so a difference in replies comes from the segment.
- Send in the founder's voice. You will hear the objections yourself. Take every call, because a handoff layer hides the buyer's words.
- Log each conversation. Record the trigger, the role, the opener, the objection, the next step and the outcome.
- Compare cohorts at the end. Look for one segment where the same pain, role and objection repeat. Replies alone are not the signal. Unify GTM warns that positive language without a real problem, authority or next step should not trigger a hire.
Here is a worked example. It is an estimate with made-up numbers, not a result. Say you choose three cohorts of 30 accounts, so 90 accounts in total. You hold 12 conversations in the first cycle. Eight of the 12 come from one cohort, and six of those eight describe the same trigger. That cohort is your segment. The other two cohorts go on pause, and you do not have to guess why.
Write the promotion gate before you send
Teams that skip this step promote on hope. Write a rule while the data is still empty. A usable gate has four parts:
- The same segment, role and message produce qualified conversations in two cycles in a row. Unify GTM uses this exact test.
- You can teach the account rule, the trigger, the message, what a qualified reply looks like and when to stop.
- Closers do not need custom product promises to win the deal. Ember lists this as a condition for handing off outreach.
- Your calendar is full of closing work, not list building.
If the gate fails, narrow the segment before you add volume. If replies come but no pain repeats, the segment is too wide.
Automate the assembly first, and keep the judgment
Unify GTM's advice is to automate assembly before judgment. Contact discovery, enrichment, signal monitoring and follow-up reminders can run without you early. Target selection, positioning, qualification and the relationship stay with you until the pattern is teachable.
| Work | Automate now? | Why |
|---|---|---|
| Contact discovery and enrichment | Yes | Repeat work with clear rules |
| Signal monitoring and reminders | Yes | A system sees a trigger sooner than a person does |
| Choosing the segment | No | This is the question the test answers |
| First message and discovery calls | No, until the gate passes | You need the buyer's exact words |
This is where a done-for-you partner fits. After the gate passes, the first three rows become work with written rules, and rules can be handed off.
How Blesso runs the repeatable part
Blesso is a done-for-you B2B go-to-market service. It runs the Outbound Engine for you: it sources accounts past the databases, scores and enriches them, and runs email and LinkedIn on one sequence, with replies traced back to the signal.
It also reports in a fixed order every week. The first tier covers activity Blesso controls. The second covers market response. The third covers business outcomes. Blesso counts a meeting only when a human attends it, it comes from the approved account list and it matches the agreed titles. Counting comes from your calendar, not Blesso's dashboard.
For Airbills, an offshore staffing company, Blesso replaced founder-led sales with systematic outreach built on signals and account dossiers. Airbills reports $1.4M pipeline in 90 days and the founder out of prospecting. Again, this is one customer's result and not an average. Engagements start at $2k a month with a three-month minimum; see the pricing page.
Mistakes that keep founders on the wrong side of the chasm
- Treating warm intros as proof of fit. Founder-network wins show access. Check them against cold replies.
- Blending segments into one list. You then cannot see which segment made the replies.
- Scaling volume before the message repeats. A large list that nobody can personalize damages sender trust. Our deliverability guide covers the limits.
- Handing the test to a new hire. A first hire should execute a playbook, not discover one. Our guide on Blesso vs. hiring an SDR covers the timing.
FAQ
How many customers should I have before I run cold outbound?
There is no fixed number, but advice clusters between 5 and 30. In Dan Oakes's survey of 41 founding AEs, every answer that named a customer count fell between 5 and 30, depending on ACV. Start cold tests earlier than you hire, because the tests are how you learn what to hand off.
What is a non-obvious ICP?
A non-obvious ICP is a buyer segment your network would not have pointed you to, but that has the same trigger and the same job to be done as your best customers. You find it by describing the buyer by event and job, then listing industries that match and are outside your contacts.
How many accounts should a cold test include?
Start with 20 to 50 named accounts per cohort. Unify GTM's framework uses that range for early discovery and 10 to 20 real conversations before a pattern shows. Smaller lists let you write a real reason for each account.
When can I hand outbound to someone else?
Hand it off when the same ICP and message produce qualified conversations across two cycles in a row, and you can teach the rules in writing. If list building and research are the bottleneck, automate those first. Hire when conversation capacity is the limit.
Run the three-cohort test first, then decide who runs the repeat work. Book a call to see what Blesso would run once your segment repeats.