CTOs are the hardest persona to cold email in B2B. Most reach a CTO inbox at 3% open rate and 0.4% reply rate, less than half what the same template pulls on a VP of Marketing. The reason is not the inbox. The reason is the wrong frame: most reps email a CTO like they would email any other VP, and CTOs filter that pattern in under 6 seconds.

This is the framework we use at GROU to email CTOs for our developer-tools, infra, and security clients. We have run 47 B2B campaigns since 2022, including 18 with CTO as the primary buyer. The templates below all pull 2 to 5 percent reply rate on real lists, sourced from Apollo's 2025 persona benchmark and our own anonymized client data.

Quick overview

CTOs respond to email that respects their time, sounds technical, and demonstrates you understand the stack. The 4-step framework: identify the CTO type, write in their technical vocabulary, lead with a question not a pitch, and follow up exactly twice.

The 4-step framework:

• Identify the CTO type (founder-CTO vs enterprise-CTO vs VP-Eng-acting-as-CTO)

• Write in their technical vocabulary (Postgres, K8s, OpenTelemetry, not "scalable solutions")

• Lead with a question, not a pitch

• Follow up twice, never more

Source: Lemlist State of Cold Email 2025 reported emails with technical specificity in the first line got 2.8x the reply rate of generic openers when sent to engineering buyers.

Why CTOs are a different buyer

Most reps treat "CTO" as a single persona. In practice there are three CTO types with materially different buying behavior:

The founder-CTO: works at startups under 50 people. Owns the stack, the hiring, and the buying. Reads every email personally. Replies fast or not at all. Highest reply rate of the three (3 to 5 percent on cold).

The enterprise-CTO: works at companies 500+ employees. Owns strategy, delegates buying to VPs and directors. Reads email through an EA or assistant. Lowest cold-reply rate (0.3 to 0.8 percent), but referrals from peers or current customers pull 8 to 12 percent.

The VP-Eng-acting-as-CTO: works at companies 50-500 employees with no formal CTO title. Owns engineering decisions including tooling. Often the real buyer for dev-tools and infra. Middle reply rate (1.5 to 2.8 percent on cold).

The biggest mistake reps make is sending the same email to all three. The founder-CTO wants honesty about scale ("we are a 6-person team, here is what we built"). The enterprise-CTO wants social proof ("3 of your portfolio companies use us"). The VP-Eng wants technical depth ("we handle Postgres logical replication without breaking your read replicas").

Source: Apollo 2025 persona benchmark cross-referenced with GROU 18-CTO-campaign dataset.

What CTOs filter out in 6 seconds

CTOs scan email faster than any other persona, and they pattern-match for sales tells. The fastest filters:

• Subject lines with marketing language ("Boost your engineering velocity 10x")

• Openers that pitch in sentence 1

• Long emails over 100 words

• Calendar links in the signature

• Generic "I noticed you are growing" first lines

• Fake personalization ("Loved your recent post" when there is no post)

• Anything that sounds like an AI-generated email

If your email triggers any of these, it gets archived in under 6 seconds. Source: Smartlead 2025 sender behavior study of inbox triage patterns by buyer persona.

7 cold email templates for CTOs

The 7 templates below cover the most common CTO outreach use cases: dev tools, infra/cloud, security, observability, hiring tools, product demo asks, and breakup. Each template lists the median reply rate from our 18-CTO test set and the best ACV range.

Template 1: Dev tools cold open (CI/CD, IDE, code review)

Median reply rate: 3.4% | Best for: $2k-$20k ACV, founder-CTOs and VP-Eng

Subject: question about your {{specific_tool_or_stack}}

Hi {{first_name}},

How are you handling {{specific_dev_workflow}} at {{company}} today? Saw the repo uses {{specific_tech_from_github}}.

Asking because we built {{product}} for engineering teams stuck running {{specific_pain_workflow}} manually. 4 of our customers replaced {{competitor_tool}} with us last quarter.

Worth a quick reply?

Aljaz

Template 2: Infra/cloud cold open

Median reply rate: 2.8% | Best for: $10k-$100k ACV, all CTO types

Subject: about your {{specific_infra_choice}}

Hi {{first_name}},

Saw {{company}} runs on {{specific_cloud_or_orchestrator}}. We help engineering teams cut {{specific_metric}} (egress, build time, cold-start latency) by 30-60% without changing the orchestrator layer.

If {{specific_metric}} is a current pain at {{company}}, worth a 15-minute chat?

Aljaz

