Skip to content

Cold outreach

Cold outreach launch for B2B SaaS

Cold outreach is the lowest-noise launch channel for B2B SaaS — no algorithmic gatekeeping, no public failure, all founder-to-buyer signal. The playbook is volume + personalization + a specific named ask. Done right, 50 cold messages produce 2-5 demos and 0-2 customers.

SaaS type: B2B SaaS at $500-$5,000/month price points where the buyer is identifiable and named.

Verified · editorial policy

Channel fit verdict

Channel fit: Strong fit

When NOT to use: If your target buyer is a developer or end-user who does not check email regularly, cold outreach is slow. If your average deal is under $50/month, the math rarely closes.

Pre-launch build-up

  1. Step 1

    Build a named dream-100 list (2-4 weeks before)

    Not a scraped list. 100 named people you would be proud to have as customers, with one specific verifiable thing about each one. The list quality is the entire game.

    Time: 10-30 hours over the period.

  2. Step 2

    Warm the sending domain (2-3 weeks before)

    If sending from a new domain, ramp up volume gradually. mail-tester score 9/10+. SPF, DKIM, DMARC aligned.

    Time: Daily 10-minute sends during warm-up.

  3. Step 3

    Draft the message template (1 week before)

    Under 100 words. Personalization slot for the verifiable thing about each recipient. One specific ask at the end (15-min call, yes/no question).

    Time: 2-4 hours of iteration.

Launch day

  1. Step 1

    Send 20-30 personal messages between 9am-2pm

    Each message manually personalized. 20-30 per day is the sustainable ceiling for genuinely personal outreach. Tools that send 200+ are sending generic spam.

    Time: 3-5 hours.

  2. Step 2

    Monitor the inbox in real-time for the first 6 hours

    Inbox response within 5 minutes of a reply is the single biggest conversion lever. The follow-up reply quality matters more than the original message.

    Time: Continuous attention.

Post-launch (7 days)

  1. Step 1

    Day 2-7 — send the follow-ups

    One follow-up per recipient, 4-7 days after the original message. References the original thread; does not say 'just bumping this'.

    Time: 30-45 minutes daily.

  2. Step 2

    Day 7+ — convert demos to paying customers

    Demos booked in the first week should be done within 14 days. Stretching the demo-to-customer cycle past 30 days kills conversion.

    Time: Demo prep + execution.

Success profile

From 100 cold messages: 15-35% reply rate, 5-15% demo-booking rate, 1-3% conversion-to-customer rate. Cold outreach to a real dream-100 list outperforms scraped-list outreach by 10-20x.

Failure profile

Sub-2% reply rate. Almost always traceable to a scraped list, generic template, or wrong-buyer-profile recipient set.

Channel-specific mistakes

  • Scraped lists with mass personalization tokens. Detectable; reply rate collapses.
  • Vague asks ('let me know what you think'). Replace with one specific question or 15-min calendar offer.
  • Multi-paragraph cold messages. Anything over 100 words gets skipped; reply rate is inverse to message length.
  • Sending without inbox monitoring. Cold-outreach replies in the first 5 minutes are 5-10x more likely to convert.

Related Brunson terms

Frequently asked

How big should the dream-100 list be?
Exactly 100 named people, not more. Pushing past 100 forces a quality drop. If you exhaust 100, build the next 100 fresh — the second cohort is always better than diluting the first.

Pair this with the pre-launch checklist

The pre-launch indie SaaS checklist names the ten things every SaaS must verify before any of the launch channels here can convert.

🚀 Explore Our Network

Full disclosure: UnlockSaaS is one of ten small products built and run by one independent operator. These are the other nine.

60 days
To First Paying Customer
7 steps
Proven Playbook
100%
Money-Back Guarantee
$49
Founding Price /mo

You shipped. Nobody paid. The playbook breaks the pattern or the code refunds you automatically.

Get Free Diagnosis

Refund runs from your dashboard, not a support ticket — the server re-checks eligibility and issues it through Stripe automatically.