Writing · Marketing Ops · Aug 15, 2026 · 6 min

Running a trade-show program from one page

A show is five things at once: a plan, a guest list, a booth kit, a lead table and a follow-up campaign. In most teams those five live in five different places. Here is the arrangement I use instead: one page per show, the same five sections every time, and a layer underneath that carries from one show to the next.

1page per show, everything reachable from it
5sections, identical on every show

This template has carried AI4 2025 and Shoptalk 2025, and AI4 2026 is being planned on it now. Here is how the page works.

The seams are where a show falls apart

Running a booth is five jobs at once. Someone writes the run of show. Someone owns the invite list and the dinner shortlist. Someone builds the film, the kiosk and the pitch. Someone works the floor and captures leads. Someone runs the follow-up two days later.

Each of those jobs has a natural home, and they are all different homes. The plan sits in a doc. The lists sit in a sheet. The assets sit in a drive folder. The leads sit in the CRM. The follow-up sits in the email tool. Every one of those is a reasonable choice on its own, and together they produce the same result every time: two weeks after the show, the only person who can answer a question about it is the person who was there.

All five tools stayed. What I added is one page sitting in front of them.

One page per show, and the page is the index

Every show gets a workspace with its own address. Opening it reaches everything built for that show: the plan, the contact lists, the asset kit, the lead table, the follow-up. Almost nothing lives on the page itself. The page is the thing that knows where the rest of it is.

That distinction matters more than it sounds. A folder holds files. An index answers questions. The question a trade-show page has to answer is always a version of the same one: where is the thing I need right now, and is it the current version.

The same five sections, every show

Each workspace carries the same five headings in the same order, whether the show is next week or was last quarter.

Plan holds the run of show, day by day. Contacts holds who was invited, who confirmed, and who turned up. Assets holds the film, the kiosk build and the pitch playbook. Results holds what the booth produced. Outreach holds what happens once everyone has flown home.

Fixing the grammar this way costs a little flexibility and buys back two things. Nobody redesigns the container before each show, so setup is close to free. And anyone who has seen one show page can navigate every other one, including shows they had nothing to do with.

Per showPlan · Contacts · Assets · Results · Outreach
Rebuilt each timethe parts specific to this city, this booth, this week
Universalbooth film · demo kiosk · pitch playbook
Carried forwardwritten once, adjusted per show rather than rebuilt
Two layers. The show-specific layer is retired after the show. The universal layer is the reason the next show costs less than the last one.

What carries between shows lives outside the show

The booth film, the demo kiosk and the pitch playbook were each written for a specific event. They are also the three things most likely to be needed again, so they sit in their own section rather than inside any one show.

The practical effect is that preparing the fourth show starts from the third instead of starting from nothing. The pitch playbook gets a diff. The film gets a new end card. The kiosk gets a new form target. Each show costs less than the one before it, which is the only version of trade-show economics that improves over time.

A link is a handoff

Because every artifact has its own address, delegating a piece of work is one message with one link in it. There is no explaining where the file lives or which copy is current.

The same property is what lets an agent do the work. An agent cannot open a drive folder and use judgment about which of four similarly named documents is live. It can take an address, read what is there, and act. Once the plan, the lists and the trackers are addressable, the routine parts of running a show become things I hand off in a sentence: draft the outreach sequence from the plan, reconcile the badge list against the invite list, flag anyone on the shortlist who never arrived.

That stays out of reach while the material is scattered across five tools with five permission models. Addressability is the prerequisite, and it is the part most people skip.

Three states, because most of the work is deciding

Shows sit in one of three states: upcoming, planned, past. Upcoming means dates are fixed and the work is live. Past means the follow-up window is open or has closed. Planned is the interesting one. It holds shows we have discussed with no dates agreed.

Keeping that state visible turns a vague conversation into a queue. A show sitting in planned for two months without dates is a decision nobody has made, and the board says so without anyone having to raise it in a meeting.

AI4 2026upcoming · dates fixed, work live
Money20/20planned · discussed, no dates agreed
AI4 2025past · follow-up window open
Shoptalk 2025past · closed, in the record
Three states, and planned is the one that earns its keep: a show sitting there for two months without dates is a decision nobody has made, and the board says so without a meeting.

What this replaced

A project tool that tracked tasks and held none of the material. A drive folder that held the material with no order of operations. A CRM that held the leads with no memory of where they came from. And a large amount of context that lived in one person’s head, which worked right up until that person was on a plane.

Now there is one surface with the material behind it, and the project tracking is a property of the page rather than a second system to keep in sync.

The test I use

The test is whether someone who was not at the last show can run the next one from the page alone.

If they cannot, something important is still living in a head or a private thread, and the page has a gap in it. That is an easier problem than the one it replaced, because the gap has an address too.

Suggested posts