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 CTO 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 introduction?

Don't call guests 'users.' They're guests. Calling it 'AI-powered' with no description of the system. Don't open with 'it's been a while' and then paste the old pitch. Those three mistakes show up constantly in Hospitality inboxes and they all read as "this was templated."

What's a good hospitality follow-up that isn't a review request?

A specific thank-you, a useful local note, a missing-item check, or a direct-book offer for a return stay. Review asks work better after you've been helpful, not as the only reason you wrote. Name the stall they care about, offer one small next step, and stop before the thread feels like a sequence.

How should a introduction to a Hospitality CTO change for long time no contact?

Fresh start. Don't scold them for the gap. Don't email during Saturday check-in chaos and expect a thoughtful reply. Be useful on weekday mornings. The CTO is guarding reliability, security, and engineering time, so the ask should stay at "a technical working session or a written teardown, not a 'vision call'." If you copy a generic template and only swap

Hospitality · CTO · Long Time No Contact

Introduction for Hospitality CTO: 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 Hospitality teams, the version that works for long time no contact has to respect Don't email during Saturday check-in chaos and expect a thoughtful reply. Write to the CTO like they already have

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 Hospitality CTO?

Credit the mutual connection clearly.
Speaks to direct bookings leaking to OTAs and follow-up that ignores seasonality instead of a generic "value prop."
Fits how a CTO actually reads: 90 words is plenty if the substance is real. Don't pad.
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 Hospitality CTO?

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 seasonality is the calendar. a great idea in july may be noise in december, or the reverse. If you're emailing a CTO, 90 words is plenty if the substance is real. Don't pad.

What this CTO actually cares about

A CTO in Hospitality is protecting reliability, security, and engineering time. They look for architecture, failure modes, and whether you'll create toil for their team. Fluff is a ranking signal that you don't know the work. The hook that earns a look is an incident class, a security gap, or a cost line they already hate. The ask should stay at this size: a technical working session or a written teardown, not a 'vision call'. Delete trigger: Calling it 'AI-powered' with no description of the system. They protect reliability, security, and engineering time, so keep the ask at "a technical working session or a written teardown, not a 'vision call'."

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 precise.
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 call guests 'users.' They're guests.

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 call guests 'users.' They're guests.
Calling it 'AI-powered' with no description of the system.

How does this long time no contact scenario compare?

Dimension	For this template
Best send window	Only when you have a trigger
Ideal length	90 words is plenty if the substance is real. Don't pad.
Primary ask	a technical working session or a written teardown, not a 'vision call'
Industry metric to cite	occupancy, RevPAR, and direct-booking mix
Tone	Precise. No slogans. It's fine to be a little dry.
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

Quick intro on [shared problem]

Body

Hi [First Name],

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

The version of this that matters for GMs, revenue managers, and owners balancing occupancy, labor, and reviews is moved 9 points of mix from OTA to direct with post-stay follow-up that didn't beg. Two reasons this might matter now: [trigger 1] and [trigger 2]. If I'm reading that wrong, tell me.

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

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.

Related templates

Want a custom draft instead? Try the email generator.