You're a startup founder or early-stage operator, and you need revenue. Cold email sounds simple enough - but when you actually sit down to write one, you hit a wall. You don't have case studies. You don't have brand recognition. You might not even have a finished product. So how do you write cold email that gets responses when you're starting from zero?
The answer isn't to fake it or get cute. It's to lean into what startups actually have that big companies don't - speed, focus, and the ability to actually solve a specific problem better than anyone else.
The Startup Cold Email Formula
Forget the generic B2B cold email templates you see everywhere. Startups need a different structure because your value isn't in your track record - it's in the problem you solve and your willingness to move fast.
Here's the framework:
- Subject line: Curiosity or specificity. No fluff.
- Opening: One sentence. Reference something specific about them or their business.
- Problem statement: One or two sentences. Name the actual pain point.
- Your angle: One sentence. How you approach it differently.
- Social proof (if you have it): One sentence. Number, outcome, or credibility marker.
- Call to action: Specific ask. Not "let's chat."
- Sign off: Name and title only.
The whole email should be 5-7 sentences. Not paragraphs - sentences.
Real Examples That Work
Let's look at what this actually looks like. Here's an email from a startup offering sales training to B2B founders:
Subject: Found you on the ARR leaderboardHey [Name],Saw you hit $500K ARR last month - that's a real milestone.Most founders we work with have a solid product but their sales conversations feel awkward. They're not closing the deals they should because they're pitching instead of listening.We work with pre-Series A founders specifically - run a 30-min sales session with you, give you one framework to use in your next 5 calls. Most see 20-30% better close rates within two weeks.Do you have 30 minutes Tuesday or Wednesday to try it?[Name]Founder, [Company]
Why this works: It's specific (ARR number, time frame, close rate), it names the real problem (pitching instead of listening), and the ask is concrete (30 minutes, two specific days). No fluff about "synergies" or "exploring opportunities."
Here's another example from a startup offering customer research tools:
Subject: Your pricing page doesn't match your docsHi [Name],I was looking at your product tour and noticed your pricing page talks about "unlimited users" but your docs say there's a 50-user limit on the Starter plan.This kind of thing usually tanks conversion. We help B2B SaaS companies audit their messaging - usually takes an hour, and we send you a doc with specific things to fix.Worth 60 minutes?[Name]Founder, [Company]
This one works because it's a real observation (not a generic pain point), it shows you did research, and the value is obvious and immediate.
Subject Lines That Get Opened
For startups, subject lines should do one of two things: trigger curiosity or be so specific it's obvious you did research.
Curiosity examples:
- Found you on the ARR leaderboard
- Your competitors are doing this
- One thing I noticed
- Quick observation
Specificity examples:
- Your pricing page doesn't match your docs
- Saw your Series A announcement
- You're hiring for sales - can I help?
- Your landing page + our tool = 40% more conversions
Stay away from "quick question," "checking in," or anything that sounds like a cold email. Your subject line should look like someone sent it because they had a reason - not because they're running a campaign.
The Problem Statement Matters More Than You Think
This is where most startup cold emails fall apart. The problem you name has to be the specific, immediate problem the person you're emailing actually feels. Not a broad category, not a symptom - the actual thing keeping them up at night or costing them money right now.
Bad: "Many B2B companies struggle with sales efficiency."
Good: "Most founders you work with have a product that sells itself until it doesn't - then they realize they can't do sales."
Bad: "Content management is a challenge for agencies."
Good: "Your designers are spending 8+ hours a week managing feedback from clients instead of actually designing."
The pattern here is real and specific. It's something someone could immediately recognize in their own business. You're naming the thing they already know is a problem - you're not trying to convince them a problem exists.
What to Do If You Don't Have Social Proof Yet
Most early-stage startups don't have case studies or numbers to share. This is fine. You have other things.
Your founding team's background counts. If you built this at a company that exits, mention it. If you spent 5 years in the industry before starting, say so. If you've already helped 3 companies without it being a case study yet, mention that.
You can also lead with the problem you're solving.