Try this before you finish your coffee: ask five colleagues to open the company intranet right now, from memory, no searching. Count how many actually can. The pause you're imagining is the entire problem — and no amount of redesigning the homepage carousel is going to fix it.

Here's the uncomfortable truth I've watched play out at company after company. Most intranets aren't broken. They're abandoned. Someone spent a quarter building a polished landing page with a rotating banner and a "Message from Leadership," everyone dutifully clicked through it during onboarding, and then it quietly became the digital version of the supply closet — full of useful things, visited only when something has already gone wrong.

This is the first post in a three-part series on using Confluence as your intranet. Before we get into spaces, databases, and the mechanics of building the thing (that's Part 2) or keeping it alive once it's built (Part 3), I want to start somewhere less glamorous and more important: why the old intranet died, and the one thing Confluence quietly gets right.

Why your last intranet flatlined

Traditional intranets fail for a reason that has nothing to do with how they look. They fail because they're a separate place. The work happens in one set of tools, and the "information" lives somewhere else entirely — a destination you have to remember to visit, maintained by a team that owns it in name only. Content goes stale because updating it means leaving the tools you actually use. Nobody can find anything because search was an afterthought. So the bookmark withers, and people just ask in chat instead.

Meanwhile, the cost of all that hunting is real. McKinsey has put the share of the workweek that knowledge workers spend simply searching for and gathering information at close to a fifth. That's a full day a week, per person, lost to "where is that document?" An intranet is supposed to be the answer to that question. Most of them are just another place to look.

The thing Confluence gets right

Confluence starts from a different premise, and it's a deceptively powerful one: your teams already live here. The meeting notes, the project specs, the runbooks, the decision logs — for a lot of organizations, that's already in Confluence. So an intranet built on Confluence isn't a new destination bolted onto the side of your work. It sits directly on top of the source of truth your teams are already creating every day.

That single shift changes the maintenance math. Content stays fresh because the people who own it are already in the tool. The HR space that holds your policies is the same place HR works. The engineering runbook your intranet links to is the live one — not a copy someone forgot to update in 2023. You're not maintaining a separate showroom. You're putting a front door on the house everyone already lives in.

Company Hub: the front door, built in

That front door has a name: Company Hub. It's a customizable, company-wide landing page available on Confluence Cloud's Premium and Enterprise plans, and the reason I like it as a starting point is that it asks almost nothing of you. It's built directly into Confluence — no add-ons, no Marketplace apps, no advanced configuration. App and site admins set it up (and can delegate editing to people across departments, so HR, IT, and Comms each curate their own corner), and most teams can stand up a genuinely useful version in a day or less.

You get a top links menu for the evergreen stuff people reach for constantly — payroll, PTO requests, the org chart, the brand kit, the on-call rotation. You get spotlight modules for the messages that actually matter this week, cards and carousels for grouping related resources, and your own name, logo, and colors so it feels like your company rather than a generic template. Worth noting for the admins reading this: Company Hub now lives inside Rovo Studio, alongside automations and assets, which is where Atlassian has been consolidating the platform's building blocks.

A little honesty before you get excited

Because we don't do hype around here, two caveats. First, Company Hub specifically is a Premium-and-up feature — but using Confluence as an intranet isn't gated behind that. Even on Standard, you can build a perfectly serviceable intranet out of spaces, customizable homepages, and space blogs (more on that in Part 2). The Hub is the polished front door; the house works without it.

Second, set your expectations honestly. Out of the box, Company Hub is a clean, functional entry point — not a pixel-perfect, multi-brand, fully personalized portal. If your comms team's north star is a heavily designed, marketing-grade experience, you may eventually want a Marketplace app layered on top. But here's what I tell clients: the goal of an intranet was never to be a museum. It's to be the place people actually start their day and actually find what they need. On that score, "built into the tool you already use" beats "beautiful but abandoned" every single time.

The Avaratak Take

An intranet doesn't earn its keep by looking impressive in a launch announcement. It earns its keep on a random Tuesday, when a new hire needs the expense policy and finds it in eight seconds instead of firing off a chat message and waiting twenty minutes. The reason we steer clients toward Confluence here isn't that it has the flashiest homepage builder — it's that it removes the fatal flaw of the old model. When your intranet and your work live in the same place, "keeping it current" stops being a heroic act of will and becomes a side effect of doing the job.

Start with the front door. Point Company Hub at the five things your people need most, and resist the urge to boil the ocean. The architecture underneath — the spaces, the databases, the search that makes it all findable — is where the real leverage hides, and that's exactly where we're headed next.

In Part 2, we'll build out the rooms behind that front door: how to structure spaces so your intranet scales instead of sprawls, how to bring in content you've already got without a painful migration, and how Rovo turns the whole thing into an intranet you can simply ask.

If you'd rather not draw up the blueprint alone, that's literally our job. As an Atlassian Solution Partner, Avaratak helps teams turn Confluence from a document graveyard into the place work actually starts. Come say hello at avaratak.com.