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

Send it the same day. Thanks that arrive a week later feel like a task. Same day, within a few hours. Next morning is the backup, not the plan. 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.

How soon should I send a thank-you after a meeting?

Same day, ideally within a few hours. Waiting until the next morning is fine if the meeting ran late. Waiting until Friday for a Monday meeting makes it look like a chore. Name the stall they care about, offer one small next step, and stop before the thread feels like a sequence.

What belongs in a post-meeting follow-up?

Decisions, owners, dates, and anything you promised to send. Keep opinions out unless they asked for a recommendation. A forwardable recap does more for the deal than a paragraph about how 'great it was to connect.' 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 thank you 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 Construction thank you?

Don't pretend you've run a job if you haven't. They'll test you. A long origin story or a request to 'pick your brain.' Don't send a pitch deck they didn't ask for as a 'recap.' Those three mistakes show up constantly in Construction inboxes and they all read as "this was templated."

Construction · CEO · After Meeting

Thank You Email Template for Construction CEO: After Meeting

A thank-you email names the specific thing someone did and, when it's natural, points to one next step without turning gratitude into a pitch. For Construction teams, the version that works for after a meeting has to respect Don't send long emails during pour days. Write to the CEO 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

Why does this thank you work for a Construction CEO?

Reflect back one insight they shared.
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 CEO actually reads: Keep the whole note under 70 words unless they asked for detail.
List what you heard, what you promised, and what you need from them, in that order.
Send it while the moment is still in their memory.

When should I send this to a Construction CEO?

Send it the same day. Thanks that arrive a week later feel like a task. Same day, within a few hours. Next morning is the backup, not the plan. For this combo, treat "Same day" as the default, then adjust around decisions bunch around bid dates and pay apps, not your sequence. If you're emailing a CEO, Keep the whole note under 70 words unless they asked for detail. If they named a board week or a freeze, believe it and leave a reopen date.

What this CEO actually cares about

A CEO in Construction 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.' They protect time, reputation, and optionality, so keep the ask at "one decision or a 10-minute yes, not a workshop."

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. Proof that lands: shortened bid-follow-up cycles from 11 days to 4 for a regional GC. Proof that lands: shortened bid-follow-up cycles from 11 days to 4 for a regional GC.

How should I customize this template before I send it?

Replace the pain line with a subcontractor who submitted a bid and then waited in silence for two weeks.
Keep the tone direct, adult, light on process jargon.
If they introduced you, report back after you meet the person.
Time it for Same day. Same day, within a few hours. Next morning is the backup, not the plan.
Don't pretend you've run a job if you haven't. They'll test you.

What mistakes should I avoid with this after meeting note?

A generic 'thanks for your time' is forgettable.
Don't send a pitch deck they didn't ask for as a 'recap.'
Don't pretend you've run a job if you haven't. They'll test you.
A long origin story or a request to 'pick your brain.'

How does this after meeting scenario compare?

Dimension	For this template
Best send window	Same day
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	win rate on bids, RFI cycle time, and retainage aging
Tone	Direct, adult, light on process jargon. Talk like a peer who did the homework.
Unlike after demo	A meeting might have been intro-only. Don't write a product recap they didn't see.
Unlike thank you	Gratitude can live in line one. The rest should be operational.

What should I copy and send?

Copy-ready template

Subject

Thank you for [specific thing]

Body

Hi [First Name],

Just a note to say thank you for [intro / time / review].

I'm writing because a bid due date, a failed inspection, or a GC switching software. I took [their advice] and [what you'll do next]. I'll send a short update once that's done.

Given this is after a meeting, confirm the next date or the open question.

If I can return the favor, say the word.

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 "Thank you for [specific thing]" 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.