Networking follow-up after an event
How to turn a busy networking night into clear follow-ups without sounding generic or waiting until the moment has gone cold.
The value of a networking event is almost never the room. It is what you do in the days after.
Most people leave with good intentions and a messy pile of inputs: cards, LinkedIn requests, half-remembered conversations, and a calendar that fills before they write a single message.
Do the triage while the night is still warm
Before you open a blank message, sort the people:
- Send now. You promised something specific, or the conversation was clearly mutual.
- Send this week. Useful, but not urgent.
- Leave it. Polite hellos do not all need a campaign.
If everyone gets the same "great to meet you" note, the message is noise. Triage is the difference between follow-up and spam.
Write from the conversation, not from a template
A good follow-up usually needs three lines:
- Where you met.
- One concrete detail from the talk.
- One clear next step.
Examples of a next step: a short intro, a link you mentioned, a fifteen-minute call, or a simple "happy to continue this".
If you cannot name a detail from the conversation, you are not ready to write yet. Go back to the capture first.
Timing that still feels human
Same night is fine when the conversation was strong and the message is short. Next day is the common sweet spot. After three or four days the thread is still recoverable, but you need a sharper reason to write.
What usually fails is waiting until the end of the week and then blasting ten people with the same paragraph.
Keep score of what happened
A follow-up is not finished when you hit send. Note whether they replied, whether a meeting landed, and what the person became for you: client, friend, partner, referral, or still open.
That record is how a night turns into a network instead of a feeling.
Where Orbit fits
Orbit keeps the event, the people, and the conversation in one place, then helps you draft the next message from what you captured. You still choose who gets a message and you still send it.
For the product path, see events and follow-ups and Orbit Assistant.
