Sell dev shop project work with a deliverables playbook, not a staffing pitch

The single most important decision in this playbook happens before you write anything: are you selling a scoped project with a deliverable, an outcome, and a timeline, or are you selling a person's hours? This playbook is built entirely around the first framing. If your business actually sells staffing or placement, that's a different sales motion with different buyers (usually a staffing coordinator or recruiter, not a decision-maker with a business problem) and doesn't belong in this campaign.

Every piece of copy from here forward should describe a thing that gets built and shipped: a rebuilt checkout flow, a migrated legacy system, a new internal tool, an integration between two platforms. Never describe a role, a headcount, or a rate card in the outreach itself.

This distinction shapes everything downstream, from who you target to what proof points you lead with. A staffing pitch sells availability. A deliverables pitch sells a specific, finished outcome the buyer can picture before the first call even happens. Keep that picture concrete through every step of the sequence, including the opener.

Dev shop outreach works best aimed at companies where a technical need is plausible and somewhat visible: a startup that just raised funding (new budget, pressure to ship), a company whose website or app clearly needs modernization, a business posting about a product launch or expansion that implies new engineering work, or a company that recently lost technical leadership (a CTO departure often means projects stall and get outsourced short-term).

Use AI Leads to describe this target directly, including funding stage or company size ranges that match your typical project size. Smaller projects usually fit smaller companies (under 50 employees, often pre-Series B); larger modernization or integration projects fit mid-size companies with an existing but under-resourced technical team.

Import a CSV instead when you already have a warmer list, past outreach that stalled, referrals you haven't followed up on, or companies you met at events. A warm-ish list combined with a strong, specific project trigger usually outperforms a larger cold list with a vague one.

Company stage matters as much as company size when picking targets. A pre-seed company rarely has budget for an external build yet, no matter how visible the technical gap is. A seed-to-Series-A company with a product already live and users to support is a better fit: they have real revenue pressure to ship faster than their current team can, which is exactly the gap a project-based dev shop fills. Filter for that stage explicitly in AI Leads rather than relying on employee count alone, since headcount and funding stage don't always move together.

Since this is a deliverables pitch, the right contact owns the product or technical roadmap, not headcount planning. Target Founder/CEO at smaller companies, CTO or VP Engineering, Head of Product, or Director of Engineering. Explicitly avoid HR, Talent Acquisition, and Recruiting titles: reaching those titles with a project pitch signals a mismatched, mass-blasted list, since they can't say yes to a project decision anyway. At larger companies, an Engineering Manager can be a useful secondary contact if the CTO is hard to reach, since they often champion a project internally even without final budget authority.

Contact research runs automatically before drafting and the transparency view shows what was found and used. For dev shop outreach, the valuable signals are a recent funding announcement, a job posting for a role your team could cover on a project basis instead (a strong sign of unmet capacity), public mention of a product launch or feature gap, or an outdated tech stack visible on their live site or job listings.

A funding announcement paired with a stale website or a thin engineering team is one of the strongest combinations you'll find: it signals budget plus need in the same research pass. Prioritize contacts where research surfaced something concrete over ones with only generic firmographic data.

Create the campaign with a meeting-booked goal. In Describe, write your offer the way you'd describe a project brief: what kind of work you do (web app builds, legacy system rebuilds, API integrations, whatever your actual specialty is), typical project length, and what the client walks away with. Concrete language here ("we typically deliver a scoped MVP in 8 to 12 weeks" or "we've rebuilt three checkout flows for e-commerce companies your size in the last year") gives the AI real material instead of generic dev-shop language.

In Practice, generate sample drafts and check that the copy always centers a deliverable and a timeline, never a rate, a headcount, or availability of engineers. If a draft reads like a staffing pitch ("we have developers available now"), that's a signal to tighten the Describe field further.

The strongest dev shop emails read like one technical person recognizing another company's problem, not a sales pitch for available capacity. Load real examples into the writing-style step.

Subject: rebuilding your onboarding flow

Hi Taylor,

Congrats on the raise, saw it on [source]. Quick thought: with the new funding, I'd guess onboarding and activation become a bigger priority soon if they aren't already.

We just wrapped a project rebuilding onboarding for a company at a similar stage, went from a multi-step form to a guided flow, took about 6 weeks start to finish. Happy to share what we learned if it's useful, or talk through what a similar project would look like for [Company].

Worth a quick call?

Sam

Notice the email cites a concrete past deliverable and timeline instead of describing team availability.

Set up a 3-step sequence with delays between touches; steps stop automatically once someone replies. Step 1 leads with the specific trigger and project idea. Step 2 can share a brief, concrete proof point (a similar project you completed, described by outcome and timeline, never a client name if that's confidential) to build credibility. Step 3 can widen slightly, asking directly what's currently on their technical roadmap that's stalled or under-resourced, which often surfaces a completely different project than the one you initially guessed at.

Keep every step anchored in deliverables language. If a sequence drifts toward "we can staff this quickly" by step 3, it undermines the framing you set in step 1.

Replies land in your unified inbox, and AI reply handling responds to what the prospect actually asked, commonly "what would this cost" or "can you share examples of similar work." Since project pricing varies widely by scope, review any pricing-adjacent replies personally before a number goes out, even if the AI drafts a reasonable first response.

On analytics, dev shop outreach to funded startups and product-led companies often performs like standard B2B (2 to 5 percent reply, 0.5 to 1.5 percent meeting) though a well-timed funding-trigger email can outperform that. If replies skew toward "we're looking for a full-time hire, not a project," that's useful signal to either adjust targeting toward companies more clearly project-shaped, or reconsider whether staff augmentation deserves its own separate campaign with its own honest framing.

Either way, track which trigger types (funding, a stale site, a job posting, a product launch) actually convert into booked calls over a few weeks. Dev shop buyers vary more by trigger type than by industry, so this is usually the fastest lever for improving reply quality on the next list.

Also worth tracking separately: how many replies ask for a portfolio or past work before agreeing to a call, versus how many agree to a call directly. A high portfolio-request rate usually means your step 1 proof point wasn't concrete enough to build trust on its own, which points back to sharpening the specific outcome and timeline you lead with rather than adding a fourth sequence step.