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

If a mutual offered the intro, send it while their permission is fresh. 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 founder who wants it will answer a clean close more often than a fifth bump.

How do I introduce myself without sounding stiff?

Use one sentence for who you help and one sentence for why now. Skip the origin story. If a mutual is involved, put their name near the top so the email has a human reason to exist. 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 introduction on LinkedIn instead of email?

Yes if this founder 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 introduction?

Don't pretend you've run a job if you haven't. They'll test you. Calling them a 'decision maker' or pitching like they're a Fortune 500 process. Don't open with 'it's been a while' and then paste the old pitch. Those three mistakes show up constantly in Construction inboxes and they all read as "this was templated."

Construction · Founder · Long Time No Contact

Introduction for Construction Founder: Long Time No Contact

An introduction email explains who you are, why this person should care, and what a good next step looks like, without making them do the homework. For Construction teams, the version that works for long time no contact has to respect Don't send long emails during pour days. Write to the founder like they already have a full calendar and

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 introduction work for a Construction Founder?

Credit the mutual connection clearly.
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 founder actually reads: Short, vivid, one proof point max.
Bring a new observation about their world, then offer a small, optional next step.
Offer a brief before a meeting so they stay in control.

When should I send this to a Construction Founder?

If a mutual offered the intro, send it while their permission is fresh. 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 decisions bunch around bid dates and pay apps, not your sequence. If you're emailing a founder, Short, vivid, one proof point max. Tuesday through Thursday mid-morning local time is a safe default.

What this Founder actually cares about

A founder in Construction is protecting runway, focus, and the company's early reputation. They context-switch constantly and reply to emails that reduce uncertainty. They can smell a template that was also sent to 400 peers. The hook that earns a look is a problem they personally still own because the team is small. The ask should stay at this size: a yes/no on timing, or a 15-minute working chat. Delete trigger: Calling them a 'decision maker' or pitching like they're a Fortune 500 process. Tone: Human and specific. Peer to peer, not vendor to 'target.'

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 human and specific.
If you're introducing two other people, write a blurb each can forward.
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 pretend you've run a job if you haven't. They'll test you.

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

Giant bios make intros feel like homework.
Don't open with 'it's been a while' and then paste the old pitch.
Don't pretend you've run a job if you haven't. They'll test you.
Calling them a 'decision maker' or pitching like they're a Fortune 500 process.

How does this long time no contact scenario compare?

Dimension	For this template
Best send window	Only when you have a trigger
Ideal length	Short, vivid, one proof point max.
Primary ask	a yes/no on timing, or a 15-minute working chat
Industry metric to cite	win rate on bids, RFI cycle time, and retainage aging
Tone	Human and specific. Peer to peer, not vendor to 'target.'
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

Construction note on bid follow-up that dies, subs who go dark,

Body

Hi [First Name],

I'll keep this short so you can decide if a conversation is worth it.

I'm writing because a bid due date, a failed inspection, or a GC switching software. I help [type of company] with shortened bid-follow-up cycles from 11 days to 4 for a regional GC. Recent example: [result] for [similar team]. If that's irrelevant, ignore this.

Bring a new observation about their world, then offer a small, optional next step.

If you'd rather I talk to [other role], I can do that.

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 "Construction note on bid follow-up that dies, subs who go dark," outperforms "Just checking in" because a founder 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.