Trade show follow-up: turn contacts into a practical next step
Editorial illustration
GURI Journal · Published 31 October 2026
The difficult part of trade show follow-up is rarely the first thank-you message. It is remembering what was discussed, delivering the right response and keeping responsibility clear as the conversation moves from the stand to the rest of the company. A badge scan records an encounter. It does not explain what the other person needs or why they should reply.
GURI treats follow-up as the continuation of a specific conversation. The first task is to preserve its meaning. Only then does it make sense to decide which contacts deserve immediate attention, which need more information and which are simply useful acquaintances for the future. Sending the same sequence to everyone obscures those differences.
Reconstruct the conversation before sending anything
Bring stand notes, appointment records and contact details into one working record. For each company, identify the person, their role, the product discussed, the business problem and any promise made by either side. If an important detail is missing, mark it as a question. A colleague's impression that a buyer has budget is not the same as a statement from that buyer.
Merge duplicates without losing context. A visitor may have spoken with a salesperson on the first day and an engineer on the second. Those conversations can contain complementary information, or contradictory expectations that need to be resolved. One contact owner should coordinate the next response while bringing the relevant specialists into the discussion.
Keep the record proportionate. Use necessary business information and the communication channel agreed at the event, with applicable privacy and messaging requirements considered for the circumstances. Make requests to stop contact visible to the team. Otherwise, a well-intended handover can restart a conversation the recipient has already declined.
Prioritise by the work required
A useful priority combines commercial relevance with a reason to act now. A promised quotation date, an upcoming technical review or a sample needed for a product decision provides that reason. A prestigious company name does not, by itself, establish urgency. Smaller buyers can have a much clearer project than large organisations gathering general information.
Separate contacts that are ready for a defined action from those that require qualification. For example, a request for a sample may still need clarification of the application, specification and evaluation method. Treating it as a near-complete sale creates pressure to ship something before either side knows what it is meant to prove.
Some contacts will not fit the current offer. Record the reason respectfully: territory, product requirement, scale or timing. This helps the team avoid repeating an unsuitable proposal and may reveal a recurring limitation in the company's market approach. It is more informative than leaving every scanned badge in an open pipeline indefinitely.
Deliver the promise that made the meeting useful
Start the first response with the topic discussed and the material you agreed to provide. If the buyer asked about dimensions, service coverage or packaging, answer that question before attaching a general company presentation. A short, relevant response shows that the conversation was understood and makes it easier for the recipient to circulate the information internally.
Check versions before sending. Specifications, sample descriptions and quotations should refer to the same product configuration. Explain assumptions that materially affect the proposal. A preliminary price based on an estimated quantity should not look like a final commitment for every order size and destination.
Consider a hypothetical equipment enquiry. The visitor wants a machine for a particular process, but the team still needs information about raw material and operating conditions. The useful follow-up asks for those details and explains how they affect the configuration. A standard price list may answer a question nobody has yet asked and leave the actual engineering problem untouched.
If the promised response is delayed, communicate before the deadline passes where possible. State what is ready, what still requires checking and when a meaningful update can be given. Do not invent a replacement date simply to make the email look complete. A partial answer with a clear limitation is often easier to work with than silence followed by an unexplained delay.
Propose a next step that resolves something
“Let us know if you are interested” gives the recipient an undefined task. A more useful proposal identifies the decision that a call, document review or sample evaluation would support. It might be confirming a specification, establishing a workable order size or deciding whether a pilot is justified.
Keep the request proportionate to the relationship. Someone who briefly explored your product range may not be ready for a detailed commercial negotiation. Offer a smaller clarification that helps establish relevance. Someone with an active project may need direct access to a technical specialist rather than another introductory presentation.
Agree the timing where possible. There is no universal number of messages that makes every follow-up effective. If a reply does not arrive, check whether the address, channel and question are appropriate, then ask whether the discussion remains relevant. Silence is neither acceptance nor reliable evidence that the product has been rejected.
Track progress beyond outgoing emails
The AUMA guidance on trade fair lead management emphasises defining qualification criteria before the event and processing contacts in a structured way afterwards. Your own stages should reflect the work required to reach a commercial decision. Examples include missing information received, technical meeting agreed, sample under evaluation or proposal awaiting a named review.
Record dependencies on both sides. “Waiting for the customer” may conceal an internal calculation that has not been completed. Split these into separate tasks, with an owner and a review date. This makes it possible to see whether a conversation is genuinely waiting on a buyer or has stalled inside your own organisation.
Be careful when reporting value. An enquiry, an estimate of possible business and an accepted order are different outcomes. If the team records an opportunity amount, preserve its assumptions and stage. Do not present all potential project values as revenue generated by the exhibition.
Use the review to improve the next participation
Review both successful continuations and stalled conversations. Did the event bring the intended buyers? Did the product answer their needs? Were promises realistic, and did the company fulfil them? These questions distinguish an audience problem from an execution problem and prevent a vague judgement about whether the show “worked”.
Some useful outcomes arrive later than the first reporting meeting. Keep a sensible review point aligned with the buying cycle, while closing contacts that no longer justify active effort. The aim is a record that explains what the exhibition enabled, what the company did next and which decisions still need evidence. That is a stronger basis for future spending than a count of messages sent.