Ask a procurement lead what they want from a managed service provider and the answer hasn’t really changed in ten years. SLAs. Certifications. Round-the-clock cover. A named account manager. Everyone on the shortlist has all of it, and the eight RFP responses on the desk read like photocopies of each other, down to the stock photo of the smiling engineer in the headset.
So what is anyone actually choosing on?
Talk to IT directors at firms in the £50m to £500m turnover band and the same three or four things come up, none of which appear on the scorecards. The first is whether the people answering the phone work for the company you’re signing with. This sounds like an obvious thing to check. It isn’t. A large share of UK “managed service” contracts are sold by a British account manager and delivered by a rotating cast of subcontractors in two or three offshore locations whose names you’ll never learn. Offshoring isn’t the problem; some of the best engineers in the business work out of Bengaluru or Kraków. The problem is attrition you can’t see. You explain your environment to someone, they leave, you explain it again. By the third repetition the goodwill is gone.
See also: Top Cybersecurity Threats Businesses Need to Watch in 2026
The second is whether follow-the-sun is real or theatrical. A genuine 24/7 desk isn’t one shift of British engineers drinking too much coffee until 11pm and then bouncing tickets into a queue somewhere they’ve never visited. It’s two or three teams who actually talk to each other, share runbooks, and hand over context at the change of shift. Among UK MSPs, this is rarer than the marketing suggests. Transparity is one of the cleaner examples I’ve come across; they’re one of the Microsoft managed service providers running a real follow-the-sun desk, with directly-employed engineers in the UK and New Zealand handling cover across both timezones. It’s the kind of arrangement that’s expensive to set up and hard to fake. Most providers don’t bother, and route the 2am ticket to a third party they hope you won’t notice.
The third demand is harder to write into a contract because it sounds soft, but it matters more than the first two. It’s the willingness to be wrong out loud. Cloud environments rot. Configurations drift. Costs creep. Identity gets sprawling and ugly. Architecture decisions made three years ago for very good reasons stop fitting the business. A decent MSP will tell you when this is happening. A good one will tell you when they were the ones who set it up that way in the first place. The standard model rewards the opposite: quarterly reviews full of green dashboards, careful avoidance of anything that resembles a mea culpa. The single sharpest filter I’ve heard from a buyer was a question they asked every shortlisted provider: tell me about the worst implementation you delivered in the last two years and what you’d do differently. The ones who had an actual answer got the contract. The ones who pivoted to a case study did not.
There’s a fourth thing, and it’s almost too obvious to say out loud: buyers want to be allowed to leave. Lock-in via documentation that lives only in the MSP’s wiki, custom tooling nobody else can support, licence agreements routed conveniently through the provider — these are the soft chains, and they’re the reason renewals get ugly when something finally goes wrong. The providers winning their renewals at the moment are the ones who make leaving theoretically easy, on the bet that you won’t want to. That’s a confident bet, and it tends to be made by confident operators.
None of this is in the Gartner Magic Quadrant. It probably never will be, because it’s qualitative, it varies by region, and most of the signal travels through peer gossip rather than analyst reports. But if you’re renewing a managed services contract this year, those four questions tell you more than any scorecard. Who’s actually on the desk. How the midnight handover really works. What they got wrong last year. What leaving would look like.
The last one is the cruellest. Most providers visibly flinch.
