Follow-Up Email After a Networking Event

Only to the people you sat with. Within 24 hours. Two to five sentences, one thing they said, no new ask. Don't wait on a reply.

• Subject: following up from [event], or good to meet you at [event]
• Two to five sentences. Name the event. Quote or closely paraphrase one thing they said.
• If you promised an intro, a link, or a call, put that on its own line so you can't drop it. Don't invent a new ask.

People who send these already have the test: "It's important to add something specific about the conversation you had with them. Otherwise it comes off like a form letter." They assume you still have that something. After one talk, you do.

Because you didn't have one talk. You had eight. By the hotel, they have smeared, and the card only has a name. The template cannot fill its own blank.

If you had one conversation, write the note tonight from memory. You will remember what they said. You might not remember the name: "I would remember the meetings, the things that got discussed, but somehow can never remember the names." That's a different embarrassment, and it is not this email.

A conference is the other scale. Software people have been saying this for years: after the event they can't map faces to names, and they can't remember most of what they discussed. The incumbent fix is analog. Walk away, jot one line on the card, email it Monday morning. You skip the jot because the next person is already talking.

So you get what every ranking page already publishes: "I really appreciated your advice on [specific point]." Publisher samples invent the specific. That's how you know the blank is the work. Pastok is not a better paragraph. It is how the bracket gets a real sentence in it, eight times, before the 24 hours is up.

Capture each sit-down. Add Pastok to the watch face, tap before that talk starts, ask once, keep talking. The phone stays in your pocket.

The emails worth sending came from talks that left the floor. A handshake isn't one of them. The conversation that moved to a table is. So is 20 minutes at a booth, and the coffee you booked for the next morning. Treat that coffee as a meeting, not as more networking.

Add Pastok to the Apple Watch face as a complication. One tap starts capture. Ask first, then leave it running until you stand up. It never starts on its own. Once it's on, it keeps going so you're not taking notes in front of them. A meeting bot doesn't apply, because nothing joins the room. Capture also starts on iPhone if that's what's in your hand. The watch is the one that doesn't put a phone on the table.

A loud booth can mix speakers. Treat names as a hint, and read the draft before you send. A conversation you never started a session for is gone. Don't reconstruct it.

A Skill, written in Chat. It reads the captures, writes one draft per person, and stops. You send the mail.

This is the part a voice memo app does not do. A Custom Skill is a standing instruction against what you captured, defined in Chat in ordinary language. Run it on demand, put it on a schedule for 8pm, or let it fire when Pastok spots a first meeting. Detection is best effort, not a promise. Output is Markdown or a PDF. It does not send, book, or update a CRM.

Paste this so each sit-down becomes a draft while you're still in the building:

When I finish a conversation with someone I haven't spoken to before, draft a follow-up. Open with one sentence of thanks that names where we met. The body must quote or closely paraphrase one specific thing they said, their words, not a topic summary. If I promised an intro, a link, or a call, list it on its own line. No new ask unless I made one out loud. Under 120 words. If the capture has no specific, say so. Markdown. Do not invent. Do not send.

For the whole day, 8pm:

From today's event captures, sit-down conversations first, then any dumps after I walked away. One section each: name, where we met, the one specific in their words, anything I promised, a draft under 120 words. Order by who I owe something to first. If there is no specific, say so. Markdown. Do not invent. Do not send.

What you'll get for one sit-down, if the capture has a specific:

Subject: Following up from [event] Hi — Good to sit down with you at [event] yesterday. You said the last integration died because nobody owned the handoff once the contract was signed. You offered to make an intro to whoever owns that on your side. I'll wait on you. Hope the rest of the week is quieter than the floor.

If a line doesn't match what you remember, you always have the transcript. Open it on the web app and double-check before you send.

Pastok can suggest lines grounded in what was said. It should not invent a plausible detail, because that's the form letter again. Editing eight notes is a different night from reconstructing eight talks.

Don't record a floor of strangers. Walk away and talk to yourself for thirty seconds, or skip them. Months later, search Pastok by meaning, not the badge.

Most cards aren't sit-downs. Don't put a microphone on that floor. If one handshake turned into something you might actually write, step away and dump the name, the one thing, anything you promised into Pastok. Same wrist tap. Nobody else is on that recording. Otherwise skip it. A wrong detail is worse than a short plain note, and a note to someone you only waved at is worse than silence.

Months later, write on the same thread so they don't have to place you. If the name is gone, search Pastok by meaning: the booth, the product they were stuck on, the trip. You don't need the name they had on the badge.