Intranet solutions: five shapes and how to pick one

TL;DR. “Intranet solutions” is one phrase covering at least five different products. A full employee-experience suite, a communication platform, a SharePoint-based hub, an all-in-one workspace, and a team wiki are not interchangeable — they serve different needs and bill very differently. Match the shape to what you actually run, not to the longest feature list. For the written-knowledge part of an intranet — docs, runbooks, decisions, onboarding — a fast wiki is the shape, and the good ones import your old one in about ten minutes.

Search “intranet solutions” and you’ll get a ranked list of thirty-five products, all scored as if they were running the same race. They aren’t. An intranet is supposed to be the digital version of a building with a lobby, a noticeboard, an HR desk, and a library. Most vendors sell you the whole building when you walked in for the library.

So this post skips the leaderboard. The useful question isn’t which intranet is best — it’s which shape fits the job you actually have. Below: a plain definition, the five shapes the category ships in with real examples, what the good ones get right, how to choose, and the one case where you should buy the whole building after all.

What an intranet solution actually is

An intranet solution is private software that gives a company one internal place to communicate, share documents, and find people and information — accessible to employees, closed to everyone else. Modern ones are cloud-hosted, browser-based, and mobile-friendly, with search, permissions, and role-based content at the core. The term predates the cloud by a decade; what changed is the scope. (For the plain definition without the shopping, our what an intranet is explainer is the sibling to this page.)

That scope is exactly why the category splinters. “One internal place” quietly bundles four jobs that used to be four products: broadcasting company news, running HR and people workflows, launching the other apps people use, and storing the written knowledge a team reads. Treat those as one purchase and you’ll buy a heavyweight platform to solve a lightweight problem — or the reverse. A Gartner market view of packaged intranets lists dozens of vendors precisely because no single shape fits every org.

The five shapes of intranet solution

The category ships in five recognisable shapes. The shape is the decision; the brand inside the shape is a footnote.

1. The employee-experience suite. The whole building. Company-wide news, an HR and people portal, an employee directory, an app launcher, personalised feeds, and enterprise governance — all in one. Microsoft Viva with SharePoint, Unily, and LumApps live here. The right fit for large organisations that need to broadcast at scale and prove who read what. Heavy by design, and priced like it.

2. The communication platform. Built to reach people, especially the ones without a desk. News feeds, surveys, recognition, and a mobile-first app aimed at frontline and deskless staff. Staffbase, Simpplr, and Workvivo fit here. Best when your problem is the warehouse never sees the memo, not engineering can’t find the runbook.

3. The SharePoint-based intranet-in-a-box. A pre-built layer that sits on top of Microsoft 365 so you don’t assemble a hub out of raw SharePoint by hand. Powell, Involv, and Omnia fit here. The natural move when your company already lives in Microsoft 365 and you want an intranet that inherits its permissions and single sign-on.

4. The all-in-one workspace doubling as an intranet. Docs, databases, and a light internal hub in one surface. Notion and Confluence get pressed into intranet duty constantly by smaller teams. Fine until the home page becomes a wall of links nobody maintains and the database-as-document model buries the docs you came for.

5. The team wiki — the knowledge layer. Not the whole intranet: the part that holds written knowledge your team reads and edits. Docs, runbooks, decision records, onboarding. Fast, searchable, multiplayer, organised into spaces with named owners. Raccoon Page fits this shape, alongside Slite and Nuclino. Best when the knowledge is prose and the readers are your own team.

Here’s the same five mapped to what you mainly need an intranet to do:

What you mainly need	Right shape	Examples
Broadcast news, HR portal, app launcher for a large org	Employee-experience suite	Microsoft Viva, Unily, LumApps
Reach frontline and deskless staff on mobile	Communication platform	Staffbase, Simpplr, Workvivo
An intranet bolted cleanly onto Microsoft 365	SharePoint-based	Powell, Involv, Omnia
Docs plus a light internal hub for a small team	All-in-one workspace	Notion, Confluence
Fast, searchable written knowledge your team reads	Team wiki	Raccoon Page, Slite, Nuclino

Pick the row, then pick the tool. Most of the regret in this category comes from buying across the wrong row — a suite priced for a thousand people to serve a team of twenty, or a wiki asked to run an HR onboarding workflow it was never built for.

What every good intranet solution gets right

Whatever shape you land on, a short list separates the ones that get used from the ones that become an expensive screensaver on the meeting- room TV.

1. People can find things. Search that returns the right page on the first try, typo-tolerant and scoped to what each person is allowed to see. A hub you can’t search is a filing cabinet with the labels removed.
2. It loads before attention wanders. If opening the intranet costs a spinner and a layout shift, people route around it to whoever sits nearest. Speed is an adoption feature, not a vanity metric.
3. Permissions you can target. Org, space, and page-level access with named roles — not just “internal” versus “public.” Half of what an intranet is for is showing the right people the right things.
4. A real editor for the written parts. Code blocks, callouts, tables, inline comments, full Markdown — a documentation editor, not a notes app wearing a tie.
5. Mobile access that isn’t an afterthought. Especially if any of your team is deskless. A desktop screenshot stretched to fit a phone is not a mobile app.
6. An export you’ll probably never use but should always have. Your content in a portable format, on demand. The hub you can leave is the one worth committing to.

