What if I didn't promise a resource?

Don't invent one. Quote the stall and offer an optional continuation. Fake resources are just pitches with nicer wrapping. If you have a genuinely useful public page, link it once. If you don't, the quote is enough. That's the working rule here.

Can I connect on LinkedIn and email the same day?

Pick one primary channel. A LinkedIn request with a two-line note plus a separate pitch email is how you look automated. If you email, keep LinkedIn to a simple connect with no pitch. One conversation. Two rooms confuse them. That's the working rule here.

Should I mention their last funding round in the follow-up?

Only if they brought it up in the hallway. Congratulating a CEO on a round they are tired of hearing about is filler. Quote the operational stall they named. Money news is public. Their sentence is not. That's the working rule here.

What if their assistant replied instead?

Treat the assistant as the reader. Restate the hallway topic in one line and ask whether to send the resource or drop it. Don't try to go around them to the CEO's personal email. That's how you get a permanent filter.

Is a photo from the event a good opener?

Almost never. It's cute until it feels like surveillance. Words they said are enough. If you were on a panel together, cite the panel title. If you weren't, don't pretend a crowd photo is a relationship. That's the working rule here.

Last updated 2026-09-02 · Reviewed by Sales Email Template editors

SaaS · CEO · After Networking

Follow-Up Email After Networking with a SaaS CEO

The note after you met a SaaS CEO at an event should pick up the sentence they left hanging, not restart your pitch. Quote the activation stall, the unused seats, or the implementation mess they named. Then offer one optional next step. Long bios are homework.

Copy-ready template

Subject

You said [Stall] at [Event] before the next intro

Body

Hi [First Name],

You said [Quote: 14-day drop / unused seats / SSO mess] at [Event] before the next intro landed. This is not a badge-scan sequence.

The [Resource: 1-page / post / intro] I promised is attached in spirit: say send and I'll pass it. If 12 minutes on that stall would help [Company Name], I can do [Day] at [Time] [Timezone] or stay async. If it was only a hallway, you can ignore this.

[Your Name]
[Your Title]

Why this follow-up works

The subject is their sentence, which they can search on a plane.
You refuse to convert the badge, which is what 40 other emails will do.
The resource is delivered, so you keep a promise they may have forgotten.
Two paths, live or async, respect a CEO calendar.
Permission to ignore is rare. It gets replies.

When should I send this to a SaaS CEO?

Within two days. After that you're a vague name from a badge. If the event ends on a Thursday, Friday morning is fine. Monday is still acceptable. Wednesday is late. Don't send at 23:00 from the after-party. Don't send a sequence email and a personal email the same morning. If they asked you to wait until after a launch, wait. One bump at day 7 if you promised a resource and they didn't confirm receipt. Then stop. Networking threads are not pipelines.

What this CEO actually cares about

They don't owe you a meeting because you shook hands. Human. If you dump a calendar link as the first follow-up, you taught them the chat was a pretext. Protect their reputation in a small industry. SaaS CEOs talk at dinners. A greedy follow-up becomes a story. Continue the topic. Offer an optional next step. Then leave. They context-switch constantly. A two-sentence continuation beats a bio. Don't call them a decision maker. Don't write like they're a Fortune 500 process. Peer to peer, not vendor to target.

How SaaS changes the note

SaaS events are a harvest of badge scans that become sequences by morning. CEOs notice. Your follow-up has to use the shared moment or you wasted the introduction. Activation, seats, SSO, and who still owns implementation are the hallway topics that actually linger. If you pitch immediately, you retroactively made the chat feel extractive. A hot listing in software is a launch week. Don't email into their GA morning because you swapped cards at dinner. Write like a peer who was in the same room. Vague loved your journey language is how you get filed with the other 200 scans. Specific is the only filter that works.

Customization tips

Name the event and the room, not a generic great to meet you.
If you promised an intro, make the intro, don't tease it.
Don't BCC a sales pod on a hallway follow-up.
If they were with a cofounder, don't email both unless you met both.
Send from your real name, not a sequence subdomain.

Common mistakes

Dumping a calendar link as the first follow-up.
Restarting your pitch like a stranger.
Opening with it's been great connecting with no topic.
CCing an AE who wasn't in the hallway.

How this scenario compares

Dimension	For this template
Best send window	Within 48 hours of the event
Ideal length	Under 90 words, quote plus optional ask
Primary ask	Resource delivered, continuation optional
Unlike a cold email	You have a shared moment. Use it.
Unlike an introduction email	You already met. Don't re-send your bio.

Questions people ask before they hit send

Within two days. After that you're a vague name from a badge. Mention where you met and the topic, send anything you promised, and keep the ask optional. If they wanted a pitch, they would have asked. Hallway chats are not demo requests.

Related templates

Want a custom draft instead? Try the email generator. Word count on this page: 963.