What if I didn't promise them anything at the event?

Send a short continuation of the seats or freeze story, plus one tiny useful artifact if you have it. Don't invent a promise. Don't attach a deck to create a reason. A clean thank-you that quotes the hallway is enough, especially around the vendor freeze and the hallway chat. Optional next steps can wait until they ask.

Should I connect on LinkedIn instead of email?

You can do both if they use LinkedIn, but don't paste the pitch into the connection note, especially around the vendor freeze and the hallway chat. Two sentences and the event is plenty. Put the exhibit in email if that's where packets live. Connection notes that read like sequences get ignored by officers who already live in portals.

What if they said ping me after the freeze?

Send a one-line thanks now so they have your address, then actually wait until the freeze ends. Write the morning after with the artifact, not a recap how fun the event was, especially around the vendor freeze and the hallway chat. Believing their calendar is the whole relationship at this stage, especially around the vendor freeze and the hallway chat.

How do I close if they never reply to the hallway note?

You don't need a breakup novel. One later note with a new observation is allowed. After that, stop. Event follow-ups aren't deals. Your reputation in that procurement circuit matters more than this thread. Adult silence after a good note is still a good note, especially around the vendor freeze and the hallway chat.

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

SaaS · Procurement Officer · After Networking

Follow-Up Email After Networking With a SaaS Procurement Officer

Q: Can I mention paid seats in a networking follow-up?

Only if they asked how to start. Otherwise send the promised page and leave paid seats out, especially around the vendor freeze and the hallway chat. Networking especially around the vendor freeze and the hallway chat. Warmth is follow-through on the hallway, not a commercial pivot they didn't invite between coffees, especially around the vendor freeze and the hallway chat.

A follow-up after networking with a SaaS procurement officer should continue the hallway, not start a funnel. Write within two days. Remind them where you met and the unused-license or portal story you both lingered on. Send anything you promised. Keep the ask optional. If you pitch immediately, you retroactively made the chat feel extractive.

Copy-ready template

Subject

The vendor-freeze chat from [Event Name]

Body

Hello [First Name],

Good to meet you at [Event Name] by [Where: the procurement roundtable / the coffee line]. I kept thinking about what you said on unused licenses after a sandbox looks live and billing still owns the start date.

Here's the one-page exhibit I promised. No need to reply unless you want me to open a thinner seat file for [Company Name]. Happy to leave it with you.

[Your Name]
[Your Title]

Why this follow-up works

The subject is the room you shared, so you aren't a stranger with a sequence, especially around the vendor freeze and the hallway chat.
You quote their story, which is the only reason the email exists, especially around the vendor freeze and the hallway chat.
You send the promised artifact first, which is basic hallway honesty, especially around the vendor freeze and the hallway chat.
The ask is optional, so the chat doesn't become a trap, especially around the vendor freeze and the hallway chat.
Warmth without a bio dump keeps the human tone you earned in person, especially around the vendor freeze and the hallway chat.

When should I send this to a SaaS Procurement Officer?

Within two days. After that you're a vague name from a badge. Same night can work if you promised a link and can send it without typos, especially around the vendor freeze and the hallway chat. Don't send from the rideshare with a messy note. A clean next-morning email is warmer. If the event sat next to a freeze, wait until they are back at the portal, not still in sessions. After this note, do not drip. If they don't reply, you can leave one archive-or-later a couple of weeks later with a new observation, not a recap of the snacks, especially around the vendor freeze and the hallway chat. Networking follow-ups that become cadences are how people start dodging badges, especially around the vendor freeze and the hallway chat.

What this Procurement Officer actually cares about

This officer is already behind on portal files of their own. Your networking email is competing with actual redlines. The first two lines have to prove you were the person from the hallway, not another logo, especially around the vendor freeze and the hallway chat. They'll spend six seconds deciding if you are homework, especially around the vendor freeze and the hallway chat. Don't CC a colleague who wasn't there. Don't add the business owner. Don't convert a coffee into a discovery call. Policy is still the scarce thing. A promised one-pager about a thinner seat start is useful. A vision paragraph is not. Be the person who followed through. Then leave them alone unless they reply.

How SaaS changes the note

SaaS procurement events are full of people who will email by Thursday with a partnership story. Your job is to be the rare note that continues a real sentence about unused licenses, a billing exhibit that never landed, or a freeze that ate last year's trial. If you write like a cold email with extra steps, you wasted the badge, especially around the vendor freeze and the hallway chat. Quiet after networking is allowed. They don't owe you a funnel. They might still want the one-pager you promised. Send it. Then stop. Warmth is leaving the next step optional. Roundtables and coffee lines are not qualified leads, especially around the vendor freeze and the hallway chat. They are conversations. Treat them that way and you might get a file opened later. Treat them like a sequence and you become a story they tell legal about vendors. Seats and billing can live in the note if that's what you talked about. Your origin story cannot.

Customization tips

Name the event and the physical moment: roundtable, dinner, booth, coffee line, especially around the vendor freeze and the hallway chat.
If you promised nothing, send a tiny useful note, not a pitch deck, especially around the vendor freeze and the hallway chat.
Don't connect on LinkedIn with the full pitch pasted into the note, especially around the vendor freeze and the hallway chat.
If they asked for a packet, send it labeled, not a Calendly.
Write like a person who was there, not like SDR copy about loving the energy, especially around the vendor freeze and the hallway chat.

Common mistakes

Dumping a calendar link as the first follow-up.
Re-introducing your whole bio as if you never met.
Pasting SDR copy about the energy in the room.
Forgetting the unused-license or freeze story you both lingered on.

How this scenario compares

Dimension	For this template
Best send window	Within 24 to 48 hours, after they are back at the portal
Ideal length	Under 90 words, promised artifact first
Primary ask	Optional thinner file or nothing but the exhibit
Unlike a cold email	You have a shared moment. Use it. Don't write like a stranger.
Unlike an introduction email	You already met. Don't restart the 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, especially around the vendor freeze and the hallway chat. If they wanted a pitch, they would have asked. Procurement roundtables especially need a human note, not a sequence.

Related templates

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