Regulars, not reviews, are the real moat

In Bistro 8's guest data, a guest who visits four times in a rolling 12 months is roughly twice as likely to return within 90 days as a guest who has visited three times. The gap between visits 3 and 4 is where independents win or die.

Design a specific, cheap 'nudge to 4' — a handwritten card at visit 3, a text from the manager, a bottle of house wine on visit 4 with no announcement. Not a loyalty scheme. Not points. Recognition.

The best public example is Dishoom, which built one of the strongest repeat-visit cultures in UK hospitality on recognition rather than a points scheme — door teams briefed on the day's regulars, managers making a point of visiting their tables. Nothing about it is technology-hard. It is culture-hard.

If your reservations vendor won't hand you an export with every guest, every visit, every note — that's not your CRM. That's their CRM. You are renting your regulars from them.

This is the single most consequential procurement decision an independent restaurant makes and almost nobody negotiates it up front. OpenTable's default contract, up until quite recently, gave you access to your bookings but heavily restricted the guest-level data. SevenRooms flipped this positioning explicitly — 'you own your data' is on their homepage — and has taken meaningful share in the fine dining segment because of it. Your contract needs a plain-English clause: 'I can export every guest with every visit, every note, every tag, in CSV, at any time, without a fee.' If it doesn't, walk.

The reason this matters isn't just leverage. It's that your regulars database is a strategic asset that appreciates. Five years of tagged visits, allergy notes, birthdays, wine preferences, seating preferences and complaint history is unreplicable — and only useful if you actually control the file.