Cold email by industry · dev shops

Cold email for web development and software agencies

Every prospect you email has been quoted a tenth of your price by an offshore shop the same week. Dev shop outbound only works when the email carries technical evidence that a cheap quote cannot — something measured, specific to their stack, and true. Positioning on price or on "quality" loses to people who will simply say a lower number.

Who you are actually selling to

CTO / Head of Engineering
At companies with an internal team, where you are selling overflow capacity or a specialism they lack.
Head of Product
Owns the roadmap and feels the backlog. Often has budget for an outside team when engineering is fully committed.
Founder
At non-technical companies, where you are the entire engineering function and trust matters more than stack.

The trigger worth waiting for

A funding round, a stalled or aging public product, a technology migration, or a job posting for engineers with a stack you specialise in. An unfilled engineering req for three months is a company that will consider an agency.

What works

  • +A measured, verifiable technical observation — a real Core Web Vitals number, a specific broken flow, a concrete accessibility failure.
  • +Naming a narrow specialism the offshore quote cannot credibly claim: a regulated domain, a specific integration, a certification.
  • +Showing a comparable build, in their sector, with an outcome attached.
  • +Being explicit that you are more expensive and why, rather than hoping it does not come up.

What fails

  • Automated audit emails with a generic Lighthouse score attached. These are sent in enormous volume and are filtered accordingly.
  • "We build websites and mobile apps using the latest technologies" — this is the offshore pitch, and they are cheaper at it.
  • Emailing a CTO about a WordPress redesign, or a founder about your microservices architecture.

A worked opener

Subject

your checkout on Android Chrome

Body

Your checkout drops the postcode field on Android Chrome when the address autocomplete fires — it is reproducible on a Pixel, and it happens before payment, so those sessions are lost silently and will not appear as failed transactions in your analytics. Short video of it happening: [link]. We build commerce front-ends in regulated retail. Happy to just tell you the fix, whether or not you ever hire us.

Why it works: A precise, reproducible bug with revenue attached, evidence in a link, and value given away for free. It cannot be sent at volume, which is exactly why it works.

Compliance notes

Ordinary B2B. One caution specific to this vertical: do not run scans or automated probes against a prospect's infrastructure to generate your opener. Observations from ordinary use of a public website are fine; anything more can cross into unauthorised access depending on jurisdiction, and it reads badly regardless.

Questions

How do I compete with offshore development pricing?
Not on price, and not on unprovable quality claims. The winning angle is domain specificity — regulated sectors, complex integrations, compliance requirements — where the buyer's risk of a cheap build failing is larger than the saving. Your cold email has to demonstrate that domain knowledge in the first two sentences.
Do automated website audit emails work?
Almost never any more. Buyers receive several a week, all generated the same way, and filters have caught up. A single specific bug you actually reproduced outperforms a generated report by a wide margin — it just cannot be sent at scale.

Have the agents do this for you

Everything on this page is what a good dev shops campaign needs someone to work out. Pipestork works it out from your website — the profile, the companies, the decision-makers, the sequences — and sends from warmed mailboxes, not your domain.

Try it with $30 in credits →