LinkedIn · 2026-02-24 · 9 min
How to Message a CTO on LinkedIn Without Getting Ignored
CTOs get more cold LinkedIn messages than almost any other title, and they ignore nearly all of them within a second. Here is what actually gets a reply, message by message, and why most outreach fails before the first sentence ends.
A CTO at a company of any real size receives cold LinkedIn messages every day, often several. Nearly all of them get archived without a reply, not because the CTO is rude, but because the message gave them nothing to react to. Reading it cost more attention than ignoring it, so they ignored it.
That is the entire problem to solve. Not "how do I sound impressive to a CTO" but "how do I make the two seconds this person spends reading my message worth more than the two seconds it takes to skip it". Almost every rule below follows from that single constraint.
Why the standard template fails immediately
The message that says "Hi [Name], I noticed you're the CTO at [Company], I'd love to connect and share how we help companies like yours..." fails for a structural reason, not a tone reason. It could be sent to any CTO at any company with two words changed. A CTO can tell within the first sentence whether a message was built for their company or built for a spreadsheet of names, and the second one goes straight into the ignored pile.
The fix is not better copywriting. It is doing the research that makes the personalisation true rather than performed.
What research to do before writing a word
Fifteen minutes per account, before any message is drafted:
- What they have actually built or shipped recently. Engineering blog posts, changelogs, conference talks, or open-source activity tell you what they are proud of and what they are working on.
- Recent hiring signals. A CTO hiring three platform engineers is dealing with a different set of problems to one hiring for a new product line.
- Company stage and likely pressure points. A CTO at a 15-person startup worries about different things than one at a 400-person scale-up. Series A pressure and Series C pressure produce different priorities.
- Anything they have said publicly. A quote in an interview, a comment on a podcast, a post they wrote. If you can reference something they actually said, the message stops looking cold.
The first message
Keep it short. A CTO reading on their phone between meetings will not read six lines.
Structure that works consistently:
- One sentence, a specific and verifiable observation about their company or their own recent activity.
- One sentence, a plainly stated reason this is relevant to them, tied to a pattern you have actually seen elsewhere, not a claim about your product.
- One sentence, a low-friction question or ask. Not "can we schedule a 30-minute demo", but something a busy person can answer in one line if they are interested, and ignore without guilt if they are not.
That is the whole message. No paragraph explaining your company. No bullet list of features. No attachment.
What to avoid entirely
- Opening with your product name. The CTO does not care what you are called yet. They care whether you understand their situation.
- Praising their company in vague terms. "Impressive growth" or "loved reading about your journey" reads as filler, because it is filler.
- Asking for time before earning attention. A demo request in message one assumes an interest that has not been established.
- Multiple links. Every link is a reason to close the message and come back never.
The follow-up sequence
Most replies from CTOs do not come from message one. They come from message two or three, sent days apart, each adding one new piece of information rather than repeating the ask.
A workable three-message sequence:
- Message one: the observation, the relevance, the low-friction question, as above.
- Message two, four to six days later, if no reply: a different angle on the same problem, perhaps a short, concrete example of how a similar company approached it. Still no pitch.
- Message three, another week later: genuinely short. Something like acknowledging they are likely busy and leaving the door open without pressure. This message alone recovers a meaningful share of eventual conversations, because it removes any awkwardness about replying late.
After three messages with no response, we stop for that account and move on. Persisting beyond that reads as pressure, not interest, and damages the credibility of the profile for the next campaign.
A short before-and-after
Before: "Hi Sam, I saw you're CTO at Northfield. We help engineering teams like yours reduce deployment time and improve reliability. Would love to connect and share more about what we do."
After: "Hi Sam, saw Northfield's post about the move to a multi-region setup, that's a heavy lift with a small platform team. We've watched a few teams at similar stage hit the same on-call strain about two months after that kind of migration. Curious whether that's shown up for you yet, or if you got ahead of it."
The second message is not longer by much, but it demonstrates that a real person read something real about the company, and it asks a question the CTO can actually answer.
Why this matters more for CTOs specifically than most titles
CTOs are unusually good at spotting a templated message, because pattern recognition is most of their job. A generic message that might slip past a marketing manager gets identified instantly by someone trained to read code for what it actually does rather than what it claims to do. The bar for credibility with this title is higher than almost any other buyer we message on behalf of clients, which is also why a genuinely researched message performs disproportionately well against it, relative to how it performs with less technical titles.
If you want to see how this looks across a full campaign rather than a single message, our how it works page walks through the research and sequencing process end to end.
Next: pick five CTOs you actually want to talk to this month, spend fifteen minutes researching each one properly, and send only those five messages before you send fifty more.