Buying managed services is hard to do well, because what you are buying is a promise about how somebody will behave in 18 months. Reference calls help. Case studies help less than people think. And by the time you find out whether the service is any good, you may be two years into a three-year agreement.
There is a practical way to reduce that risk, and it costs very little.
What should a managed services assessment tell you?
An assessment worth paying for produces a document you could hand to your finance director and have them understand it. It should give you the following.
- A number for the waste. Unused licences, over-provisioned resources and duplicated tooling, in pounds rather than percentages.
- A measured security position. A score or posture measurement you can track and improve, with the specific gaps named, rather than a description of your risk.
- A prioritised remediation plan, with what it costs and what it fixes, separated from any ongoing service.
- The things you should stop paying for, including anything the provider itself would not sell you.
- A clear statement of what it did not cover, so you know the scope of the picture you have been given.
If what comes back is a slide deck describing your challenges in general terms and recommending a three-year agreement, that is a sales document. Sales documents have their place, but you have not bought any reduction in risk.
“The test we would apply to ourselves is simple,” says Martin Summerhayes, Head of Managed and Support Services at Northdoor. “If the assessment does not tell a client something they did not already know, in a number they can act on, we have not earned the next conversation. Nobody should be signing a long agreement to find out whether their provider is any good.”
Why does the sequence matter?
Assessment, remediation, then the ongoing service. Running those in order does three useful things.
It separates the fixing from the running, which are different jobs at different prices. Bundling them lets a provider recover remediation cost inside a long service term, which is one way organisations end up locked in.
It gives you a genuine decision point. After the assessment you can take the findings and do nothing, do the work yourself, or go to market. That option has real value, and it keeps the provider’s behaviour disciplined throughout.
It shows how the provider works before you are committed. You see their people, their reporting, their responsiveness and whether they tell you inconvenient things, which is usually more informative than a reference call.
Who owns your provider, and why does it matter?
Ownership is a question buyers rarely ask at the start, and it can matter a great deal later.
Private equity is a large part of this market. Moore Kingston Smith’s tracker of UK IT services deals found that 66 per cent of the 164 transactions completed in the first quarter of 2026 involved private equity, and that IT managed services made up 32 per cent of deals in the outsourcing and distribution segment, with buyers pursuing buy-and-build strategies (Moore Kingston Smith, April 2026). When a provider changes hands, a common pattern follows: the senior, named contacts who won the account move on or move up, delivery is standardised to a central model, and the responsive service that made the firm worth choosing becomes a ticket queue with a target response time.
That is not necessarily bad value. Standardisation lowers cost, and for a commodity service it may be what you want. But it is a different service from the one you evaluated, and it often arrives without a conversation.
So ask directly: who owns the business, has it changed hands recently, is a sale being contemplated, and what happens to our named contacts if it does. Then look at the answer against your contract term. A three-year agreement with a provider in the middle of a sale process is a bet on something you cannot see.
For context on the other side of the argument, we have been independently owned for more than 35 years and have never been acquired, which is why we think the question is fair to ask of anyone, including us.
How should you structure the first engagement?
- Scope it small and real. One domain, one site or one service, chosen because it matters rather than because it is easy.
- Agree what success looks like in writing, with numbers, before work starts.
- Insist the boundary is documented per system, showing who is responsible for what, in a table rather than a paragraph.
- Ask for a redacted monthly report from an existing client. It will tell you more about the service than the proposal will.
- Test the out-of-hours path during the pilot, not after go-live.
- Keep the exit cheap, with documentation, configuration and data handed back in a usable form, written into the agreement from the start.
- Benchmark the price before you negotiate. Knowing the market range changes the conversation, and our managed services cost estimator is one way to get one.
What does good look like six months in?
You should be able to point at something specific. A cost that came down and stayed down, an incident handled well out of hours, an audit request answered without your team assembling it by hand. Your own people should have more capacity than they did.
If none of that is true after six months, the service is not working, and it is far better to discover that inside a scoped engagement than a third of the way through a long contract.
What this means for your organisation
Most of this moves risk back to the party better placed to carry it, and none of it requires a long negotiation. If your team is stretched and you are weighing whether to keep work in-house, share it or hand it over, our article on co-managed IT sets out the difference. If you would like a view on your own estate before committing to anything, that is how our IT managed services engagements start. You can also read how we work, see our modern workplace managed services, or ask us a question.