Who/where
The LOCAL Place is a café and ice cream parlor on the square in Centerville, Tennessee, sharing a roof with the MADE @ The Local pottery studio — The LOCAL Drive-Thru, three and a half miles down the road, is part of the same family. It's ours — the same family behind LocalWebRank. One weekend a month, the café turns into a six-course Italian dinner night: ten tables, two seatings, one small crew. At the July 2026 debut, that meant 92 covers across two sold-out nights.
The problem
The dinner ran on paper. Servers wrote orders at the table and carried forms to the register, where every line was re-keyed into the point of sale; tickets were printed, stapled, and hand-run to the kitchen; an expediter checked plates against handwriting. Course pacing across ten tables lived in people's heads. Allergies were handwritten notes — and gluten-free pasta needs prep lead time, so finding out at fire time was too late. The phrase "who had the chicken?" was banned at this dinner; the seating-position system that replaced it lived entirely on paper.
What we built
A custom app that gives every station its own screen — seven role-specific screens running on nine tablets, all talking to each other in real time over the café's own network:
- The host gets a live map of the dining room — who's seated where, color-coded by party.
- Servers take orders seat by seat on a tablet. If a guest has an allergy, the menu greys out anything flagged unsafe for that seat — and the kitchen knows about every gluten-free order from the moment it's entered, not when it's fired.
- The kitchen sees courses in firing order with timers; the expo station checks plates against a digital ticket by seat position, so the right plate lands in front of the right guest without a word.
- The dessert-and-drinks station and the register each get their own queue, so nothing gets made twice or missed.
- The chef changes the menu — tonight's rotating main, allergen tags, what's available — from a manager screen, no developer needed.
- If the internet goes out entirely, service keeps moving — the system runs on the café's own network and doesn't need the internet.
Key decisions
- No app store, nothing to install — it runs in the browser on ordinary tablets.
- The app deliberately holds no payment data; the point-of-sale system stays the single source of truth for money.
- We built the part that hurt — service night — not a fifty-feature platform.
Proof of rigor
Built and tested with 326 automated backend tests and full simulated service runs — a test harness that drives all seven screens through a complete dinner caught real bugs before staff ever saw them. Then it faced the real thing.
The debut
The app ran its first live services July 10–11, 2026 — two sold-out nights, 92 covers, 38 reservations, six courses each night, one small crew. Zero no-shows, zero cancellations, zero refunds, zero system downtime, and not one paper ticket. The kitchen fired courses off timers instead of memory; every allergy was on the right screen before the first plate; and 12 of 23 Saturday desserts were added table-side mid-service — upsells that used to die on a paper form.
"I spent the whole weekend in my dining room instead of chasing tickets. Every plate landed in front of the right guest, the kitchen stayed calm, and I got to actually visit with the people at our tables. I will never go back to paper." — Concetta, The LOCAL Place
The takeaway
This wasn't built for a client. It was built because our own dinner night needed it — which means it was built for a real small-business budget, a real small crew, and zero tolerance for software that falls over mid-service. If your business has a night like this — or a paper system holding it together — that's exactly the kind of problem we like.