Cold email template

Cold email template for a Head of Customer Success

CS leaders rarely get cold-emailed about outbound, which is exactly why this works. CS owns expansion in many companies. Expansion looks a lot like outbound.

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

What a Head of Customer Success is dealing with this quarter

  • An NRR target the board is now scoring quarterly
  • A CSM team that is at 1:30+ ratio and burning out
  • An expansion playbook that has not been refreshed in a year
  • A churn quarter that nobody wants to talk about

Buyer signals to look for on a Head of Customer Success's LinkedIn

  • Recent post on NRR, expansion, or land-and-expand
  • Hiring for CSMs

Sample cold email written to a Head of Customer Success

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

Subject: your post on NRR being a writing

Hey Jess, your post on NRR being a writing problem more than a product problem was the right framing.

Most heads of CS at Series C companies find the expansion-outbound layer is doing 1.0x of its potential because the CSM team is not built to write outbound at scale.

We give CSMs the same per-prospect 4-sentence opener tool the SDR team uses, so expansion plays read like outbound, not like tickets.

Worth 12 minutes Thursday to walk through what an SDR + CS hybrid team did?

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

Does this work for CS expansion outbound?

Yes. Same 4-sentence structure, same Chrome extension, same per-prospect opener. The only thing that changes is the value prop you load into the prompt.

More role-based templates