← Back to playbooks

March 15, 2026

Cold Email Framework for Dev Tools

Most cold emails for technical products fail for the same reason: they sound like they were written by someone who doesn’t understand the product or the buyer.

Technical buyers can smell generic messaging from a mile away. They’ve been pitched a thousand times. The only way to break through is precision: understanding their stack, their pain points, and their incentives well enough to write something that feels like it came from a friend, not a salesperson.

Here’s a framework I’ve used to book meetings for dev-tool and infrastructure founders. I recommend YC’s Startup School video on cold email, as well as the Zazu guide.

The Structure

Every cold email follows a three-sentence structure shaped like an F. First sentence is the longest and the last is the shortest that is the call to action that points directly to your signature. Mobile friendly. No exceptions. 300 characters max.

1. Context — Why I’m reaching out to you specifically with enough punch in the text preview that you open the email.
2. Why now — A specific challenge (trigger) I know you’re dealing with framed as a pattern (social proof)
3. Ask — A low-friction next step

That’s it. If you can’t make your point in three sentences, you don’t understand your value prop well enough.

Sentence 1: Context

This is where most emails fall apart. “I saw you’re a founder” is not context. Context means demonstrating that you’ve done the work:

• “I noticed you’re hiring for a second SDR role after running outbound yourself for six months.”
• “Saw your HN thread about moving from PLG to sales-led. We’re seeing a lot of dev-tool companies hit this wall around $2M ARR.”
• “I’ve been following the launch of your Supabase adapter. The architectural choice around real-time sync is interesting.”

The bar is: would this sentence be true for anyone at the target company? If yes, it’s not specific enough. Casual, like from a friend.

Sentence 2: Why now & the pattern

Don’t pitch your solution. Avoid using your company name or any links. Name the pain you know they feel:

• “The challenge most infrastructure founders hit at this stage is that founder-led selling doesn’t scale — you can’t be in every deal while also building the product.”
• “Pipeline becomes unpredictable. Some months you have six meetings, some months you have zero.”
• “The PLG motion is generating leads, but they’re not converting to enterprise deals because there’s no sales touch.”

The problem should be true, specific, and painful. If they don’t nod reading it, rewrite it.

Sentence 3: Ask

Low friction. One click. No discovery call pitch:

• “Worth a 15-minute call to compare notes?”
• *“Reply if you are you the right person…”
• “Shoot me a reply and I’ll…”

The Subject Line

Short. Specific. Avoid marketing language.

Good examples:

• “Outbound at [company]”
• “Pipeline question”
• "[Product] + enterprise sales"
• “Quick thought on your PLG → sales transition”

Bad examples:

• “Unlocking your growth potential”
• “Partnership opportunity”
• “Quick question”
• *“Stars and emojis”

When to Follow Up

At least three follow-ups, spaced 1-2 days apart for fast iteration:

1. Day 2 — Add a piece of relevant context (new blog post, product launch, industry signal)
2. Day 3 — New differentiator, share a specific result or case study (without naming the client)
3. Day 5 — One final, direct ask: “Still interested?”

After that, move to nurture. Cold outreach has a shelf life. Don’t chase.

The Golden Rule

If you wouldn’t want to receive the email you’re sending, don’t send it.

Every email should pass the bar of: “If a peer at another company sent me this, would I read it?” If the answer is no, rewrite it before you hit send.