Skip to content
home

SharePoint Intranet Business Case: How to Get It Approved

Most intranet proposals fail for the same reason: they sell technology to people who are buying an outcome. Leaders don't approve "a SharePoint intranet". They approve less time wasted, fewer mistakes, faster onboarding and less risk. This is how I help clients write a business case that gets a yes, using evidence from their own company instead of borrowed statistics.

Quick answer

How to write a SharePoint intranet business case leaders approve: the problems to show, what to measure first, costs to include, and a one-page outline.

Daniel AwokunleDaniel AwokunleUpdated 13 November 2026 6 min read
Watch first: the whole guide in 100 secondsWatch on YouTube
Video transcript

Your intranet idea keeps getting a not now? Here's how to write a business case that gets approved.

Meet James, operations director at Brightwater Foods. He asked for an intranet because people can't find anything. The answer: we already have shared drives. Let's revisit next year.

First, start with problems people already feel. Search for the travel policy, and you get six versions. Which one is right? Nobody knows.

Second, measure your own company before you ask for anything. A short survey and one real quote from a manager are more convincing than any industry statistic.

Third, sell the outcome, not the technology. Not hub sites, but one current policy, found in seconds.

Fourth, show what you already own. Most Microsoft 365 plans include SharePoint. Then list the real costs honestly: people's time, planning, migration, training, and upkeep.

Fifth, the risk of doing nothing. Messy permissions mean Copilot can surface files nobody should see.

Sixth, ask for a pilot, not a big bang. Agree the success measures first, then prove it.

And keep it to one page. Problem, evidence, outcome, pilot, cost, risk, and the decision you need.

Approved.

The full guide, with a one-page outline you can copy, is free at winstack365.com.

1. Start with problems people already feel

Before you mention SharePoint, list the everyday problems your staff complain about. These are the ones I hear most:

  • People can't find the latest version of a policy, form or price list, so they ask a colleague or use an old copy.
  • New starters spend their first weeks asking where things are.
  • Company news goes out by email and gets buried.
  • Files live in personal drives, email attachments and an old file server, so nobody knows which copy is right.
  • When someone leaves, their files and know-how leave with them.

Pick the three that cost your business the most. A short list that everyone recognises is more convincing than a long list of features.

2. Measure the current state before you ask for anything

Decision makers trust numbers from their own company far more than industry figures. You can gather useful evidence in a week without any tools:

  1. Run a five-question survey: how long it takes to find a document, how often people use an out-of-date version, and where they look first.
  2. Ask three new starters what they struggled to find in their first month.
  3. Count the places documents live today: shared drives, Teams, email folders, personal OneDrive.
  4. Ask IT how many requests they get for access to folders and for lost files.
  5. Note any recent mistake caused by an old document, such as a wrong price or an outdated procedure.

Write down what you find exactly as people said it. One real quote from a manager often does more than a chart.

3. Describe the outcome, not the technology

Turn each problem into a result someone can picture. For example: "Every policy has one current version, in one place, that anyone can find in seconds." Or: "A new starter has everything they need on one page on day one."

Keep SharePoint in the background. It matters to IT, but the board is approving the result. Save the technical plan for an appendix.

4. Show what you already own

Most organisations on Microsoft 365 business or enterprise plans already pay for SharePoint, Teams and OneDrive. An intranet is often about using licences you already have properly, rather than buying a new product.

Check your plan in the Microsoft 365 admin center under Billing. If SharePoint is included, say so clearly in the business case. It changes the conversation from a new purchase to getting value from an existing one.

5. List the real costs honestly

A business case that hides costs gets rejected later. Include all of them:

  • Time from your own people: a content owner per department and a project lead.
  • Planning: site structure, navigation and permissions designed before anything is built.
  • Build and migration: creating the sites and moving the right files, not everything.
  • Training and launch: short sessions and a simple guide for staff.
  • Running costs: who keeps news and pages up to date once it's live.

If you use a consultant, ask for a quote that breaks these down. A single number with no detail makes your business case harder to defend.

6. Include the risk of doing nothing

Leaders often say yes to reduce risk rather than to gain something. Spell out what happens if nothing changes: sensitive files shared too widely, staff working from outdated documents, knowledge lost when people leave, and a messy file structure that makes Microsoft 365 Copilot unsafe to switch on later.

That last point matters now. Copilot can surface anything a user is allowed to open, so cleaning up structure and permissions is groundwork you will need anyway.

7. Propose a pilot, not a big bang

Ask for approval to build one area first, such as HR or onboarding, and measure it against the evidence you gathered in step 2. A pilot is easier to approve, it shows quality early, and it turns your business case into proof.

8. A one-page outline you can copy

Keep the main document to one page. Put detail in an appendix.

  1. The problem: three problems in plain English, with one real quote.
  2. The evidence: what you measured in your own company.
  3. The outcome: what will be true after launch.
  4. The approach: a pilot area first, then the rest in phases.
  5. What it needs: people's time, budget lines and a named owner.
  6. The risk of doing nothing.
  7. The decision you're asking for, and by when.

If the reader only gets to the bottom of page one, they should still know exactly what they're approving and why.

Want this done for you?

I build this for clients every week. Book a free 30-minute call and I'll tell you exactly what your team needs.

Free: the Microsoft 365 clean-up checklist

The 12 checks I run before building anything in a client's tenant: security, sharing, files and quick wins. Two pages, PDF.

Used only to send the checklist and the odd useful tip. Never shared or sold.

Daniel Awokunle · replies within a day

Tell me what's slowing your team down.

Thirty minutes, no cost, no pitch deck. You'll leave knowing exactly what to build and what it should cost.

Book a free 30-min call
  1. Step 1

    Free 30-min call

    Show me the problem. I'll tell you what I'd build and how long it takes.

  2. Step 2

    Clear quote

    A fixed price and timeline in writing, usually within a day.

  3. Step 3

    Built and handed over

    Built in your own Microsoft 365, with a walkthrough for your team.