A new intranet homepage can look deceptively simple. A branded banner, a news carousel, staff directory, organisation chart and a few shortcuts may appear to be a modest SharePoint job. Then the estimates arrive: discovery, design, SPFx development, testing, accessibility checks, deployment and support. The buy versus build SharePoint decision becomes much clearer once the full cost of ownership is on the table.

For most small and mid-sized organisations, the question is not whether SharePoint can be customised. It can. The question is whether a custom feature is genuinely distinctive enough to justify the time, risk and ongoing maintenance that come with building it.

Buy versus build SharePoint starts with the problem

A custom build makes sense when the business process itself is unusual and strategically important. Perhaps a regulated approval process has rules that cannot be accommodated by standard Microsoft 365 tools, or an internal application must bring together data from several line-of-business systems. In those cases, shaping the solution around the organisation may be the sensible route.

But many intranet requirements are not unique. Employees need to find news, colleagues, policies, links, events and recognition. Internal communications teams need an attractive way to publish information. Intranet owners need pages that work properly on mobile, respect tenant permissions and do not create another platform to administer.

Those are established requirements. Building them from scratch can turn a straightforward intranet improvement into a lengthy software project.

What custom SharePoint development really costs

The visible development estimate is only part of the bill. A bespoke SPFx web part needs requirements gathering, interface design, development, testing across browsers and devices, accessibility review, deployment, documentation and handover. It then needs attention whenever requirements change or Microsoft 365 evolves.

A well-made custom web part is not a bad investment. It is simply an investment that should be assessed honestly. A tailored news carousel or employee directory can easily cost £8,000 or more to design and develop properly. Add changes after user testing, project management and support, and the figure rises further.

There is also opportunity cost. If the intranet launch is delayed by three months while components are built, communications teams continue working around an underused site. Employees keep relying on bookmarks, shared drives and word of mouth to find what they need. The cost is not always shown on a project plan, but it is felt every day.

Custom development also creates a maintenance commitment. Someone must own the code, understand the deployment process and budget for changes. If the original developer moves on, the organisation needs a usable codebase and enough technical knowledge to support it. That is manageable for a large digital workplace team. It is less attractive for a lean IT department already responsible for security, devices, users and the wider Microsoft 365 estate.

When buying a SharePoint web part is the better commercial choice

Buying is usually the stronger option when the requirement is common, the desired outcome is clear and speed matters. A production-ready web part has already passed through the repetitive work of designing, building and testing a familiar capability. The buyer is paying for the feature, not funding its first creation.

For example, an Experience Pack web part can be licensed individually from £249 per year, covering up to 500 users. The Starter Bundle, covering five core intranet apps, starts at £999 per year, while the Complete Bundle of 18 web parts is £2,499 per year. Tenant installation and configuration are included.

That does not mean every bought component will suit every requirement. The right question is whether it covers the 80 to 90 per cent of functionality people will actually use without forcing awkward workarounds. If it does, purchasing is often the more disciplined decision. The remaining budget can go towards content, information architecture, governance and adoption – the areas that usually determine whether an intranet succeeds.

A ready-made web part should also fit the environment it is being bought for. For SharePoint buyers, that means checking that it is built on SPFx, works within Microsoft 365, honours existing permissions and does not move data outside the tenant. It should inherit the organisation’s branding rather than introduce a disconnected visual style.

Delivery time changes the value calculation

There is a material difference between a component available this week and one available after a development cycle. A purchased web part can be trialled before commitment, installed in minutes and configured as part of the intranet rollout. That allows teams to gather feedback from real users early, rather than relying on assumptions made at the start of a project.

Speed is particularly valuable where the intranet has lost credibility. Perhaps the homepage is static, staff cannot find the right contact, or key announcements disappear into email. A few visible improvements can reset expectations quickly. A better welcome area, clearer navigation, accessible news and a usable employee directory give people a reason to return.

Buying does not remove the need for good implementation. It simply shortens the route to a useful starting point. Someone still needs to decide what belongs on the homepage, who owns content, how news is governed and which audience needs which information. Those decisions are where experienced SharePoint support earns its place.

The risks of buying the wrong thing

A low licence price is not automatically good value. Some products overlap with existing Microsoft 365 capability, add unnecessary complexity or solve a problem that users do not recognise. Others look impressive in a demonstration but require considerable manual administration once live.

Before buying, test the web part against a real scenario. Can an intranet editor configure it without developer support? Does it work with the organisation’s existing branding and permissions? Is the mobile experience acceptable? Can users understand its purpose without training? And, crucially, will it still be useful after the initial launch excitement fades?

Free trials are useful here because they replace a sales conversation with evidence. Put the component on a test site, add representative content and ask the people who will manage it to use it. A trial should reveal both the value and the limitations quickly.

A practical decision framework

The decision becomes easier when each requirement is placed in one of three categories. First, there are standard intranet capabilities: news, navigation, people information, engagement and personal productivity views. These are usually strong candidates to buy.

Second, there are configurable business processes. These may need a mixture of Microsoft 365 configuration, Power Automate, Power Apps and targeted consultancy. Building every element from zero is rarely necessary, but some tailored work may be justified.

Third, there are genuinely differentiating systems or complex integrations. These are the cases where bespoke design and development can deliver value that no off-the-shelf web part will provide.

This avoids an unhelpful all-or-nothing choice. A sensible SharePoint programme often buys the repeatable intranet elements and invests custom effort only where the organisation has a real operational difference to support.

Buy the common parts, build where it counts

The best buy versus build SharePoint decision is rarely about technical preference. It is about directing budget towards the work that changes how people operate. There is little commercial advantage in commissioning a bespoke staff directory if a tested, tenant-native option can be deployed for £249 a year. There may be real value in tailoring an approval process that removes several manual handoffs every week.

ThePoint’s approach is deliberately built around that distinction: deploy familiar intranet capabilities quickly from a production-ready catalogue, then apply senior consultancy where process, governance or integration needs proper attention.

Start with the employee experience you need to improve next. If it is a common problem with a proven answer, buy it, test it and get it live. Save custom development for the parts of your organisation that truly cannot be bought off the shelf.