Every booth has a night before.
For three straight years I ran Arxan Technologies’ presence at RSA Conference, on a show floor with forty thousand attendees and a vendor hall that takes 25 minutes to cross, with our booth wedged between Palo Alto Networks and CrowdStrike. Both of them spent more than we did. Every year. What we had was the people in our booth, and the briefing I gave them before doors opened, and that briefing is what this Field Note is about.
The booth staff training guides that rank for this cover the basics well. Give everyone a role and cross-train them so lunch breaks don’t leave a hole. Keep your arms uncrossed and your phone in your pocket. Ask about the visitor’s problem before you start in on the product, and qualify people instead of chatting all afternoon with whoever wanted a pen. I agree with every word of that (the pen people are lovely, and they are not your pipeline). What none of them talk about is the twenty seconds after a good conversation ends, when the scanner beeps and the visitor walks off toward the next aisle. I think that’s where more trade show budget quietly leaks out than anywhere else on the floor.
The Aisle Is a Sidewalk
I learned to read foot traffic behind the counter of my own sunglasses shop in San Francisco, years before anyone handed me a lead scanner. A stranger decides in their first three steps whether to stop. At RSA you get about 0.6 seconds of that decision, and the booth can only carry part of it. We built Arxan’s to read cleanly from 30 feet, with one anchor message and no clutter. The rest of the work is whoever is standing at the front edge of the carpet.
I tell the team where to stand. Front corners, angled toward the aisle, and never in a cluster behind the demo table catching up on last night’s dinner. A booth with your own people huddled in the middle of it looks like a private party, and nobody walking past wants to crash one.
Ninety Seconds, No Card
At Arxan we staffed the booth with people who could hold a 90-second technical conversation without reading from a card. That bar is higher than it sounds. The buyers on that floor are mostly CISOs and security architects, with a healthy sprinkling of channel partners, and they can hear a memorized paragraph from two booths away.
Most guides tell you to rehearse a 30-second pitch, and you should. I care more about the second question, the one a security architect asks after nodding politely through your first answer, because that’s the moment the visitor finds out whether they’re talking to someone who knows the product or someone who got handed a logo shirt on Sunday night. Anyone who can’t answer it needs to know exactly who in the booth can, and how to walk the visitor over with an introduction instead of a shrug.
The Twenty Seconds After the Scan
This is the part of my briefing that runs longest.
A badge scan is a maybe. On its own it gives you a name, a title and a company. In Year Two at Arxan, leadership asked whether I could prove the booth produced revenue, and a pile of maybes was never going to answer that. We tagged every scan in the CRM as RSA-sourced, got every lead to a rep within 24 hours, and tracked a 30-60-90 day follow-up cadence every single week. That spreadsheet is what bought us Year Three.
The spreadsheet has a blind spot, though. The rep who picks up a lead on Tuesday has no idea what was said in the aisle on Monday, unless the person in the booth wrote it down, right then, before the next visitor walked up and wiped it out of their head.
My rule for the booth team is one sentence in the notes field after every real conversation. Something the human actually said. A renewal with their current vendor coming up in the spring. A question they asked twice. The boss who makes the call and stayed home this year. Their kid starting college in the fall, if it came up and they lit up talking about it. “Wants pricing” doesn’t count, because everyone wants pricing. It’s the same habit I use for guest notes on the concierge side of events, pointed at pipeline instead of oat milk.
The best follow-up email starts with something the buyer said at the booth. The worst one starts with “Great meeting you at RSA!” and a calendar link, and lands in the inbox of someone who only stopped for the swag. Give your staff a quick tag for those scans, too. The rep working down the list on Wednesday will thank you, and so will whoever has to defend the trade show budget in January.
One Person Owns the Broken Stuff
Something will go wrong. I once watched a breakout speaker walk on stage with no screen because a sales rep had forgotten the TV, and I ended up on a very fast Target run. On a show floor the problems are smaller and constant. A scanner dies at 10 a.m., or the demo laptop picks the busiest hour of the day to install an update.
In the briefing I name one person who handles anything broken, and it’s usually me. Everybody else stays at the front edge of the carpet and keeps talking to the person in front of them. A booth where three staffers are crouched over a dead monitor is a booth with nobody in the aisle.
Snacks
Feed them before they ask, and rotate lunch in shifts, because a hungry rep pitches like a hostage.
How the Briefing Ends
I end the same way every time. Who’s here that we most want to see, and who on the team knows them. Where the notes go. Where I’ll be. Then I tell everyone that the scanner count at the end of the day is the number I care about least, and I watch the new folks look relieved.
The Takeaway
The booth is the part everybody photographs. The briefing, and whatever your staff type into the notes field between conversations, decide whether the show earns its spot on next year’s calendar. I did this on the most crowded floor in cybersecurity, three years in a row, next to neighbors with much bigger budgets, and Arxan’s pipeline contribution from RSA grew every one of those years. If your team has a show coming up and you’d like someone who cares about the notes field as much as the carpet, let’s talk. I’ll bring snacks for the booth.