How should we follow up after a conference?

Assign ownership before the event, not after, and split it by tier: name who sends the personal notes for real conversations within twenty-four hours, and who manages the lighter nurture tracks for the other two tiers. Without that assignment made in advance, the highest-value personal notes usually sit in a rep's inbox behind the stack of ordinary work that piled up while they were traveling, and the fastest-decaying tier gets the slowest response.

What do we do with a badge-scan list?

Clean it before segmenting it, not after. A scanner export is a machine's reading of a badge at a busy moment, so duplicate entries, truncated names, and misrecognized company fields are exactly what a cleaning pass exists to catch, and a merge-field error in the first line of an email is a fast way to make a stranger permanently ignore your company. A basic pass for duplicates and obviously broken fields is worth doing before any send, badge-scan tier or otherwise.

Why does event pipeline die two weeks later?

Alongside the attendee's own attention fading, an internal cause runs in parallel and gets less attention: the rep who owns follow-up has also returned to an existing pipeline and quota pressure, so any event lead that is not already hot loses an internal competition for that rep's time, not just the external one for the attendee's. A lead that looked promising on the show floor can die in a queue on your own side before the attendee's interest ever gets the chance to.

How to follow up after an event

Guide · Market Growth · 5 min read · last verified 2026-07-29

Reviewed before publication Editorial board Independent commercial review

In shortEvent follow-up has a failure mode that is structural rather than lazy, and it is the one this piece can do something about: a list of a few hundred badge scans gets handled as though it were a few hu

Event follow-up has a failure mode that is structural rather than lazy, and it is the one this piece can do something about: a list of a few hundred badge scans gets handled as though it were a few hundred qualified leads, so the same three-email sequence goes to someone who spent twenty minutes with your VP of product and to someone who let a scanner beep at their badge on the way to the next booth. The fix starts with segmenting by what happened in the conversation, matching the follow-up to that tier, and moving fast — because whatever attention the event bought starts fading the moment the attendee's flight lands back home, and "we'll follow up next week" rarely survives contact with a full inbox.

Segment by what actually happened, not by who scanned a badge

Three tiers cover most of what a booth or a sponsored session produces. A real conversation — someone who stopped, engaged with a specific problem, and left you with something concrete they said or asked for — deserves a personal, specific follow-up referencing that exact conversation. A booth drive-by — someone who browsed, asked a general question, maybe grabbed a demo — deserves a warmer, more general nurture that assumes interest but not urgency. A badge scan with no conversation at all deserves the lightest touch of the three: an opt-in invitation to hear more, not a sales sequence. Collapsing these three into one list because they all came from the same event wastes the spend that got them in the room, and it does so in both directions at once: the real conversation gets a template it will not answer, and the scanner beep gets a sequence it never asked for. A virtual event produces a different raw list — registrations, minutes attended, questions typed into a chat box — but the same three-way split survives the translation; in-person vs virtual events for B2B is the choice that comes before this one.

The window closes faster than the follow-up usually ships

Attention from an event has a short half-life: the conversation was vivid on the show floor and gets less vivid every day the attendee is back in a normal inbox, buried under whatever piled up while they were away. There is no reliable public curve for exactly how fast that decay runs — treat any specific number here as someone's guess, not a fact — but the direction is not in question, and it argues for speed over polish. That is why a same-day or next-day note works even when it is plain text and slightly rough: it arrives while the recipient can still place who you are, which is the one thing a later sequence cannot design its way back to. Two weeks of cleaning, segmentation, and three approvals buys polish the reader was never going to notice, at the price of the only advantage the note had. Ship the personal note fast, even by hand, and let the more built-out nurture for the lighter tiers follow after.

What to send: the thing you promised, not the deck

The artifact list itself is not event-specific. Send the sourced answer to the question they asked, one public page that carries the claim, a matching story if you genuinely have one, and never the all-purpose deck — that is the discipline in what to send a prospect after the first call, and none of it changes because the conversation happened at a booth.

What does change is the promise. It was spoken, not written, in a crowded aisle, to someone who had eleven other conversations that afternoon: "I'll send you the comparison sheet for your stack," or "let me get you that case study from a company your size." A week later that person may not be able to reconstruct which vendor said it, so the note has to rebuild the context before it delivers anything — where you met, what they described, what you offered — and then deliver that exact thing, because a generic nurture track arriving in its place reads as a broken commitment rather than an alternative content offer. How to write outreach that cites your research is the harder version of the same discipline, where the specific hook has to be found; here the buyer already handed it over and the only failure available is forgetting.

Badge scan is not consent to a sequence

It's worth stating directly, because the sponsorship contract's lead-list terms invite the opposite reading: a badge scan is a mechanical event, not a conversation and not consent to an ongoing sequence, whatever those terms technically permit. Treating every scan as a qualified opt-in burns the list twice — once when the recipient marks the first email as spam because they do not remember agreeing to anything, and again, more expensively, the next time your company is at the same event and their inbox already associates your name with an unwanted sequence. A lighter, clearly optional invitation respects what actually happened at the booth and protects the list for the next event.

What this protects: the spend decision made weeks earlier

The sponsorship decision rests on a premise: sponsorship buys presence, and something specific has to convert that presence into attention. Follow-up is where that conversion either happens or does not — a sponsorship budget can be entirely justified on paper and still produce nothing if the follow-up treats a real conversation and a badge scan identically. Whoever owns the follow-up discipline is, whether they realize it or not, the person responsible for whether the sponsorship spend survives the next budget review.

Measuring whether it worked

The same discipline that makes follow-up worth doing — segment first, do not treat every contact as identical, check what happened rather than assume — is worth applying to whether the event mattered at all. Pipeline sourced from the real-conversation tier is worth tracking separately from pipeline that merely touched a badge-scan email, because collapsing them back together at the reporting stage repeats the exact mistake the follow-up itself was built to avoid. A different, slower signal worth watching, if the event produced any published material — a session recap, a quoted comment, a case study that came out of a conversation there — is whether that material starts showing up as a source when an assistant answers a question in your category. Magrios is built to track that specific kind of change on a fixed schedule, separate from and slower than the pipeline number, but real when it appears.