How to choose intranet software: off-the-shelf product, SharePoint or custom build
Choose intranet software by route first and by vendor second. An off-the-shelf product fits standard needs and a short timeline, SharePoint fits companies already licensed for Microsoft 365, and a custom build fits company-specific processes, on-premises requirements or a subscription that is large for what it delivers. Write the requirements, count the 5-year cost of each route and test a shortlist with real content before signing.

Choose the route before the vendor
Searches for intranet software lead to long lists of products with star ratings. Those lists skip the first decision, which is the kind of solution. There are three routes, and they differ in cost shape, ownership and how far they can be adapted. Once the route is clear, the shortlist is short.
This post does not rank or review vendors. Where products are named, they are examples of a category only, with no claims about their features or prices.
For the basics of what an intranet is and what it contains, see what is an intranet. For the wider category of systems a company can own instead of renting, see internal systems.
The three routes
Route 1: an off-the-shelf intranet product
A dedicated product, usually sold by subscription and hosted by the vendor. It arrives with news, directory, pages, forms and templates ready. Examples of the category include Simpplr, Staffbase and Blossom. Some products in this category run on top of Microsoft 365 and others are independent of it.
You get speed and a finished design. You accept a recurring fee, the vendor’s roadmap and the limits of its settings.
A product still has to be implemented: structure, permissions, content, integrations with the directory and HR system, training. That project is what our intranet software implementation service covers. Shai implemented and ran an off-the-shelf organizational portal for an industrial company with about 400 users.
Route 2: SharePoint in Microsoft 365
A platform many companies already license. It is strong at publishing, documents and search, and ties into Teams and the company directory. A standard intranet needs configuration only. Custom features need development. Details and cost components are in our post on the SharePoint intranet.
You get an intranet with no new subscription if every user is already licensed. You accept the platform’s page model and the need for governance.
Route 3: a custom-built portal
A system written for the company, which the company owns. It can run in your cloud or on your own servers, connect as deeply as needed to HR, ERP and production systems, and has no per-user fee.
You get an exact fit and ownership. You accept a higher first-year cost, a maintenance budget and the need for an internal owner. This is our employee portal development service.
A fourth, lighter option exists for small teams: a wiki or knowledge base tool used as the intranet. Confluence and Notion are examples of that category. Used this way, the intranet is a set of searchable articles. Personal data, approval chains and a synced directory usually have to come from other systems.
Decision table
| Question | Off-the-shelf product | SharePoint | Custom build |
|---|---|---|---|
| Are all employees licensed for Microsoft 365 | Not required for independent products | Required | Not required |
| How fast is a first version needed | Weeks | Weeks to a few months | A few months, in phases |
| Are needs standard: news, documents, directory, simple forms | Good fit | Good fit | More than needed |
| Does the portal show personal HR, payroll or ERP data | Depends on available connectors | Needs custom development | Good fit |
| Must it run on your own servers | Rarely possible | Only with SharePoint Server | Good fit |
| Are there many frontline staff without company accounts | Check the product’s licensing model | Each user needs a licence | No per-user fee |
| Is there an internal owner with technical support | Helpful | Needed | Required |
| Cost shape | Subscription plus setup | Existing licences plus project | One-time build plus maintenance |
| Who controls changes | The vendor | You, within the platform | You |
| Exit | Export and rebuild elsewhere | Content stays in your tenant | You own code and data |
Read the table by columns that fail. A route with one hard failure, such as an on-premises requirement that a hosted product cannot meet, is out no matter how well it scores elsewhere.
Requirements checklist
Write the answers before speaking to any vendor. A product demo is much more useful when you bring your own list.
People and access
- Number of users today and expected in three years
- Share of staff without a desk, a company email or a company device
- Sign-in method: the existing work account, with single sign-on
- Languages and text direction, including right-to-left if needed
- External users such as contractors, and what they may see
Content
- Who publishes news and who approves it
- Volume and state of existing documents and policies
- Targeting by department, site or role
- Search across pages, files and people
- Review dates and owners for policies
Processes
- The ten most frequent employee requests, with monthly volume
- Which need an approval chain, and where the manager data comes from
- Personal data to display: leave balance, payslips, attendance
- A manager view for approvals
Integrations
- User directory
- HR and payroll systems
- ERP or finance
- Help desk
- Document storage
- For each: API, file export or neither
Security and compliance
- Where the data is hosted and in which country
- Permission model by group and role
- Audit log of access to personal data
- Backup and restore, and who is responsible
- What happens to access when an employee leaves
Commercial terms
- Pricing basis: per user, per tier or flat
- What is billed outside the subscription: setup, support, changes, integrations
- Price terms at renewal
- Contract length and notice period
- Data export format and help with leaving
Ownership after launch
- A named owner for the intranet
- An owner for each section
- Who handles technical changes
- How usage is measured
Count the cost over five years
A subscription that looks modest per month is a large number over five years. Compare the routes on the same basis:
| Cost line | Product | SharePoint | Custom build |
|---|---|---|---|
| Licence or subscription | Yearly fee times five | Zero if already licensed, or the licence gap | None |
| Setup or build | Implementation project | Structure, design, content, any custom code | The build, by phase |
| Integrations | Connectors or custom work | Custom development | Part of the build |
| Support and changes | Vendor support plan, paid change requests | Internal admin or outside help | Yearly maintenance |
| Internal time | Owner and authors | Owner, authors, administrator | Owner, authors, technical contact |
| Exit | Migration at the end of the contract | Low | Low |
One company’s figure, for scale: an industrial company with about 400 users paid about 100,000 NIS a year for an off-the-shelf organizational portal, of which about 70,000 was the product and 30,000 was support. That is roughly $31,000 a year, or about $155,000 over five years at a flat price. It is one company’s figure and not a market price.
Put your own numbers in the table. The method, with a worked example and the cases where buying wins, is in build vs buy software.
How to run the selection
- Write the requirements. Use the checklist. Mark each item as required or optional.
- Pick the route. Use the decision table. Remove any route with a hard failure.
- Shortlist two or three options within the route. No more.
- Ask for a demo of your scenarios. Give each vendor the same five tasks, for example: publish a news item to one site only, find the travel policy, submit a leave request, approve it as a manager on a phone, remove a leaver’s access.
- Run a pilot with real content. One department, real documents, real users, two to four weeks.
- Check the exit. Ask for a sample export and read the contract terms on renewal pricing.
- Decide on the 5-year number and the pilot feedback. A feature list is the weakest input of the three.
Mistakes to avoid
- Choosing by feature count. Most employees use search, the directory and three forms. Extra features add cost and clutter.
- Skipping the content work. Every route fails with stale content.
- No owner. The tool does not maintain itself.
- Ignoring frontline staff. If half the company cannot sign in, it is a head-office site.
- Underestimating integrations. The connection to HR and the manager chain is where projects slip.
- Signing a long contract before a pilot. A month of real use tells you more than any demo.
What to do next
Fill in the requirements checklist and the 5-year table for your current situation. In most cases that leaves one or two routes standing.
If the result is a product, we run the project through intranet software implementation. If it is a system you own, Shai scopes and builds it through employee portal development. Projects start at $25,000 at a fixed price per phase, and we will tell you if the numbers favor a route we do not sell.