We sell one of the things being compared here, so treat the framing with appropriate suspicion. What we can do is show the arithmetic rather than the adjectives, and be specific about where we're the wrong answer — which is more often than a vendor comparison usually admits.
The claim in most of this category is "saves you time". Almost nobody says how much, from what baseline, or which minutes.
The baseline
One independent restaurant, fourteen reviews a week — a busy site, a mix of platforms, six of them worth a written reply. That's the volume where this decision starts to matter; below it, see the last section.
Where the minutes go
| Dashboard | Alerts and replies | Agency | |
|---|---|---|---|
| Logging in and checking | 3 × 6 min = 18 | 14 alerts read on a phone ≈ 3.5 | 0 |
| Triage and reading | 14 × 1 min = 14 | included above | 0 |
| Writing 6 replies | 6 × 4 min = 24 | 6 × 3 min = 18 | approving drafts ≈ 10 |
| Reporting | monthly report, 20 min ÷ 4 = 5 | weekly summary read = 4 | monthly call, 30 min ÷ 4 = 7.5 |
| Weekly total | 61 min | 25.5 min | 17.5 min |
The dashboard-to-alerts difference is 35.5 minutes a week, which is 30.8 hours a year. Call it thirty-one hours — the best part of a working week, recovered.
Three things about that number are worth saying plainly.
It's smaller than the marketing suggests. Thirty-one hours a year is real, and it is not transformative. If a vendor tells you they'll save you a day a week on reviews at fourteen reviews a week, the arithmetic doesn't support it, because there aren't that many minutes there to begin with.
Most of what's left is writing. In the alerts column, 18 of the 25.5 minutes — 71 per cent — is composing replies. No tool removes that, and the ones that claim to are offering to generate the reply for you, which is a different product with a different failure mode. The genuine savings come from not logging in and not deciding who owns it, and those savings are capped.
The agency column is the fastest and it isn't the winner. Seventeen and a half minutes of your time, and the lowest number on the table. The cost is elsewhere: a reply that goes out a day or two later, written by someone who wasn't there and doesn't know that the Friday problem is the pass rather than the kitchen. And crucially, nobody in your building ever reads the reviews, so the operational signal in them — which is the actual value — never reaches a rota or a pre-shift brief.
That's the trade. Outsourcing reviews buys back the most time and throws away the information.
Where the dashboard genuinely wins
Not on speed. On everything that involves looking backwards.
If you need to know how site four compares with site one on service complaints per hundred covers over six months, an alert stream is useless and a proper dashboard is the right tool. Alerts are a queue; queues have no memory. Anything involving trend lines, franchise compliance reporting, brand-level roll-ups or an export for a board pack is dashboard work.
Which is why the sensible answer for most multi-site operators is both, with the division of labour drawn honestly: alerts for the thing happening now, dashboard for the monthly question. The one-screen version of the monthly question is here.
Four situations where we're the wrong purchase
You get fewer than about four reviews a week. At that volume the whole problem is smaller than the software. A Google notification, a recurring calendar entry on Monday, and fifteen minutes will do it, and the theme analysis has nothing to work with — the rate arithmetic needs volume to mean anything. Don't buy anything. Come back at forty sites' worth of volume or when your reviews double.
Nobody has been told that replying is their job. This is the big one. If reviews currently go unanswered because ownership is undefined rather than because they're hard to find, then alerts make it worse, not better — you have added a notification that everybody can see and nobody owns, and within three weeks the whole team has learnt to dismiss it. Settle who replies first, on paper, with names. Then look at tools.
Reporting is the actual requirement. If the thing driving the purchase is a franchisor's compliance pack, a monthly investor report or a multi-brand comparison, buy the reporting product. We'd be a poor fit and you'd be back in six months.
Your problem isn't reviews. If the reviews all say the same true thing — that Friday nights are slow because Friday nights are understaffed — then no reputation software changes the outcome. You'd be buying a faster way to be told something you already know. Some review themes are a resourcing decision wearing a training costume, and the honest response is a rota change or an accepted trade-off, not a subscription.
The questions worth asking any vendor, including us
- What's the baseline you're comparing against, in minutes? If the answer is a feature list, you have your answer.
- Does this reach the duty manager's phone, or my phone? Tools that only reach the owner scale to exactly one site.
- What happens on the shift where nobody acknowledges anything?
- Can I see the raw reviews, or only your summary of them? Summaries are where the operational detail dies.
- What does it cost to leave, and do I keep the history?
What we'd actually say
At fourteen reviews a week with a manager who already replies, the honest pitch is thirty-one hours a year, the allergen and illness language flagged the moment it lands rather than on Monday, and the themes arriving in a form you can brief from. That's it. It's a real, modest, specific benefit.
If you were hoping for a number ten times that size, the number isn't there, and anyone quoting it is measuring against a baseline where nobody was doing the job at all.