What Is the ROI of Implementing an Intranet for a Mid-Sized Company?

Done well, the return on a first intranet is not subtle. It shows up within months, not years, and it shows up whether a company is standing one up for the first time or trying again after an earlier attempt quietly died from lack of use. What's harder to pin down isn't whether the ROI is real. It's how to put a number on it that survives contact with a CFO, because most of the value here shows up as time given back rather than revenue generated, and time has no fixed address until someone forces it to.

For a mid-sized company, somewhere in the 250 to 2,500 employee range, this question tends to come up in one of two situations. Either the company has grown past the point where Slack, a shared Drive, and institutional memory can hold everything together, and someone is proposing a first intranet from scratch. Or there's already something technically in place, inherited from a previous IT decision, that nobody actually uses, which for ROI purposes is functionally identical to having nothing. Either way, finance wants a number. Leadership wants a number. And whoever is championing the project, usually someone in internal comms, HR, or Ops, is left trying to translate "people can't find anything" into a figure a CFO will sign off on. It can be done. It just requires being honest about which numbers are independently verified, which are vendor-reported, and which are reasonable estimates built from your own headcount and salary data.

Why this is harder to calculate than it should be

The difficulty isn't proving the opportunity exists. It's that "we don't have an intranet" and "we have an intranet nobody opens" tend to get treated as different problems, when the underlying cost to the business is identical: information exists somewhere, but finding it depends on already knowing where to look, or knowing who to ask. Both situations get resolved the same way, and both get valued the same way once you sit down to do the maths.

The cost of not having one

Before getting to what an intranet returns, it's worth quantifying what its absence costs. Close to a fifth of the working week, 19.8%, is lost to employees simply searching for information they should already have access to, according to a widely cited figure originally published by Interact. That's the better part of one full working day every week, gone before anyone's actually done anything with it. 

A separate and more recent data point comes from a Harvard Business Review study of 137 employees across three Fortune 500 companies, which found that the average digital worker toggles between applications and websites nearly 1,200 times a day, costing each person almost four hours a week, or roughly 9% of their working time, simply reorienting after each switch.

McKinsey Global Institute's research remains one of the more cited pieces of work in this space for good reason: it found that better internal communication and collaboration tools could raise the productivity of interaction workers, meaning managers and other knowledge-heavy roles, by 20 to 25%. Their breakdown of where that time goes is telling. The same report found that interaction workers spend around 28% of their week on email alone, and close to a fifth of their time hunting for internal information or the colleague who might have it. None of that is new information to anyone who's worked in a mid-sized company with five different places content could theoretically live. What's useful is having someone else's research validate the frustration with a number attached.

There's also a headcount-scaling effect worth noting here, since it changes how the business case should be framed depending on company size. A KMWorld and eGain survey of more than 300 knowledge management practitioners found that 54% of organisations are already juggling more than five separate platforms just to document and share information internally, and that fragmentation tends to compound as a company grows past a few hundred people, not shrink.

When "we already have one" doesn't count

It's worth addressing the second scenario directly, because it's arguably more common than starting from nothing. A frequently cited Prescient Digital Media poll found that 31% of employees say they never use their company's intranet.

Separately, an IntraTeam survey found that fewer than 5% of organisations describe themselves as satisfied with their intranet or digital workplace "to a very large degree," with most landing at only "some degree" of satisfaction. The pattern behind this is usually the same: an intranet gets built once, often as a rushed add-on to a broader IT migration, content gets uploaded without much thought to whether anyone can find it, and within a year it's quietly reclassified as "the place old policies go to die." Once that reputation sets in, getting people to check it again is harder than getting them to use something new; they've already learned it isn't worth the click.

For ROI purposes, this matters because a dead intranet still shows up on the balance sheet as a cost. The company is paying for hosting, for whatever governance overhead exists, for the original implementation, and getting essentially nothing back, since employees have simply routed around it back into email, Slack threads, and asking a colleague. The honest way to frame this to a CFO isn't "we need to fix our intranet." It's "we are currently paying for a tool that delivers none of the returns described below, and the fix costs roughly the same as starting fresh would."

Where the returns actually come from

Employee engagement is where the ROI conversation tends to get its most defensible numbers, mostly because Gallup has been measuring this relationship for decades across hundreds of thousands of business units. The 11th edition of Gallup's Q12 Meta-Analysis, covering more than 183,000 business units, found a 23% difference in profitability and an 18% difference in productivity between top-quartile and bottom-quartile business units on engagement. Gallup's State of the Global Workplace 2025 report also puts a price on the alternative: declining engagement is estimated to have cost the global economy $438 billion in lost productivity in a single year. An intranet won't single-handedly fix engagement, of course; culture and management matter too. But it removes one of the more mundane sources of disengagement, the daily low-grade friction of not knowing what's going on or where to find the answer to something that should take thirty seconds.