Skip the top of that list and nobody opens the thing. Skip the bottom and you’ve signed a lease you can’t break.

How to choose an intranet solution

A short, boring procedure that beats reading another ranked list:

1. Name the main job first. Broadcast, frontline reach, Microsoft 365 integration, a small-team hub, or written knowledge. The answer picks your row from the table above before you open a single pricing page.
2. Count the people who’ll actually use it. Twenty knowledge workers and two thousand deskless staff are different purchases. Buy for the people, not the org chart.
3. Test it on your real content. Not the polished demo space — your actual messy docs. A tool that imports cleanly in ten minutes has earned the next call.
4. Search your own stuff. Type the half-remembered title you’d actually type on a Tuesday. If it finds the page, keep going.
5. Check who owns each section. A space with a named owner gets maintained. A space without one becomes the museum nobody dusts.
6. Confirm you can leave. Export everything in a format another tool can read. If you can’t, you’re not choosing a solution; you’re choosing a landlord.

Run those in order and most of the shortlist eliminates itself before the first sales call. If your main job turned out to be written knowledge, our corporate wiki guide and the knowledge management platform breakdown go deeper on that one row; the SharePoint alternatives post covers the Microsoft-ecosystem decision specifically.

When the whole intranet suite is the right call

The honest part, because a vendor that only ever says “yes, us” is the one to distrust. Sometimes a wiki is the wrong tool and a full intranet suite is exactly right.

If your real need is company-wide broadcast — mandatory-read campaigns with reach analytics, a personalised news feed for ten thousand people, an HR portal wired to payroll and time-off, an employee directory, an app launcher, and a mobile push that reaches the loading dock — then buy an employee-experience suite or a communication platform. That is not what Raccoon Page does, and pretending otherwise would waste your budget and our credibility. We’re the knowledge layer: spaces, labels, a real editor, fast search, real-time co-editing, version history, and an MCP surface for agents. We don’t broadcast HR announcements, and we never will.

What plenty of teams discover, though, is that the knowledge half of their intranet was the part everyone actually opened — and the news feed was a noticeboard nobody read twice. If that’s you, you don’t need the whole building. You need the library, fast. Sub-second loads. Keyboard-first. The Confluence importer moves a typical space — page tree, attachments, the common macros — in about ten minutes, and Raccoon Page Free is $0 for three users, one space, and a hundred pages, no card. Team is $8/user/month and Business is $15/user/month when you outgrow it. Run the wiki next to the suite, or instead of one you never needed.

Things people actually ask

What is an intranet solution? Private software that gives a company one internal place to communicate, share documents, and find people and information, accessible to employees and closed to outsiders. Modern intranet solutions are cloud-hosted and mobile-friendly, with search, permissions, and role-based content at the core. In practice the phrase covers five product shapes — employee-experience suites, communication platforms, SharePoint-based hubs, all-in-one workspaces, and team wikis — that do genuinely different jobs.

How much do intranet solutions cost? It depends entirely on the shape. Mid-market platforms commonly run roughly $7–12 per user per month, while full enterprise employee- experience suites climb far higher once setup, migration, and training are added on top. For the team-wiki shape specifically, Raccoon Page Free is $0 for three users, one space, and a hundred pages, no card; Team is $8/user/month and Business is $15/user/month. Budget for the job, not the longest feature list.

Which intranet solution is best for Microsoft 365? If you’re committed to the Microsoft ecosystem, a SharePoint-based intranet-in-a-box — Powell, Involv, Omnia — or Microsoft Viva on top of SharePoint inherits your existing permissions and single sign-on. If the part you struggle with is fast, searchable written documentation rather than the broadcast layer, a dedicated wiki alongside it often serves the docs better than SharePoint does alone.

What’s the best intranet solution for a small business? For a small business, the heavyweight suites are usually overkill and overpriced. The honest answer is often the all-in-one workspace you already use, or a fast team wiki for the written knowledge. Start on a free tier, get one space genuinely used, and add broadcast or HR tools only when you can name the specific job they’d do.

Do I still need a separate intranet if I already have SharePoint? Often, no — raw SharePoint can be the intranet, and an intranet-in-a-box makes it usable without custom builds. Where teams add a second tool is the written-knowledge layer: if engineers and operators can’t find the runbook fast, a dedicated wiki next to SharePoint fixes that one job without ripping out the rest.

Is a wiki the same thing as an intranet? No. A wiki is one shape of intranet — the written-knowledge layer. A full intranet can also include company news, an HR portal, a directory, and an app launcher, which a wiki doesn’t do. Many teams find the wiki is the part they actually use daily, but the two are not synonyms.

Can AI agents use an intranet solution? Only the ones with a real API behind the buzzword. Tools that expose an MCP surface — Raccoon Page ships one on every plan — let an agent search, read, create, update, and label pages with the same audit trail your humans get. “AI-powered” on a feature card with no API behind it is a demo, not a capability.

---

Intranet solutions aren’t one product with one winner. They’re a building with several rooms, and the trick is buying only the rooms you walk into. Name the job, count the people, test the import. If the room you keep returning to is the library — the written knowledge your team actually reads — bring the one you already have; the Confluence importer handles a typical space in about ten minutes, and Raccoon Page Free is three users, one space, a hundred pages, no card. Buy the building if you need it. Otherwise, just take the library, and make it fast.