Cold email template

Cold email template for a CTO

CTOs are skeptical buyers by training. The cold email that works is one that is short, technically literal, and respects that they have already evaluated the category before.

Updated June 2026 · 5 min read · By the IntelSDR team

What a CTO is dealing with this quarter

  • An infra cost line that grew 40% YoY without proportional headcount
  • A platform team that is asking for headcount the CFO will not approve
  • A security review they have not finished
  • A vendor list that grew uncontrolled across business units
  • A board ask on AI strategy

Buyer signals to look for on a CTO's LinkedIn

  • Public technical writing or a thoughtful conference talk in the last 6 months
  • GitHub activity or a thoughtful Hacker News comment trail
  • A recent post about platform consolidation, infra cost, or AI

Sample cold email written to a CTO

Hook · pain · bridge · ask. Subject line is a fragment of the hook.

Subject: saw your talk at QCon on the

Hey Felix, saw your talk at QCon on the move from monolith to event-driven. The line on 'consolidation is a feature' is exactly the right read.

Most CTOs at Series C companies hit a quarter where the per-seat AI line items across go-to-market start adding up faster than the platform team can rationalize.

We collapse the AI cost on the sales side to a flat $299/mo with bring-your-own OpenAI key, so the LLM spend lives where you can actually monitor it.

Worth 12 minutes Thursday to walk through the actual setup with someone on your platform team?

The 4-sentence structure, named

  1. Hook — one specific reference to something they said or did publicly in the last 60 days.
  2. Pain — one real problem buyers in this role hit at this stage.
  3. Bridge — one sentence on how IntelSDR closes that gap, with a peer reference if you have one.
  4. Ask — one small ask, on a specific day, for a specific length of time.

That is the structure IntelSDR enforces at the prompt layer. Generic ChatGPT outputs hit 1-3 of these sentences. The fourth is what gets the reply.

Frequently asked

Why would a CTO care about a cold email tool?

Because the AI tax across go-to-market tools is increasingly material on the consolidated AWS or Stripe bill, and bring-your-own-key tooling is the cleanest cost-control posture for the platform team.

Is IntelSDR safe from a security review standpoint?

It is a Chrome extension that runs in the browser, sends page text to the user-controlled OpenAI key only on click, and does not store data server-side. The full privacy posture is at privacy.intelsdr.com.

More role-based templates