Post-Event Follow-Up Plan: The First Two Weeks

Follow-up is where event value is decided

A conference produces conversations. It does not produce pipeline. Pipeline comes from what happens in the days after, and that is exactly when most teams are at their least organised: travelling home, catching up on a week of missed work, and trying to remember who said what at stand four on Tuesday afternoon.

The pattern is familiar. Everyone agrees follow-up is important. A lead list is exported. Someone sends a generic "Great to meet you at the show" email to everyone on it a week later. A handful reply. The rest of the value quietly evaporates.

A good follow-up plan is mostly decided before the event, and executed on a clock after it.

Prepare before the event ends

Three decisions made before the event make the follow-up dramatically easier:

Decide what "follow-up" means for each kind of contact. A prospect who had a scheduled thirty-minute meeting with a specialist is different from someone who had their badge scanned in passing. Define two or three tiers in advance, each with its own follow-up action and owner.

Capture notes during the event, not after. Every meeting should end with a two-minute record: what was discussed, what the contact wants, the agreed next step, and who owns it. Written within minutes it is accurate. Reconstructed a week later it is fiction. If an AI tool tidies those notes into a summary, check what it wrote before it reaches a customer.

Pre-write the follow-up templates. Draft them before the event, one per tier, with clear placeholders for the personal detail. Writing templates on the flight home produces worse templates.

Programmes that capture meeting data at the point of scheduling find this far easier, because much of the record already exists by the time the meeting ends.

The first 48 hours

Speed matters most for your highest-value contacts, the ones who had real conversations and expressed specific interest.

Within two working days of the event:

• Send personal follow-ups to every scheduled meeting. Reference the specific conversation, restate the agreed next step, and propose times for it. If the next step was "send the security documentation", send it.
• Book the next meeting, not just the next email. "Let me know if you would like to talk further" puts the work on them. "Would Tuesday or Thursday next week work for the architecture review we discussed?" moves the conversation forward. See when to propose times and when to send a link.
• Handle anything promised on site. Documents, introductions, pricing, answers to open questions. A promise kept quickly is one of the most persuasive things a vendor can do.
• Hand over cleanly. If the event contact will be managed by someone who was not at the event, the handoff needs the same care as any SDR-to-AE transfer.

Days three to seven

Now work through the wider list:

• Follow up with contacts from shorter conversations, using the tiered templates with at least one genuinely personal line. If there is nothing personal to say, the contact probably belongs in a lighter-touch tier.
• Reach out to target accounts you did not meet. You now have a legitimate reason: "We were at the event and did not manage to connect — would a short call be useful?" This works better than cold outreach because of the shared context.
• Debrief internally. An hour with everyone who attended: what topics came up repeatedly, which objections recurred, what competitors were saying, what should change next time. Write it down. An assistant can surface the recurring themes across everyone's meeting notes, as long as you check its counts by hand.

The second week

By the second week, the event is fading from your contacts' memories. The goal now is converting interest into scheduled next steps, and making sure nothing has been dropped.

• Chase unanswered high-value follow-ups once, with something new — a relevant resource, an answer to a question they raised, a specific proposed time. Not "just checking in".
• Check every agreed next step has an owner and a date. Any that do not should be assigned or explicitly closed.
• Move lower-tier contacts into your normal nurture process, with a note of the event context attached so future outreach can reference it.

Follow-up messages that get replies

The follow-ups that work share a few traits:

• They reference something specific from the conversation, proving it was remembered.
• They lead with the contact's interest, not your product. "You mentioned your team double-booked two executive meetings at your last event" is a better opening than "CallShark is a scheduling platform that…".
• They contain one clear next step, with a proposed time or a direct way to book.
• They are short. Four or five sentences is usually enough. Anyone who wants more will ask.
• They come from the person the contact met, not from a marketing address.

A simple structure: one line referencing the conversation, one line restating what they cared about, one line on the next step with a proposed time, and a sign-off. If an assistant drafts it, run the checks for AI-drafted follow-up before it goes.

What to measure

Track follow-up as a process, not only as an outcome:

• Time to first follow-up, by tier.
• Share of scheduled meetings with a follow-up sent within 48 hours.
• Share of follow-ups that produced a booked next meeting.
• Next steps agreed at the event versus next steps actually completed.

That last gap is the most telling. If agreed next steps frequently do not happen, the problem is not your event strategy — it is the plan for the fortnight after it.

CallShark is being built to capture meeting notes and next steps at the event itself, so follow-up starts from a complete record rather than memory. The product is temporarily down.