Intranet development is the planning, design and build of a private website or app where employees find company news, documents, policies, tools and each other. For small and mid-sized companies, the right intranet is usually not the biggest one: it solves the three or four daily frustrations staff actually have, fits the tools the company already uses, and is easy enough to keep current that it does not go stale within a year. This guide covers where to start, the choice between a custom intranet and a ready-made platform, what the work involves in practice, how to measure whether it works and the mistakes to avoid.
Last updated: 20 November 2026.
What is a company intranet today?
A company intranet is a private, signed-in space for employees. Early intranets were static pages of news and phone numbers. Today’s intranets are closer to a workplace front door: a single place to start the day, with announcements, search across documents, links to the tools people use, forms for common requests and a directory of colleagues.
For a company of a few dozen to a few hundred people, the intranet often replaces a tangle of shared drives, email attachments, chat threads and “ask Maria, she knows”. Its value is time saved and mistakes avoided: the right policy found in seconds, the latest version of a template, a holiday request that does not get lost.
At Odduel, a creative and technology agency in Barcelona and São Paulo, intranets and internal tools are part of our application development service, and they often grow out of a simpler question: where do our people waste the most time looking for things?
In short: start with staff interviews and a list of daily frustrations; check what your existing office suite already offers; choose a ready-made platform when your needs are standard and a custom intranet when they are not; build a focused first version; assign content owners; and measure use and time saved.
Where should a company start with intranet development?
Start with people, not features. A short discovery phase prevents the most common outcome: a polished intranet nobody opens.
- Interview a cross-section of staff. Office and field, new joiners and long-serving people, managers and individual contributors. Ask what they looked for last week and how long it took.
- List the top frustrations. Typical ones: finding the current version of a document, knowing who does what, requesting time off or equipment, keeping up with company news, onboarding new people.
- Map your existing tools. Email, office suite, chat, HR software, project tools, shared drives. The intranet should connect them, not compete with them.
- Define a few measurable goals. For example: fewer “where is” questions to HR, faster onboarding, one place for policies.
- Agree ownership. Who will publish news, keep policies current and answer questions about the intranet itself?
Only then decide on the platform and the features.
Custom intranet or a ready-made platform?
Many small and mid-sized companies already pay for an office suite that includes intranet features, such as SharePoint in Microsoft 365 or Google Sites in Google Workspace. There are also dedicated intranet products sold as subscriptions. The alternative is a custom intranet built for your company.
| Factor | Office suite intranet (SharePoint-type) | Dedicated intranet product | Custom intranet |
|---|---|---|---|
| Starting point | Often already licensed | New subscription | New build |
| Time to first version | Weeks | Weeks | A few months |
| Fit to your processes | Good for documents; workflows need configuration | Good for standard needs | Built around your processes |
| Integrations | Strong within the suite | Common connectors | Any system with an API |
| Design and brand | Templates, limited styling | Themes | Fully yours |
| Field and frontline staff | Requires suite accounts | Usually mobile apps | Designed for their devices |
| Ongoing cost | Included or per-user | Per-user subscription | Hosting, maintenance, improvements |
| Ease of maintenance | Needs a confident admin | Vendor-managed | Depends on the build and support |
When a ready-made platform is enough
Choose the office suite or a dedicated product when your staff all have accounts in that suite, when the main need is documents, news and a directory, and when nobody needs custom workflows or integrations with specialist systems. Spend the effort on structure, content and training rather than on code.
When a custom intranet makes sense
Choose a custom intranet when:
- Many staff work in shops, warehouses, kitchens, sites or on the road, without office accounts or desks.
- Daily work depends on specialist systems, such as production, booking, stock or field service software, that the intranet must show data from.
- You need workflows that off-the-shelf tools handle poorly, such as multi-step approvals specific to your business.
- The experience matters for culture and retention, and you want it to look and feel like your company.
- Per-user subscription costs would grow faster than the value as the company grows.
A hybrid is common: documents stay in the office suite, and a custom front end brings news, tools, forms and live data together on top of it.
What does intranet development involve in practice?
Whatever the platform, a successful intranet project has the same workstreams.
- Information architecture. A structure of sections and pages based on how employees think, tested with card sorting or simple click tests.
- Content. Migration and clean-up of policies, templates and guides, with an owner and review date for each.
- Design. A clear home screen, accessible components and a brand that feels like your company.
- Search. Good search across intranet pages and connected documents; poor search is the most common complaint about intranets.
- Identity and permissions. Sign-in through your existing accounts where possible, with content restricted by team, location or role.
- Integrations. Links or live data from HR, calendar, ticketing, project or operational systems.
- Mobile access. A responsive web app at minimum; a native app if frontline staff rely on it.
- Launch and adoption. Training, champions in each team and a reason to visit on day one.
For a custom build, add the usual software foundations: hosting in a suitable region, backups, monitoring, security testing and a release process. Our app development timeline explains how these phases fit together.
Which features should a first version include?
Keep the first version small and useful. A typical starting set for a company of a few dozen to a few hundred people:
- A home screen with news, upcoming events and the most-used links.
- A people directory with roles, teams, locations and contact details.
- Policies and guides in one searchable place, each with an owner and a date.
- Forms for common requests, such as time off, equipment, expenses or IT help, routed to the right person.
- Onboarding pages that walk new joiners through their first weeks.
- Search across all of the above.
Leave social features, complex dashboards and personalisation for later, once you know how people use the basics. For more ideas from other internal tools, see our business app examples.
How do data protection and accessibility apply to an intranet?
An intranet processes employees’ personal data: names, photos, roles, contact details and sometimes requests that reveal more, such as absences. The General Data Protection Regulation applies, and national labour rules in some countries add consultation duties with employee representatives when new workplace systems are introduced. Practical steps:
- Show only the personal data colleagues need; let people choose whether to add a photo.
- Restrict sensitive requests, such as sick leave, to the people who process them.
- Set retention periods and delete old requests automatically.
- Record the intranet in your records of processing, with processor agreements for hosting and email providers.
Accessibility matters too: employees with disabilities must be able to use the intranet as easily as anyone else. Designing to the W3C’s Web Content Accessibility Guidelines from the start, with keyboard use, clear headings, captions and good contrast, is far easier than fixing it later.
How do you measure whether an intranet works?
Decide on measures before launch, linked to the goals from discovery. Useful ones include:
| Measure | What it tells you | How to collect it |
|---|---|---|
| Active users per week | Whether people come back | Intranet analytics |
| Searches with no result | Gaps in content or poor search | Search logs |
| Requests submitted through forms | Whether processes moved to the intranet | Form data |
| “Where is” questions to HR and IT | Time saved for support teams | Ticket counts before and after |
| Onboarding time to productivity | Value for new joiners | Manager survey |
| Pages past their review date | Content health | Content inventory |
Combine numbers with a short staff survey a few months after launch. Ask what people still cannot find; the answers become the next round of improvements.
What are the most common intranet mistakes?
- Building for management, not staff. An intranet full of announcements and empty of useful tools gets ignored.
- Migrating everything. Moving every old file creates a search problem from day one. Clean first.
- No content owners. Without named owners and review dates, information goes stale and trust disappears.
- Ignoring frontline staff. If people without desks cannot use it on their phones, half the company is left out.
- Launching without a reason to visit. Day one needs something people want: a form that saves time, the new holiday calendar, useful onboarding.
- Choosing the platform first. The tool should follow the needs, not the other way round. Our guide on how to choose an app development company helps if you go custom.
Questions people ask
Where should a company start with intranet development?
Start by interviewing a cross-section of staff about what they looked for recently and how long it took. List the top frustrations, map the tools you already use, set a few measurable goals and name content owners. Only then choose between your office suite, a dedicated intranet product or a custom build.
Should we use SharePoint or build a custom intranet?
Use SharePoint or a similar office suite intranet when all staff have suite accounts and the main needs are documents, news and a directory. Build custom when many staff work without desks, when data from specialist systems must appear, when workflows are specific to your business, or when per-user costs outgrow the value.
What does intranet development involve in practice?
It involves discovery with staff, an information architecture tested with real employees, content clean-up with owners and review dates, interface design, search, sign-in and permissions, integrations with HR and operational systems, mobile access and a launch plan with training and team champions. Custom builds add hosting, security testing and maintenance.
How long does intranet development take?
An intranet on an office suite or dedicated product can launch within weeks if content is ready. A custom intranet with integrations usually takes a few months from discovery to launch. Content clean-up and decisions about structure and ownership often take longer than the technical build, so start them early.
How do you measure whether an intranet works?
Track weekly active users, searches with no result, requests submitted through intranet forms, the number of “where is” questions to HR and IT, onboarding time and pages past their review date. Add a short staff survey a few months after launch, asking what people still cannot find, and use it to plan improvements.
Ask ten colleagues what they searched for last week and how long it took; their answers are the brief for your intranet. If your needs go beyond what an off-the-shelf platform offers, see our application development service or tell us how your company works.


