Skip to content

Intranet

How to Choose a UK SharePoint Intranet Partner (2026)

16 November 2026 · Lucy

Choosing a SharePoint intranet partner is mostly an exercise in working out what you are actually buying. Every UK consultancy in this market will tell you they build intranets in SharePoint, hold Microsoft partner designations and care about adoption. Those claims are true often enough to be useless as a way of telling them apart.

What separates them is narrower and harder to see from a website: whether the intranet is built inside your tenant or sold as a product on top of it, whether governance happens before the design or after the complaints, and whether anyone will tell you what it costs. This guide sets out the criteria that matter, the questions that get past the pitch, and what we found when we went through the published material of the main UK providers.

What should you look for in a SharePoint intranet partner?

Six things decide whether an intranet project works, and only one of them is technical skill.

  • Where the intranet lives. A SharePoint-native build sits inside the Microsoft 365 licence you already pay for. A separate employee experience platform sits alongside it with its own licence, its own admin interface and its own renewal conversation. Both are legitimate. Confusing them at the shortlist stage is not.
  • When governance happens. The information architecture, metadata, retention rules and permissions model should be agreed before any page is designed. A partner who treats governance as a phase near the end is describing a rework.
  • Whether content gets restructured. A lift and shift reproduces your current structure, including the parts people complain about. Restructuring costs more and is the only approach that fixes findability.
  • What happens after launch. Ask whether support is a named service with a scope and a price, or something arranged later. Intranets fail about a year after go-live, not on launch day.
  • Breadth beyond the intranet. Intranet projects grow into document management, process automation and Copilot readiness. A partner who covers that saves you a second procurement.
  • Whether they will say no. A partner who recommends a smaller first phase than you asked for is more use than one who agrees to everything.

What the UK market publishes, and what it does not

We went through the published material of the main UK SharePoint intranet consultancies in November 2026. A few patterns are worth knowing before you start comparing.

Almost nobody publishes a price. Across the providers reviewed, project pricing is quoted on request in nearly every case. Where numbers do appear they are usually for ongoing support rather than the build, and they tend to start around £600 a month for incident cover and rise to several thousand for strategic advisory. For the build itself, published ranges are rare. ThinkShare publishes a SharePoint migration range of £20,000 to £50,000 and pre-built intranets from £12,500 up to 100 users and £17,500 up to 500 users, which is unusual rather than typical.

Everyone has Copilot services now. In 2026 every serious UK Microsoft partner publishes Copilot readiness or deployment work. It has stopped being a differentiator and is no longer a useful filter.

Everyone offers post-launch support, but the shape varies. Models range from rolling monthly agreements with a quarterly governance review, through published tiered pricing, to managed IT services where the intranet is one workload among many. The differences are commercially significant and rarely visible until you ask.

Published timescales cluster around four to twelve weeks for a SharePoint intranet project. Faster is possible when scope is tight: a charity whose previous platform was discontinued had a replacement out-of-the-box SharePoint intranet live within a month.

Case study volumes vary enormously, from a handful to nearly sixty. Volume alone means little. What matters is whether any of them resemble your situation in size, sector and starting point.

Questions that get past the pitch

On governance

Ask them to show you an information architecture document from a real project, with the client details removed. A partner who does this routinely will have one to hand. Ask who decides what gets deleted, because that decision is the one every organisation avoids and the one that determines whether the intranet is still usable in two years.

On permissions

Ask how they handle permissions that have accumulated over a decade. The right answer involves redesigning rather than migrating them. This matters more than it used to, because Microsoft 365 Copilot surfaces whatever a user technically has access to, and in a tenant nobody has audited that is routinely more than intended.

On scope

Ask what they would leave out of the first phase. A partner who proposes news, policies, people search and your top ten tasks has built one before. A partner who agrees to every department in phase one is managing your expectations rather than your project.

On cost

Ask for the three-year cost, not the project cost. That means the build, the support arrangement, any platform licence beyond Microsoft 365, and the internal time of whoever will own it. A cheap build with an expensive licence attached is not a cheap intranet.

On ownership

