Cold Emailing a CEO vs a VP: Tone and Length

How to cold email a CEO vs a VP: adjusting tone and length

A CEO and a VP of Sales might both sit on your ICP list, both have signing authority on a $60K deal, and both ignore 95% of cold email. But the email that earns a reply from one will actively annoy the other. The difference isn't seniority. It's what each role is paid to think about on a Tuesday morning.

Most reps write the same email and just swap titles in the salutation. Then they wonder why CEO reply rates crater while their VP cadence performs. The fix isn't a longer email or a shorter one. It's writing to the specific calculation each person runs when an unknown sender appears in their inbox.

What the CEO is actually scanning for

A CEO opens cold email (when they open it at all) on a phone, between meetings, with their thumb already hovering over archive. They are not reading. They are pattern-matching on two things: does this person understand my business, and is the ask trivially small?

That second part is what most reps miss. CEOs don't reply to 15-minute meeting requests from strangers because 15 minutes isn't trivial. It's a calendar negotiation, a context switch, and a decision about whether to loop in someone else. The ask has to be smaller than the cost of declining.

That changes the email shape entirely. CEO outreach should be short enough to read in one thumb-scroll (roughly 60 to 90 words), specific enough that it could not have been sent to anyone else, and end with a question that can be answered in a single line.

Compare these two openers to a Series B CEO whose company just announced a Head of Revenue hire:

Wrong: "Hi Sarah, I noticed Acme just hired a new Head of Revenue — congrats on the momentum! I'd love to share how we help companies like yours scale outbound. Open to a quick 15 min next week?"

Right: "Sarah — the Head of Revenue hire usually means a rebuild of the SDR motion in the next 90 days. We help post-Series-B teams avoid the standard ramp tax during that window. Worth a 2-line reply on how you're thinking about it, or not relevant yet?"

The second one is shorter, makes a specific bet about her near-term reality, and offers an exit. CEOs reply to exits. They almost never reply to enthusiasm.

What the VP is actually scanning for

A VP runs a different calculation. They have a number. They have a team. They have a quarterly review in six weeks where they need to explain why something is or isn't working. When a cold email hits, they're triaging it against the operational problem on their mind that morning.

That makes the VP a longer, more substantive read. Not bloated, but meatier. A VP will give you 150 to 220 words if those words demonstrate you understand the specific mechanics of their role. They want to see that you've thought about the problem, not just identified it.

A VP of Sales doesn't need you to tell them their pipeline is leaky. They need you to name which stage leaks for companies that look like theirs, why, and what changes when that stage is fixed. The proof of relevance lives in the specificity of the diagnosis.

The structure that tends to work: one sentence of context that proves you've done the research, two or three sentences of substantive point of view about the problem, one sentence on what changes when it's solved, one specific ask. The ask can be bigger than what you'd send a CEO. VPs will accept a 25-minute working session if the premise is interesting enough, because evaluating new approaches is part of the job.

The tone shift no one talks about

Here's the part most cold email guides get wrong. They tell you to be "more formal" with executives. The opposite is closer to true.

CEOs read peer-to-peer email all day. Board members, other founders, investors. The register is direct, slightly understated, occasionally blunt. When a rep writes to a CEO in the inflated, deferential tone of someone trying to sound important, the email reads as junior on contact. It triggers the "this is a vendor pitch" reflex before the content even registers.

Write to a CEO the way a peer founder would write asking for a favour. Lowercase subject lines often outperform Title Case ones. Contractions are fine. The phrase "worth a reply or not" is more effective than "would you be open to exploring a conversation."

VPs sit in a different register. They get pitched constantly and they evaluate vendors as part of their job, so they're not offended by sales language. But they are allergic to fluff because fluff signals you don't actually know how their function works. A VP wants you to sound like someone who could plausibly do their job, not someone who sounds important.

The tone test: read your email out loud. If it sounds like a press release, you're writing to no one. If it sounds like a Slack message to a colleague who happens to be senior, you're closer.

Subject lines split by role too

CEOs respond to subject lines that look like internal email. Three to five words, lowercase, no punctuation gymnastics. "quick question on the Q3 hire" outperforms "Helping Acme Scale Outbound in 2026" by a wide margin in CEO inboxes, because it pattern-matches to email from people they already know.

VPs are more tolerant of subject lines that signal topic. "SDR ramp time for post-Series-B teams" works because it tells them whether to open it. They're triaging by relevance to current problems, not by sender familiarity.

The single biggest mistake is using a CEO-style subject for a VP audience or vice versa. A vague "quick question" subject to a VP looks like time-wasting. A topical subject to a CEO looks like marketing.

A worked comparison

Suppose your target is a 200-person fintech that just raised a Series C. You want to reach both the CEO and the VP of Sales about the same product, a conversation intelligence tool.

The CEO email is about strategic risk: the Series C means the board now expects a step-change in revenue efficiency, and the team's coaching infrastructure probably hasn't caught up. Ninety words, ending with "is this on your radar yet or too early?"

The VP email is about operational reality: at this stage of scaling, new AE ramp typically slows because senior reps stop having time to listen to junior calls, and call review becomes the first thing to fall off the calendar. Two hundred words, ending with a specific offer to share a teardown of what the top-quartile teams change at this headcount.

Same product. Same company. Two completely different emails, because the reader is solving a different problem.

The takeaway

• Audit your last 20 sent emails. If the CEO version and the VP version are structurally identical, you're getting one of them wrong, probably both.
• Cap CEO emails at 90 words and end with an explicit exit option. The ask must be smaller than the cost of declining.
• Give VPs 150 to 220 words of substantive diagnosis, not enthusiasm. Prove you understand the mechanics of their function.
• Match subject line register to role: short and internal-looking for CEOs, topical and specific for VPs.