The wall

The pitch

A QR code on the table. The guest scans, WhatsApp opens, the bill shows up, they pay, they leave. No cashier queue. The kitchen and the waiter see the same table status they always did — just with "paid" arriving from a new direction.

That was the pitch. It was easy to demo on a whiteboard. It was hard to sell.

Fifty no's

We pitched it to roughly fifty restaurants before anyone agreed to let us try it in their dining room. The rejections were not about price. They were almost always about one of three things.

The first was the cashier. The cashier is a person, usually a senior one, and the register is their station. Removing the payment moment from the cashier sounded to them like removing the cashier. It didn't matter that we said the cashier's screen would still show everything. It sounded like a demotion.

The second was the waiters. A waiter who walks past a table and sees a plate on it wants to know whether that table has paid. The objection we heard most was some variant of: "and what happens when the customer just walks out — how do I know they paid?" The waiters were not worried about the payment system. They were worried about being the person left holding the unpaid check.

The third was shape of risk. "And if it breaks on a Saturday night?" "What if the internet goes down?" "Who do I call when a guest can't pay?" Restaurants at peak hour do not have time for novelty. They have time for whatever worked last weekend.

The first yes

The restaurant that said yes was a mid-size place run by an owner who made the decision without running it past the floor. They said yes on one condition: the PoS screen had to keep being right.

Their exact ask was that when a guest paid through WhatsApp, the waiters should see that table change status on the handheld they were already carrying — the same screen they looked at a hundred times a shift. Nothing else was negotiable. If we could not update the PoS, we did not have a deal.

That constraint is the rest of this document.