What is an intranet? Uses, features and the three ways to get one
An intranet is a private website that only a company's employees can reach. It holds company news, policies, forms, a staff directory and links to the systems people use every day. There are three ways to get one: buy an off-the-shelf intranet product, build it on SharePoint in Microsoft 365, or have a custom portal built that the company owns.

A private website for the people who work there
An intranet answers the questions employees ask every week: where the leave form is, who handles purchasing, what the travel policy says, what changed this month. Without one, those answers live in email threads, shared folders and the memory of long-serving staff.
The word is old, and so are many intranets. A page of links last updated three years ago is still an intranet, only a poor one. A current company intranet is closer to a working tool: it knows who you are, shows what is relevant to your role and site, and connects to the systems behind it.
This post covers what an intranet contains, what it is used for, a few example setups and the three ways to get one. It is part of our writing on internal systems that a company can own instead of renting.
Intranet, extranet and portal: the terms
| Term | Who can reach it | Typical content |
|---|---|---|
| Internet site | Anyone | Marketing pages, public information |
| Intranet | Employees only, after sign-in | News, policies, forms, directory, links |
| Extranet | Selected outsiders, after sign-in | Supplier documents, customer orders, shared projects |
| Intranet portal or employee portal | Employees only | Intranet content plus personal data and actions from other systems |
In daily use, “intranet”, “intranet portal” and “employee portal” overlap. The practical difference is depth. A basic intranet publishes content. A portal also lets people do things: submit a request, approve an expense, see a payslip.
What a company intranet is used for
Communication
Company news, management updates, new hires, events and safety notices. The advantage over email is that the content stays findable and can be targeted by site, department or role.
Finding documents and policies
The employee handbook, procedures, templates and forms, in one place with one current version. This is the use that removes the most repeated questions.
Finding people
A directory with name, role, department, phone, manager and photo, usually fed from the company’s user directory. An organization chart built from the same data.
Getting things done
Forms and requests: leave, equipment, travel, purchase approval, IT help. Each form starts a process that routes to the right approver. This is where an intranet meets business process automation.
A front door to other systems
Links, and ideally single sign-on, to payroll, the ERP, the help desk and the learning system. One address that every employee remembers.
Onboarding
A section for new staff with first-week tasks, required reading and the people to meet. It pairs well with automated account creation, described on our employee onboarding automation page.
Core features, as a checklist
- Sign-in with the existing work account, with no separate password
- A home page with news that can be targeted by audience
- Search across pages, documents and people
- A staff directory and organization chart synced from the user directory
- A document area with permissions and version history
- Forms that start an approval process
- A links area for internal systems
- Works on a phone, including for staff without a desk
- Permissions by group, so that content can be limited to a department
- Simple editing, so that HR and communications can publish without a developer
- Support for the languages and text direction the workforce uses
- Usage data, so that owners can see what is read and what is ignored
Features that are useful but not required on day one: social feeds, comments, recognition, surveys, an event calendar and an AI assistant that answers from the content. An assistant of that kind depends on clean, current documents. Our post on what a RAG chatbot is explains why.
Intranet examples, described as patterns
These are generic patterns and not descriptions of named companies.
A manufacturer with office and shop-floor staff. The home page shows safety notices and shift information first. Most staff reach it by phone or a shared screen. Forms cover leave, equipment and maintenance requests. The directory matters because people on different shifts rarely meet.
A professional services firm. The centre is knowledge: templates, past proposals, methods and client procedures, organized by practice area and found by search. News is secondary.
A company with several sites or countries. One global home page and a local page per site, with content targeted by location and language. Policies are marked global or local.
A fast-growing company. The onboarding section is the busiest part. The intranet is how a new hire in week one finds what longer-serving staff carry in their heads.
In each pattern the software is similar. What differs is which three or four things sit at the top of the home page.
The three ways to get an intranet
| Off-the-shelf intranet product | SharePoint in Microsoft 365 | Custom-built portal | |
|---|---|---|---|
| What it is | A ready product, usually by subscription | Sites and pages on a platform many companies already license | A system written for the company, which the company owns |
| Time to first version | Short | Short to medium | Medium |
| Cost shape | Recurring subscription plus setup | Licences often already paid, plus design and build | One-time build plus yearly maintenance |
| Fit to your processes | As far as the product’s settings go | Good for content, more work for applications | As specified |
| Where it runs | Usually the vendor’s cloud | Microsoft’s cloud | Your cloud or your own servers |
| Who changes it later | The vendor, within its roadmap | Your administrators or a developer | You or any developer you choose |
Off-the-shelf product
A dedicated intranet product comes with news, directory, forms and templates ready. It is the fastest route and the one with the least design work. The cost is a recurring subscription and the limits of the product. Setting one up well is still a project: structure, content, permissions, integrations and training. That work is what intranet software implementation covers. Shai implemented and ran an off-the-shelf organizational portal at an industrial company with about 400 users, so we know that side of the work from the customer’s seat.
SharePoint
If the company is on Microsoft 365, SharePoint is the default candidate, since the platform is already there. It handles news, pages, documents and search well, and integrates with Teams. Deeper custom features need development. See our post on the SharePoint intranet, with example page types and cost, and the basics in SharePoint vs OneDrive.
Custom build
A custom portal is written for the company’s own structure and processes. It costs more up front and has no subscription, it can run on the company’s own servers, and it can go as deep into HR, ERP and production systems as needed. It suits companies that are paying a large recurring fee for a product they use lightly, or that need the portal to do real work. That is our employee portal development service.
The cost logic for choosing between renting and owning is worked through in build vs buy software.
Why intranets fail
The software is rarely the cause. The usual reasons:
- No owner. Nobody is responsible for content, so it goes stale and people stop trusting it.
- Content was copied, not cleaned. Ten versions of the same policy were moved from the shared drive into the new site.
- Search returns noise. Without structure and current documents, search is useless, and search is how most people use an intranet.
- It does nothing. A site with only news is visited once. A site where people request leave is visited every week.
- It needs a separate login. Each extra password costs visits.
A named owner per section, a review date on every policy and one useful action on the home page prevent most of these.
What to do next
Write down the ten questions that reach HR and IT most often, and the five forms people ask for most. That list is the first version of your intranet’s home page, and it tells you whether you need a content site or a working portal.
If you are choosing a route, a scoping call with Shai covers the three options against your systems and budget. We implement products through intranet software implementation and build owned portals through employee portal development. Projects start at $25,000 at a fixed price per phase.