Template 3: Security cold open

Median reply rate: 2.6% | Best for: $20k-$200k ACV, enterprise-CTOs and VP-Eng

Subject: {{specific_compliance_or_threat_pattern}}

Hi {{first_name}},

Most {{their_segment}} engineering teams handle {{specific_compliance_requirement}} by {{common_painful_approach}}. We have 14 customers who switched to {{counter_approach}} and cut audit prep from 6 weeks to 8 days.

If SOC 2 / ISO 27001 / FedRAMP renewal is on your plate at {{company}}, worth a reply?

Aljaz

Template 4: Observability/monitoring cold open

Median reply rate: 3.1% | Best for: $5k-$50k ACV, VP-Eng buyers

Subject: about your {{specific_alerting_pattern}}

Hi {{first_name}},

Saw {{company}} just hit {{trigger_event_like_funding_or_scale_milestone}}. Usually that means {{specific_observability_pain}} hits in the next 60 days.

If you are already running into noisy alerts, dropped traces, or {{specific_metric_blindspot}}, worth a quick reply?

Aljaz

Template 5: Engineering hiring tools cold open

Median reply rate: 2.4% | Best for: $3k-$25k ACV, founder-CTOs

Subject: your engineering hiring queue

Hi {{first_name}},

How are you handling the engineering hiring queue at {{company}} this quarter? Saw {{specific_job_postings_count}} open eng roles.

We built {{product}} so CTOs can run technical screens in 15 minutes per candidate instead of 90. {{number}} customers using us hired their last 5 engineers in under 4 weeks each.

Worth a reply if eng hiring is a 2026 priority?

Aljaz

Template 6: Product demo request (post-engagement)

Median reply rate: 5.8% | Best for: any ACV, when CTO already engaged

Subject: re: your {{specific_engagement_signal}}

Hi {{first_name}},

Following up because {{specific_engagement_signal_e.g._starred_our_repo_replied_to_post}}. Want to send a 6-minute video walkthrough of how {{product}} handles {{specific_technical_concern}}?

No pitch, just the technical detail. Reply with "yes" and I will send it today.

Aljaz

Template 7: Breakup template (touch 4)

Median reply rate: 0.7% | Use 14 days after touch 1

Subject: closing the loop

Hi {{first_name}},

3 emails about {{product}}, no reply, which is a fine answer.

Two options:

• Not a fit, I will stop

• Wrong timing, ping me in 90 days

Either works.

Aljaz

These 7 templates cover the most common CTO outreach use cases. For the full 20-template library across cold open, follow-up, value-add, and referral, see cold email templates that work.

Anatomy of an email that gets past a CTO

A CTO-grade cold email has 5 markers that distinguish it from generic SDR copy. Drop any one and reply rate falls below 1 percent.

Technical specificity in the first 10 words. Reference the actual stack (Postgres 16, K8s 1.29, OpenTelemetry, Cloudflare Workers). Not "your engineering team". Source the specifics from GitHub, their job postings, their tech blog, or their engineering team's Twitter.

Plain English on the business side. CTOs hate when technical email gets dressed up in marketing language ("scalable cloud-native synergy"). Pair technical specifics with plain business language ("cuts your audit prep from 6 weeks to 8 days").

One ask, answerable in 1-3 words. "Worth a reply?" "Is this on your radar?" Not "book a 30-minute discovery call". CTOs respond to questions they can answer in seconds.

Under 75 words in the body. CTO emails over 100 words get archived. Under 50 lifts reply rate 2x in our test set.

First-name sign-off, no calendar link. Calendar links in signatures register as "this is automated sales". Hold the link until reply 2.

Source: GROU 18-CTO-campaign A/B test data, 2024-2026. Smartlead 2025 benchmark reported the same 5 markers as the top drivers of reply rate on engineering-buyer inboxes.

Subject line patterns that get CTOs to open

CTOs open email that looks like internal engineering communication. The subject lines that pulled highest open rates across 12,000 emails to CTO inboxes in 2025:

• "about your {specific_tech_from_their_repo}" — 54% open. Specificity to their stack signals real research.

• "question about {your_workflow}" — 49% open. Questions get opened.

• "re: {their_recent_post_or_blog}" — 48% open. The "re:" implies prior thread.

• "{specific_compliance_or_threat_pattern}" — 45% open. Compliance + threat language reads urgent.

• "{mutual_eng_leader} suggested I reach out" — 47% open. Real engineering mutuals open at qualified-traffic rates.

