Collaboration

SharePoint Intranet

Connect Your Workplace, Inspire Your People

Modern intranets that drive engagement and productivity.

See Intranet Examples

Key Capabilities

What SharePoint Intranet Delivers

Custom Branded Design

News & Announcements Hub

Employee Directory & Profiles

Document Libraries & Knowledge Base

Department & Team Sites

Mobile-Responsive Experience

What an intranet project costs

Clear ranges so you can plan a budget before the first call. Pick the tier closest to your situation.

Essential

A clean communications site with news, links and documents.

$1,600 to $4,000

one-time project

Get a fixed quote
Best fit for most organizations

Standard

A full intranet with workflows, forms and departmental sites.

$15,000 to $28,000

one-time project

Get a fixed quote

Enterprise

A multi-country intranet with integrations and governance.

From $65,000

one-time project

Talk to an expert
  • A range becomes a fixed price after a short scoping call. What moves a price: users and departments, data to migrate, integrations, and how much is configured versus built.
  • Optional annual support and managed governance starts at 18% of the project value per year (minimum $1,800). Changes after go-live are $85 per hour, or a prepaid 20-hour block for $1,600.
  • Prices exclude VAT (16% in Kenya) and withholding tax.

Not sure which fits? Tell us your team size and what you use today and we will point you to the right option.

Who this is for

  • Organizations where finding a policy, form or contact means asking a colleague, and where the answer depends on who you ask.
  • Distributed workforces across sites or countries, where internal communication currently means all-staff email nobody reads.
  • Microsoft 365 customers whose SharePoint exists but has become an unloved file dump.
  • Organizations onboarding regularly, where new staff spend weeks learning where things are.

What an intranet deployment covers

The technology is the easy part. An intranet succeeds or fails on information architecture and on whether anyone owns the content after launch.

  • Information architecture: how content is organized, named and found by someone who does not already know where it is.
  • Site structure, hub design and navigation, built around how people look for things rather than around the org chart.
  • News, announcements and targeted communication, so a message reaches the relevant site or department rather than everyone.
  • Policy and document libraries with ownership, review dates and version control.
  • Search configuration, which is what most people will actually use.
  • A content governance model naming who owns each area and how often it is reviewed.

How the engagement runs

  1. 1

    Discovery and architecture

    What content exists, who owns it, and what people are unsuccessfully searching for. Card-sorting with real staff beats an architecture designed in a workshop of managers.

  2. 2

    Design and build

    Structure, branding, navigation and templates configured, with a working site to react to early.

  3. 3

    Content migration and creation

    Content moves, is rewritten where it is stale, and is retired where it is obsolete. This is the heaviest part and it needs your people.

  4. 4

    Launch and adoption

    A real launch with communication, not a quiet URL change. Intranets that appear without announcement stay unvisited.

What you need in place

  • Microsoft 365 licensing covering SharePoint Online.
  • Named content owners per area, with the time to write and maintain. An intranet with no owners is stale within two quarters.
  • A decision on what does not migrate. Most existing intranet content is out of date and should be retired rather than moved.
  • Internal communications involvement. This is a communications product as much as a technical one.

Working with Sibasi on intranets

Why did our last intranet fail?

Usually because nobody owned the content after launch. An intranet is a product with an ongoing operating cost, not a project that finishes. The second most common cause is an information architecture built around the organizational chart, which only helps people who already know which department owns what, precisely the people who did not need the intranet. We design around tasks and questions instead, and we insist on named content owners before launch.

How is this different from just using Teams?

They do different jobs and work best together. Teams is for conversation and collaboration inside a group. The intranet is for authoritative, organization-wide content, the current policy, the approved form, the announcement everyone needs. Content that belongs in one is poorly served by the other, and the design should make the boundary obvious to staff rather than leaving them to guess.

Can we target content to specific groups?

Yes, and you should. Audience targeting means a site-specific announcement reaches that site rather than everyone, which is what stops staff tuning out internal communication altogether. It requires your directory groups to be reasonably accurate, so that is worth checking during discovery.

How long before staff actually use it?

That depends on whether the things people need daily are genuinely easier to find than before, and on whether leadership uses it. If the CEO announcement still arrives by all-staff email, the intranet is decorative. Launch planning covers this deliberately, because adoption is driven by where the valuable content lives rather than by training.

New to this category? What is an intranet?, a buyer's guide to what the category is, what to look for and how to compare options, whoever you end up choosing.

Let's put SharePoint Intranet to work for you

Talk to our specialists about your goals, timeline and budget.

Talk to an Expert