The follow-up window is 72 hours, and two clocks decide it.
Most advice optimizes one clock. Conference follow-up runs on two, and 72 hours is where they cross.
By Thursday, the names have already gone abstract
Tuesday's conference ended at five. By Thursday morning the stack of cards on the desk has gone quiet. You remember the good conversations as a feeling now, not a transcript. The woman from the logistics startup who said something sharp about procurement timelines. The guy who wanted an intro. The three people you genuinely liked and meant to write. The specifics that made each of them worth a follow-up have started to blur into a single warm haze. Forty-eight hours did that, and you have not even reached the weekend.
The two-clock window
Most follow-up advice treats timing as a single dial. Sooner is better, full stop. The number that actually matters sits at the intersection of two separate clocks, both running from the second the conversation ends. One clock is your memory of the context: the detail that lets you write a note only you could have written. The other is their memory that you exist and are worth a reply. Seventy-two hours is roughly where both clocks still read in your favor. It is also the last point where they do. No neuroscience paper crowns the number; it comes from somewhere else, the place where those two decay curves overlap while both are still useful.
The famous follow-up statistic is the wrong one to apply here
The sales internet has one celebrated rule about follow-up speed, and it is the wrong one for a hallway. It comes from inbound web leads, where someone fills a form with active intent and a competitor is one tab away, so the odds of qualifying that lead collapse if you wait past the first hour. A conference handshake is not that. There was no form, no live buying intent, no tab. Racing to send a five-minute follow-up to someone you met at a booth reads as automation, and they know it. The opposite camp makes the inverse error: be thoughtful, take your time, a polished note a week later is fine. That advice ignores your own context rot. The handshake camp protects their attention. The thoughtful camp protects your craft. Neither protects the one resource that actually expires fastest, which is the specific detail in your own head.
What memory research and response data actually say
Two bodies of evidence sit under the seventy-two hour number. The first is memory. Hermann Ebbinghaus measured retention decay in 1885 and found the now-familiar shape: a steep early drop, then a slow flattening. Modern consolidation research adds the mechanism. The brain moves a fresh memory from fragile short-term storage toward durable storage over hours and days, and sleep does much of that work. The retrievable detail, the part that makes a follow-up specific, is the most fragile piece, and it goes first. The second body is response behavior. Research on inbound web leads, the Lead Response Management Study by James Oldroyd, found the odds of qualifying a lead drop sharply once you wait past the first hour. Conference contacts burn slower than web leads, but the direction holds: warmth decays from the moment you part. 48% of sales teams never attempt a follow-up after an initial interaction. ([source](https://www.invespcro.com/blog/sale-follow-ups/)).
Retention by elapsed time, Ebbinghaus savings-method curve (1885). The classic shape: steep early loss, then a slow flatten. Verify exact figures before publish.
What you lose first
What decays first isn't the fact that you met someone. It's the retrievable detail that made the meeting worth a follow-up. By Thursday you still know you talked to her. You no longer know what she said.
Why 24 hours and 7 days both fail the same pile
Picture the real constraint: 200 cards from a three-day event, and you are flying home Wednesday into a backlog. Run it at 24 hours. You cannot write 200 follow-ups that each carry a real detail in a single travel day, so most of the pile never gets written at all. The fast deadline does not produce fast follow-ups; it produces a small handful sent and a large majority abandoned. Now run it at day seven. You finally have the hours to reach everyone. But the specific is gone, so the note degrades to "great meeting you at the conference, let's stay in touch." Technically a follow-up. Functionally a form letter, and it gets read as one. Seventy-two hours is the only window wide enough to triage the pile and still narrow enough that the details are pullable. It is the spot where you can write the note that names the procurement comment, because you can still hear her saying it. Our earlier piece on the four-question triage covers how to rank the pile once you accept the window.
The fix is upstream of the deadline
If the two-clock window is right, the usual advice is aimed at the wrong stage. Telling people to follow up faster assumes the bottleneck is sending speed. It almost never is. The bottleneck is whether the context survives to hour seventy-two in a form you can actually use. By Thursday, willpower cannot reconstruct a detail your brain already filed and flattened. So the move is not to race the clock on the back end. It is to protect the context on the front end, at hour zero, while you are still standing in the room and the detail is still sharp. Everything downstream gets easier once the specific is captured instead of remembered. The 72-hour window stops being a scramble and becomes a comfortable runway.
Capture the detail before the detail expires
This is the quiet case for capturing context in the moment rather than trusting Thursday's memory. Met's Event Mode keeps the room captured while you keep talking: scan the card, drop the one line that matters ("sharp on procurement timelines, wants the logistics intro"), and move to the next conversation. The note you send on day two then writes itself, because the specific is sitting there waiting instead of dissolving in your head. Storage is iCloud-only, so the contacts stay yours and not on someone else's server. No ads in the flow, nothing sold. The product does one unglamorous thing well: it makes hour zero permanent so hour seventy-two still has something real to work with.
What we are tracking next
The open question is whether the window compresses at scale. A 40-card sales trip and a 400-card mega-conference may not share the same operative number, because the volume side of the first clock changes faster than the memory side. We are watching whether high-density events push the practical deadline inside 72 hours purely on triage math, and whether capturing context at hour zero is what buys it back.
Capture the detail while it is still in the room. Get Met.
Met was built around the hour-zero end of this window. Scan the card and capture the one detail that matters while you are still in the room, so the note you send on day two still has the specific in it. Storage is iCloud-only, the contacts stay yours, and nothing in the flow is sold or surfaced as an ad.