• "quick question" — 42% open. Lower than other personas but still beats sales-pitch openers.

Avoid: "Boost your engineering velocity 10x", "Transform your DevOps", "Strategic partnership", anything with "synergy" or "leverage" or "cutting-edge". These pull 8 to 14 percent on CTO inboxes.

Source: GROU 12,000-email sample to CTO inboxes, 2025. Median open rate per subject pattern.

How CTOs object and how to respond

When a CTO replies, the most common objections are predictable. The wrong response burns the lead. The right response gets a meeting.

"We already use {competitor}." Wrong: argue feature parity. Right: "Yes, lots of teams move off {competitor} when they hit {specific_pain}. What is the most painful part of your current setup?"

"Send me a deck and I will look." Wrong: send the 40-slide deck. Right: "Happy to. Want the 4-slide version or the full deep-dive? The 4 covers the technical fit in 2 minutes, the deep-dive needs 25."

"We are not buying this quarter." Wrong: ask "when would be a good time?". Right: "Understood. The reason I asked is that {specific_compliance_or_scaling_trigger} usually hits at quarter Q. Want me to share what {similar_company} did when they were in your spot?"

"What is the price?" Wrong: give a single number. Right: "Range is $X to $Y depending on {specific_dimension}. Where {company} fits depends on {specific_question_about_their_environment}."

"Send to my VP of Eng." Wrong: blind-forward to VP of Eng. Right: "Will do. Quick context for the intro: {1-sentence_pitch}. Should I cc you or just hand off?"

Source: GROU 18-CTO-campaign reply analysis. The "right response" examples are A/B tested against the "wrong response" patterns and pulled 2.4x meeting conversion rate.

When to email CTO vs when to email VP Eng

Not every engineering-tools sale should go to the CTO. The matrix below maps company size and ACV to the right contact.

Under 50 employees, any ACV: email the founder-CTO directly. They own buying.

50-200 employees, ACV under $20k: email VP Eng first, cc the CTO if you have their email. VP Eng owns the buy at this stage; CTO signs off.

50-200 employees, ACV over $20k: email CTO first, cc VP Eng. CTO involved in any 5-figure decision.

200-1000 employees, ACV under $50k: email VP Eng or Director of Engineering. Skip the CTO. CTO is too senior for this ACV.

200-1000 employees, ACV over $50k: email CTO. Mid-market enterprise CTOs decide on five-figure-plus spend.

1000+ employees: do not cold email the CTO. Use referrals (template 19 in the cold email templates that work library) or multi-thread VP Eng + Head of Platform + Director of Infrastructure.

Common mistakes when emailing CTOs

The mistakes that kill CTO email reply rate fastest, ranked by impact across our 18-campaign dataset:

1. Sending to a personal Gmail address. CTOs use work addresses for work email. Personal addresses trigger spam filters.

2. Generic technical claims. "We make your stack faster" with no specifics. CTOs filter this immediately.

3. Pitching in email 1. Ask a question. Pitch comes after reply.

4. Long emails (over 100 words). CTOs scan, do not read. Under 75 words.

5. Marketing-team subject lines. "Boost", "transform", "10x", "synergy" — all kill open rate.

6. Calendar link in signature. Reads as automated sales. Hold the link until they engage.

7. Sending more than 4 touches. CTOs unsubscribe (or mark as spam) at touch 5+.

8. Fake personalization. Worse than no personalization. "Loved your recent post" with no real post triggers immediate distrust.

Tools and infrastructure for CTO outbound

The 7 templates above run on any sender, but some tools materially help when targeting CTOs:

• Smartlead ($39/month entry): the best sender for CTO outbound because of the inbox rotation and warmup features. CTOs are filter-aggressive, so deliverability matters more than other personas.

• Apollo ($59/month entry): the best CTO list source. Apollo has 90% accuracy on CTO emails for companies under 1000 employees. Read the full Apollo review.

• Lemlist ($59/month entry): the best for video personalization, which lifts CTO reply rate by 0.6-1.2 percentage points for high-ACV outreach.

For deliverability, run a separate sending domain and 3 mailboxes per domain. See the cold email for SaaS founders playbook for the founder-grade infrastructure stack and best cold email tools 2026 for the full sender comparison.

Frequently asked questions

What is the best subject line for a cold email to a CTO?

The best subject line for a cold email to a CTO is "about your {specific_tech_from_their_repo}" (54% open rate in our test set) or "question about {your_workflow}" (49% open). Both look like internal engineering email rather than a sales pitch. Avoid "Boost", "10x", "Strategic partnership" — these pull 8-14% on CTO inboxes.

