In this article
Ask an operator what their software costs, and the answer comes in two seconds: a list of subscriptions, added up to a monthly total. Ask what it costs that those subscriptions don't talk to each other, and the room goes quiet.
That second number never appears on any invoice. It's hidden in the ten seconds it takes to switch from the till to the delivery platform, a hundred times a shift. In the booking that gets retyped three times because no system passes it on to the next. In the half hour on a Sunday evening spent laying three payout statements side by side, none of which show the same total as the till.
Every system on its own does exactly what it promised. The till takes payment, the booking system remembers guests, the delivery app delivers orders. The problem is never in one tool — it's in the seam between them, which nobody pays for and nobody watches, until someone adds it up.
This guide counts the seven places where that seam costs money and time, with the numbers behind each one. Further down, you can put your own systems into the calculator: how often your team switches screens per shift, how much you retype, how much the weekly reconciliation costs, and what a missed sync costs you in revenue. You get a figure per year, in hours and in euros.
Everything runs in your own browser: nothing is sent anywhere and nothing is stored. These figures are reference points for an independently run venue — your team, your systems and your own volume have the final say.
Why your software bill feels small, and the friction doesn't
A subscription has an amount and a date. It shows on your bank statement, you see it come through every month, and eventually you get around to trimming it — which is exactly the subject of another article on this site, about pruning your software bill itself. Friction has no amount and no date. It's spread across ten people, a hundred times a week, in pieces too small for any one of them to ever write down separately.
That's also why sprawl rarely feels like a software problem. It feels like "we're just busy," or "that's just hospitality." Research into knowledge workers points to something more specific: according to Asana's Anatomy of Work Index, the average office worker switches between around ten apps roughly 25 times a day — and research by Gloria Mark at the University of California, Irvine found that after an interruption it takes an average of 23 minutes and 15 seconds to return to the same level of focus. Those 23 minutes apply to deep, uninterrupted desk work and don't translate one-to-one to glancing at a delivery tablet between two tickets — but the underlying mechanism, attention that has to be rebuilt after every switch, plays out during a shift just the same. Only shorter, and more often.
And restaurants are no exception to sprawl itself. Hospitality technology research from 7shifts found that a significant share of growing independent venues still rely on spreadsheets and group chats to make systems "talk" that should really be doing that themselves. That's not an operator failing — it's what happens when every system looked like the right choice on its own.
The 7 numbers, and what each one costs you
They're in the order a venue usually runs into them: first the systems themselves, then what it costs to switch between them, and only after that what goes wrong once nobody's sure which system is right.
1. How many systems you're actually running
Ask an operator how much software they use and the answer is usually "three, maybe four." Get them to actually count — every separate login screen, not every subscription — and it quickly climbs to six or ten. A till. A booking system, separate from that. Two or three delivery platforms, each with its own tablet and its own dashboard. An accounting package. A rota or time-tracking tool, or just a spreadsheet standing in for one. A stock list.
None of those systems is redundant — each one solves a real problem. The point is that "three or four subscriptions" on the bill and "eight places where the same information has to be entered separately" are two very different counts, and the second is the one that matters for the rest of this article. The calculator further down asks for that second one.
2. Switching between screens during service
Every time someone glances from the till to the delivery tablet, or from the floor to the booking screen, that doesn't cost 23 minutes — most switches during a shift are short, a glance lasting a few seconds to a few minutes. But they happen often: on an average shift with some volume, easily fifteen to twenty times.
Run the numbers for a bistro doing ten shifts a week, eighteen switches per shift and ninety seconds per switch: that's 270 minutes a week, 13,500 minutes over fifty weeks — 225 hours. At €20 an hour, that's €4,500 a year, just on glances between screens that have no idea what the other is doing.
3. The same booking, typed into more than one system
A guest calls for a table of four. At a venue with one system, that booking sits everywhere it needs to after thirty seconds. At a venue with separate systems, it goes into the booking system first, then again onto the paper or spreadsheet floor plan because the two don't feed each other, and sometimes a third time into a list for regulars. Three times typing the same thing for one phone call.
At sixty such bookings and orders a week, three extra minutes each, at €20 an hour: 180 minutes a week, 9,000 minutes a year over fifty weeks — 150 hours, €3,000 a year. That's money for work that, with systems that share what they know, simply wouldn't exist.
The same phone reservation, at a venue with one system, with four separate systems and with seven scattered systems. Height is the time one booking takes, from phone call to confirmation.
The extra cost is calculated on sixty bookings a week, at €20 an hour, over fifty weeks. Every extra system that needs the same information entered separately doesn't add — it multiplies, because every system has its own screen, its own login and its own way of turning something simple into three times the same work.
4. The weekly reconciliation of till, bank and platforms
Every source of money has its own rhythm. The till counts per shift. The bank books per deposit. Each delivery platform pays out on its own schedule, with its own commission already deducted, in a statement that never uses the same order or the same names as the till. Anyone trying to lay that side by side every week is effectively doing the same sum four times, in four different languages.
With four sources to reconcile — the bank and three platforms — twenty minutes per source per week, at €24 an hour: 80 minutes a week, 4,000 minutes a year over fifty weeks — 67 hours, €1,600 a year. And that's just the time to confirm nothing went wrong, not the time to fix it if it did.
5. The dish that's "out" in the kitchen and still "for sale" on screen
The kitchen strikes a dish off the menu the moment an ingredient runs out. On the till, that happens instantly. On the delivery platform, it only happens once someone switches it off there separately — and until then, a guest can simply order it. The result is a phone call, an apology, a refund, and sometimes a review that stays up for years, for something a connection could have prevented.
The same pattern shows up with a double-booked table: the phone list and the booking system don't know each other, and on a busy night someone books what's already taken. Both are the same kind of mistake — two systems that each think they're the source of truth.
At five such mistakes a month, an average of €45 in damage each — the refund, the time to put it right, a small slice of reputational damage included: €2,700 a year, for something that never shows up on the books as a "software cost."
6. The training time that adds up per system
Learning one system takes a morning. Learning eight systems doesn't take eight mornings — it takes eight rounds of figuring out where something is, with a different button in a different place in a different colour each time. For a new hire, that's the first impression of the business: not the food, not the team, but the feeling that there are seven screens nobody ever explained.
At four new hires a year, seven systems on top of the first, forty-five extra training minutes per system — counted for both sides, the new hire and whoever's explaining it — at €20 an hour: 21 hours a year, €420 a year. The smallest of the seven numbers, and the only one that never disappears as long as new people keep joining.
7. Where a manager's week actually goes
Add up the previous six numbers and you get an amount. Look at where in the week that amount actually sits, and you see something a figure alone can't show: how many of the hours meant for guests and the kitchen go into maintaining screens instead of the trade itself.
An illustrative fifty-five-hour working week, at three levels of sprawl. Systems & admin doesn't grow in a straight line with the number of systems — it grows faster, because every extra connection also makes the previous ones harder to keep track of.
This is an illustrative model, not a measured study of your own business — but the direction rings true for almost every operator who hears it: the more systems, the more of the week goes to the systems themselves, and the less to the reason you started the business in the first place.
Put your own systems next to it
Fill in how many systems you use, how often your team switches between them, how much you retype, how much the weekly reconciliation costs and how often something goes wrong between two systems. The fields are pre-filled with the example of a bistro running eight systems — overwrite them with your own.
Fragmentation Scan
Five places where the seam between systems costs money, and what they add up to per year.
—
These figures are reference points for an independently run venue and don't account for your concept or your team. Everything runs in your browser; nothing is sent or stored.
What to do with this — this week, this month, this quarter
Nobody closes five seams at once. This order does work, because every step makes the next one measurable.
This week — count what you can already count
- Write down on one sheet which systems you actually use — every separate login screen, not every subscription.
- Ask your team to track, for one shift, how often they switch screens for the same booking or order.
- Find the one connection that hurts most often — usually between bookings and the floor, or between delivery platforms and the till.
- Fill in the calculator above with your own figures, even if they're rough estimates.
This month — measure instead of estimate
- Count, for a month, how often a dish gets sold that's no longer available, or a table gets double-booked.
- Time how long the weekly reconciliation actually takes, instead of estimating.
- Look at where in your stack the same information lives in more than one place, and whether one of them can be made redundant.
This quarter — connect the one seam that costs the most
- Fix the connection you flagged as most painful in step one first — not the most expensive system, the most keenly felt seam.
- After a month, measure what it saves in time, and only then move on.
- Put your software bill next to your friction cost: often the second figure is bigger than the first, and that's exactly why trimming subscriptions alone rarely fixes the feeling of "too many screens."
The cost isn't in your stack — it's in the seams
Almost every operator who hears this recognises the same pattern: every system was a good choice on its own, and yet the sum still feels like too much. That's not a contradiction. Seven good decisions that never learned to talk to each other are exactly what sprawl is.
The good news is you don't have to replace everything at once to do something about it. Fixing one connection — the seam your team feels most often — usually costs less time than the friction it causes every week. Fix it, measure what it saves, then move on to the next. Sprawl doesn't disappear all at once this way, but it does disappear measurably, seam by seam.
If you want to tackle it more thoroughly, start with what you already have today: your POS system, your booking system and your delivery platforms are the three places where most seams form, and the three where one connection gives back the most time.