Custom intranet development: when to build instead of buying an off-the-shelf intranet

Build a custom intranet when it has to be more than an internal newsletter: the front door to your company's requests and workflows, a tool frontline staff can use without a desk or a work email address, or a single entry point that pulls together your HR system, ERP and rosters. If what you need is internal news, a staff directory and shared documents, the office suite you already pay for, or an off-the-shelf intranet, will do it better, faster and for less.

Most pages about custom intranet development are written by agencies selling builds or by vendors selling packaged intranets. This guide does not push either by default. It helps you work out which situation you are in.

Two very different tools share one name

"Intranet" covers two tools, and confusing them causes most bad decisions.

The communication intranet publishes: leadership updates, a staff directory, an org chart, reference documents, department pages, events. People read it. This is what packaged intranet products do best.

The services intranet gets things done: ordering equipment, booking a room or a vehicle, reporting an incident, checking a roster, approving an expense, tracking a request, opening every company application with one login. People use it. This is where generic products hit their limits, because every company routes work differently.

If your project is mostly the first kind, buy. If it is mostly the second, read on.

Four options

The options combine. A pattern that often works: the office suite keeps documents and email, and a custom internal application runs the services and workflows behind the same single sign-on. Employees see one front door.

When a custom build pays off

Part of your workforce has no desk and no work email

Cleaners, warehouse pickers, field technicians, retail and site staff: in many companies a large share of employees has neither a computer nor a work address. Licensing a full office suite for each of them is expensive, and the tool is not designed for them anyway. A custom intranet can offer simple phone login, screens cut down to what matters (roster, payslip, safety instructions, time-off request) and work on a weak connection. Our guide to web apps, PWAs and native apps helps you pick the right format.

The intranet has to run your workflows

Internal requests rarely follow a standard path: approval by the site manager, then by a director above a certain amount, a heads-up to facilities, an update to the equipment inventory. A packaged intranet gives you forms. It does not know your rules. When requests currently live in email threads and spreadsheets, a custom intranet can replace them with clear, tracked, measurable workflows, the same logic as replacing Excel with a custom application.

It has to connect the systems you already have

Employees want to see their leave balance (in the HR system), their shifts (in the scheduling tool), their site's instructions and the documents for their role in one place. If off-the-shelf connectors do not cover your systems, the intranet becomes one more island. A custom intranet is built around your sources, each remaining the system of record for its own data. See our guide to integrating a custom app with your ERP.

Your organisation is a network

Several legal entities, franchisees, branches, subcontractors who see part of the content: permissions become fine-grained, by entity, site and role. It is close to the multi-site back office problem, and it is better handled by a structure designed for it than by stacked groups and exceptions.

The data is sensitive

Occupational health information, HR data, confidential documents: you may want to choose the hosting provider, the hosting region and the logging policy rather than accept a vendor's defaults.

When not to build a custom intranet

• Your need is internal communications: packaged intranets are built for it, with years of user feedback behind them.
• Everyone already has an office suite account that includes intranet features: use them before adding another tool.
• You are a small team in one office: a well-organised shared drive and a team chat are often enough.
• Nobody will own it: an intranet without an owner goes stale, bought or built.

What each path costs

Packaged intranets are sold by subscription, usually per user per month, sometimes with a minimum. Cost therefore follows headcount, including frontline staff who open it once a week. Add configuration, content migration and training for contributors.

A custom intranet has no per-user fee. It has an upfront design and build cost, driven by the number of services and integrations, then hosting and maintenance. The larger the workforce and the more specific the workflows, the more competitive it becomes. For the factors that move a quote, see custom business application cost. You do not have to pay it all upfront either: custom software can also be funded through a monthly subscription.

Employee data and worker representation

Data protection. An intranet holds personal data: names, roles, contact details, sometimes absences or rosters. Under the GDPR and similar laws, that means retention periods, role-based access, informing employees and documenting the processing. Our GDPR checklist for business applications lists what to plan for.

Photos in the directory. Treat staff photos as optional: let each person choose whether to add one and remove it at any time, and make sure profiles work perfectly without a picture. Employment relationships make freely given consent hard to demonstrate, which is why regulators such as the French CNIL ask employers for a clear, documented agreement.

Works councils. In several European countries, employee representatives must be involved before certain tools go live. In Germany, the works council has co-determination rights over the introduction of technical systems designed to monitor employee behaviour or performance (section 87(1) no. 6 of the Works Constitution Act). In France, article L2312-38 of the Labour Code requires the CSE to be informed before automated HR processing is introduced, and informed and consulted before tools that can monitor employee activity. An intranet that manages absences or rosters, or tracks usage per person, can fall into these categories. Build the consultation into your timeline and check your own case with legal counsel.

Security essentials

• One login: single sign-on through your company directory where it exists, simple and robust authentication for frontline staff otherwise.
• Leavers: accounts disabled on the day someone leaves, ideally triggered automatically by the HR system.
• External users: temps and contractors see only what concerns them, with an end date.
• Confidential documents are never reachable through a simple shared link.

What about AI search?

The most common complaint about intranets is that nothing can be found. An assistant that answers staff questions from internal documents (procedures, policies, safety instructions) is realistic today, on two conditions: it must only show each person documents they are allowed to see, and every answer must cite its source so it can be checked. Our guide to RAG for business documents explains how. Keep it for a second release: it is only as good as the documents it reads, which means content owners have to keep them current.

The most common mistakes

• Starting with the homepage and the news feed instead of the services people will use every week.
• Copying the org chart into the menu: employees look for a task, not a department.
• Migrating everything at once, including ten years of outdated files.
• Forgetting frontline staff, then finding half the workforce never logs in.
• Launching without content owners: six months later, nothing is up to date.
• Forgetting employee representatives and having to delay the launch.

How to tell whether it is working

Page views say little about an intranet. Track instead what shows it has become part of the working week:

• the share of internal requests submitted through the intranet rather than by email or phone;
• weekly active users per group, office and frontline separately, so a silent half of the workforce cannot hide behind a healthy average;
• the time it takes to process a request from submission to approval;
• outdated content: pages past their review date, per owner.

Set these four indicators before launch and review them after the first month. They tell you which service to build next, and whether the intranet is earning its maintenance budget.

A four-step method

1. List the internal requests that currently go through email, phone or spreadsheets, with their volume and approval path.
2. Interview people from each group, office and frontline: what they look for, what they keep asking for, what wastes their time.
3. Define a short first release: login, directory, two or three high-volume services, the reference documents. Our software requirements document guide helps you write it.
4. Roll out site by site or team by team, measure use, then add the next services.

Before committing a budget, let the people who will use the screens try them. We build a free prototype, presented on a video call within 5 working days, so a team leader and a frontline employee can click through their screens before anything is developed. The idea is explained in see your software before you pay.