Sales EmailTemplate

Construction · CEO · After Demo

Referral Request for Construction CEO: After Demo

A referral request email for a Construction CEO (after a demo) is a short message that reopens the thread without making them do extra work. A referral request email asks someone to make an intro by doing the work for them: who, why, and a forwardable blurb. In this setting, that means speaking to bid follow-up that dies, subs who

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 referral request work for a Construction CEO?

  • Explain why they'd look good for making the intro.
  • 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.
  • Replay the two moments they leaned in, and the one concern they named.
  • Include a forwardable paragraph.

When should I send this to a Construction CEO?

Ask after you've given them a reason to want to help, not after the first coffee. Same day with the recap. A value bump 3 days later if they went quiet. For this combo, treat "Same day, then 3 days if silent" 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.

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. If you cannot name a bid due date, a failed inspection, or a GC switching software, wait until you can. If you cannot name a bid due date, a failed inspection, or a GC switching software, wait until you can.

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.
  • Never send a referral ask from a brand-new relationship.
  • Time it for Same day, then 3 days if silent. Same day with the recap. A value bump 3 days later if they went quiet.
  • Don't pretend you've run a job if you haven't. They'll test you.

What mistakes should I avoid with this after demo note?

  • Asking 'who do you know?' is lazy and gets no names.
  • Don't send a 19-page deck that relitigates features they skipped.
  • 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 demo scenario compare?

DimensionFor this template
Best send windowSame day, then 3 days if silent
Ideal lengthKeep the whole note under 70 words unless they asked for detail.
Primary askone decision or a 10-minute yes, not a workshop
Industry metric to citewin rate on bids, RFI cycle time, and retainage aging
ToneDirect, adult, light on process jargon. Talk like a peer who did the homework.
Unlike after meetingThey have product context now. Speak to what they saw, not to a generic intro.
Unlike after proposalPricing may not be on paper yet. Don't jump to 'ready to sign.'

What should I copy and send?

Copy-ready template

Subject

Forwardable blurb inside, if you're open to an intro

Body

Hi [First Name],

I'm looking for a warm intro to [specific role] who owns [pain], and you came to mind because [reason].

The version of this that matters for PMs, estimators, and owners who live in change orders and weather is shortened bid-follow-up cycles from 11 days to 4 for a regional GC. Ideal person: [role] at a [company type] dealing with bid follow-up that dies, subs who go dark, and paperwork that lags the jobsite. Not trying to spray this across your whole book.

Answer the real objection and make internal forwarding easy.

Comfortable making that intro, or should I find another path?

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 "Forwardable blurb inside, if you're open to an intro" 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.