An intranet does not fail on launch day. It fails about fourteen months later, when the person who owned it has moved on, nobody has run a content review since the project closed, and the search results have quietly filled up with policies from two reorganisations ago. A managed service is the arrangement that stops that happening, and what it covers varies far more between suppliers than the name suggests.
"Managed intranet service" covers two quite different things, and the difference matters more than the price.
Platform support keeps the technology working: permissions, site provisioning, incidents, upgrades, service availability. It is measurable, it is what most providers lead with, and it is what SLAs are written against.
Content and adoption support keeps the intranet worth visiting: content reviews, analytics interpreted rather than merely reported, editor training as people join and leave, and someone noticing that a section has not been touched in eight months.
Many organisations buy the first and assume they are getting the second. Check which one you are signing, because an intranet with perfect uptime and no content governance still ends up unused. The failure mode nobody has a contract for is the one that actually happens.
Most UK providers quote on request, but enough publish figures to give you a sense of the range. Where indicative pricing is published, incident-management cover tends to start around £600 a month. Broader tiers covering change requests, consultancy and Microsoft 365 administration run into the low thousands, and strategic advisory arrangements reach four to five thousand a month. Pay-as-you-go call-off options exist, as do rolling monthly agreements with no long commitment.
Treat any of those as a starting point rather than a quote. The number depends on the size of your estate, how much content work is included and whether the arrangement covers the whole Microsoft 365 tenant or the intranet alone.
The question worth asking is not the monthly figure but what arrives in a normal month when nothing has broken. Every provider describes onboarding well. The honest answer about month seven is sometimes nothing at all, and that is worth knowing before you sign rather than after.
A provider who reports which searches returned nothing, which pages nobody opens and where people drop out of a task is giving you something you can act on. A provider who sends a visits chart is giving you a number you will stop reading by the third month. Ask to see a real report with the client details removed.
Stale content is the most common intranet complaint and the least commonly covered contract item. If the answer is that you chase content owners, that is a legitimate model, but price it as your own team's time rather than treating it as covered.
People trained at launch leave, and their replacements are usually shown the intranet by a colleague who learned it the same way. Training new editors is a small line item that prevents a large problem.
Someone has to be able to say a section has no owner and must be archived. If neither your contract nor your own structure gives anyone that authority, content decay is guaranteed regardless of what you are paying.
| Your situation | What you need |
|---|---|
| You have an IT team but no one owning content | Content and adoption support, not platform cover you already have |
| No internal Microsoft 365 capability | Full platform support, ideally with published SLA performance |
| Intranet works but engagement is sliding | Analytics, content review and a scheduled governance review |
| Budget approval is the blocker | A provider publishing tiered pricing, so you have a figure without a sales process |
| You want to try before committing | A rolling monthly agreement rather than an annual contract |
| Running a product-based intranet such as Omnia or Involv | A supporter who knows that product, not only SharePoint |
Our managed intranet service is built around keeping the intranet useful rather than only keeping the platform up. It covers content management support, technical fixes, analytics and adoption optimisation, with a separate analytics and continuous optimisation service for organisations that want the improvement work treated as its own stream.
That follows from how we build intranets in the first place, where governance, ownership and content structure are agreed before anything is designed. The same questions carry into the support arrangement: who owns each section, when was it last reviewed, and what do the analytics say people are failing to find. We support SharePoint, Omnia and Involv, so the service covers product-based intranets as well as bespoke builds.
If you want to talk through what your intranet needs after launch, book a call with our team.
An ongoing arrangement where a provider looks after your intranet after launch. It covers some combination of platform support, permissions and site management, content reviews, analytics reporting, editor training and governance reviews. The scope varies widely, so compare what is included rather than the headline price.
Where providers publish figures, incident cover tends to start around £600 a month, broader tiers run into the low thousands, and strategic advisory arrangements reach four to five thousand. Many providers quote on request. Rolling monthly and pay-as-you-go options both exist.
It depends which gap you have. An IT team can run the platform. What they usually cannot do, because it is not their job, is chase content owners, review whether sections are current and interpret adoption analytics. If that is your gap, look for content and adoption support rather than platform cover you are already paying for internally.
A scheduled check that the intranet still matches its own rules: sections have owners, pages have been reviewed, permissions have not drifted and the structure still reflects the organisation. Quarterly is the useful interval. Without one, governance decays invisibly until someone goes looking for a policy and cannot find it.
Chasing content owners, followed by training new editors. Both involve talking to your people rather than your tenant, which is why they fall outside most technical support contracts, and both are the direct cause of the content decay that makes intranets fail.