A cold email to a CRO is read by the one person in the company who owns every stage of revenue at once: new logos, expansion, renewals, and the forecast that ties them together for the board. Most cold emails to a CRO are written as if they were a bigger VP of Sales, all quota and pipeline, and the CRO forwards those down with 'thoughts?' or deletes them. The CRO's own week goes to forecast credibility, net revenue retention, and the seams between marketing, sales, and customer success where deals and renewals leak. A note that speaks to any of those, with a signal proving you looked at their company, gets read. The three templates below are built at that altitude. Each names something visible from the outside, makes one claim about the whole number rather than a slice of it, and asks for a forward rather than a meeting. The prompt after them does the reading first.
What a CRO is measured on, and what they delete
A CRO is measured on total revenue against plan, net revenue retention, and forecast accuracy, and the third one decides whether the board trusts the first two. They read email on a phone before 6am and between back-to-backs, and at any company past a few hundred people a chief of staff or an executive assistant screens it first, forwarding what looks like it comes from a peer. The CRO's own filter is altitude: anything about rep productivity or sequences gets forwarded to the VP of Sales, anything about churn to the VP of CS, and the sender loses the executive. They delete anything that reads like an SDR sequence they have coached against, anything with 'AI' as the subject, and anything about a single stage of the funnel. They reply to a note about the whole number, with a signal from their own company in line one.
Cold email to a CRO: three templates
Choose by the signal you found: a leadership change, a forecast or retention problem you can infer from the outside, or a peer CRO whose NRR story they would recognize. Every template speaks to the whole number; if your product only touches one stage, say so and ask for the forward.
Subject: your first 90 days at {{company}}
{{first name}}, congratulations on the CRO role. The first board meeting is usually where you find out what the forecast was actually built on.
The CROs who come out of that meeting well usually have one thing in common: a view of pipeline, renewals, and expansion they trusted before presenting it. Acme Observe's CRO set that up in the first {{n}} weeks and walked into the board with {{result}}.
Worth a note on how, or is that better sent to your RevOps lead?Subject: the forecast and the board
{{first name}}, most CROs can defend the new-logo number and go quiet when the board asks about expansion and renewals in the same breath.
That quiet is a data problem: sales, CS, and finance each hold a different version of the customer the week the deck is due.
We build the one account record all three read from. Northwind Freight's CRO went from a {{before}} miss to {{after}} in {{timeframe}}.
If that sounds familiar, reply "forecast" and I will send the setup.Subject: how Harlow Logistics got NRR to {{result}}
{{first name}}, Harlow Logistics' CRO inherited what your {{careers page / earnings call}} suggests you have: a strong new-logo team and a renewal motion nobody owned in full.
They used {{product}} to put expansion signals in front of the account team every week, and NRR moved from {{before}} to {{after}} over {{timeframe}}. Their board deck now leads with it.
I have the write-up their CRO reviewed. Want it, or should I walk your CS and sales leads through it together?your first 90 days at {{company}}
the forecast and the board
how Harlow Logistics got NRR to {{result}}
new logo vs. NRR at {{company}}
the sales-to-CS handoff
{{first name}}, one thought before the board deckWrite for the whole number or the CRO will route you to whoever owns the slice you wrote about, and you will not get back up; if your product only touches new business, say so and ask for the forward yourself.
Personalize these to the account, not just the persona
A CRO template without a real signal in line one gets forwarded down with 'thoughts?' or deleted, and both end the executive conversation. The version that gets a reply names a leadership change, a public forecast comment, or a visible reorg and speaks to the whole number. Paste the template with the prompt and let Claude find the signal before you write a word.
You are writing a cold email to the CRO of {{company}} ({{company URL}}) for {{my company}}, which sells {{one-line description}}.
First, read their site, careers page, newsroom, and any public statement about revenue (earnings call, funding announcement, interview). Look for: a new CRO or CS leader, a reorg that moved CS or marketing under revenue, a stated retention or growth target, a pricing change, expansion into a new region.
Then rewrite the template below for this CRO. Line one must reference one of those signals. Frame the value in terms of the whole number, forecast credibility, net revenue retention, or the handoffs between teams, never rep productivity alone. Keep one idea, one soft ask for a forward or a write-up, and the body under 90 words. Use {{customer proof}} exactly as stated.
Mark anything inferred. Then give me three subject lines under six words that would pass a chief of staff.
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 CRO instead of a VP of Sales?
Change the altitude. A VP of Sales note is about quota, coverage, and ramp. A CRO note is about the forecast they defend to the board, net revenue retention, and where revenue leaks between marketing, sales, and customer success. Open with a signal from their company, a new appointment, a reorg, a stated growth target, and make one claim about the whole number. Ask for a forward or a write-up rather than a meeting; the most common good outcome is the CRO sending your email to a direct report with a one-word instruction, so write the email that survives that forward.
What makes a CRO delete a cold email?
Anything they have coached their own team against. A CRO has reviewed thousands of sequences and can spot the 'quick question' subject, the three-paragraph company intro, the fake 'bumping this to the top' follow-up, and the calendar link in the first email. They also delete notes about one stage of the funnel, because those belong to a VP, and notes that use 'AI' as the product instead of saying what it does. A tracking pixel or a personalization token that misfires, with {{first name}} left in, is an instant delete and a screenshot to the team.
When should you send a cold email to a CRO?
Tuesday to Thursday, timed to land before 6am in their time zone, because that is when most CROs clear email before the first call. Avoid the last two weeks of a quarter and the first week of the next; the forecast and the board deck consume both. The best window is a leadership change: a CRO in their first ninety days is building a view of the business and is unusually open to a note that helps them see it. After that, a reorg, a funding round, or a public revenue target are the next-best triggers.