How many times should I follow up with a CTO (after an interview)?

Don't follow a cold email the next morning. Give it 4 business days. Within 24 hours. Same day is better. 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. Tie the note to one metric or stall they already own, and keep the ask answerable in a single sentence.

What should I say in a follow-up email after an interview?

Thank them for a specific part of the conversation, add one example you didn't get to, and restate interest in the actual work. Keep it under 150 words. Then stop. Daily pings after interviews read as panic, not enthusiasm. Tie the note to one metric or stall they already own, and keep the ask answerable in a single sentence.

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. Tie the note to one metric or stall they already own, and keep the ask answerable in a single sentence.

What should I never say in a Construction cold email?

Don't pretend you've run a job if you haven't. They'll test you. Calling it 'AI-powered' with no description of the system. Don't recap your whole résumé. They were in the room. Those three mistakes show up constantly in Construction inboxes and they all read as "this was templated."

Construction · CTO · After Interview

Cold Email Template for Construction CTO: After Interview

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 Construction teams, the version that works for after an interview has to respect Don't send long emails during pour days. Write to the CTO like they already have a full calendar and a reason to

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

Copy-ready template

Subject

Wrong person for [topic]?

Body

Hi [First Name],

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

In Construction, that usually shows up as bid follow-up that dies, subs who go dark, and paperwork that lags the jobsite. Teams like [peer example] use [Your Product] to shortened bid-follow-up cycles from 11 days to 4 for a regional GC in [timeframe]. The fit depends on whether bid follow-up that dies, subs who go dark, and paperwork that lags the jobsite is actually costing you win rate on bids.

Reaffirm interest, add one proof point, and make next steps easy.

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

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

Why this cold email works

Make the first ask smaller than a 30-minute call.
Speaks to bid follow-up that dies, subs who go dark, and paperwork that lags the jobsite instead of a generic "value prop."
Fits how a CTO actually reads: 90 words is plenty if the substance is real. Don't pad.
Reference a real moment from the conversation and connect it to how you'd do the work.
Give them permission to say you're early.

When should I send this to a Construction CTO?

Don't follow a cold email the next morning. Give it 4 business days. Within 24 hours. Same day is better. For this combo, treat "Within 24 hours" as the default, then adjust around decisions bunch around bid dates and pay apps, not your sequence. 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 Construction 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. 90 words is plenty if the substance is real. Don't pad.

How Construction changes the note

Construction buyers are PMs, estimators, and owners who live in change orders and weather. Don't send long emails during pour days. Be concrete about schedule and docs. Fluffy 'partnership' language wastes a PM's time. A credible proof point in this vertical sounds like: shortened bid-follow-up cycles from 11 days to 4 for a regional GC. Watch the language. Words that land here include bid, RFI, retainage, punch list, GC, change order. Decisions bunch around bid dates and pay apps, not your sequence. Don't pretend you've run a job if you haven't. They'll test you.

Customization tips

Replace the pain line with a subcontractor who submitted a bid and then waited in silence for two weeks.
Keep the tone precise.
Don't attach a deck on the first email.
Time it for Within 24 hours. Within 24 hours. Same day is better.
Don't pretend you've run a job if you haven't. They'll test you.

Common mistakes

Opening with your company story is how cold email dies.
Don't recap your whole résumé. They were in the room.
Don't pretend you've run a job if you haven't. They'll test you.
Calling it 'AI-powered' with no description of the system.

How this scenario compares

Dimension	For this template
Best send window	Within 24 hours
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	win rate on bids, RFI cycle time, and retainage aging
Tone	Precise. No slogans. It's fine to be a little dry.
Unlike thank you	A thank-you is part of it. The rest should show you understood the role.
Unlike after meeting	The power dynamic is different. Don't 'check in on next steps' like a vendor chasing a PO.

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.