How to capture leads at a trade fair without renting a badge scanner

A stand produces contacts in bursts and loses them slowly. The losses do not happen during the conversation, they happen in the week afterwards, when a stack of cards waits for someone to type it up and nobody does.

Removing the retyping is most of the fix, and it costs nothing to set up.

Before the fair

Open a campaign for the event and give it the event's name, not your own. It keeps those three days separate from your everyday contacts, which is what lets you export them on their own afterwards.

Write the campaign address to a blank tag. Any NTAG works, and leaving it unlocked means the same card serves the next fair.

Print the QR code at about two centimetres and put it where a phone can reach it without anyone bending over: on the stand panel at standing height, on the counter, on the back of whatever you hand out. Taps fail for ordinary reasons and the camera never does.

Write the follow-up email before the doors open, while you still have time to write it properly. Afterwards you will not.

At the stand

The gesture is the part people get wrong. Do not hand your phone to the visitor, and do not read their details out loud while typing them. Turn the card or the panel towards them and let them use their own phone. It takes them twenty seconds, it produces no transcription error, and it puts the consent checkbox in front of the person it concerns.

Then write the note immediately, before the next conversation starts. Three words is enough: what they asked for, what they objected to, when they said to call. On the Monday that note is the only thing that distinguishes one line from the forty around it, and no memory survives a fair intact.

The Monday after

Export the campaign to XLSX and sort by your notes, not by capture time. Time tells you nothing; the note tells you who was buying.

Send the follow-up in the first three days, while the stand is still a shared reference. The window matters more than the wording: a good email in week three arrives after the person has forgotten which of forty stands you were.

The two limits worth knowing

Connectivity. The form is a web page, so it needs the visitor's phone to be online. Fair wifi is routinely saturated and mobile data in an exhibition hall can be poor. Nothing works around that entirely, but a QR code scanned into a browser that retries is more forgiving than a tap into a loading page.

Badge holders. A scanner reads any badge automatically, including from people who would not have stopped to type. A form requires twenty seconds of willingness. That filters out passers-by, which is a loss if you count contacts and a gain if you count conversations.

When several people share the stand

Two setups work, and they answer different questions.

One card each gives every person their own page and their own register, which suits a stand where each rep follows their own conversations afterwards. Nobody has to sort out who spoke to whom, because the answer is already in the data.

One shared card gives the stand a single register, which suits a team that qualifies together on the Monday and distributes afterwards. It also means one person has to own the export, and that should be decided before the fair rather than during the argument about it.

A team pass covers the second case, priced by how many people share the card. Either way, write the same address to several tags so a queue never forms around one piece of plastic.

The rush and the quiet hour

They call for different gestures, and a stand alternates between them all day.

In a rush, the tag does the work: turn it towards the person, let them fill the form, write three words, move on. Twenty seconds each, and nobody waits.

In a quiet hour, capture last. Have the conversation, understand what they came for, and take the details at the end when you already know what to write in the note. A contact captured in the first ten seconds of a conversation carries no context, and context is the thing you will be missing on Monday.

The trade fair use case covers the same ground from the product side.