Most founder-led sales starts the same way: a cold email that sounds like a product announcement. It gets no reply, the founder decides "outbound doesn't work for us", and the pipeline goes back to waiting for referrals. This post is a practical set of sales tips for cold email: a structure, three templates, a follow-up sequence and a checklist you can run before you hit send. It is written for founders, engineers and solutions engineers who sell, plus SDRs and AEs who want a cleaner baseline.
Why most founder cold emails fail
When you build the product, you naturally write about the product. The prospect does not care about it yet. They care about a problem they already have, in words they already use.
Common failure patterns:
- The feature dump. Five bullet points of capabilities, zero mention of the reader's situation.
- The vague ask. "Would love to connect sometime" gives the reader work to do. Most people skip work.
- The fake personalisation. "I saw you're the Head of Sales at Acme" is not research; it is the To field read aloud.
- The essay. If it needs scrolling on a phone, it is too long.
A cold email has one job: earn a short reply that leads to a discovery call. Not to close the deal, not to explain the roadmap.
A simple cold email structure: Trigger, Problem, Proof, Ask
Use four short parts, one or two sentences each.
- Trigger: why you are writing to this person now (a hire, a job post, a talk they gave, a launch).
- Problem: the pain you suspect, framed as a question or a pattern you see, not a diagnosis.
- Proof: one concrete reason you are credible on this problem. Keep it true and small.
- Ask: a low-effort, specific next step that can be answered with yes or no.
Target length: 50 to 120 words. Subject line: 2 to 5 words, lowercase is fine, no clickbait.
Cold email template 1: the trigger email
Subject: new SDR hires
Hi Lena,
Saw you're hiring three SDRs this quarter. In teams that ramp
several reps at once, the first weeks often go to call shadowing,
and reps still freeze on their first real objection.
We work on sales practice for exactly that moment: reps rehearse
discovery calls and objection handling before they touch pipeline.
Worth a 15-minute call to compare how you ramp today?
Why it works: the trigger is specific, the problem is phrased as a pattern ("often"), and the ask is small and concrete.
Cold email template 2: the founder-to-founder email
Founder-led sales has one unfair advantage: you can write as a peer.
Subject: founder-led sales
Hi Marco,
You're still running most sales calls yourself, judging by your
recent post about closing your first enterprise deal.
Quick question: when you hand calls to your first sales hire,
how will you check they handle pricing pushback the way you do?
Happy to share the discovery question list we use. Want it?
Notice the ask is not a meeting. Offering something useful first lowers the bar for a reply, and the reply opens the conversation.
Cold email template 3: the problem-question email
When you have no trigger, lead with a sharp question about a common pain.
Subject: objection handling
Hi Priya,
How do your AEs practise objection handling between live calls?
Most teams we talk to rely on manager role play, which is hard to
schedule and easy to skip.
If that's a gap for you, open to a short call next week?
The follow-up email sequence
Most replies come after the first email, so plan the sequence before you send anything. Keep every follow-up shorter than the one before, and add something new each time.
| Day | Message | Purpose |
|---|---|---|
| 1 | Main email | Trigger, problem, proof, ask |
| 3 | Bump: "Any thoughts on this, Lena?" | Resurface it in the inbox |
| 7 | New angle: one useful insight or resource | Give value, not pressure |
| 14 | Breakup: "Should I close the loop on this?" | Permission to say no |
The breakup email works because "no" is also an answer. A clear no is better pipeline hygiene than a maybe that never moves.
Turning a reply into a discovery call
A reply is not a meeting yet. Common replies and what to say:
- "What does it cost?" Give a range or how pricing works, then: "It depends mostly on team size. Can I ask two questions to see if it's even a fit?"
- "Send me more info." "Sure. So I send the right thing: is this more about ramping new reps or sharpening the current team?" (We covered this brush-off in depth in an earlier post on handling "send me some info".)
- "Not now." "Totally fair. What would need to change for this to be a priority?"
Each answer pushes toward discovery questions instead of a long email thread. Prepare these replies like a cold calling script: write them once, practise them out loud, reuse them.
Pre-send cold email checklist
Run this before every send:
- [ ] Is there a real reason I am writing to this person now?
- [ ] Does the first line talk about them, not me?
- [ ] Is the problem phrased in their words?
- [ ] Is every proof point true and checkable?
- [ ] Is it under 120 words and readable on a phone?
- [ ] Is there exactly one ask, answerable with yes or no?
- [ ] Is the subject line 2 to 5 plain words?
- [ ] Is the follow-up sequence already written?
Practise the call the email books
The best cold email in the world just books a conversation. If you freeze on the first objection in that call, the email did its job and the deal still dies. Treat the email and the call as one system: write the email, then rehearse the discovery call and the three objections you expect, out loud, before the meeting happens.
That rehearsal step is what we're building at Kulissa: a sales coach where you practise sales calls against realistic virtual customers. If that sounds useful, take a look at kulissa.com.
Top comments (0)