Organising an expo when you are not a large company

A large company treats an expo as a line in a marketing plan. For a smaller business it is usually a significant share of the year’s budget spent across two or three days, decided months earlier, and judged afterwards on a number nobody agreed in advance.

That difference is the whole reason this is written. Most expo advice assumes a team, a fabrication partner already on retainer and somebody whose job is the stand. If none of that is true for you, the decisions shift.

Decide what the expo is for before you book the space

The question is not “should we exhibit”. It is what has to be true when the doors close on the last day for the spend to have been worth it.

Leads in a spreadsheet is not an answer. Leads you have already qualified, meetings booked for the following fortnight, one distributor relationship opened, a product shown to people who could not otherwise see it — those are answers, and each one produces a different stand.

A stand built to start conversations looks nothing like a stand built to demonstrate a product. If nobody chose, you get the one that looks nicest empty.

The floor plan matters more than the stand

Organisers sell position, and position is most of the result. Corners take traffic from two directions. Space near an entrance gets volume but people who are still orienting. Space near catering gets dwell time. Space at the end of an aisle that terminates gets very little of anything.

Ask for the floor plan before you commit, ask where last year’s traffic actually went, and be willing to take a smaller stand in a better position. A smaller business usually should: the size of the stand is a vanity metric and the position is not.

Build for the fourth hour of the second day

A stand is photographed when it is finished and lived in for the rest of its life. By halfway through, the literature is disordered, something has been knocked, and whatever surface people lean on shows it.

So: surfaces that can be wiped rather than protected, spares made with the build for the parts that will fail, and somebody on site with the tools to fix them between peaks. This is ordinary production thinking and it is the difference between a stand that holds and one that visibly tires.

Graphics get read at three metres, not thirty centimetres. One sentence that says what you do, legible from the aisle, outperforms a panel of copy nobody stops for.

The venue’s rules are not negotiable

Height limits, rigging permissions, what may be fixed to a floor or a wall, build and dismantle windows, power draw, noise. Organisers publish these and they do not bend.

Read them before anything is designed. A stand drawn to a height the hall will not permit is not a negotiation, it is a rebuild in the worst possible week — and for a smaller business that cost usually comes out of the same budget as the staffing.

Staff are the stand

The most common failure we see is not a bad build. It is two people who have been standing for six hours, one of whom is on a phone, in front of an environment that cost more than both of them.

Brief whoever is on the stand on the product, on who they should be looking for and on what to do when they do not know an answer. Roster breaks properly — three people covering two positions is not overstaffing, it is the minimum that keeps anyone alert. And put somebody there with enough authority to make a decision, because the conversation that matters will happen when it is inconvenient.

The follow-up is planned before you go, not after

Leads decay fast, and the week after an expo is the week everyone is catching up on what the expo displaced. If the follow-up is not scheduled before you leave — who contacts whom, in what order, saying what — it slips, and the spend becomes a stack of business cards.

Decide the capture method in advance and make it something one person can do while talking to another. A scanner that nobody uses is worse than a notebook that everybody does.

What this costs you to get wrong

A stand that goes up late, staff who cannot answer the question that matters, or a list nobody calls. None of those is a design failure, and all three are avoidable months earlier — which is the only useful time to think about them.