How many times should I follow up with a Founder (after a demo)?

If a mutual offered the intro, send it while their permission is fresh. Same day with the recap. A value bump 3 days later if they went quiet. 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.

Should I include a recording in the demo follow-up?

If you recorded it and they agreed, yes, plus timestamps for the two parts they cared about. A raw 40-minute link with no map is homework. Add the three bullets they'd need to brief a colleague. 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 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 SaaS introduction?

Don't promise 'AI that runs itself.' They hear that weekly. Calling them a 'decision maker' or pitching like they're a Fortune 500 process. Don't send a 19-page deck that relitigates features they skipped. Those three mistakes show up constantly in SaaS inboxes and they all read as "this was templated."

SaaS · Founder · After Demo

Introduction Email Template for SaaS Founder: After Demo

Use this introduction template when you're emailing a Founder in SaaS (after a demo). They saw the product. Now they're comparing, forwarding, or quietly deciding it wasn't for them. Keep the note aligned with Human and specific. Peer to peer, not vendor to 'target.'

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 SaaS Founder?

Credit the mutual connection clearly.
Speaks to time-to-value that slips past the first 14 days and quietly becomes churn instead of a generic "value prop."
Fits how a founder actually reads: Short, vivid, one proof point max.
Replay the two moments they leaned in, and the one concern they named.
Offer a brief before a meeting so they stay in control.

When should I send this to a SaaS Founder?

If a mutual offered the intro, send it while their permission is fresh. 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 evaluation can close in two weeks for a point tool or drag a quarter when security is involved. If you're emailing a founder, Short, vivid, one proof point max.

What this Founder actually cares about

A founder in SaaS 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. They protect runway, focus, and the company's early reputation, so keep the ask at "a yes/no on timing, or a 15-minute working chat."

How SaaS changes the note

SaaS buyers are software teams juggling seat growth, churn, and a stack that's already too loud. They've been burned by tools that demo well and then die in implementation. Lead with integration and time-to-value, not feature lists. A credible proof point in this vertical sounds like: cut onboarding from 19 days to 6 for a 40-person customer success team. Watch the language. Words that land here include activation, seats, SSO, sandbox, expansion, churn. Buyers here measure success with net revenue retention, time-to-first-value, and expansion inside existing accounts. Buyers here measure success with net revenue retention, time-to-first-value, and expansion inside existing accounts.

How should I customize this template before I send it?

Replace the pain line with a B2B SaaS company adding usage-based billing on top of a messy seat model.
Keep the tone human and specific.
If you're introducing two other people, write a blurb each can forward.
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 promise 'AI that runs itself.' They hear that weekly.

What mistakes should I avoid with this after demo note?

Giant bios make intros feel like homework.
Don't send a 19-page deck that relitigates features they skipped.
Don't promise 'AI that runs itself.' They hear that weekly.
Calling them a 'decision maker' or pitching like they're a Fortune 500 process.

How does this after demo scenario compare?

Dimension	For this template
Best send window	Same day, then 3 days if silent
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	net revenue retention, time-to-first-value, and expansion inside existing accounts
Tone	Human and specific. Peer to peer, not vendor to 'target.'
Unlike after meeting	They have product context now. Speak to what they saw, not to a generic intro.
Unlike after proposal	Pricing may not be on paper yet. Don't jump to 'ready to sign.'

What should I copy and send?

Copy-ready template

Subject

[Company Name] / net revenue retention

Body

Hi [First Name],

[Mutual] thought we should talk because you're dealing with [pain] and I spend my week on [adjacent work].

The version of this that matters for software teams juggling seat growth, churn, and a stack that's already too loud is cut onboarding from 19 days to 6 for a 40-person customer success team. Happy to send a 5-line brief before any call so you know what you'd be walking into.

Replay the two moments they leaned in, and the one concern they named.

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 "[Company Name] / net revenue retention" 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.