Cold email templates for engineering managers and CTOs

Engineers distrust marketing language and can check a technical claim in minutes. This sequence keeps to one technical detail you really read and a plain description of the product.

We wrote these and have no reply rate for them, so we quote none. We make GrowFast, a tool that sends sequences like this one. How these were checked.

Who this is for

You sell a developer tool, API or infrastructure service. You are writing to an engineering manager, the CTO of a small company or a staff engineer who owns the decision.

Before you write: find one true thing

The first bracket of the first email is the whole point. Spend five minutes on the recipient's public pages and write down something you can name exactly.

What to look for and where
What to look forWhere
A library, API or integration they publishtheir public repositories and documentation
A status page incident or a changelog entrythe status page and the changelog
The stack they namejob posts and the engineering blog
A conference talk or post by the person you are writing totheir public profile or the company engineering blog

The sequence

Everything in [square brackets] is yours to fill in. If you cannot fill in the first bracket with something real, do not send that email: a generic opener is exactly what these templates exist to stop.

  1. 1. First email

    Send day 1

    Subject: your [repo or API name] docs

    Hi [First name],
    
    I was reading the [repo or docs name] and noticed [one concrete technical detail, such as how you handle retries or versioning].
    
    I'm [Your name] at [Your product]. [What it does, in one plain sentence with no adjectives.]
    
    How do you handle [the problem] today? If it's not relevant, tell me and I'll stop emailing.
    
    [Your name]

    Why it is written this way. A technical reader responds to a detail that shows you read the work. The question asks how they do it today, not whether they want to buy, and engineers tend to enjoy answering that.

  2. 2. Follow-up 1

    Send 3 days after the first

    Subject: how [Your product] works

    Hi [First name],
    
    To be concrete: [Your product] works by [how it works, in one sentence an engineer could repeat]. The part that differs from [the common alternative] is [one real difference].
    
    Would a short example against your [API or stack] help?
    
    [Your name]

    Why it is written this way. It says how the product works. Engineers want the mechanism, not the benefit, and an example against their own stack makes the claim checkable.

  3. 3. Follow-up 2

    Send 6 days after the second

    Subject: closing this thread

    Hi [First name],
    
    Last email from me. If [the problem] becomes a priority at [Company], the docs for [Your product] are at [your docs URL].
    
    Thanks for your time.
    
    [Your name]

    Why it is written this way. It points at the docs, not a sales page, and leaves.

The same sequence, filled in

Invented for illustration: Priya builds Tracewell (replay of failed webhook deliveries) and writes to Tomas, an engineering manager at Lumen Payments. Neither company is real; the technical detail is made up to show how concrete the first line should be.

  1. Email 1. Subject: your Lumen API docs

    Hi Tomas,
    
    I was reading the Lumen API docs and noticed the webhook retry guidance says to retry up to five times with no mention of an idempotency key.
    
    I'm Priya at Tracewell. It records failed webhook deliveries with their request IDs so a team can replay them.
    
    How do you handle failed webhook deliveries today? If it's not relevant, tell me and I'll stop emailing.
    
    Priya
  2. Email 2. Subject: how Tracewell works

    Hi Tomas,
    
    To be concrete: Tracewell sits in front of your outbound webhooks and stores each failed attempt with its payload. The part that differs from a plain retry queue is that you can replay one attempt by request ID.
    
    Would a short example against your webhook endpoint help?
    
    Priya
  3. Email 3. Subject: closing this thread

    Hi Tomas,
    
    Last email from me. If failed webhooks become a priority at Lumen Payments, the docs for Tracewell are at docs.tracewell.example.
    
    Thanks for your time.
    
    Priya

The footer every email needs

CAN-SPAM requires a postal address and a working way to opt out in every commercial email, B2B included, and Gmail and Yahoo ask bulk senders for one-click unsubscribe. The templates above leave the footer out because your sending tool should add it. GrowFast puts the sender's saved postal address and an unsubscribe link on every email and follow-up. If you send from another tool, add them yourself, for example:

[Your name], [Your company], [Street address, city, postal code, country]
Don't want these emails? [Unsubscribe link]

Then paste each email, with the brackets filled in, into the cold email checker and tick the footer box only if your tool really adds it. Plan the volume with the send schedule calculator. Law differs by country and we are not lawyers; see is cold email legal.

What to avoid with this audience

  • Saying 'revolutionary', 'AI-powered' or 'game-changing'. If the mechanism is interesting, describe the mechanism.
  • Inventing a technical detail about their stack. Wrong specifics are noticed immediately.
  • Sending to a shared support@ or dev@ alias. Find a named engineer or manager.

Questions

Should the first email include a link to my docs?
Not in the first email. One link is not forbidden, but a first email with none reads more like a person wrote it. Offer the link in a follow-up once you have a reason to.
How do I find a technical decision maker?
Look at the team page, the engineering blog's authors and the repositories' maintainers. Use an address they publish and do not guess one.

Want the first line researched for you?

Paste your product's domain and GrowFast finds companies that fit, using only addresses they published and checked for a mail server, and drafts a first email from what each company says on its own site. Nothing is sent without you, and the scan needs no account.

Scan my domain