A cold email to a head of RevOps arrives in the inbox of the person who owns the stack every other vendor wants to bolt onto, which means they have already received your category's pitch this week. The head of RevOps reading a cold email is also the most technically literate buyer in the revenue org: they know the object model, the fields, the integration limits, and exactly which promises in your deck break at implementation. Vague notes about 'alignment' and 'a single source of truth' confirm you have never sat in their seat. What gets a reply is specificity: the CRM they run, the process you have seen break at companies like theirs, and a claim about adoption or data quality you could prove in a sandbox. The templates below are built that way. Each names something concrete about their stack or team, makes one claim, and asks for something a RevOps leader can evaluate in fifteen minutes. The prompt after them finds the stack details first.
What a Head of RevOps is measured on, and what they delete
A head of RevOps is measured on forecast accuracy, CRM data quality, rep adoption of the process, quote-to-cash speed, and the cost of the stack, and the last one makes them the person most often pitched and least often persuaded. They read email at a desk, on a laptop, mid-day, between the Slack threads where most of their real work happens, and nobody screens it for them. Their filter is technical: an email that does not name the CRM they run, the object it touches, or the integration path is deleted as a template. They also delete anything that promises to replace part of the stack they built, anything that says 'single source of truth,' and anything with 'AI' doing unspecified work. They reply to a peer who names the field, the failure, and the adoption number.
Cold email to a head of RevOps: three templates
Fill the CRM and tool names from their job postings before anything else; a wrong system name ends the email in line one. Then pick by evidence: a hiring signal, a process failure you can name, or a peer RevOps team with documented numbers.
Subject: the RevOps analyst role and {{CRM}} hygiene
{{first name}}, the RevOps analyst posting on {{company}}'s careers page lists {{CRM}} data hygiene and forecast reporting in the first three bullets.
That usually means the team is spending its week fixing records instead of building the process, and hiring to keep up.
We fix the inputs upstream: reps complete the fields because enrichment and next step are pre-filled. Acme Observe cut manual CRM updates {{result}} and gave the analyst better work.
Want the field-level spec to check against your object model?Subject: adoption, three weeks after rollout
{{first name}}, most RevOps teams can get a process into {{CRM}} in a sprint and then watch reps route around it by week three.
Adoption dies at the field level: every required field a rep has to look up by hand is one they will fake.
We pre-fill the research and next-step fields so the process is the easiest path. Northwind Freight went from {{before}} to {{after}} field completion in a quarter.
Reply "fields" and I will send the mapping we used.Subject: how Harlow Logistics got forecast variance under {{result}}
{{first name}}, Harlow Logistics' head of RevOps runs {{CRM}} with {{n}} reps and a {{sales motion}} motion, which looks a lot like {{company}} from the outside.
They put {{product}} in front of the team and forecast variance dropped from {{before}} to {{after}} in {{timeframe}}, with the rep adoption numbers to back it. Their RevOps lead documented the object changes.
Want that doc, or a fifteen-minute call with them?the RevOps analyst role and {{CRM}} hygiene
adoption, three weeks after rollout
how Harlow Logistics got forecast variance under {{result}}
{{CRM}} field completion at {{company}}
one object, one field
re: your {{CRM}} migrationName the CRM, the object, and the field, and offer the spec instead of the deck; a RevOps leader who can check your claim in their sandbox in fifteen minutes will, and one who cannot will file you with the other forty pitches.
Personalize these to the account, not just the persona
A RevOps leader can tell in one line whether you know their stack, and a template with {{CRM}} still in it fails that test. The version that gets answered names the CRM from their job posts, the process their hiring hints is broken, and the field-level change you would make. Paste the template with the prompt and let Claude pull the stack details first.
You are writing a cold email to the head of RevOps at {{company}} ({{company URL}}) for {{my company}}, which sells {{one-line description}} and touches {{objects and fields, e.g. Opportunity stage and next step}}.
First, work out their stack from public sources: job postings (CRM, enrichment, sequencing, and CPQ tools named in the requirements), integration pages, and any RevOps talk by their team. Note the sales motion and team size where visible.
Then rewrite the template below. Line one must name the CRM or a tool they run and a specific process signal from the postings. Make one claim about adoption, data quality, or forecast variance, at the field level where possible. Keep one soft ask for a spec or mapping, and the body under 90 words. Use {{customer proof}} exactly as stated.
Mark anything inferred. Then give me three subject lines that name a system or an object.
TEMPLATE:
{{paste the template}}Write cold email at scale with Claude
- B2B cold email templates skill →The Claude skill that writes cold email in your brand voice with the banned-word list and the one-idea rule baked in.
- Cold email from a value prop prompt →The copy-paste prompt version: one value prop in, one specific email out.
- Personalize cold email with Clay and Claude →The use case that runs these templates across a whole list with real enrichment data.
Frequently asked questions
How do you write a cold email to a head of RevOps?
Prove in line one that you know their stack: name the CRM from their job postings, the object your product touches, and the process signal that told you it is broken. Make one claim about adoption, data quality, or forecast variance, with a customer number you can back up, and offer the field-level spec or the mapping doc rather than a demo. Under 90 words, plain text, no tracking. A head of RevOps evaluates vendors for a living and will test your claim in a sandbox; the email that makes that test easy gets the reply.
What do RevOps leaders hate in vendor emails?
Three things, in order. First, 'single source of truth' and 'alignment,' because every tool in the stack they already built was sold on those words. Second, a promise to replace part of that stack; they chose it, they integrated it, and they will defend it. Third, a deck where the demo is the only evidence, with no object model, no field list, no integration path. Add 'AI' doing unspecified work and a calendar link in the first email, and you have the complete profile of what gets deleted before the second sentence.
Should you email RevOps or the VP of Sales first?
RevOps first when your product changes the CRM, the process, or the data, because they will be asked to evaluate it anyway and they resent being the last to know. The VP of Sales first when your value is booked meetings or pipeline and the CRM change is minor. Whichever you choose, tell the other you have written; RevOps and sales leadership talk daily, and an email that surfaces in that conversation as 'did this person write to you too?' does better than one that surfaces as a surprise.