Following up after an exec dinner
Your executive dinners can hold the most valuable conversations of a trade show, yet your team rarely captures anything from them into your CRM.
Why do executive dinners need their own follow-up process?
Because they combine the best conversations of the show with the worst record of them. Your hosts don’t have a scanner at the table, and they don’t type notes between courses. Your executives do the talking, and they pass the conversation on by word of mouth, if at all.
It’s the clearest case of the argument in the FieldXM thesis: the work that produces your in-person GTM revenue happens between teams, in rooms your CRM never sees.
Budgets are moving toward satellite events too. One marketing leader runs a satellite event at about half of her company’s shows, and at those shows her pre-show goal is filling the room. Operators at 3 companies independently described an add-on event, the night before or after a major conference, as worth more than the booth on its own.
“You just have to hope and pray that like the people who are at the booth recognize that’s a VIP situation. Not ideal.”
A director of events at an enterprise software company running about 200 events a year, on what happens when a target-account contact reaches the booth
If that’s true at the booth, where you have a scanner, it’s even more true at a table for 12.
How should a dinner relate to the parent show?
Run it as a child event. Give the dinner its own invite list, owners, capture, and follow-up, and roll all of it up to the parent show. Most teams run the dinner as a line item in the show’s budget and a tab in the show’s spreadsheet. That’s how its conversations end up counting toward nothing.
| Parent show | Satellite event | |
|---|---|---|
| Purpose | Presence, coverage of target accounts, volume of conversations | Depth with the 10 to 20 accounts that matter most |
| List | The attendee list if you can get one; your own account list if not | A curated invite list that draws on the parent’s target accounts |
| Capture path | Scans, meetings, walk-ups | A host’s debrief per guest, the same night |
| Owner | Events lead, with reps covering accounts | A named host per table, an inviter per account |
| Success measure | Coverage, conversations, meetings, sourced and influenced pipeline | Target accounts in the seats, agreed next steps, completed follow-up |
| Rollup | The show’s total | Inside the show’s total, and reported on its own |
Treating the dinner as a child keeps 2 things true at once. Its conversations count toward the show that made the room possible. And it reports on its own, so you can see whether 14 seats produced more pipeline than 400 scans. That’s why FieldXM’s event tracker keeps your dinners and other satellite events under their parent show.
Why is the invite list the highest-value pre-show moment?
Because the room is the product. Seats are scarce, and who sat down decides everything afterward. The invite list is the most valuable hour of pre-show work, and usually one person does it, reading a spreadsheet and searching names one at a time.
- Start from the parent show’s target accounts, which you have already matched against the CRM: open opportunities, strategic prospects, at-risk customers, partners. The dinner is for the accounts the show exists to reach.
- Enrich and tier before you invite. Title, seniority, and fit decide who gets a seat. If you do it after the invitations go out, the table fills with whoever said yes fastest.
- Assign an inviter per account. Pick the rep who owns the account, or an executive for the strategic ones. An invitation from the person who’ll sit beside them means more than one from a stranger.
- Invite early. The invitation competes with every other dinner in the city that night, and your reps work a list in time only when they trust it.
- Track invitation state per account as coverage: invited, accepted, declined, attended. The coverage gap for a dinner is a target account your team hasn’t invited.
- Plan the seats. Decide who from your side sits with whom, and give each pairing a purpose. The seating chart is the dinner’s account plan.
“They didn’t have strong confidence in the target account list… it took them weeks… then everybody already has plans for that night.”
A director of performance marketing at a B2B software company around $25M ARR, on why reps in a prior role started outreach too late
What should the host capture at the dinner?
Get one line per guest from the host who sat with them, the same night, before the flight home wipes it out.
| Field | What goes in it |
|---|---|
| Guest and account | Who, and which account they resolve to in the CRM |
| Host | Who from your side sat with them |
| What mattered to them | The 1 or 2 things they raised: a pain, a project, a timeline |
| Interest | What they reacted to, if anything |
| Next step | What you both agreed to, in the guest’s words if possible |
| Owner and urgency | Who follows up, and how fast |
The debrief takes each host 5 minutes. Skip it, and a CRO-level conversation with a strategic prospect never reaches your CRM. That happened at one company: the rep who followed up couldn’t find the person in the system.
What does the follow-up process look like in the days after?
Give every guest an owner, a next step, and a personal follow-up within days, and let whoever paid for the room see where each guest stands.
- The morning after: put every guest in the record with an owner and a next step. A Slack thread doesn’t count.
- Within a few days: the host who sat with each guest sends a personal note about the conversation they had. A marketing sequence tells a dinner guest the dinner was a lead-generation exercise.
- Within the week: schedule the next step: a meeting, an introduction, a proposal, a site visit.
- Visible state: mark each guest worked, unworked, or converted. Your events leader sees the unworked list without asking for it.
- Attribution at capture: tag each guest’s interaction to the dinner, the dinner to the parent show, and each resulting opportunity as sourced or influenced.
- After 2 weeks: check the dinner’s attempt rate. For 12 guests it should be 100 percent. If it’s lower, you can name the guest and the owner behind each gap.
The dinner is the cleanest test of whether your follow-up is a process or a policy. 12 people, 12 owners, 12 next steps. If your team can’t close that loop, the 400 scans at the booth never had a chance.
Go deeper
- The FieldXM thesis: why the in-person channel runs on spreadsheets, heroics, and hope.
- The coverage gap: target accounts with no owner and no invitation.
- Attempt rate: the follow-up metric a 12-seat dinner should pass at 100 percent.
Part of
- The Last Unmanaged Workflow in B2B RevenueRead the longer piece this post builds on.
More from the field guide
- A pre-show target list your reps will actually useBuild a pre-show target account list your reps will use. Source it, match it to your CRM, tier it and show why, assign owners, and find coverage gaps.
- Badge scan leads with no context: how to fix themSee what your reps should capture beyond the badge scan, where that context goes missing, and the 72-hour check that shows whether you kept it.
- How to get sales to follow up on event leadsGive each event lead a named owner and a clock, put unworked leads in front of your sales manager, and catch the leads reps work outside the process.