Cold Emailing a CEO vs a VP: Tone and Length

CEOs and sales VPs may influence the same purchase, but public research does not establish one universal template for each role. This guide treats role-based differences as hypotheses to test, not measured laws.

What the evidence supports

Two vendor datasets are worth knowing before writing either email, and both say less than the usual role-stereotype advice claims.

Gong's analysis of more than one million executive sales cycles reports that messages to C-level recipients performed best between 50 and 100 words, with reply rates dropping once emails passed 100 words; that subject lines of one to four words were associated with the highest open rates; and that CTAs offering something concrete, such as a benchmark or peer comparison, outperformed immediate meeting requests. That is observational platform data with limited published methodology, covering C-level recipients generally. It is not a controlled CEO-versus-VP comparison.

Lavender's benchmark report, built from 231,818 cold emails across roughly 50,000 connected inboxes, breaks results out by department and seniority. Notably, its seniority findings group C-suite and VP recipients together as executives who respond to company-level strategy and timing: revenue, cost, and risk. Neither dataset supports writing substantially longer emails to VPs. Gong supports testing its 50-to-100-word range with C-level recipients; a distinct VP optimum remains unestablished.

So the honest position is narrow. Brevity, a concrete offer, and a short accurate subject line have observational support for executive recipients as a group. Everything below about splitting the message by role is a SalesTap editorial hypothesis to test on your own cohort.

Should the CEO or the VP receive the email?

Before tuning tone, decide who should get the email at all. Routing is mostly a function of structure, not psychology:

• Company size. As an illustration, at a 30-person startup the CEO may own the problem operationally. At a 2,000-person enterprise, an interested CEO may delegate it, so a forward can be a useful outcome.
• Problem ownership. If a named functional owner exists (a VP of Sales, a Head of RevOps), the operational conversation will usually start with them. Email the CEO only when the problem genuinely sits at company level: category strategy, material cost or risk, cross-functional trade-offs.
• Purchase scope. A tool used by one team will often begin as a functional decision. A platform that changes how several departments work may be closer to a CEO-level topic, and even then may reach the CEO through the team.

Your pre-call research should answer the routing question before you write a word.

A fictional CEO-versus-VP comparison

Corvid Freight is a fictional composite: a 200-person logistics-software company whose public careers page lists five open SDR roles. The sender sells call-review software. The trigger in both emails is that verifiable public listing, and nothing else; neither email claims a relationship or knowledge of internal plans.

To the CEO (organisation-level implication, 62 words):

Subject: SDR ramp cost

Hi Dana. Corvid's careers page lists five SDR openings. If those roles represent net growth, one planning question is how quickly the investment becomes productive. We make call-review software for onboarding. If it's useful, I can send a two-page summary of how similar-sized teams structure early call coaching. If this sits with someone else on your team, happy to be pointed there.

To the VP of Sales (operational mechanism, 55 words):

Subject: call review while hiring

Hi Marco. Corvid's careers page lists five SDR openings. If those roles represent net growth, manager coaching capacity may need to expand with the team. We make call-review software for onboarding. I can share a one-page outline of how teams maintain weekly call reviews during a hiring period. Useful, or is call review already covered?

Only offer a summary, benchmark, or customer comparison if it genuinely exists and every claim in it is supportable.

What changed between them is the level of abstraction, not the level of deference: the CEO version frames the same fact as an investment-payback question, the VP version as a workflow question. Both stay inside the 50-to-100-word band the Gong data favours, both offer information rather than requesting a meeting, both use short subjects that describe the actual content, and both are plain and direct. Do not manufacture familiarity in either: no fake "Re:" prefixes, no misleading subjects, and no invented references to internal initiatives; a public hiring or funding announcement is a research prompt, not proof that any internal project exists.

How to test the role hypothesis

If you want to know whether role-tuned emails outperform a single template, test it properly. Randomise variants within each role cohort: CEO recipients split between the tuned and generic versions, VP recipients split the same way. Do not compare raw CEO reply rates with VP reply rates; company mix, list quality, and deliverability differ between the cohorts, so the comparison would be confounded from the start. If several elements change together, the result evaluates the bundled template, not tone, length, or CTA individually.

Measure positive replies or held meetings rather than opens, which machine activity inflates, and track bounces, complaints, and opt-outs as guardrails. Size the test before sending with the A/B Test Designer. If your executive cohort is small, expect directional results and plan the observation window in advance. Casing is a fair thing to test too. Current vendor evidence conflicts on it, so treat lowercase-versus-title-case as an experiment, not a rule.

Where the legal lines sit

For readers sending into the UK or US, neither jurisdiction turns B2B cold email into a free-for-all. In the UK, the ICO's business-to-business guidance explains that PECR's electronic-mail marketing rule does not apply to corporate subscribers, but sole traders and some partnerships count as individual subscribers, and processing a named person's work contact details still falls under UK GDPR, which means a lawful basis, transparency, and honouring objections. In the US, the FTC's CAN-SPAM guidance states the law makes no exception for business-to-business email: headers and subjects must be accurate, the message needs your physical postal address, and a functioning opt-out is mandatory. This is a summary, not legal advice; check your own counsel for your markets.

The takeaway

• The supported playbook is role-agnostic: short, concrete, honest. Gong's executive dataset favours 50-to-100-word emails, one-to-four-word subjects, and offers over meeting requests; Lavender's benchmark groups C-suites and VPs together rather than splitting them.
• Treat role-splitting as a hypothesis. Change the level of abstraction for the same verified trigger, then test tuned against generic within each role cohort, measuring replies and meetings with deliverability guardrails.
• Stay truthful and legal in both inboxes. Do not manufacture familiarity or invent internal knowledge. Use accurate subjects and headers, and follow the relevant transparency and opt-out requirements where those legal regimes apply.

Source check: 31 July 2026. The Gong and Lavender findings, ICO guidance, and FTC requirements were checked against the linked pages. The routing questions, fictional Corvid Freight emails, and role-splitting framework are SalesTap editorial hypotheses, not measured findings.