Most restaurant operators don’t change IT providers because their tech is broken - they change because they’ve quietly outgrown the relationship. Here are the 12 signs it’s time.
I have this conversation a lot. An ops director or an FD will book a call, spend the first ten minutes telling me everything is “basically fine”, and then spend the next forty minutes describing a relationship that anyone outside hospitality would have ended years ago. The provider isn’t malicious. They’re not even bad at IT in a generic sense. They’re just the wrong shape for a business that trades seven days a week, runs an EPOS estate across multiple sites and loses real money the second a card terminal stops talking to the acquirer.
If any of the below sounds familiar, you’re probably already past the point of switching. You just haven’t said it out loud yet.
1. You find yourself explaining hospitality to them every conversation
Every ticket starts with a tutorial. You explain what a KDS is. You explain why the bar printer matters more than the back-office printer. You explain that “the till” is not the same as “the PC at reception”. By the time the engineer understands the problem, your GM has already worked around it with a paper pad.
A provider who gets hospitality doesn’t need the preamble. They know what an Oracle Symphony workstation looks like, they know the difference between a Zonal Aztec and a Tevalis terminal, and they know that a stuck print spooler at 7pm is a P1, not a “we’ll log it and come back tomorrow”. If you’re still teaching your MSP the basics in year three, you’re paying them to learn on your time.
2. Your tickets sit in a queue behind law firms and accountancies
A generalist MSP services dentists, solicitors, accountants and a couple of restaurants. Guess whose tickets get triaged first when the queue is busy. It isn’t yours, because your “the EPOS is slow” sounds vague next to a law firm’s “the document management system is down”.
This isn’t a moral failing on the MSP’s part - it’s a portfolio mismatch. You need a partner whose entire SLA model assumes that a Friday evening is the busiest part of the working week, not a wind-down. That’s the whole premise of hospitality-specialist IT support: the queue is built around your trading pattern, not against it.
3. They still don’t know your EPOS vendor’s support line by heart
Your EPOS vendor is the single most important third party in your stack. If your MSP has to Google the support number, ask you for the account reference, and then warm-transfer you back into a queue you could have phoned yourself, what exactly are you paying them for?
A good hospitality MSP has a direct relationship with the major EPOS vendors. They know which engineer at Zonal handles your account, they have the case history in front of them, and they can escalate without you sitting on hold. That’s not a nice-to-have. That’s the difference between a 20-minute outage and a 90-minute one.
4. Your SLAs are written for “business hours” but you trade 7 days a week
This one is almost comedic when you read the contract back. “Response within 4 business hours, Monday to Friday, 9am to 5:30pm, excluding bank holidays.” Your busiest shift of the year is Boxing Day lunch. Your second busiest is New Year’s Eve. Your provider is on annual leave for both.
Out-of-hours cover should not be a premium add-on for a restaurant group. It’s the baseline. If your contract treats Saturday night as overtime, the contract was written for somebody else’s business and you’ve been quietly subsidising the mismatch.
5. They’re slow on new site openings
You’ve signed the lease, the fit-out team is in, and the opening date is locked. You email your IT provider with the address and ask them to scope the site. Three weeks later you’re chasing them for a quote on cabling. Two weeks after that the quote arrives and it’s wrong because nobody visited.
Site openings are the single biggest test of whether an MSP can actually move at hospitality speed. They involve circuits, cabling, switch and AP installs, EPOS provisioning, payment terminal pairing, guest WiFi, CCTV integration and a hundred small decisions that all have to land on the same Tuesday. If your provider treats every opening as a one-off project rather than a repeatable playbook, you’ll feel it on every launch.
6. You’re the one who told them about your Cyber Essentials renewal
Cyber Essentials is not a surprise. It renews on the same date every year. If you’re the one reminding your MSP that it’s coming up - or worse, if you’re the one filling in the self-assessment because they “don’t really do that side of things” - your provider is not running cyber security for you. You’re running it for yourself and paying them anyway.
A grown-up provider tracks your certifications, your PCI DSS scope, your insurance requirements and your supplier audits in the background. You should hear about renewals in a quarterly review, not at 11pm the night before the deadline.
7. Their ticket system needs you to explain “the till is down” in detail every time
You raise a ticket that says “till 3 won’t take card”. The system asks you to fill in seventeen fields, attach screenshots and select a “category” from a dropdown that doesn’t include the word EPOS. By the time you’ve finished, the till is back up and the table has paid in cash.
Friction in the ticketing process is friction on your service. A good provider gives you a one-tap way to flag a P1, a phone number that gets answered, and an engineer who already knows which sites you have, what’s installed at each one, and what changed last. If logging a ticket feels like filing a tax return, the system is wrong.
8. They can’t tell you what’s running on your network across sites
Ask your current provider, on a random Wednesday, for a list of every device on your network across every site. Switches, APs, EPOS terminals, KDS screens, CCTV NVRs, payment devices, BMS controllers, the lot. Give them an hour. See what comes back.
If the answer is a half-finished spreadsheet from 2024, you don’t have a managed network - you have an unmanaged one with an invoice attached. Visibility is the floor, not the ceiling. Without it, nobody can tell you what’s vulnerable, what’s end-of-life, or what’s about to fall over.
9. They haven’t proactively suggested anything in 12 months
Think back over the last year. How many times has your IT provider come to you with an idea? Not a quote you asked for, not a renewal - an actual suggestion. “We’ve noticed your guest WiFi controller is end-of-life next March, here’s a plan.” “Your EPOS server is on Windows Server 2016, we should talk about the migration path.” “Your card terminals are still on 4G, we could put them on the LAN and save you the SIM cost.”
If the answer is zero, your provider is in maintenance mode. They are keeping the lights on and waiting for you to leave. That’s not a partnership, it’s a slow goodbye.
10. Every new request becomes a quote and a debate
You ask for a new user account. You get a quote. You ask for a printer to be moved. You get a quote. You ask for a Wi-Fi password change. You get a quote and a four-day lead time.
There’s a balance here - out-of-scope work should be chargeable, and any provider who says otherwise is lying to win the deal. But if every interaction feels transactional, the contract is wrong. The day-to-day stuff should be inside the managed service, and the conversation should be about outcomes, not line items.
11. You’ve started to self-host things in Teams just to avoid going through them
This is the tell I see most often. The ops team has built a shadow IT stack in Microsoft Teams, SharePoint and a couple of free SaaS tools because going through the official provider takes too long. Rotas live in a spreadsheet someone in HR maintains. Site documentation is in a OneNote nobody backs up. The “IT request form” is a WhatsApp group with the area managers.
Shadow IT isn’t a sign your team is rogue. It’s a sign your provider has become an obstacle. People route around obstacles. The longer it goes on, the harder it’ll be to bring everything back into a managed environment when you finally do switch.
12. You dread the quarterly review instead of looking forward to it
The QBR should be the one meeting in the quarter where you actually feel like your IT spend is doing something. It should cover what broke, what got fixed, what’s coming up, what’s at risk and what you should do about it. You should leave it with two or three decisions made and a clearer picture of the estate.
If instead you dread it - if it’s a slide deck of ticket volumes, a polite chat about “the relationship”, and a vague promise to look at something next quarter - the QBR is theatre. And once the QBR becomes theatre, the rest of the relationship usually isn’t far behind.
So, how many did you tick?
If you ticked three or more, it’s probably time. Not because your current provider is incompetent, and not because you’re being unfair - but because hospitality is a specialist sport, and a generalist provider can only carry you so far before the seams start to show. The cost of staying isn’t a line on the invoice. It’s the slow drag on every opening, every service and every QBR where nobody quite says what everyone is thinking.
If any of this sounds like your week, have a look at how we run IT support for hospitality - or just drop me a line and we’ll have a straight conversation about whether switching makes sense for you. No quote, no slide deck, no debate.