"Analytics" sounds like something for big chains with a data team. It isn't. For an independent Nairobi restaurant, a handful of numbers. Ones you already generate every night. Tell you where you're leaking money and where to push. Here are the metrics actually worth watching, in plain language, and what each one is telling you.

Covers per service

The number of guests you serve in a given service, broken down by day and hour. This is your foundation: it tells you which nights carry the month, when your real peak hits, and whether that new Wednesday promo actually moved anything. Track it by hour and you can staff and prep to the curve instead of to a hunch.

No-show rate

The percentage of booked covers that never arrive. Most owners badly underestimate this because it's invisible in a paper book. Put a number on it and it usually justifies M-Pesa deposits on peak slots on its own. Watch it weekly. It should fall once you add deposits and reminders.

Table turnover

How many times you seat a table during a service. On a packed Saturday, the gap between turning a table 1.5 times and 2 times is enormous over a year. If turnover is low during your peak, the fix is usually seating flow and pacing, not more marketing.

Revenue per guest & repeat rate

Average spend per cover tells you whether upselling and menu changes are working. Repeat rate. How many guests come back. Tells you whether the experience is good enough to build a business on. Rising covers with a flat repeat rate means you're filling a leaky bucket; fix retention first (our loyalty guide covers this).

Where the data comes from

You can't get any of this from a diary. It comes automatically once bookings, tables and payments live in one system. Which is the real argument for going digital in the first place.

DineBook turns every booking into these numbers automatically, no spreadsheets required. See the analytics features or read the deeper analytics-to-revenue guide.