IT & Dev Shops

ICP: Founder, BD Director, or CEO at a software development firm, IT managed services provider, or technical consultancy. 10–200 people. Revenue from project work, retainers, or staff augmentation.

The core problem: Technical founders are great at delivery and terrible at sales. New clients come from referrals and past relationships. When a key client ends, pipeline is dry. Outbound feels misaligned with their “we let the work speak for itself” identity — but referrals alone don’t scale.

---

Best-performing signals for IT & dev shops

1. Engineering hiring spikes — a company posting 5+ engineering roles is about to need an external delivery partner when hiring takes too long
2. New CTO or VP Engineering hire — evaluating all technical vendors in the first 90 days
3. Funding round at a non-technical company — they have money and no engineering team; they’ll outsource
4. Tech stack migrations — companies moving from legacy systems need implementation partners
5. Product launches and roadmap announcements — expanding product scope without engineering capacity

---

Two distinct ICPs to separate

ICP A — Companies buying dev services:

• Non-technical founders who need a dev partner
• Companies that tried to hire and can’t find the right people
• Funded startups that need to move fast

ICP B — Companies buying staff augmentation:

• Larger companies with existing teams that need to scale temporarily
• Companies with specific skill gaps (AI, mobile, specific frameworks)
• Post-acquisition integrations

The copy, signals, and approach are completely different between these two. Mixing them in one sequence kills conversion.

---

The copy framework

For non-technical founders (ICP A):

“You’ve probably found that hiring for [role] in [location] right now takes 3–4 months minimum — if you find the right person at all.
We work with a few [industry] companies that solved this by building the core product with an external partner while the internal team scales.
Worth 20 minutes to see if the model fits?”

For staff augmentation (ICP B):

“Noticed [Company] is expanding into [area] — saw the recent engineering postings.
If the hiring timeline is creating pressure on the roadmap, we’ve helped similar teams augment specific skills on a 30-day timeline.
Happy to share how we approached it for [similar company type].”

---

Verifiable claim is essential

IT and dev shop buyers are technical. They’ll evaluate the quality of your claim immediately. Vague claims fail fast.

What works:

• Specific technology expertise (“Python ML pipelines” beats “AI development”)
• Named client types (“Series B fintech companies” beats “startups”)
• Specific timelines (“deployed in 6 weeks” beats “fast turnaround”)

---

What to avoid

• Generic “digital transformation” language — it’s meaningless to a technical buyer
• Overloading with technology names — pick the 2–3 most relevant to their stack, not a list of 15
• Pitching before understanding their stack — a brief context question (“what are you primarily building on?”) before a detailed pitch dramatically improves conversion