Insights
What is an intranet – and when does a smaller company need one?
A practical guide to what an intranet is, which everyday problems it solves, how it relates to the systems you already use, and when the need genuinely appears.
- Intranet
- Workflows
- Integrations
Published 2 September 2026 · Consitus
“Intranet” has been used for very different things over the years — from a static news page to a full internal platform. In practice, the useful definition is simple: an intranet is the internal system where employees find information, follow tasks and work to the same processes.
This guide is written for smaller companies. It covers what an intranet actually changes in day-to-day work, why integrations matter more than features, and how to tell the difference between a system that removes work and one that adds it.
Overview is the key word
If an intranet is only allowed one purpose, it is overview. Everyone involved should be able to see the same picture of a customer, a case, a document or a task — without asking a colleague, searching an inbox or opening three systems.
That matters because most delays in a smaller company are not caused by lack of effort. They are caused by information being one step away from where the work happens: the agreement is in an email thread, the price is in the accounting system, the status is in somebody's head.
What it means for the individual employee
For the person doing the work, an intranet should make the day simpler, not more documented. A good test is a single ordinary task: how many places do you have to look before you can answer a customer?
- The customer, the case and the documents are visible in the same view.
- Status is readable instead of something you have to ask about.
- Tasks have an owner and a deadline, so follow-up does not depend on memory.
- New colleagues can find their way without a guided tour.
Efficiency is only half the gain
The measurable gain is time: fewer clicks, fewer searches, fewer clarifying questions. The less obvious gain is motivation. Working in uncertainty is tiring, and constantly chasing information wears people down more than the actual work does.
Less friction, more real work
When people can see the whole picture themselves, energy goes into the professional work instead of into searching, asking and double-checking.
Shared workflows save more than time
The second reason to build an intranet is consistency. When a recurring task follows the same path every time — the same steps, the same fields, the same handover — the result stops depending on who happened to do it.
- Fewer mistakes, because steps are not skipped when things get busy.
- Less loss, because nothing falls between two people.
- Faster handovers, because the next person can see what has been done.
- Less dependence on individuals, because the process is not private knowledge.
Start with the workflows that hurt
Do not begin with the question “which system should we buy?”. Begin by describing one workflow that repeats every week and note where you switch systems, type the same thing twice, or cannot see status.
Integrations: an intranet should not replace everything
An intranet is not meant to take over your accounting system, your telephony or your webshop. Those systems solve their own jobs well, and replacing them is rarely where the value is.
The value appears when they are connected. Invoice status from accounting, calls from telephony and orders from the webshop become visible inside the workflow that uses them — so the information comes to the task instead of the other way round.
The webshop as a concrete example
A webshop already holds customers, orders and product numbers. What it usually lacks is a connection to the work that happens afterwards: picking and stock, service and repairs, complaints, and follow-up on customers who have not ordered for a while.
Without that connection the webshop is a system somebody has to remember to check. With it, the shop becomes a source for the workflows that drive the week.
Integration is a decision, not a detail
Whether your systems talk to each other — and in which direction — decides more often than anything else whether an intranet feels like help or like extra work.
Signs your company would benefit from an intranet
- The same information is entered in more than one system.
- Status can only be confirmed by asking a specific colleague.
- Important agreements live in email threads rather than on the case.
- Several versions of the same document are in circulation.
- Follow-up happens only when somebody remembers it.
- New employees spend weeks learning where things are kept.
- Holidays and sick days create real uncertainty about ongoing work.
If several of these sound familiar, the problem is usually not a missing system. It is that the systems you already have are not gathered around the work.
The biggest pitfall
An intranet must not become another layer on top of the others. If an employee has to register the same thing both in the new system and in the old one, work has been added rather than removed — and people will quietly go back to the old way.
The measure is simple: after implementation, a typical task should take fewer steps, fewer system switches and fewer questions than before.
A good intranet removes work
You can recognise one by the fact that people use it because it is the fastest route through the day — not because they were told to.
Next steps
Start by describing one workflow that repeats every week, and count the systems and lookups it requires today. Then read more about the custom-built intranet and about the digital workplace it becomes part of.
FAQ
Frequently asked questions
- What is an intranet, in short?
- An intranet is an internal system where employees find information, follow tasks and work to shared processes. The key word is overview: everyone sees the same picture of customers, documents, tasks and status.
- Is an intranet only relevant for large organisations?
- No. The need appears when information becomes scattered, not when a company reaches a certain size. Many companies with 5–50 employees gain more than a large organisation, because their day-to-day work runs on email, spreadsheets and the memory of a few key people.
- Should an intranet replace our accounting system or webshop?
- No. An intranet for small businesses rarely replaces accounting, telephony or a webshop. The value comes from integrating them, so data and workflows are gathered in one place and nobody has to log into five systems to understand a single case.
- What does it cost to get started with an intranet system?
- It depends on how many workflows the system has to support and which integrations are needed. A sensible starting point is the foundation everyone uses daily, and only then the modules that are unique to your business.
- How do we avoid the intranet becoming just another system?
- By making sure it removes work instead of adding it. If the same information has to be entered twice, something is wrong. A well-built intranet pulls threads together from the systems you already use and makes the daily task shorter, not longer.
Related pages
Related reading
Contact
Should day-to-day work live in one place?
Write a few lines about what you would like to work better. We will come back with an honest view of what can be done.