The follow-up that lands was written in the room, not at your desk.
Conference follow-ups don't fail at the keyboard. They fail three days earlier, when the one detail that would have earned a reply has already left your memory.
Friday, and eighty strangers on your desk
It's Friday afternoon and the lanyard is still coiled on the hotel dresser. Eighty cards sit under a rubber band. You remember maybe six of the faces cleanly. Somewhere in that stack is the head of partnerships who said the specific thing about their Q3 roadmap that you were going to build the entire email around, and you cannot for the life of you remember which card is hers, or what the thing was.
So you do what the stack forces you to do. You send eighty versions of "Great meeting you at the show, would love to continue the conversation." Two reply. Both of them were already going to.
That is the real failure rate of conference follow-up, and it has almost nothing to do with the words you chose on Friday.
The reply is won in the room
Here is the uncomfortable part. The quality of your follow-up was decided before you opened your laptop. It was decided in the ninety seconds you spent talking to that person, by whether you captured the one detail that proves you were actually listening.
Call it the room-to-reply gap. The message is only the delivery vehicle. What makes it land is specificity, and specificity has a shelf life measured in hours. The exact phrase they used, the constraint they're stuck on, the name of the system they're migrating off, the reason they said they can't buy yet. That is the payload. By Friday it has decayed into "nice person, works in fintech, seemed interested."
You can't write your way back to a detail you didn't keep.
A follow-up lands because it proves you were in that conversation, not because you were fast.
Why the template-and-timing advice misses
Most follow-up advice optimizes the two things that matter least. "Send within 24 hours." "Use this five-line framework." "Open with a mutual-interest line." All of it treats the follow-up as a composition problem to be solved at the keyboard.
It isn't. A perfectly timed, perfectly structured email that opens with "it was great connecting about the future of the industry" tells the recipient exactly one thing: you don't remember them. The framework was fine. The tank was empty.
The tooling makes this worse, not better. Business-card scanners like CamCard and ABBYY are built to digitize the card, which is the single least useful artifact from any conversation. A card gives you a title and an email. It gives you nothing about what was said. CRMs like Salesforce, HubSpot, and Pipedrive start every record at "lead," a database row with fields for deal stage and next action but no obvious home for the sentence that would actually earn a reply. Both categories optimize the stage after the detail is already gone.
What people are actually searching for
The search demand tells on the whole category. The volume doesn't cluster around "follow-up template" nearly as much as around "follow up that gets a reply," "after a conference so it lands," and "what to do with conference contacts." People aren't asking how to word an email. They already know how to word an email. They're asking why the emails they word don't work.
That gap is the tell. The market has plenty of templates and plenty of scanners. What it doesn't have is a way to walk out of a room still holding the reason each conversation mattered. Everyone is solving Friday. The problem was Tuesday.
Fast and empty loses to slow and specific
The 24-hour rule is real, but a same-day note that says nothing beats nothing. A Wednesday note that names the exact thing you discussed beats both. Speed only starts helping once the content is worth reading.
The same follow-up, twice
Picture the head of partnerships from the opening. Same conversation, two versions of the aftermath.
Version one: you scanned her card into an app. On Friday you have her name, title, company, and a mental note that she was "sharp, seemed like a fit." You send the great-to-meet-you email. It reads like the other seventy-nine because it is the other seventy-nine.
Version two: while you were still standing there, you recorded that she's migrating off a legacy system in Q3, that onboarding is the part keeping her up at night, and that she doesn't sign anything she hasn't seen survive a live demo. On Friday you don't write to eighty people. You write to twelve, and each of those twelve gets an email that could only have been written to them.
The difference between the two versions is not writing skill. It's what you were holding when you sat down.
The default send
Written from the room
"Great to meet you at the show! Would love to stay in touch."
"You mentioned the Q3 migration off the legacy system is the thing keeping you up. The onboarding gap you described is exactly what we closed for a team your size last spring."
"Let's find time to explore ways we might work together."
"You said you don't sign until you've watched it survive a live demo day. Here's a two-minute clip of precisely that."
Sent to all 80, identical.
Sent to the 12 that matter, each one different.
Illustrative. Both columns follow the same event; only the capture step differs.
What changes when you believe this
If the reply is won in the room, your whole prep list inverts. The night before the conference, you stop drafting a follow-up template and start deciding how you'll capture. The important skill is no longer writing a good email under time pressure on Friday. It's leaving each conversation with the one line that makes Friday easy.
The follow-up stops being a chore you dread and batch-process badly. It becomes a short, obvious set of notes you're transcribing rather than inventing. You send fewer of them. You send them to the right people. And the ones you send read like they came from someone who was there, because they did.
Capture the room, not the card
This is the exact seam Met is built for. Event Mode keeps the room recorded while you keep talking: the person, the face, the thread of what was actually said, held together as one contact instead of a card in one app and a scribbled note in another. When Friday comes, the specific detail is still there, so the follow-up writes itself from real context instead of a template.
The capture is deliberately quiet. No ads in the flow, no notification spam, no interruptions while you're mid-conversation trying to be present. Storage is iCloud-only, so the contacts you collect stay yours and don't land on someone else's server to be resold. The point isn't to make you a faster emailer. It's to make sure that by the time you email, you still have something worth saying.
What we're watching next
The interesting open question is where capture and triage meet. Holding the context is step one. Deciding which twelve of the eighty are worth a real follow-up, and in what order, is a separate discipline, and the two are starting to converge in how operators actually work a room. We'll come back to that scoring problem in a future piece. For now, the move is simpler than the advice industry makes it sound: keep the detail while it's still in the air.
Keep the detail while it's still in the air. Get Met.
Met is built for the capture moment, not the Friday cleanup. Event Mode keeps the conversation in the room recorded, the name, the face, the specific thread, so your follow-up starts from what was actually said. iCloud-only storage means the contacts you collect stay yours, not on someone else's server.
