The dinner starts at the booth.
I’ve written run-of-show documents for customer dinners during conference week, and the part that goes sideways is almost never the food. It’s the stretch between the expo hall closing and the first glass of wine, when your guests are tired, their phones are at eight percent, and the restaurant you booked is a fifteen-minute walk that somebody’s calendar invite described as “right around the corner.”
The guides that rank for planning a conference customer dinner are solid on the front half of the job, and I’d say most of the same things. Build the invite list from the accounts you actually want in the room, and mix customers with prospects so the customers do some of the selling for you. Keep the table small enough for one conversation. Book a private room early, because every vendor at the show wants the same handful of restaurants on the same Tuesday. Send your own team a briefing with guest bios, make a seating chart, skip the product demo, follow up within a couple of days. All good advice! Then they jump straight from “send the invite” to “the dinner,” as if forty people teleport from a convention center into a private dining room.
Write the Run of Show Backward from the Reservation
The restaurant is your immovable cue. A kitchen that has forty covers plated for 7:30 will not hold them while a CISO finishes a conversation at your booth, so I do what I do for every run of show and write the evening from the bottom up. Seated at 7:30 means everyone walking in the door by 7:15. That means leaving the venue by 6:50, which means the booth team needs to be told at 6:30 which guests are theirs to collect.
Then I go walk it myself, at the same hour, on a show day if I can, in the shoes I’ll actually be wearing.
At RSA Conference, the vendor floor alone took 25 minutes to cross, and that was before anybody stepped outside into a few thousand other people also heading to dinner. A walk the map app calls eight minutes is a different walk at 6:45 p.m. during a 40,000-person conference. I time it, and I note where the walk gets confusing, because a guest who gets lost on the way to your dinner arrives a little annoyed with you, even if they’re too polite to say so.
Every Guest Gets an Escort
This is my strongest opinion about conference dinners, and the cheapest one to act on. Each guest gets one named person from your team who is responsible for physically getting them from the show floor to their chair.
Escort means their name sits next to the guest’s name in the briefing doc, and the two of them have agreed on a meeting spot by lunchtime. Not “the lobby.” Every conference center has several. Usually it’s the rep who owns the account. Sometimes it’s whoever invited them. The rep gets fifteen uninterrupted minutes with their customer on the walk over, which reps love, and the guest never has to wonder whether they’re going to the right place. A shared rideshare works too, if the distance calls for it.
It also tells you, by 6:55, exactly who isn’t coming. The escort texts me. I text the restaurant. Nobody is staring at an empty chair at 7:40 wondering whether to wait.
Plan for the Empty Chairs and the Surprise Guest
Conference week makes people unreliable in the nicest possible way, because a better meeting comes up or their boss grabs them for a drink with somebody important. Some of your confirmed guests will not show. Plan the seating chart so that losing any one of them doesn’t leave a VP stranded between two of your own employees with nothing to talk about but the weather. I seat in small clusters, where each guest has at least one person beside them they’d want to meet, and I keep a short list of nearby colleagues who can slide into a seat on short notice.
The opposite happens too. A customer arrives with a colleague you didn’t invite, and the right answer is a warm hello and a chair, every time. I tell the restaurant in advance that we’ll flex by a couple of covers in either direction, and I agree on what that costs before the night instead of during it.
Seating is the part I think about longest. I wrote in my Field Note on concierge work about the partner who ends up spending forty unplanned minutes with your CRO because somebody seated them together on purpose. That somebody was paying attention earlier in the day. The seating chart for a conference dinner should get rewritten at least once after the show floor opens, because by mid-afternoon your team knows things about who wants to meet whom that nobody knew when the invitations went out.
The VP Who Landed at Five
Somebody at your table flew in that afternoon, came straight to the venue, and has not eaten since a bag of pretzels over Nevada. I make sure there is food on the table within a few minutes of guests sitting down, bread or something small, before any welcome remarks.
Dietary notes go to the restaurant two days out, by name. The allergy file I keep on guests is the same one that tells me who takes oat milk, and for a dinner it gets printed and handed to the captain. Asking the person with the shellfish allergy to explain it again in front of eleven colleagues is a small thing. It’s also the kind of small thing they’ll remember about your company.
Toasts
One, short, from the most senior person on your side, after the first course arrives.
The Notes Go Out Before Breakfast
The guides say follow up within 48 hours, and that’s fine for the thank-you email. My deadline is earlier. Every person from our team at that table sends me two or three lines about each guest they talked to before they go to sleep, or at the latest over coffee the next morning. Something the guest actually said, like an evaluation starting next quarter or a teammate they want us to meet.
It’s the same discipline I teach the booth team before a trade show, where one sentence typed after every badge scan beats a perfect memory that has faded by Friday. At Arxan we got every RSA lead to a rep within 24 hours and tracked a 30-60-90 day follow-up cadence every week. A guest who gave you three hours of their evening deserves at least that much rigor. Day two of a conference is a blur. By day four, nobody remembers which customer mentioned the renewal between the main course and dessert, unless somebody wrote it down on day one.
The Takeaway
A customer dinner during conference week gets measured by what happens at the table, but whether it works gets decided in the forty minutes before anybody sits down, when every guest either has someone walking beside them or is alone on a crowded sidewalk checking the address again. Plan the walk.
If your team has a big conference on the calendar and a dinner that needs to land with the right people in the right chairs, let’s talk. I’ll already have timed the walk.