From Event Conversation to Qualified Opportunity

Separate the request from the opportunity

The follow-up was fast, personalised — and wrong.

Effective event follow-up preserves the meaning of a conversation through every handoff. It keeps a request for information separate from an agreement to evaluate a supplier, and it keeps the promised work visible until someone checks that it actually happened.

The retailer in this example has stated a problem and requested a resource. They have also mentioned when they expect to review their current setup — useful facts, but they leave the real questions open. Nobody knows the cause of the delayed updates, whether replacing the integration is necessary, or whether any budget or procurement decision exists. Reviewing a setup next month is not the same as buying a system next month.

The first job is specific: send the promised checklist. A commercial conversation can follow if both sides find it useful, but it should never be written into the record as though it already happened. For an exhibitor, that discipline protects a relationship already worth the stand fee; for a retailer’s own team, it means the answers and next steps that come back to the business are ones people can actually act on.

Agree the categories before the event: a resource request, a technical question, an introduction, an agreed future discussion and a declined follow-up each need a different next step. Staff should also know that leaving a field unknown beats filling it with a plausible guess — a badge scan with no note should stay a badge scan, not become an invented opportunity.

Capture a four-field conversation card

A useful note has to survive a handoff to a colleague who was not in the room. Four fields capture the substance without turning a booth conversation into a sales interrogation:

• Current situation — what the attendee is actually doing today, in their own context (e.g. reviewing an existing inventory integration next month).
• Stated problem — the issue in their own words, with cause and commercial impact marked unconfirmed if they are.
• Promised material — the exact resource offered, not a generic “send info.”
• Agreed next action — who does what, by when, and whether any further conversation was actually agreed.

Attach the card to the event, contact, organisation, date and staff member, and keep the original note alongside any cleaned-up summary. Resolve an actual deadline to a calendar date and time zone — “next Tuesday” becomes ambiguous the moment someone processes it a week later.

Keep interpretation separate from fact. A colleague’s hunch that the problem fits your service well is a hypothesis worth testing, not evidence that the retailer wants to buy. An impressive job title does not establish who owns this particular decision, either — if the attendee mentions a colleague who owns the review, record that statement, but do not start contacting them until the next step has actually been agreed.

Give every commitment an owner and a completion rule

A follow-up task records work to do. It does not prove the work got done.

Before a commitment gets a completion rule, it needs the right identity behind it. The same attendee can appear in an event system, a colleague’s notes and an existing customer record — three records describing one person, or two similar names describing two different businesses. Use the organisation’s documented matching method rather than merging on a shared surname or company domain, and check whether the retailer is already a customer or mid-evaluation elsewhere before treating the new conversation as a fresh prospect. Two colleagues from the same buying group can raise two genuinely different requests; they should not collapse into one, and nor should two notes of the same promise multiply into two tasks.

Each commitment needs an owner who can see the request, find the recipient, and know what completion actually looks like — plus a resource reference, a current state (awaiting review, ready, fulfilled, blocked) and, critically, a completion rule that matches what was promised. Sending a checklist is complete when the checked file reaches the verified recipient through the agreed channel, with the send record kept. An introduction is a different promise entirely.

A drafted email is not an introduction. A saved draft is not a sent message.

Keep drafting, sending and fulfilment visible as separate states, and reconcile exceptions rather than assuming silence means success. If a task shows complete but no action evidence exists anywhere, that is a reason to investigate, not to report the promise as kept. When a retailer replies, books a meeting through another channel, or declines further contact, update the plan and check anything still queued that could now contradict it — recovery should fix the live conversation, not quietly delete the history to make a dashboard look clean.

Count commitments, meetings and opportunities in their own units

Contacts, conversations, commitments, meetings and opportunities are not interchangeable, and treating them as one number hides exactly the gap you need to see.

Take an illustrative cohort: thirty contacts from thirty organisations, each with one conversation. Twenty-two receive one commitment and eight receive two — thirty-eight commitments, not thirty-eight opportunities. At the review date, thirty of those are due: twenty-four fulfilled on time, four late, two still overdue. On-time fulfilment is 24 ÷ 30 = 80%, and the four late completions do not disappear just because the work eventually got done.

Commercial progress is a separate count. Of the thirty contacts, twelve agree to a follow-up discussion; ten of those happen, and four lead to four distinct accepted opportunities. Against a fictional €6,000 event cost, that maps to four very different costs per outcome:

These are different outcomes from the same spend, not benchmarks or a return on investment — no sale has been supplied, so the example cannot say whether the event paid back. What it can do is separate a weak-relevance problem from an unfulfilled-promise problem, which is the actual debrief worth having.

Before your next event, pick one promise your team commonly makes and follow it all the way to fulfilment:

• Agree the follow-up categories before the event — resource request, technical question, introduction, agreed discussion, unknown intent.
• Capture the four-field card while the conversation is still fresh.
• Resolve identity and ownership, and give each distinct promise one accountable owner.
• Match every commitment to a completion rule that fits what was actually promised.
• Verify fulfilment with real evidence, not a task status.
• Report commitments, meetings and opportunities as separate counts, with the cohort and cost basis stated.