For SaaS founders

Your first 10 customers aren't on your landing page.

Organic traffic takes 6 months to build. Word of mouth is unpredictable. Cold email finds the specific people most likely to buy your product and puts a conversation in front of them this week.

Why cold email works especially well for SaaS

Most products solve a specific problem for a specific type of company. That specificity is cold email's biggest advantage: you're not running ads hoping the right person sees them. You're finding the companies that match your ICP and reaching out directly.

SaaS products also have clear signals for targeting. If you replace Asana, you can find companies using Asana. If you're a better version of Intercom, you can find companies running Intercom scripts. Distribute identifies these signals automatically from your product URL and uses them to find prospects.

The other thing cold email does well: it generates feedback fast. A week of replies tells you more about your positioning than a month of analytics.

48 hrs median time to first positive reply after campaign launch
$0.07 per contact reached, research and writing included
$25 minimum to run your first campaign, no subscription required

Who to target

The sharper your ICP, the better your reply rates. Vague targeting gets ignored. Specific targeting gets responses.

01
Companies using the tool you replace If your product replaces or improves on an existing tool, target companies that use that tool. Prospect databases and Distribute's targeting layer can identify companies running specific software. This is the highest-intent segment: they already pay for the problem you solve.
02
Companies at the right growth stage Headcount signals buying stage. A 10-person startup probably can't afford enterprise pricing. A 200-person company likely has budget but will take 3 months to close. Find the range where your product fits without requiring a long sales cycle. For most early-stage SaaS, that's 20-150 employees.
03
The right title, not just the right company Email the person who will use your product and has budget authority. For dev tools, that's an engineering manager or CTO. For sales tools, a VP Sales or Head of Growth. Emailing a CEO for a $49/month tool usually goes nowhere. Emailing the practitioner who will actually use it converts better.
04
Recent triggers (funding, hiring, product launches) A company that just raised a Series A is actively buying tools. A company posting 10 engineering jobs is scaling fast. These events create natural timing for outreach. "I saw you just raised your Series A and are expanding the team" is a real reason to reach out.

What to write

The goal of a cold email is one thing: a reply that starts a conversation. Not a sale. Not a demo booking. A reply. Everything in the email should serve that goal.

subject
Short, specific, no hype 5-7 words. Reference something real: the company name, a specific tool they use, or the problem. "Quick question about your onboarding flow" beats "Boost your conversions by 10x."
line 1
Prove you looked at their product One specific observation about their company or product that shows this email isn't a template blast. "I noticed you're using Intercom for support but not automating the initial triage" is better than "I've been following your company."
body
What you do, in one sentence Not a feature list. One outcome: "We help B2B SaaS teams cut support ticket volume by 30% without adding headcount." If they want more detail, they'll ask. Give them the one thing that makes them want to ask.
CTA
Ask a question, not for a meeting "Would this be worth a 15-minute call?" has lower conversion than "Is this something you're actively looking at right now?" A yes/no question is less friction than a calendar commitment.
mail.google.com
solo.fm's onboarding flow
from: kevin@distribute.you  ยท  to: sara@solo.fm

Hey Sara, noticed solo.fm lets creators go live in under 60 seconds but the first-time setup still requires 4 manual steps after signup.

We built a drop-in onboarding kit that cuts that to one. Teams using it see 40% better activation week one.

Worth a quick look?

Distribute generates emails like this at scale, personalizing each one to the specific prospect's product and context.

Pre-launch vs post-launch: when to start

Pre-launch Ideal for validation

Cold email before launch tells you whether your ICP will pay for what you're building. A handful of interested replies is better signal than 500 waitlist signups. Some founders close their first paying customer before writing a line of code.

Use a landing page with a "request early access" CTA. The emails drive to that page. The replies become your first user interviews.

Post-launch Ideal for acquiring paying users

With a working product, the conversion path is cleaner. Positive replies go directly to a demo or trial signup. You're not guessing at the value proposition anymore because you can show it.

At $10k MRR, cold email runs alongside product-led growth rather than replacing it. The same $25-$50/week keeps new conversations coming in without depending entirely on inbound.

What a first campaign looks like

These are real numbers from a Distribute campaign in week one. Not a best case, not an average, just a typical first run.

47 emails sent, week 1
18 opened (27%)
4 replied
3 calls booked

Total spend: $34. Three conversations with people actively interested in the product, in the first week. That's the mechanic. Run it every week.

Running your first campaign

The full setup takes under 10 minutes if you have a product URL and a clear sense of who buys it.

01 Add your product URL Distribute reads your landing page and pulls out the product description, key features, and implied use cases to inform both targeting and copy.
02 Define your ICP (or let Distribute suggest one) Distribute proposes a default ICP from your URL. Adjust industry, headcount range, and job title, or enter your own.
03 Set a weekly budget $25 reaches roughly 350 contacts. Start there, see what converts, then scale the budget on what works.
04 Replies land in your inbox Interested replies come to your connected Gmail, tagged and ready. Follow-ups for non-replies run automatically.
05 Use the data to sharpen your positioning After 100 emails, open rates and reply patterns tell you more about what lands than a month of analytics.

Common questions from founders

I don't have a big list. Do I need to buy one?

No. Distribute finds prospects based on your ICP definition using live data sources. You don't need to bring a list. You describe who you want to reach, set a budget, and the system builds and works through the list continuously.

My product is very technical. Will the emails sound generic?

Distribute reads your product URL and generates copy from the actual content on your page. If your landing page is technical and specific, the emails reflect that. The more specific your landing page, the better the generated copy. The system also reads each prospect's website before writing their specific email.

What if prospects ask me to unsubscribe?

Every email includes a plain-text unsubscribe mechanism. Distribute tracks unsubscribes and removes those addresses from all future campaigns automatically. CAN-SPAM and GDPR compliance is handled out of the box.

How long before I see results?

The first replies typically come within 24-72 hours of launching. Full domain warmup takes 2-3 weeks, but Distribute starts with a small daily send volume on day one and increases gradually. You'll see early signal before you're at full capacity.

Can I run multiple products at once?

Yes. Distribute is built for founders running multiple products, which is exactly why the portfolio dashboard exists. Each product runs its own campaign with its own budget, ICP, and results tracking. You can compare cost per contact across products and reallocate budget to whatever's working. See the use cases page for how portfolio founders use it.

Your first 10 customers are out there.

$25 sends your first campaign. No domain setup, no copywriting, no account manager. Results in your inbox this week.

Start free, $25 credits