Skip to content

A trade-fair playbook: before, during and after the stand

Team cards, a code on every surface of the stand, demo slots, and a lead list that is sorted before the train home.

ExampleDigital cardQR codesPlacementsFormsBookingsLeadsAutomationsAnalyticsNeeds the Company plan or above

Three days, five people on the stand, and the usual problem: a stack of business cards nobody types in, and no idea which part of the stand worked.

Before

Two weeks out

  • Cards for the stand team

    One company card template; each person gets their own card with the logo and the fair hall in the locked fields.

  • A code for every surface

    Back wall, counter, brochure, product samples and the demo screen: one campaign, one shared design, each code its own placement.

  • Demo slots

    A form with a booking field: 20-minute demos, three people per slot, bookable from the invitation e-mail.

During

The three days

  • No more card stacks

    Visitors scan a team member's card and send their details back with the exchange button. Consent is stored with each contact.

  • Every contact sorted on arrival

    An automation tags every new lead from the fair, assigns it round-robin to the sales team and sends the visitor a thank-you e-mail with the brochure.

  • See what's working by lunchtime

    Scans per placement, live. If the counter code outperforms the back wall, move the brochure stand.

After

The week after

  • Follow-ups that happen

    Each lead has an owner and a follow-up date; the morning digest tells each salesperson whom to call.

  • The report for whoever paid for the stand

    A read-only share link to the campaign's analytics, with an expiry date.

  • Reuse the stand

    Point the codes on the printed materials at next year's registration page. Nothing is reprinted.

Team card templates, roles and the five seats are on the Company plan. Bookings, automations and campaign comparison are included.

More use cases

Try your own version

Start free with three codes, a page, a card and a form. Upgrade when the use case needs it.