The costs don’t appear anywhere on the balance sheet. Yet they’re there.
An employee who spends ten minutes searching for a document that does exist, but is never in the right place. A new colleague who uses the wrong version of the onboarding document for three weeks. A manager who answers the same question five times a week because the answer isn’t stored anywhere centrally.
None of those moments show up as a line item in your accounts. Together, they cost an organisation of 300 employees hundreds of thousands of euros per year.
What you’ll learn in this article:
- Why digital fragmentation is an organisational problem, not an IT problem
- How to calculate the hidden cost for your own organisation
- Which three routes organisations take to close that gap, with their TCO profile
- Four questions every decision-maker must ask before signing
- Answers to objections every CFO and IT director has
Digital fragmentation: how it starts, what it costs
Nobody chooses it. Yet there it is.
An organisation grows. New teams emerge. To move faster, departments create their own SharePoint site, their own Teams channel, their own shared folder. A document library here, a communication site there. Every step seems logical at the time. Until nobody can see the whole picture anymore.
The result is called digital fragmentation: a workplace that grew organically but was never designed. Documents exist in multiple places. The same information is shared through different channels. Some departments work in Teams, others stick to email, and WhatsApp gets used unofficially on the side. There is no central knowledge hub, no structure that everyone follows.
And that is exactly where the cost starts to show – even if it never appears on an invoice.
The three cost layers of fragmentation
| Cost layer | Cause | Measurable? |
|---|---|---|
| Time lost searching | Information is spread across tools and channels | Yes – see calculation |
| Communication overload | Same information shared through multiple channels, no central source | Partly |
| Low engagement and turnover | Employees feel disconnected from the organisation and its direction | Yes – see Gallup |
Layer 1: time lost searching
Is that document on SharePoint, in a Teams channel, on the shared drive or in an email attachment? For many employees, that is a daily question. Research by Coveo (2025) found that knowledge workers spend an average of three hours per day searching for the right information.
Even if you scale that figure down significantly to 30 minutes per week, the impact remains considerable:
0.5 hours × 48 weeks × €50 wage cost × 500 employees = €600,000 per year. Capital that disappears into the search bar, instead of being invested in customers or innovation.
Note: this is not a wage cost. That employee works regardless and gets paid regardless. This is opportunity cost: the value lost because those 30 minutes are not spent on customers, projects or decisions.
Layer 2: communication overload
According to the Microsoft Work Trend Index, 57% of the working day is spent on communication: email, chat and meetings combined. In a fragmented workplace, that figure is even higher. You have to follow the same information across multiple channels. Teams rebuild documents from scratch. Processes get written twice. Decisions slow down.
A central information layer removes the biggest source of noise: the question “where does it live?” that has to be asked over and over again.
Layer 3: low engagement and turnover
This is the most expensive layer – and the least visible. Gallup found that disengaged employees cost an average of 18% of their annual salary in lost productivity. Digital fragmentation is not the only cause of low engagement, but it is an amplifier: employees who can’t find information, who don’t know what’s happening in the organisation, who feel disconnected from direction and decisions – they leave sooner. And every departure has a price.
The question for the CFO is therefore not “can we afford an intranet”, but “can we afford to let the current cost keep running?“
Is Microsoft 365 already an intranet?
No, but the answer is more nuanced than that. Three reasons why the misconception is so persistent:
Microsoft’s marketing
Microsoft actively promotes Viva Connections as an intranet solution. That is not incorrect – it is their intranet strategy. But Viva Connections is a gateway, not a complete intranet. Targeted communication per audience, a mobile app for frontline workers, structured onboarding and adoption analytics are functionalities that Viva Connections does not yet fully cover today.
The “we already have it” argument
If finance is already paying for 300 E3 licences, additional investment feels like paying twice. Logical at first glance – until you factor in the three cost layers above.
The homepage illusion
One SharePoint communication site with a few news posts looks like an intranet. But without targeting, without governance and without a maintenance routine, it becomes an abandoned page nobody visits within three months – what the industry calls the “Dead Intranet Syndrome”.
The problem is not that Microsoft 365 delivers nothing. The problem is that the step from “tools” to “a working intranet for 300 people” requires work. And that work costs money, whether it sits in an internal build project, in a platform nobody uses, or in a specialist solution.
A case study: from fragmentation to structure
A Belgian healthcare organisation with 650 employees used SharePoint for documents, email for internal communication, and informally WhatsApp for employees without a fixed workstation. For three years, digital fragmentation grew: documents in multiple places, news that never reached the shop floor, an onboarding process that rested entirely on individual team leaders.
After implementing Involv Intranet – built on the existing SharePoint environment – HR helpdesk tickets dropped by 35% within six months. Onboarding time for new employees was cut in half. And for the first time, news and policy updates also reached frontline workers, via the mobile app.
The investment had paid for itself within fourteen months.
Want to know how other organisations went through this journey? Read our customer stories.
Three routes to close the gap
You have roughly three options to bridge the gap between your Microsoft 365 licence and a working digital workplace. Each has a different risk and cost profile.
| Route | Profile |
|---|---|
| Route 1: Custom build on SharePoint | Maximum flexibility. Variable cost. High overrun risk. |
| Route 2: Ready-to-go intranet | Fixed scope. Shorter implementation. Predictable TCO. |
| Route 3: Do nothing | No visible investment. Highest hidden cost over 3 years. |
Route 1: Custom build on SharePoint
You take SharePoint Online and have an internal IT department or external consultancy build the information architecture, templates, governance and customisations.
- Advantage: maximum control over architecture and functionality
- Disadvantage: implementation typically takes 3 to 6 months, sometimes longer
- Risk: without a clear end goal, a SharePoint project tends towards scope creep and overruns
- TCO element that is often overlooked: the governance role that must continue after launch
What consultancies charge for this varies widely by market and scope. What consistently comes back: the licence savings compared to Route 2 are often wiped out by build and maintenance costs over three years.
Route 2: Ready-to-go intranet on top of Microsoft 365
You choose a solution that runs on SharePoint, uses your existing Microsoft 365 tenant, and already brings the information architecture, templates, mobile app and governance. Involv intranet is exactly that – an omnichannel SharePoint intranet that brings all departments together, working within your existing Microsoft environment, with all data inside your own tenant.
- Predictable licence cost per employee per year
- Shorter implementation time, because architecture and components already exist
- Ongoing updates, support and new features included
- No migration: all data stays in your own SharePoint environment
The difference from Route 1 is not only in price, but in predictability. A fixed scope is easier for finance to budget than an open-ended build project.
Route 3: Do nothing
This is the most expensive route, and at the same time the least visible on your budget. You keep paying for your M365 licence. Employees keep searching. Communication stays fragmented.
For an organisation of 500 employees, the projected cost of search time alone adds up to €1.8 million over three years (3 × €600,000 based on 30 min/week). And search time is just one of the cost factors.
Three objections every CFO and IT director has
“We already have it – we’re already paying for M365.”
True. But M365 delivers different building blocks, not a working intranet. The cost of the three fragmentation layers above keeps running regardless of your licence. The question is not whether you’re already paying – the question is whether you’re getting value.
“Our IT department wants to build this themselves.”
That is a legitimate consideration. Building in-house gives control. The question is: what is the cost of building that knowledge, and what is the opportunity cost of IT capacity going here instead of to core systems?
Building an intranet on SharePoint is not hard to start. It is hard to finish properly: governance, adoption, mobile experience, analytics, ongoing development. Organisations that go down this path often end up choosing a ready-to-go solution after 12 to 18 months anyway – but with the cost of the initial build project added on top.
A hybrid approach also works: IT manages the SharePoint environment, a specialist solution delivers the intranet layer. That way IT doesn’t have to reinvent the wheel.
“What if Microsoft Viva builds what you offer themselves?”
This is the most strategic question, and the most honest one. Microsoft is actively investing in Viva Connections and the broader Viva suite. The possibility that Microsoft will deliver more on top of M365 in time is real.
What we know now: Viva Connections has existed for several years and still does not deliver a complete intranet experience for organisations of 200+ employees. The level of configuration, guidance and ready-to-use components you need to go live within four weeks is not something Microsoft offers today.
And even if Microsoft closes that gap in three years: you will have left three years of productivity gains on the table. The TCO calculation works in your favour if you act today.
Four questions every decision-maker must ask
- What is the Total Cost of Ownership over three years?
Not just the licence, but licence + implementation + maintenance + governance + adoption. Compare that figure against Route 1 and Route 3. - How quickly do you reach break-even?
An intranet that halves search time, speeds up onboarding and reduces HR tickets typically pays for itself within 12 to 18 months for mid-sized organisations. Calculate this with a ROI calculator based on your own figures. - Does our data stay within our Microsoft tenant?
For finance this is a compliance question, not a tech question. The answer must be “yes”: no separate SaaS tenant, no data outside your M365 environment. That is exactly how Involv intranet works. - What if we want to stop after a year?
Ask about contract terms, data ownership and the exit route. With a ready-to-go solution on SharePoint, your content stays in your own environment – no migration needed to walk away.
Conclusion: the cost is nowhere on paper, but it’s there.
Digital fragmentation rarely starts with a wrong decision. It grows from logical choices that together lead to a workplace nobody can oversee anymore. The bill – search time, communication overload, low engagement – does not appear on the balance sheet. But it grows every year, as long as the structure is missing.
Anyone making a well-founded decision as a CFO or decision-maker looks at Total Cost of Ownership over three years. And in that calculation, doing nothing is almost always the most expensive option, and a ready-to-go intranet on your existing Microsoft 365 foundation is the most predictable route.
Want to calculate this based on your own figures? Our ROI calculator gives you an estimate in two minutes based on your organisation size and average wage cost.
Is Microsoft 365 already an intranet?
No. Microsoft 365 delivers the building blocks for an intranet: SharePoint, Teams, OneDrive, Viva Connections. But an intranet is an experience – a central, findable, reliable information hub that works for all employees, including those without a fixed workstation. You build that experience on top of M365, not around it.
What does an intranet on top of Microsoft 365 cost?
The cost varies by route. A custom build on SharePoint has variable costs with an implementation time of 3 to 6 months or longer. A ready-to-go solution has a fixed licence cost per employee per year and a shorter lead time. A ROI calculator based on your own organisation size gives the most concrete picture.
Does my data stay within my Microsoft 365 tenant?
With Involv intranet: yes. The intranet runs within your existing SharePoint environment and all data stays within your own Microsoft tenant. There is no separate SaaS tenant and no migration needed.
How long does an implementation take?
With a custom SharePoint build, typically several months to a year depending on scope. With a ready-to-go solution like Involv intranet, typically a few weeks – because the information architecture, templates and components already exist.
Why aren't Viva Connections and Teams sufficient as an intranet?
Viva Connections is Microsoft’s intranet gateway within Teams: a powerful starting point, but not a complete intranet. Teams is built for collaboration within groups, not for broad one-to-many communication. For targeted communication, mobile access for frontline workers, policies, onboarding, alerts and analytics, both are complementary to an intranet, not a replacement.
Our IT department wants to build this themselves. Is that a good idea?
Building in-house gives control, but the real cost lies in finishing it properly: governance, adoption, mobile experience, development. Many organisations end up choosing a ready-to-go layer after an internal build. A hybrid approach – IT manages SharePoint, a specialist solution delivers the intranet layer – often gives the best of both worlds.
What if Microsoft Viva grows into a full intranet?
Microsoft is actively investing in Viva, but today still does not deliver a complete intranet experience for organisations of 200+ employees. Even if Microsoft closes that gap in the coming years, you will have left those years of productivity gains on the table. The TCO calculation works in your favour if you act today.
