How many times should I follow up with a CEO (after networking)?

Don't follow a cold email the next morning. Give it 4 business days. Within 24 to 48 hours while they still remember your face or handle. After that, send a breakup note and archive it. A CEO who wants it will answer a clean close more often than a fifth bump.

Should I mention a mutual connection in a cold email?

Only if the connection would be comfortable with it. Name-dropping someone who barely knows you can backfire. If you do mention them, say exactly how you know them in one clause and move on. Name the stall they care about, offer one small next step, and stop before the thread feels like a sequence.

How soon should I follow up after a networking event?

Within two days. After that you're a vague name from a badge. Mention where you met and the topic, send anything you promised, and keep the ask optional. If they wanted a pitch, they would have asked. Name the stall they care about, offer one small next step, and stop before the thread feels like a sequence.

Is it okay to send this cold email on LinkedIn instead of email?

Yes if this CEO is actually active there and the thread isn't about long attachments. Keep the LinkedIn version even shorter. Don't paste the full email. One context line and one question is plenty. Name the stall they care about, offer one small next step, and stop before the thread feels like a sequence.

What should I never say in a Technology cold email?

Don't say 'we disrupt.' They will mute you. A long origin story or a request to 'pick your brain.' Don't dump a calendar link as the first follow-up unless they asked. Those three mistakes show up constantly in Technology inboxes and they all read as "this was templated."

Technology · CEO · After Networking

Cold Email Template for Technology CEO: After Networking

A cold email is a first-touch message to someone who didn't ask for it, so relevance has to show up before the pitch does. For Technology teams, the version that works for after networking has to respect Skip the vision deck. Write to the CEO like they already have a full calendar and a reason to be cautious.

Last updated: 2026-09-02 · Reviewed by: Sales Email Template editors

We write templates the way we wrote emails on quota: short, specific, and easy to forward. When we cite research below, it is because the number changes how a buyer reads your note, not to pad the page.

Sources: HubSpot sales email benchmarks; Gong follow-up research

Why does this cold email work for a Technology CEO?

Show you understand their bottleneck in their language.
Speaks to security reviews that stall deals and tools that create toil for on-call teams instead of a generic "value prop."
Fits how a CEO actually reads: Keep the whole note under 70 words unless they asked for detail.
Remind them of the exact topic you both lingered on.
Lead with an observed trigger, not a compliment about their About page.

When should I send this to a Technology CEO?

Don't follow a cold email the next morning. Give it 4 business days. Within 24 to 48 hours while they still remember your face or handle. For this combo, treat "1-2 days" as the default, then adjust around a tactical buy can be fast. anything in the critical path gets architecture and security votes. If you're emailing a CEO, Keep the whole note under 70 words unless they asked for detail.

What this CEO actually cares about

A CEO in Technology is protecting time, reputation, and optionality. They skim on a phone between meetings. If the first two lines don't name a business outcome, the rest never gets read. The hook that earns a look is a P&L, risk, or competitive issue they already feel. The ask should stay at this size: one decision or a 10-minute yes, not a workshop. Delete trigger: A long origin story or a request to 'pick your brain.' a P&L, risk, or competitive issue they already feel They skim on a phone between meetings. If the first two lines don't name a business outcome, the rest never gets read.

How Technology changes the note

Technology buyers are engineering leaders and IT owners who have seen every vendor trick. Skip the vision deck. Send architecture, security posture, and what happens at 2 a.m. A credible proof point in this vertical sounds like: cut vendor questionnaire turnaround from 3 weeks to 4 days with a cleaner security pack. Watch the language. Words that land here include SLA, SSO, audit log, on-call, roadmap, architecture review. Words that work: SLA, SSO, audit log, on-call, roadmap, architecture review. A thread that ignores security reviews that stall deals and tools that create toil for on-call teams reads like every other vendor bump.

How should I customize this template before I send it?

Replace the pain line with an IT org consolidating overlapping monitoring tools after a noisy quarter.
Keep the tone direct, adult, light on process jargon.
Send from a real name. Role accounts get filtered.
Time it for 1-2 days. Within 24 to 48 hours while they still remember your face or handle.
Don't say 'we disrupt.' They will mute you.

What mistakes should I avoid with this after networking note?

Opening with your company story is how cold email dies.
Don't dump a calendar link as the first follow-up unless they asked.
Don't say 'we disrupt.' They will mute you.
A long origin story or a request to 'pick your brain.'

How does this after networking scenario compare?

Dimension	For this template
Best send window	1-2 days
Ideal length	Keep the whole note under 70 words unless they asked for detail.
Primary ask	one decision or a 10-minute yes, not a workshop
Industry metric to cite	ticket volume, deploy frequency, and time spent on vendor questionnaires
Tone	Direct, adult, light on process jargon. Talk like a peer who did the homework.
Unlike cold email	You have a shared moment. Use it. Writing like a stranger wastes the introduction.
Unlike introduction	You already met. Don't re-introduce your whole bio.

What should I copy and send?

Copy-ready template

Subject

Noticed [trigger] at [Company Name]

Body

Hi [First Name],

I'll be direct: I help [role peers] cut [pain] without adding another bloated tool.

In Technology, that usually shows up as security reviews that stall deals and tools that create toil for on-call teams. Teams like [peer example] use [Your Product] to cut vendor questionnaire turnaround from 3 weeks to 4 days with a cleaner security pack in [timeframe]. The fit depends on whether security reviews that stall deals and tools that create toil for on-call teams is actually costing you ticket volume.

Turn a real moment into a light next step, or just leave a good note.

Wrong person? Point me to whoever owns [pain].

Best,
[Your Name]
[Your Title]
[Your Company]

Questions people ask before they hit send

Name the situation and the business object, not your excitement. Something like "Noticed [trigger] at [Company Name]" outperforms "Just checking in" because a CEO can decide from the preview text whether it's worth opening. Keep it under 50 characters when you can.

Related templates

Want a custom draft instead? Try the email generator.