What reply rate should I target when emailing a CTO?

A cold email to a CTO on a clean list should pull a 2 to 4 percent reply rate on the cold open and 1 to 1.5 percent on the follow-up. Founder-CTOs reply highest (3-5%), enterprise-CTOs lowest (0.3-0.8% on cold but 8-12% on referral), VP-Eng-acting-as-CTO sit in the middle (1.5-2.8%).

How long should a cold email to a CTO be?

A cold email to a CTO should be 40 to 75 words in the body. Subject lines should be 2 to 6 words. Going over 100 words drops reply rate by 1.4 percentage points per our 18-CTO benchmark. CTOs scan, they do not read.

Should I email the CTO or the VP of Engineering?

Email the founder-CTO at companies under 50 employees. Email the VP of Engineering at 50-200 employees with ACV under $20k. Email both (CTO primary, VP Eng cc) at 50-200 employees with ACV over $20k. At 200-1000 employees email VP Eng or Director of Engineering for ACV under $50k. Use referrals only for 1000+ employee companies.

Are CTOs more likely to reply to founder-led email?

Yes. Founder-CTOs especially respond better to founder-led email (2.3x reply rate vs SDR-sent on identical lists). The reason is peer-to-peer signaling: founder-CTOs read founder emails as "from someone who builds product" rather than "from someone selling to me". For enterprise CTOs, founder-led email lifts reply rate by 0.4-0.6 percentage points but referral still beats it.

How do I find a CTO's email address?

The three best sources, ranked: Apollo ($59/month, 90% accuracy for CTO emails at sub-1000-employee companies), Clay (multi-source enrichment, 95% accuracy, $149/month entry), and manual sourcing from company tech blogs + GitHub + LinkedIn Sales Navigator. Avoid scraping personal Gmail addresses, those trigger spam filters.

How many cold emails should I send to a CTO in a sequence?

Send a 4-touch sequence over 14 days: cold open at day 0, follow-up at day 3, value-add at day 7, breakup at day 14. Past 4 touches reply rate drops below 0.2% and complaint rate climbs above 0.6%, which is enough to drop sender reputation per Google's bulk sender requirements.

Should I use video personalization when emailing CTOs?

Video personalization adds 0.6 to 1.2 percentage points to CTO reply rate for high-ACV outreach (over $30k ACV). Not worth doing for sub-$10k ACV self-serve deals — the production time exceeds the lift. Tools like Lemlist have video personalization built in.

What technical details should I reference in a CTO cold email?

Reference the actual stack: specific Postgres version, K8s version, observability tool, cloud provider, CI/CD platform, language and framework. Source the specifics from GitHub repos, tech blog posts, engineering team Twitter, and job postings. Generic claims ("your engineering stack") get filtered as sales spam.

Is cold email to CTOs GDPR compliant?

Cold email to CTOs is GDPR compliant in the EU if you have a documented Legitimate Interest Assessment, target professional business email addresses (no personal Gmail), and include a working unsubscribe. CTOs working at EU companies fall under GDPR; CTOs working at non-EU subsidiaries do not. Read the full GDPR cold email playbook.

What is the worst mistake when cold-emailing a CTO?

The single worst mistake is sending a generic SDR template with no technical specificity. CTOs filter generic email in under 6 seconds. The second-worst mistake is fake personalization — claiming you read a post they did not write, or referencing a tech they do not use. Both burn the lead permanently.

Should I send the CTO a 6-minute video walkthrough?

Yes, but only after they reply or engage. Sending a video link in touch 1 reads as automated marketing. Sending a video link in touch 3 (after they have engaged) lifts conversion to meeting by 1.8x in our test set. Use template 6 above for the post-engagement video offer.

About GROU. GROU runs B2B pipeline for SaaS startups, dev-tools, and infra companies out of Colombia, Mexico, and Argentina. Since 2022 we have managed cold email and LinkedIn outbound for 47 clients including 18 campaigns with CTO as the primary buyer across developer tools, observability, security, and cloud infrastructure. The framework in this article is the same one we deploy on every CTO engagement. Methodology: reply rates are medians across the test set on warmed sending infrastructure and verified CTO email lists. If you want help applying this to your campaigns, book a call.

This article contains affiliate links to Smartlead, Apollo, and Lemlist. We earn a small commission if you sign up, at no extra cost. We only recommend tools we deploy on live client campaigns.