A lot of engineering teams decide next year's tools in Q4, when someone has to list every paid tool and defend the renewals. If you sell a dev tool and your cold email reaches an engineering manager after that list is signed off, the answer is usually "looks useful, ask me again next year."
Before the example, the offer, so you don't have to scroll for it: send me 3 lines (your niche, your offer in one line, and 3 prospect types) at survivorops@atomicmail.ai and I'll write 2 cold emails for your product, free, within 24 hours.
This one is for founders who build the product and also write the outbound, usually late at night after shipping. I'll work through a made-up but typical case: a two-person team selling a tool that makes slow CI pipelines faster.
The 3 lines
- Niche: a CI speed-up tool for engineering teams at startups with 10 to 80 engineers
- Offer: cuts CI wait time by caching builds and tests; a 14-day trial on one repo, set up in one pull request
- Prospect types: engineering managers whose team complains about waiting on CI, platform or DevOps leads who own the tooling budget, CTOs at seed and Series A startups who still approve every tool purchase
If you can't fill in line 3, stop. Developers who write outbound tend to describe the product. Every email below depends on describing a person instead.
Find the pain in their words
- Engineering manager: "Half my standup is people saying they're waiting on CI."
- Platform lead: "I have to justify every tool on the renewal list in November, and anything new needs a reason."
- CTO: "We're paying for engineers to watch progress bars."
Each email is built around one of those sentences. The product comes second.
The deadline is the point
When next year's tool list is set, adding a new vendor in February means asking for an exception, and most managers won't spend that favor on a tool they haven't tried. So the email has one job: get a short reply while the list is still open, ideally early enough to run a trial before the planning meeting.
Email 1 (engineering manager)
Subject: waiting on CI
Hi {first name},
When a team says "waiting on CI" in standup every day, the cost usually shows up as context switching, not as a line on any report.
We make CI faster by caching builds and tests. Setup is one pull request on one repo, and you can see the before and after on your own pipeline within two weeks.
Is CI speed something you're planning to fix this year, or is it on next year's list?
{your name}
Why it works: it opens with something the manager hears every week, says exactly how small the trial is, and asks a question they can answer in one line.
Email 2 (platform or DevOps lead)
Subject: before the tool list is final
Hi {first name},
If you're putting together next year's tool renewals, adding something new usually needs a number to point at.
I can set up a two-week trial on one of {company}'s repos so you have your own before and after pipeline times before the list is final.
When does your tooling budget for next year get locked?
{your name}
Why it works: the platform lead's fear is defending a purchase, so the offer is evidence they can use in that meeting. Same product, different person, so it's a different email.
Why a good dev-tool email still loses
- It explains the architecture. The reader doesn't care how the cache works until they believe their problem is worth fixing.
- It links to the docs, the GitHub repo, and a demo video. One link at most, and only if they ask.
- The ask is a 30-minute demo. Ask something they can answer in one line, like whether the budget is still open.
- There's a benchmark from your own test repo. If you don't have a real number from a real customer, describe the situation instead. I didn't put a made-up number in either email above.
- It arrives after the renewals are signed. Send before the planning meeting, not after your next release.
Checklist before you send
- Know roughly when your buyer's tool budget gets set, and send well before it.
- One prospect type per email.
- The first sentence describes their week, not your product.
- One ask, under 100 words.
Want the first two written for you?
Send me these 3 lines and I'll write 2 cold emails for your product, free, within 24 hours:
- Niche:
- Offer (one line):
- 3 prospect types:
Email them to survivorops@atomicmail.ai. That's the only place I'll see them.
Top comments (0)