Agencies
Cold Email Playbook: Dev & Product Studios
Sell custom development, MVP builds, and product consulting. Technical buyers, long sales cycles, high deal values.
34%
avg open rate
3.8%
avg reply rate
1.2%
meeting rate
26%
close rate
Who to target
Titles
CTO, VP Engineering, CEO (non-technical), Product Director
Company size
20-200 employees
Trigger
Funding, product rewrite, legacy migration, new product line
Budget signal
Job postings for senior devs, tech debt discussions
Industry focus
SaaS, fintech, healthtech, marketplace
Geography
Same timezone preferred
Messaging angles that work
These are the 3 approaches that consistently get replies in this vertical. Pick the one that fits your prospect best.
1. Build vs hire
"You have 3 open senior engineer roles. Average time to fill: 4 months. We can ship the feature in 6 weeks."
Why it works: Hiring is painful and slow. An agency that ships faster than you can hire wins.
2. Tech debt observation
"I looked at your public repo / job posts. Sounds like you're migrating from [old tech] to [new tech]."
Why it works: Specific technical observation = instant credibility with CTOs.
3. MVP speed
"You're spending 6 months building V1. Your competitor shipped theirs in 6 weeks with a studio."
Why it works: Speed to market is everything for funded startups. Time = money.
The 7-step sequence
Email + LinkedIn, orchestrated over 21 days. The channel alternation is what makes this work.
Day 1
Build vs hire
Reference their specific open roles.
Day 2
Connect
"Noticed {{company}} is scaling the eng team. Sent you a note."
Day 5
Engage with tech content
Comment on a CTO post about hiring challenges or tech decisions.
Day 7
Tech debt or MVP speed angle
Different trigger, same pain.
Day 11
Send message
"Quick q -- is the migration timeline on track or falling behind?"
Day 14
Case study with timeline
"Week 1: onboarding. Week 3: first PR merged. Week 6: feature live."
Day 21
Breakup
Clean close.
Ready-to-use templates
Copy these directly into your campaign. Each one is pre-scored for deliverability.
Build vs hire
Score: 86/100
Subject: {{company}} engineering bandwidth
Hi {{firstName}},
I noticed {{company}} has 3 open engineering roles. Senior devs are taking 4+ months to hire right now.
Meanwhile, the product roadmap isn't waiting.
We're a 20-person dev studio that embeds with your team. We ship production-ready features in 4-6 week sprints while you hire. When your team is ready, we hand off clean code with full documentation.
Worth a 15-min call to see if the model fits?
Best,
John
When they push back
The most common objections in this vertical and exactly what to say.
"We only build in-house"
We embed IN your house. Same codebase, same PRs, same standups. The difference: we're productive on day 1, not month 4.
"Agencies produce throwaway code"
Bad agencies do. Ask for our GitHub history. 100% test coverage, typed, documented. Our code has to survive the handoff -- that's how we get rehired.
Run this playbook in Overloop
Every template is ready to paste into a campaign. First meetings in 3 weeks.
Try Overloop free