How many times should I follow up with a CTO (long time no contact)?

Don't follow a cold email the next morning. Give it 4 business days. Send when you have a real trigger: news, a useful artifact, a role change, a season. After that, send a breakup note and archive it. A CTO 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.

Is it weird to email someone after six months of silence?

Not if you have a new reason and you don't pretend the old thread is still warm. Lead with the trigger, remind them who you are in one line, and make the ask optional. Nostalgia without news is just another cold email with extra steps.

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

Yes if this CTO 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 Manufacturing cold email?

Don't send a brand video. Send a process. Calling it 'AI-powered' with no description of the system. Don't open with 'it's been a while' and then paste the old pitch. Those three mistakes show up constantly in Manufacturing inboxes and they all read as "this was templated."

Manufacturing · CTO · Long Time No Contact

Cold Email for Manufacturing CTO: Long Time No Contact

When a Manufacturing CTO goes quiet (long time no contact), the right cold email does one job: make a reply cheaper than silence. They look for architecture, failure modes, and whether you'll create toil for their team. Fluff is a ranking signal that you don't know the work. That's why this template leads with OEE, scrap, and on-time-in-full instead of

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 Manufacturing CTO?

Give them permission to say you're early.
Speaks to lead-time surprises, quality escapes, and vendors who don't speak the floor instead of a generic "value prop."
Fits how a CTO actually reads: 90 words is plenty if the substance is real. Don't pad.
Bring a new observation about their world, then offer a small, optional next step.
Make the first ask smaller than a 30-minute call.

When should I send this to a Manufacturing CTO?

Don't follow a cold email the next morning. Give it 4 business days. Send when you have a real trigger: news, a useful artifact, a role change, a season. For this combo, treat "Only when you have a trigger" as the default, then adjust around capex waits. operational fixes can move this week if you reduce risk. If you're emailing a CTO, 90 words is plenty if the substance is real. Don't pad.

What this CTO actually cares about

A CTO in Manufacturing is protecting reliability, security, and engineering time. They look for architecture, failure modes, and whether you'll create toil for their team. Fluff is a ranking signal that you don't know the work. The hook that earns a look is an incident class, a security gap, or a cost line they already hate. The ask should stay at this size: a technical working session or a written teardown, not a 'vision call'. Delete trigger: Calling it 'AI-powered' with no description of the system. They protect reliability, security, and engineering time, so keep the ask at "a technical working session or a written teardown, not a 'vision call'."

How Manufacturing changes the note

Manufacturing buyers are plant leaders and supply-chain owners who get paid when the line runs. If you can't talk about downtime in dollars and minutes, you're entertainment. Be precise. A credible proof point in this vertical sounds like: reduced supplier follow-up lag from 6 days to 36 hours on late POs. Watch the language. Words that land here include OEE, takt, scrap, PPAP, lead time, changeover. Buyers here measure success with OEE, scrap, and on-time-in-full. Buyers here measure success with OEE, scrap, and on-time-in-full. Buyers here measure success with OEE, scrap, and on-time-in-full. Buyers here measure success with OEE, scrap, and on-time-in-full.

How should I customize this template before I send it?

Replace the pain line with a plant waiting on a vendor who only updates them when the buyer yells.
Keep the tone precise.
Research one real trigger. Fake personalization is worse than none.
Time it for Only when you have a trigger. Send when you have a real trigger: news, a useful artifact, a role change, a season.
Don't send a brand video. Send a process.

What mistakes should I avoid with this long time no contact note?

Opening with your company story is how cold email dies.
Don't open with 'it's been a while' and then paste the old pitch.
Don't send a brand video. Send a process.
Calling it 'AI-powered' with no description of the system.

How does this long time no contact scenario compare?

Dimension	For this template
Best send window	Only when you have a trigger
Ideal length	90 words is plenty if the substance is real. Don't pad.
Primary ask	a technical working session or a written teardown, not a 'vision call'
Industry metric to cite	OEE, scrap, and on-time-in-full
Tone	Precise. No slogans. It's fine to be a little dry.
Unlike no response	This isn't a 4-day bump. It's a re-introduction with a new reason.
Unlike breakup	You're opening a door, not closing one. Still keep it easy to ignore.

What should I copy and send?

Copy-ready template

Subject

Wrong person for [topic]?

Body

Hi [First Name],

Saw [trigger] and figured this might be on your plate.

The version of this that matters for plant leaders and supply-chain owners who get paid when the line runs is reduced supplier follow-up lag from 6 days to 36 hours on late POs. Most [industry] teams I talk to aren't short on tools. They're short on [specific bottleneck]. That's the slice we handle.

Given this is long time no contact, ask if the old problem still exists, or if you should leave it archived.

If I sent a 1-page sketch, would you glance at it?

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 "Wrong person for [topic]?" outperforms "Just checking in" because a CTO 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.