Ask who owns the intranet on the day the project closes, and expect the answer to be a named person in your organisation with time formally allocated. If nobody can name them, that is the thing to fix before you choose a supplier.

Comparing a SharePoint build against a separate platform

Consideration Built in SharePoint Online Separate employee experience platform
Licensing Inside your existing Microsoft 365 licence Additional platform licence, usually priced on employee count
Where content sits In your tenant, managed with your other content Documents typically remain in SharePoint, publishing happens in the platform
Administration One set of tools and permissions A second system for your team to learn
Time to first release Depends on how much is built from scratch Faster start, less structural freedom
Best suited to Organisations keeping investment in Microsoft 365 Large multi-site organisations with complex internal communications

A middle route exists and is often overlooked. Pre-built intranet products such as Omnia and Involv sit on top of SharePoint, so content stays in your tenant while you get more publishing and targeting capability than out-of-the-box SharePoint provides. That suits organisations that want a faster start without a second platform.

Warning signs

Be careful with a partner who leads on the visual design before asking what people are trying to find. The homepage is the part everyone has an opinion about and the part that matters least.

Be careful with a fixed price given before anyone has looked at your content volumes. Fixed pricing is a legitimate model, but it has to be scoped against something real, usually a site count or a content inventory.

Be careful with a proposal that treats training as a line item at the end. Editors decide whether an intranet stays current, and if they are trained in the last week of the project they will not be.

Be careful with any comparison, including this one, that is written by a supplier. Use it to work out what to ask, then verify the answers against the suppliers themselves.

How ThinkShare approaches it

We build SharePoint intranets with governance agreed first: information architecture, metadata, sensitivity labels and permissions settled before anything is designed, so the structure is right for Microsoft Purview and Copilot from the start rather than being retrofitted.

We offer three routes rather than one. Out-of-the-box SharePoint, Omnia, or Involv, and we will tell you which fits your size, content volume and budget. We publish our prices, which makes the budgeting conversation shorter. We have moved organisations off discontinued platforms including LiveTiles and Valo, and rebuilt one charity's intranet on out-of-the-box SharePoint within a month when their previous product was retired.

If you want to talk through which approach suits your organisation, you can book a call with our team, or read more about our SharePoint intranet services and migration services.

Frequently asked questions

How much does a SharePoint intranet cost in the UK?

Published prices are rare. ThinkShare publishes pre-built intranets from £12,500 up to 100 users and £17,500 up to 500 users, and SharePoint migrations at £20,000 to £50,000. Most UK consultancies quote on request, so expect to run a short procurement to get comparable numbers. Add ongoing support, which where published tends to start around £600 a month.

How long does a SharePoint intranet project take?

Four to twelve weeks is the range UK providers typically publish. Tightly scoped replacements can be faster, and a month is achievable for an out-of-the-box build with agreed content. Duration depends far more on how much content you are willing to leave behind than on the technology.

Do I need a SharePoint specialist or can any IT company build my intranet?

A generalist can configure SharePoint. A specialist brings information architecture, governance and adoption experience, which is what decides whether people use the result. The practical test is whether they talk about content ownership and permissions before they talk about design.

What is the difference between a SharePoint intranet and a separate employee experience platform?

A SharePoint intranet runs inside your existing Microsoft 365 tenant, so content, permissions and governance stay in one place. A separate employee experience platform adds its own licence and its own administration alongside Microsoft 365. Documents usually still live in SharePoint, but publishing and administration move into the platform, which means your team learns a second system.

Can a SharePoint intranet work for regulated organisations?

Yes. SharePoint integrates with Microsoft Purview for retention policies, sensitivity labels and data loss prevention. The determining factor is whether retention and records decisions are made during the build rather than afterwards.

What should we do before approaching suppliers?

Audit your content and find out how much of it has been opened in the last two years. On most intranets it is well under half, and that number is the biggest single lever you have on cost and timescale. Agree who will own the intranet after launch, and decide what your first phase will deliberately leave out.

Talk to our team.

Tell us what you are working on and we will come back to you within one working day to arrange a call.

Contact us