The speaker follow-up that gets answered is written during the talk.

The Monday after the keynote

A conference speaker opens their inbox the Monday after the event and finds a stack of messages that could have come from the same person. Great session. Really enjoyed your talk. Your point on procurement was so valuable. Would love to connect.

Each one is sincere. Not one of them tells the speaker who the sender is, which part landed, or why a reply would be worth five minutes of a crowded week.

So they get a polite one-liner. Or nothing.

And the sender files it under "speakers are busy," when the actual problem was sitting in their own drafts folder the whole time.

The Room Test

Every speaker runs the same quiet check on the follow-ups that arrive after a talk. Could this email have been written by someone who skipped the session and read the abstract?

If yes, it reads as noise. If the email holds something only an attentive person in that room could know (a claim from minute twenty-two that cut against the slide before it, a number the speaker said out loud but never put on screen, the question that would have come next in Q&A if time hadn't run out), it reads as a person. That's the Room Test.

Passing it comes down to one thing: whether you wrote anything down while the speaker was still talking. You can't recover in the inbox what you didn't keep in the room.

A speaker follow-up is a capture problem that surfaces late, dressed up as a copywriting problem.

How do you follow up with a conference speaker?

The standard advice is reasonable. Reference the talk in the subject line. Keep it short. Compliment something specific. Offer value. Make one clear ask.

But "compliment something specific" assumes you have something specific. The advice treats specificity as a writing choice, when it's really a memory you either kept or lost. By the time most people sit down to write, they've sat through more sessions, a lunch, a dozen hallway conversations and a flight. The talk has blurred into the conference.

Try it on the last session you attended. Most people can recall the title, the speaker's company and the general topic. Which is exactly what ends up in the email.

Templates make this worse. They hand you a confident first sentence that hides an empty middle, and the speaker reads straight past the opener to the empty part.

What a speaker can tell from three kinds of follow-up

Memory research going back to Hermann Ebbinghaus's experiments in the 1880s shows recall of new, unrehearsed material dropping steeply within the first day before it levels off. A forty-minute talk is about as unrehearsed as information gets. You hear each point once, at the speaker's pace, with no way to rewind.

There's a second problem. The generation effect, documented by Slamecka and Graf in 1978, finds people remember material they produced themselves better than material they only took in. In a hallway conversation you're at least talking. In a session you're on the receiving end the entire time, unless you write. Met's earlier piece on the 72-hour memory cliff traced the decay for conversations; a talk you sat through quietly has even less to hold onto.

The result shows up in the email, and a speaker can read it in seconds.

Two attendees, one session

Picture two operations leads in the same breakout on supplier onboarding. Halfway through, the speaker mentions in passing that their team cut onboarding time after moving legal review ahead of the technical integration, and that the change started with a vendor complaint. Then Q&A runs long and ends early.

The first attendee nods along and writes nothing. The second types three lines on their phone: legal before integration, vendor complaint started it, does this hold for vendors on custom contracts?

Two days later both send a follow-up. The first says they enjoyed the session, the onboarding section resonated, and they'd love to connect. The second names the sequencing change, mentions their own team runs it in the opposite order, and asks the custom-contract question in one line.

The speaker can answer the second email from their phone in a minute. The first gives them nothing to answer at all.

The second attendee's edge came from forty seconds of typing during the talk, two days before the email existed.

What to capture while the speaker is still talking

If the Room Test holds, the follow-up gets decided in the session. Three things are enough, and they don't need to be tidy:

The claim that surprised you. The question you didn't get to ask. The line that mapped onto a problem you're working on right now.

Add roughly when in the talk it came up, so you can find it in the recording later if there is one. That's the whole capture. Ugly notes typed in the moment beat clean notes written at the hotel.

And if you captured none of it? Skip the speaker follow-up for now. Watch the recording, find the moment that mattered, then write. A topic-level email spends your one shot on a message the speaker can't tell apart from the rest of the pile.

Where Met fits

Met is built around the capture moment: who, plus what was said, logged together while you're still in the room. That's the same idea whether the person is someone you met at the coffee line or the speaker you watched from row twelve.

Event Mode keeps capture open for the length of the event, so the speaker's name and three lines from the middle of their talk go in between sessions, before the next keynote overwrites them. When you sit down to write, the follow-up draft starts from what you noted at the time. Your contacts stay in your own iCloud, and there are no ads in the way.

The email that gets answered on Thursday was mostly written during the talk on Tuesday. The inbox part is just typing it up.