Twelve tests you can run on your own restaurant tonight.
The outside-in checks from the walkthrough, given away in full. Run three of them tonight and see what comes back.
Daniel M. Ortiz · September 2026
These are the twelve outside-in tests from our own walkthrough, published in full. They need no vendor, no new login, and no budget — a few phone calls, two small orders, one evening.
The method matters more than the score: write down exactly what happens, in the order it happens. The notes are the finding. And take notes rather than recording — call-recording consent laws vary by state, and paper needs no lawyer.
Call your own restaurant six times.
Six calls at six different hours across one week. If the team knows your voice, have a friend place them. For every call, write down: how many rings, who or what answered, whether they could actually take the order or the booking, and what the voicemail says when it catches you.
Half an hour before open
Who owns the phone when the room is set but the doors aren't? Callers at this hour are planning tonight.
The mid-afternoon lull
The easiest call of the week. If this one fails, the busy ones aren't being missed — they're being surrendered.
Friday, mid-service
The call everyone on the floor can hear and nobody can get. Usually the most valuable one on this list.
Saturday, an hour before close
The “are you still seating?” call. The answer is money either way — if anyone answers.
Just after close
Listen to the after-hours experience like a stranger: does the message take a booking, offer a path, or apologize and hang up?
A day you're closed
Callers don't know your calendar; they know what the search listing says. Read your own listing first — hours, phone number, menu link — then call. Where does Monday's phone go, and does anyone ever hear about it?
Six checks that never touch the phone.
The other half of the walkthrough happens where a guest can't hear a ring: the online book, the large-party inbox, the two ordering paths, your own email list, the review page. Same discipline — write down exactly what happens, in the order it happens.
Book a table for two online
Tomorrow night, from your own website, on a phone. Count the taps. Then read the confirmation like a first-time guest: does it arrive, does it look like your restaurant, does it answer the questions people call to ask, and what happens if you don't show?
Try to book for eight
Most online books quietly cap party size. Watch where the eight-top gets sent — a phone number (see tests 1–6), a form, a dead end. Weigh the friction against the check size: the biggest tables usually hit the most of it.
Send a large-party inquiry
Use the website form or the listed email, and start a timer. What comes back, when — and does it carry a name and a next step, or does it read like a machine clearing a queue?
Place the same order twice
Once through your direct ordering, once through the third-party app: same items, same time of day. Put the receipts side by side — item prices, fees, what you keep. For scale, DoorDash's published merchant pricing puts commission on delivery orders at 15, 25 or 30 percent by plan, so the difference on your two receipts has a floor you can name. Then check the kitchen: did the modifiers survive both trips?
Join your own email list
Sign up with a fresh address. What arrives, when, and from whom? If nothing comes, find out where the address went — someone is paying monthly for wherever that is.
Read your last ten critical reviews
Look only at the responses: who answered, how fast, in whose voice. From the outside, silence and boilerplate read exactly the same.
Don't score it. Rank it.
Rank the three worst things you wrote down and fix the first one this week. The usual first fixes cost nothing: an after-hours message re-recorded so it books instead of apologizes; the large-party inbox given one named owner and an auto-reply; the online party cap raised, with the phone as a real fallback.
Then re-run the tests you failed. They're repeatable — that's the point. What you measured this week, you can measure again after the fix.
Turn the Twelve Tests into a working record.
The public name stays Twelve Tests: it has earned recognition here, describes the method plainly, and avoids implying a benchmark or a precise score we do not have. Mark what you observed. Your result stays on this device until you reset it.
0 of 12 marked.
What the assessment adds
The twelve tests are the outside of the business — anyone can run them, which is why we publish them. The Operations Assessment is the walkthrough of the whole thing: the same twelve tests run and written down word for word, plus two services observed, five interviews, every seam where data gets re-keyed by hand traced, and your software bill priced line by line.
The money math comes back with every figure labeled Measured or Assumed — the assumption printed beside the number, so you can change it and watch the number change. It ends in a fixed-price plan you own either way. If the tests took you an evening, the walkthrough takes three weeks.
If three of the twelve came back ugly and you'd rather not run the other nine alone: