Cold Email to CTOs: Name the Change, Ask One Question

If you are selling to CTOs, this playbook gives you one angle: name the technical change you saw on their site or in their job posts, and ask one question.

The angle works only if the observation is true and you can point to where you saw it. Most of this guide is about keeping it true, checkable and short. It also covers the sending setup and the rules around it.

Who buys

A guide cannot tell you which companies buy from you. Your own deals can.

Outlevo can import past deals from a CSV or your CRM and run a win/loss analysis that proposes ICP hypotheses [[1]](#sources). The analysis counts companies, not deals, and it labels small samples: under 10 won companies is very low confidence [[2]](#sources). If you have fewer than 10 won companies, treat any pattern you find as a guess to test, not a rule.

If you have no deal history yet, the free assessment reads up to 5 public pages of your website. It returns facts labeled as verified observations or AI inferences, and up to 5 experimental segment hypotheses [[3]](#sources). Segments proposed this way stay labeled experimental until a person approves them [[2]](#sources).

Outlevo asks which countries you sell into and never proposes markets [[2]](#sources). The same applies here: this guide does not tell you where to sell. You decide that.

Roles to reach

This guide does not hand you a fixed title list for engineering leaders. Take the titles from the people who bought from you and from the people who replied to you.

If you use HubSpot, Outlevo can import contacts with email, name, job title and email opt-out. That happens only after an admin turns on contact import with a stated purpose [[4]](#sources). Look at your won deals to see which titles signed or championed the purchase.

Some rules of thumb for the email itself:

Write to one role per company in the first email. A copy of the same note sent to several people in one engineering org reads as a list.
Match the observation to the role. Something seen in a job post is a hiring manager's concern. Something seen on a product page may belong to someone else.
If you are unsure who owns the change, ask that as your one question.

Finding contacts has a credit cost in Outlevo: contact discovery costs 4 credits and volume contact discovery costs 2 credits [[5]](#sources).

Triggers to watch

The trigger in this playbook is a technical change visible in public. Two places to look are the company's own site and its job posts.

Examples of what that can look like, as plain categories: a new product page that implies a new architecture, a documentation or status page that changed, a job post that names a new tool or a new kind of role. These are categories to scan for, not findings about any company.

Rules for keeping a trigger honest:

Quote it. Outlevo keeps facts read from a website only when their quote is found on the page [[6]](#sources). Hold yourself to the same rule. If you cannot copy the line, you do not have the fact.
Date it. A Readiness Card needs at least three observations, each with a source and a date [[6]](#sources). One trigger is a lead. Three dated observations start to look like a pattern.
Label guesses. Outlevo labels guesses as hypotheses and never presents them as findings [[6]](#sources). Do the same in your email: "it looks like" is honest when you inferred, and "you posted" is honest when you read it.

Two more signals can sit beside the public ones. The website visitor script shows which companies visit and which pages they read, and it never identifies a person [[7]](#sources). It costs 1 credit per company identified per day [[7]](#sources). A signal check costs 1 credit [[5]](#sources). A visit from a company is a reason to look at it, not a reason to claim you know what someone read.

What to name in the first line

Name one change. Not two, and not a list of everything you noticed.

A good first line has three parts: what you saw, where you saw it, and roughly when. Anyone at the company can check it in a minute.

Weak: "I saw your company is scaling its engineering team."
Better: "Your careers page lists a role for a platform engineer who would own the build pipeline."

The second one is checkable and narrow. It also does not claim to know why they posted it. Leave out the reason unless it is written on the page.

Two habits help:

Do not flatter. Skip "love what you're building." State the observation and move on.
Do not explain their own system to them. They know it. You are not there to prove you read about it. You are there to show you read one specific thing.

Ask one question

The email gets one question. It should be answerable in a sentence and cost the reader nothing to answer.

Useful shapes:

A question about a decision: "Is the new pipeline role replacing the current setup or sitting beside it?"
A question about ownership: "Who owns that change on your side?"
A question that lets them say no: "Is this on your list this year, or not?"

Avoid questions that hide a pitch, such as "Would you be open to a quick call to see how we reduce build times?" That is a meeting request wearing a question mark. If the reply is interested, Outlevo can answer with your Calendly or Cal.com link with their name and email filled in [[8]](#sources) [[9]](#sources). That comes after they reply, not in the first message.

Sample first email (example)

Example only: written for this playbook, not sent to anyone.

Subject: Your platform engineer role

Hi [First name],

Your careers page lists a platform engineer role that owns the build pipeline. I assumed it is new, but I may be wrong.

One question: is that role meant to replace how builds are handled today, or to sit beside it?

If it is not a priority, a one-word reply is enough and I will not follow up on it.

[Sender name]

[Sender company, street address, city, postal code]

[Unsubscribe link]

Why it is written this way:

The subject line is the thing observed, not a promise.
The first sentence can be checked on a public page. The second sentence is worded as a guess ("I assumed it is new, but I may be wrong") because the sender has not verified it. Keep a line like that only as a guess, unless you did check the page earlier and can say so.
There is one question and no calendar link.
The sender does not describe their product at all. If the reader wants to know what you sell, they will reply and ask, or look you up.
The footer holds the postal address and the unsubscribe link, for the reasons in the next section.

Before you send anything like this, replace every bracket, and replace the observation with one you quoted and dated yourself. Do not reuse this wording across companies. The point of the angle is that each email says something true about one company.

Follow-ups and a second channel

Send a short follow-up that adds one new fact or repeats the question in fewer words. Do not write "just bumping this."

If you also use LinkedIn, Outlevo sends a connection invitation with a short note of at most 300 characters, then one message after the person accepts. A reply stops that lead's emails [[10]](#sources). Automatic LinkedIn sending is included on Growth and Managed. On other plans, the invitations and messages are drafted for you to send by hand [[10]](#sources). Keep the note to the same single observation. Do not paste the email into it.

Sending setup and rules

A good message does not help if the mail does not arrive. Set up sending before you write the first line. The glossary has short entries on deliverability and DMARC.

Mailboxes and domains. With Smartlead, Outlevo builds the campaign in Smartlead and sends from the mailboxes in your Smartlead account [[11]](#sources). Before a campaign sends, every mailbox must be connected and warmed up. Its domain must also have SPF, DKIM and DMARC checked in the last 7 days [[11]](#sources). With Outlevo managed mailboxes, a new mailbox sends nothing until it is warm: at least 14 days, usually about 3 weeks [[12]](#sources). Builder includes 1 domain and 2 mailboxes, and Growth includes 2 domains and 4 mailboxes [[12]](#sources).

Bad addresses. Verify addresses before you send. Email verification costs 1 credit in Outlevo [[5]](#sources). There is a capability page on email verification. If you compare standalone verifiers, the ZeroBounce page quotes that vendor's plans with the date each was read.

Unsubscribe. Google's sender guidelines say: "Marketing messages and subscribed messages must support one-click unsubscribe, and include a clearly visible unsubscribe link in the message body." [[13]](#sources) Treat a cold email to a CTO as a marketing message and include the link.

Postal address. The FTC's CAN-SPAM guide says: "Your message must include your valid physical postal address." [[14]](#sources) Put it in the footer.

Volume rules. Microsoft says: "For domains sending over 5,000 emails per day, Outlook will soon require compliance with SPF, DKIM, DMARC." [[15]](#sources) A targeted campaign to engineering leaders is unlikely to be near that volume. Authentication still matters at any volume.

Privacy law. Rules differ by where the recipient is, so check them for the countries you sell into. Two quotes are useful starting points, not legal advice. GDPR Article 6(1)(f) allows "processing is necessary for the purposes of the legitimate interests pursued by the controller or by a third party". [[16]](#sources) Recital 47 adds: "The processing of personal data for direct marketing purposes may be regarded as carried out for a legitimate interest." [[17]](#sources) The UK regulator's PECR guidance says: "You can email or text any corporate body (a company, Scottish partnership, limited liability partnership or government body)." [[18]](#sources) Ask a lawyer before you rely on any of these.

Approval. Outlevo sends nothing outside a policy that a person approved, and every external action is checked against that policy and recorded in a ledger [[19]](#sources). Policies set who can be contacted, on which channels, how often and with what budget [[19]](#sources). Kill switches pause a campaign, a channel or the whole workspace at once [[19]](#sources). For a small, hand-written campaign, that approval step is the moment to re-read each observation against its quote.

What to expect

Set your expectations from published numbers, not hope. Belkins' 2026 cold email study covers 7.5M B2B emails sent in 2025, with reply rate defined as replies divided by emails sent [[20]](#sources). In that study, 0.45% of emails get a reply across industries [[21]](#sources). Smartlead reports that 0.74% of contacts reply for the median sender [[22]](#sources). The two figures count different things: one counts emails, the other counts contacts.

None of these figures is specific to engineering leaders, and none says that naming a technical change changes the reply rate. Treat the angle as a test. Run it against a plain version on similar companies, and compare replies.

A smaller list written by hand is a different job from a large template send. With a short list, read every reply and write down what the reply said about the observation. If people correct your observation, fix your research step before you send more.

Cost of running this

Outlevo's Builder plan is USD 29 per month with 320 credits, and Growth is USD 149 per month with 1650 credits [[5]](#sources). Credits go to research steps such as signal checks and email verification, which cost 1 credit each [[5]](#sources). Sending, follow-ups and the mailboxes your plan includes use no credits [[11]](#sources).

A short checklist

Before you send each email:

Can you quote the line you saw, and do you know its date?
Is the change one thing, stated in one sentence?
Is there exactly one question, and can it be answered in a sentence?
Is any inference worded as an inference?
Does the footer carry a postal address and an unsubscribe link?
Is the address verified, and is the sending domain authenticated?

If any answer is no, fix it or skip that company.

Related playbooks cover other buyers: cold email to finance leaders and outbound to RevOps leaders at SaaS companies.

Next step

Start with the part you can check today: who your buyers are. The free ICP assessment reads your public site and asks which countries you sell into [[23]](#sources). It returns facts labeled as verified observations or AI inferences, and up to 5 experimental segment hypotheses [[3]](#sources). Use it to choose the first small list, then write each first line by hand from something you can quote.