How to Prepare for a Convention Booth

A convention booth is a conversion machine with three components: a kiosk-proof demo (10-15 minutes, auto-resetting, crash-hardened, playable by someone who reads nothing), visibility (one readable banner, a screen with motion, the game's name legible from across the aisle), and a capture loop — QR codes to the Steam page everywhere, because a wishlist scanned now outlives a flyer thrown away tonight. That's the short version — the sections below get into the how, the why, and the mistakes worth dodging.

The demo build is a different product

Show-floor reality: strangers walk up mid-loop, play with headphones in chaos, ignore all text, and leave without warning. The build must accommodate: a curated 10-15 minute slice starting at the fun, an attract mode or instant-restart when abandoned, an idle-timeout auto-reset (the single most forgotten feature), saves disabled, and a kiosk key/controller-only scheme that survives curious children mashing.

Crash-harden it ruthlessly and wire in crash reporting anyway — the show floor is a hardware-stress and edge-case marathon, and the silent crash that loses you booth visitors all afternoon is otherwise invisible until you wonder why the queue died.

Design for distance and decision speed

Attendees triage booths in seconds from meters away. The hierarchy: a banner readable across the aisle (game name, one-line hook, key art — not paragraph soup), a large screen showing motion (gameplay loop or trailer; movement catches eyes that text never will), and the playable station as the closer. Your booth's job from afar is one sentence: 'that looks like something I'd play'.

Practice the human layer too: a 15-second pitch, a 'want to try?' that isn't desperate, and the discipline to talk to watchers (the player's friend is also a customer). Booth energy is hospitality, not sales.

Capture or it didn't happen

The conversion moment is fleeting: someone enjoyed the demo, said kind things, and will forget the name by the hotel. Make capture frictionless and ubiquitous — QR codes to the Steam page on the banner, table tents, the demo's end screen, and your shirt; a mailing-list tablet for the deeply interested; cards with the QR for pocket-stuffers. Ask for the wishlist directly: 'if you liked it, the QR takes two seconds' converts shocking percentages when asked warmly.

Log the intangibles each evening: feedback patterns, which pitch lines worked, who from press/publishers came by (follow up within days). And budget bodies honestly — two people minimum, because a solo booth means no food, no bathroom, and no trade-show serendipity for three straight days.

Talk where your players already are

The best channel isn't the biggest one; it's the one where people who like your genre already gather. A cozy-game TikTok audience, a niche subreddit, a genre Discord — a hundred genuinely interested people beat ten thousand passers-by every time.

Find three places your exact players hang out and become a regular, not a billboard. Contribute first, share your game second. Communities can smell the difference instantly.

Marketing is a generosity game

The indie marketing that works rarely looks like advertising. It looks like sharing something genuinely interesting: a clip that makes people grin, a devlog that teaches something, a thread about a problem you solved. People share what makes them look good for sharing it.

So lead with the most interesting true thing about your game, not with the ask. 'Wishlist now' earns nothing by itself; a great 15-second clip earns the wishlist without asking twice.

Close the loop with real players

Advice gets you to a sensible starting point; only real player behavior tells you if it worked. Ship the change, then watch what actually happens — the reports that come in, the errors that spike or vanish, the place sessions end.

Make that loop short. When a player can report a bug in ten seconds and you see it with logs attached, you stop guessing what to fix next. Tight feedback loops are the closest thing indie development has to a cheat code.

Putting it to work

Don't try to act on all of this at once. Pick the one change that costs you the least and pays the most this week, do it, and see what actually happens before reaching for the next.

Most of this rewards steadiness over intensity. A small improvement made every week, checked against how real players respond, outruns any single burst of effort — in this corner of game development and every other one.

Show up where your players already are, lead with the interesting thing, and keep the cadence.