The room where DriftTable became real
Building DriftTable one Wednesday at a time.
DriftTable did not begin as a finished software pitch. It began as a weekly attempt to give one real restaurant a reason for people to gather on Wednesday without adding a separate trivia host.
WeeklyA new show built, tested, and put into the same room.
5 playing tablesObserved during one live week, with other tables still watching and reacting.
Paper + phoneBoth methods used in the same room instead of forcing one answer system.
No dedicated hostThe show runs while restaurant staff keeps serving.
The original problem
A slow room did not need another employee.
The goal was not to recreate a professional-hosted trivia company inside the restaurant. The goal was to prepare the experience ahead of time so a bartender or server could put it on the screen, show customers how to join, and keep the normal shift moving.
The useful test was never whether the idea sounded good. It was whether it could survive a real Wednesday while food, drinks, customers, and staff all needed attention.
How the build changed
Every week exposed the next problem.
- Prepared videoThe questions, timers, breaks, and reveals moved onto the screen.
- Better pacingThe format settled into three rounds of fifteen instead of leaving the room waiting too long.
- Venue workflowThe host sheet, current show, schedule, and score controls moved into one venue page.
- Player identityQR check-in, accounts, and persistent teams replaced disposable names where players choose to sign in.
- Public memoryWeekly and all-time scoreboards gave teams a result that still existed after the screen turned off.
- Separate online playThe physical venue remained first while the weekly game gained its own later online release.
What the field test supports
The operating model works in a real restaurant.
- A venue worker can start and manage the prepared show
- Customers understand a single QR instruction
- Paper and phone teams can coexist
- Non-playing tables can still watch and interact
- Returning team identity matters more than a throwaway score name
What it does not promise
One room is proof of operation, not a guarantee of results everywhere.
- No guaranteed crowd size or revenue increase
- No claim that every customer will play
- No claim that every venue should use the same schedule
- No claim that the product is finished learning
Use the proof honestly