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

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. After that, send a breakup note and archive it. A team lead who wants it will answer a clean close more often than a fifth bump.

Should I offer a referral fee in the email?

Only if that's already how you work and it won't make them look mercenary. Many operators prefer a clean intro. If you do mention a fee, keep it secondary to why the intro helps the other person. 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 referral request on LinkedIn instead of email?

Yes if this team lead 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 Hospitality referral request?

Don't call guests 'users.' They're guests. CC'ing their skip-level to apply pressure. Don't send a 19-page deck that relitigates features they skipped. Those three mistakes show up constantly in Hospitality inboxes and they all read as "this was templated." Name the stall they care about, offer one small next step, and stop before the thread feels like a sequence.

Hospitality · Team Lead · After Demo

Referral Request for Hospitality Team Lead: After Demo

The query is practical: what should a referral request email to a Hospitality Team Lead say for after a demo? Start with a direct answer, add one proof point about direct bookings leaking to OTAs and follow-up that ignores seasonality, and close with ask who else needs to see it, or whether a narrower use case is the better start.

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 Hospitality Team Lead?

Include a forwardable paragraph.
Speaks to direct bookings leaking to OTAs and follow-up that ignores seasonality instead of a generic "value prop."
Fits how a team lead actually reads: Very short. They'll read it between standups.
Replay the two moments they leaned in, and the one concern they named.
Explain why they'd look good for making the intro.

When should I send this to a Hospitality Team Lead?

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 seasonality is the calendar. a great idea in july may be noise in december, or the reverse. If you're emailing a team lead, Very short. They'll read it between standups.

What this Team Lead actually cares about

A team lead in Hospitality is protecting the team's focus and their own already-split calendar. They're in the tools all day. They care whether this creates more tickets for their people. Titles don't impress them. Friction does. The hook that earns a look is a daily annoyance, a broken workflow, or a report they have to build by hand. The ask should stay at this size: a 10-minute look or a sandbox, not an executive readout. Delete trigger: CC'ing their skip-level to apply pressure. They're in the tools all day. They care whether this creates more tickets for their people. Titles don't impress them. Friction does.

How Hospitality changes the note

Hospitality buyers are GMs, revenue managers, and owners balancing occupancy, labor, and reviews. Don't email during Saturday check-in chaos and expect a thoughtful reply. Be useful on weekday mornings. A credible proof point in this vertical sounds like: moved 9 points of mix from OTA to direct with post-stay follow-up that didn't beg. Watch the language. Words that land here include RevPAR, occupancy, OTA, group block, shoulder season, ADR. If you cannot name a shoulder-season slump, a renovation, or a review spiral, wait until you can. If you cannot name a shoulder-season slump, a renovation, or a review spiral, wait until you can.

How should I customize this template before I send it?

Replace the pain line with a boutique hotel whose guest follow-up is still a TripAdvisor plea.
Keep the tone informal, useful, zero corporate fog.
Don't attach a commission offer unless that's already your model.
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 call guests 'users.' They're guests.

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 call guests 'users.' They're guests.
CC'ing their skip-level to apply pressure.

How does this after demo scenario compare?

Dimension	For this template
Best send window	Same day, then 3 days if silent
Ideal length	Very short. They'll read it between standups.
Primary ask	a 10-minute look or a sandbox, not an executive readout
Industry metric to cite	occupancy, RevPAR, and direct-booking mix
Tone	Informal, useful, zero corporate fog.
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

Hospitality note on direct bookings leaking to OTAs

Body

Hi [First Name],

If you're willing, I wrote a blurb you can forward as-is.

In Hospitality, that usually shows up as direct bookings leaking to OTAs and follow-up that ignores seasonality. Blurb you can paste: '[Your Name] helps [audience] with moved 9 points of mix from OTA to direct with post-stay follow-up that didn't beg. They asked if you'd be open to a short intro about [topic].'

Given this is after a demo, ask who else needs to see it, or whether a narrower use case is the better start.

If you want changes to the blurb, tell me and I'll rewrite it.

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 "Hospitality note on direct bookings leaking to OTAs" outperforms "Just checking in" because a team lead 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.