The first show a team exhibits at gets a lot of attention. By the sixth show of the year, the process has drifted. One rep tags leads in a spreadsheet, another keeps notes on paper, the regional office rents the organizer's scanner, and the marketing manager tries to compare three shows that were captured three different ways. The data exists, but none of it lines up.
This playbook is for teams that exhibit at several events a year. It covers what to standardize, how to run each show as its own campaign, how to bring temporary staff up to speed, how to manage seats, and how to compare results fairly.
To run one lead process across many events, standardize the parts that make results comparable: the qualification fields and their options, the categories, the capture app, follow-up timing and the report format. Create a campaign for each show so every contact is grouped under it automatically. Pre-set defaults so temporary staff record leads the same way as your core team, and review each show with the same few figures, such as qualified leads and cost per qualified lead, before deciding whether to return.
| What drifts | What happens | Fix |
|---|---|---|
| Qualification fields | Each team uses different words for the same thing; leads cannot be filtered across shows | One org-wide set of fields with fixed options |
| Capture method | Some shows end with badge files, others with photos of cards | One app for badges, cards and QR codes at every show |
| Event tagging | Contacts from different shows mix in one list | A campaign per event, created before the show |
| Follow-up ownership | Leads from smaller shows wait for weeks | One follow-up rule set and named owners per show |
| Reporting | Each show is reported in a different format | One report template with the same core figures |
None of these is a technology problem on its own. They are process decisions that a tool can then enforce.
Agree four or five fields for the whole organization, each with fixed options. A typical set:
| Field | Options |
|---|---|
| Interest | Browsing, interested, wants a quote, wants a demo |
| Quantity or size | Tiers that fit your product, such as 100, 500, 1,000, 5,000 units |
| Timeline | This quarter, next quarter, this year, later |
| Role | Decision maker, influencer, user |
| Next step | Quote, demo, sample, call, none |
Allow one event-specific field when it matters, for example "Saw the new model" at the show where you launch it. Do not let each show invent its own core fields. Our lead qualification guide explains how to turn questions into fields.
Categories group contacts by what they are to you: customer, prospect, distributor, partner, supplier, press. Keep the list short and identical everywhere.
The capture method is where drift starts. At one show the organizer rents a scanner, at the next the badges carry a plain QR code, and at the third half the visitors hand over business cards. If each show uses whatever the organizer offers, every show ends with a different file in a different format.
A capture app your team owns removes that variation:
Some shows still need the organizer's system, for example when badge codes are encrypted so only the licensed app can read them. In that case, rent the minimum for badge scans, capture everything else in your own app, and import the organizer's lead file after the show and resolve duplicates.
Create a campaign for each event before the show. Every contact captured there is then grouped and tagged under it, and the report builds itself as reps capture. A useful campaign setup includes:
Large shows bring people who do not usually do events: engineers, regional sales staff, distributor partners, local hires. They have one morning to learn the process. Make it hard to get wrong:
Run the same script at every show. Core team members can deliver it, which keeps the standard in the hands of the people who use it every day.
Teams that exhibit often need more people at some shows than others. With per-event rentals, every show starts with a new order. With a seat-based app, you plan seats for the year.
On Habsy Platform, seats are prepaid. You can add users at any time and pay right away on a pro-rata basis, remove users, freeze a user (billing continues while frozen), or move a seat to another user. In practice, that means a seat used by a sales rep at a spring show can move to an engineer for an autumn show, without a new contract.
The same buyer often visits your booth at several shows in a year. If each visit creates a new record, the second rep does not know about the first conversation, and the buyer has to explain themselves again.
Habsy Platform shows contact history across events: the same person met at several shows appears as one contact, with the history from each event. That helps in three ways:
Habsy Platform produces one post-event report for each event campaign. Side-by-side comparison of events in the platform is planned, not available yet. Until then, compare shows with a simple table built from each report:
| Figure | Show A | Show B | Show C |
|---|---|---|---|
| Contacts captured | |||
| Unique companies | |||
| Qualified leads | |||
| Senior contacts reached (Director and above) | |||
| Total cost | |||
| Cost per qualified lead | |||
| Opportunities at 90 days |
Fill it in within a week of each show for the first five rows, then add opportunities from your CRM at 90 days. Our trade show ROI guide has the formulas.
A building materials company exhibits at four shows in a year with the same process. After the third show, the table shows:
| Figure | Spring regional show | National trade fair | Overseas expo |
|---|---|---|---|
| Contacts captured | 180 | 410 | 260 |
| Qualified leads | 42 | 61 | 58 |
| Total cost | 9,000 | 31,000 | 24,000 |
| Cost per qualified lead | 214 | 508 | 414 |
The national fair produced the most contacts, but the regional show produced qualified leads at less than half the cost. Because every show used the same qualification fields, the team could see that the difference came from the audience, not from how reps tagged leads. They kept the national fair for visibility, cut its booth size, and added a second regional show.
Leadership rarely needs every report. Once a quarter, send one page:
Process health matters as much as results. A show with weak results and half-empty qualification fields says more about the booth team than about the event. Fix the process before you judge the show.
| Mistake | Effect | Fix |
|---|---|---|
| Each region designs its own fields | Leads cannot be filtered or compared across shows | One org-wide field set, owned by one person |
| Campaigns created after the show | Contacts from several shows mix together | Create the campaign before build-up day |
| Judging shows on contact counts | Big, busy shows always look best | Compare qualified leads and cost per qualified lead |
| Temporary staff skip qualification | Their contacts cannot be prioritized | Pre-set defaults and a first-hour check |
| Rebooking by habit | Weak shows stay in the calendar for years | A decision date for every show, using the comparison table |
At the start of the budget year, put every show in one plan:
| Column | What to record |
|---|---|
| Show and dates | From the TradeShowIntel calendar and the event page |
| Role | Exhibit, visit to evaluate, or skip |
| Owner | Who runs the show |
| Goal | Qualified leads, meetings or orders |
| Budget | By the same cost categories every time |
| Key deadlines | Booking, advance orders, shipping |
| Decision date | When you decide whether to rebook |
Use TradeShowIntel event pages to check visitor profiles and exhibitor categories when adding new shows, and visit a show before committing a booth when you are unsure. Our guide to choosing which trade shows to exhibit at has a scorecard.
Habsy Platform is built for exactly this: the same process at every show, with managers seeing it as it happens.
Habsy Platform is charged separately from Habsy Plus, on a custom quote, with no per-event or per-lead fees, and includes a product demo and onboarding support. See Habsy for teams or Habsy Platform.
Before each show:
During the show:
After the show:
A team that exhibits at many events wins by doing the same thing well every time. Standardize the fields, the app and the report, run each show as its own campaign, and make temporary staff productive in ten minutes. Then the comparison table, not opinion, decides which shows earn a place in next year's calendar.