I run a steakhouse in Canada, the oldest one still standing in the country. Five years in now, and some nights the dining room is loud enough that you can't hear the pass calling out tickets over the noise. Those are the nights that used to fool me. Full room, wine flowing, a line at the door by eight, and I'd walk out at close feeling like a king. Then I'd actually sit down with the numbers a week later and realize the labour had crept up, a supplier had quietly raised prices two months earlier, and that "great night" barely broke even. Busy and profitable are not the same thing, and nobody tells you that until you've lost real money learning it.
So I built the discipline myself. Every week, without fail, actually reading what happened instead of just remembering how it felt. It changed how the whole business ran, and once it worked, I couldn't unsee how many other restaurants were making decisions the exact same way I used to, on instinct and adrenaline instead of numbers.
"I've watched that street come alive over the years, and I've also watched a few of my favourite local spots quietly go quiet."
A few years ago I fell for Lombok, hard enough to buy a villa just off the main street in Kuta. I've watched that street come alive over the years, new restaurants opening almost every season, the road humming with scooters and string lights by 7pm. But I've also watched a few of my favourite local spots quietly go quiet. Fewer tables filled on a Tuesday. A menu that didn't change even as costs clearly did. The kind of slow fade an owner is often too close to see happening in their own restaurant. I recognized it immediately, because I'd lived through my own version of it.
Every restaurant deserves to know the difference between busy and profitable, not just the ones in Toronto or New York. So I put together a small team who think about restaurant numbers the same way I do, and we decided to bring that discipline first to the place I actually love spending my time.
We're not consultants who've read about restaurant margins from the outside, we're built by people who've managed real restaurants themselves. Every report is put together the way we'd want one sent to us, specific, honest, and useful by Thursday morning, not filed away and forgotten. The team runs out of North America, which means the same operational rigor you'd expect from a Western analytics group, delivered at a price that actually makes sense for an independent restaurant, not an enterprise one.
"We're not trying to build the biggest restaurant analytics company. We're building the one I wish we'd had five years ago, a team that actually reads your numbers, every week."
Talk to our team →