Onboarding is another place the numbers show up quickly, and it's usually one of the first things a mid-sized company notices once a proper intranet is in place. Staffbase and USC Annenberg's 2024 Employee Communication Impact Report found correlations between structured internal communication and faster ramp-up times for new hires, largely because new employees stop having to ask five different people the same basic questions about benefits, tools, and who's who. For a company hiring even modestly, say 40 people a year, shaving even a few days off the time it takes someone to become fully productive adds up fast once you multiply it against a loaded salary.

IT support tickets are a quieter but genuinely underrated line item. When policies, processes, and "how do I request X" answers live in a searchable, governed space instead of scattered PDFs and tribal knowledge, the volume of basic support requests tends to drop meaningfully, freeing up IT time for work that actually requires IT. Tool consolidation compounds this further. Coveo's 2022 workplace research found that fragmented systems are a persistent drag on productivity, and the practical fix, an intranet that federates search across the tools a company already pays for rather than adding another silo, tends to reduce redundant software spend as much as it improves findability.

A worked example

Numbers land better with a concrete scenario, so here's one, built on assumptions stated plainly rather than dress up as fact. Take a mid-sized company of 500 employees with an average fully loaded salary of $65,000, which works out to roughly $31.25 an hour across a standard 2,080-hour working year. If even a conservative 5% of that time, well below the 19.8% Interact benchmark cited above, is recovered through better findability, that's about 104 hours per employee per year, or two hours a week, back in productive time. At $31.25 an hour, that's roughly $3,250 recovered per employee annually. Multiply that across 500 employees and the annual value of time recovered comes to approximately $1.6 million. Set that against an intranet's typical annual cost for a company that size, which will vary considerably by vendor and package but often lands somewhere between $10,000 and $50,000 depending on scope, and the payback period is usually measured in months, not years, even using deliberately cautious assumptions.

This is illustrative, not a guarantee. Actual results depend on adoption rates, how much duplicate work the intranet genuinely eliminates, and whether the organisation follows through on making it the actual source of truth rather than one more tool competing for attention. But the direction of the maths holds up even when you're conservative with every input, and it holds up whether the starting point is a blank slate or an old system nobody trusts anymore. The company with the abandoned SharePoint site isn't starting from a better position than the company with nothing; if anything, it has an extra job to do first, which is convincing people to give a "new" intranet a chance after the last one burned that trust.

The harder-to-quantify part

Some of the value here resists a spreadsheet entirely, and pretending otherwise would be a disservice. A single, trusted source of information changes how a company feels to work at, particularly for anyone hybrid or remote who doesn't get the incidental knowledge transfer that happens near a coffee machine. It reduces the quiet anxiety of not knowing whether you're looking at the current version of a policy. It gives leadership a way to be visible without another all-staff email nobody opens. None of that shows up neatly on a P&L, but culture affects retention, and retention has a very real, very calculable cost once someone leaves.

How Happeo fits into this

Happeo is built on Google Workspace, so for companies already living in Gmail, Drive, and Calendar, whether they're standing up their first intranet or have never quite trusted the term "intranet" after a bad previous experience, the search and findability gains described above aren't theoretical; they come from federating search across the tools people are already using rather than asking employees to adopt yet another destination. Happeo's own reported figures put average weekly usage at around 78%, and our G2 page shows a 4.5 out of 5 rating across more than 150 reviews, the kind of ongoing usage that a ghost-town intranet never manages to hold onto. Crucially, very little technical lift is involved in getting content live. Setting up a page, a channel, or a space is closer to building a slide deck than configuring software; there's no metadata to wrangle and no dependency on IT to publish an update. For a mid-sized company weighing whether the investment is worth it, that ease of setup is itself part of the ROI case, particularly for a greenfield buyer with no existing intranet team or governance model to lean on: the faster people can actually use the thing, the faster the productivity gains above start accruing rather than sitting on a six-month implementation roadmap.

Getting to your own number

If you're building this case internally, the most credible version of it combines external, independently verifiable research, the kind cited throughout this piece, with your own company's specific numbers: headcount, average loaded salary, current tool spend, and a conservative, defensible estimate of time currently lost to searching or duplicated effort. Resist the temptation to use the most dramatic stat available. A CFO will trust a cautious 5% productivity assumption backed by a citation far more than an aggressive 25% figure with no source behind it. The case for an intranet doesn't need inflating. The underlying data, and the daily experience of anyone who's ever spent twenty minutes looking for a document they know exists somewhere, already makes it.

If you'd rather run your own numbers than build the spreadsheet from scratch, Happeo's webinar, The First-Time Buyer's Guide to Choosing and Launching Your Company Intranet, walks through this exact process and gives access to Happeo's Knowledge Tax Calculator, a tool built specifically to put a number to the hidden costs your organization pays when people can't find what they need to do their work.