“We got our IT folks to build our Intranet and… This Is What We Got”: When SharePoint Isn’t the Core Capability

Posted on by

TL;DR

  • Paying $25k for an intranet isn’t the problem. Paying it to a team where intranets aren’t their core capability often is.
  • Having a bit of know-how means you  can build something in SharePoint, but building a useful, scalable intranet is a specialist skill set.
  • When intranets aren’t the core skill, organisations usually end up with something that exists but doesn’t get used.
  • The real cost isn’t the build. It’s low adoption, workarounds, and rebuilding later.
  • The best outcomes happen when generalists and intranet specialists work together, each doing what they’re best at.

A little while ago, we spoke with an organisation that was… frustrated. That quiet, disappointed kind of upset.

They’d paid around $25,000 for a new intranet, delivered by their generalist IT provider.

And the result?

Technically, it existed. Practically, it didn’t help. Emotionally, it felt like a let‑down.

Their words were simple and honest:

“I guess you really do get what you pay for. And you pay for what you get.”

That sentence stuck with us. Not because it was harsh, but because it’s something we hear a lot.

And usually, it’s not about money at all.

Generalist IT Providers Aren’t the Problem. Misaligned Expectations Are

Let’s say this upfront: good IT providers are incredibly valuable. We partner with some great teams who are excellent at their job. They keep the lights on. They keep you secure. They make sure things don’t fall over at 9:07am on a Monday.

But here’s the tricky bit.

Building a great intranet in SharePoint is not the same skill as:

  • Managing devices
  • Handling tickets
  • Provisioning users
  • Keeping systems secure

It’s a different muscle.

Many generalist IT providers can build something in SharePoint.

Very few specialise in designing, structuring, and shaping SharePoint so it works for humans.

That difference matters more than people realise.

Just Because Someone Can Do SharePoint…doesn’t mean they should

This is where the gap usually shows up.

Yes, IT:

  • Knows SharePoint
  • Can create sites
  • Can build libraries
  • Can deploy pages

But if SharePoint isn’t their core capability, the intranet often ends up:

  • Technically correct
  • Functionally basic
  • Conceptually thin
  • Painfully hard to scale

It’s a bit like asking a general GP to perform heart surgery. They’re both doctors.

One does this all day, every day.

What $25k Often Buys (When Intranets Aren’t the Focus)

When intranets aren’t the primary craft, that budget usually goes into:

  • Pages that look fine but don’t solve real problems
  • Navigation that reflects organisational structure, not user thinking
  • Little to no information architecture
  • No content model, no governance plan
  • And a quiet handover that sounds like: “You can tweak it from here.”

And of course, you can tweak it. For the next 3-5 years. With frustration slowly compounding.

The Real Cost Isn’t the Build. It’s the Aftermath

This is the part that stings for most organisations.

It’s not the $25k. It’s:

  • Low adoption
  • Staff going back to email and shared drives
  • Leaders are wondering why “no one uses the intranet”
  • A rebuild two years later that costs more than doing it properly once

That’s when the phrase “you get what you pay for” shows up. But a little too late.

So… Should You Never Get someone who knows a bit of SharePoint to Build an Intranet?

Not exactly.

But you shouldn’t expect someone with a bit of skill to deliver a strategic digital workplace unless:

  • Intranets are a core offering
  • They do this repeatedly, not occasionally
  • They talk about information architecture, governance, and user behaviour. Not just features
  • They work with a partner who knows intranets like the back of their hand

The best outcomes usually happen when you bring in SharePoint Intranet specialists to focus on what they’re brilliant at.

The Takeaway (Without the Guilt Trip)

If you’re thinking about an intranet, ofcourse cost is a consideration, but you must also consider :

“Is building intranets the core thing this team does?”

SharePoint is a platform. But an intranet is a product, an experience, and a trust layer.

Frequently Asked Questions

Is $25k a reasonable price for a SharePoint intranet?

It can be, if the money is going into the right things. A quality intranet investment usually covers discovery, information architecture, governance, user experience, and long‑term scalability. When those areas are skipped, even a cheaper build can end up costing more over time.

How do we choose the right partner for an intranet project?

To find the right partner you need the right fit. These questions usually surface that quickly:

  • Is intranet work a core part of what they do?
    Not “we’ve done a few”, but something they deliver regularly and deliberately.
  • Do they start with how people work, not just what SharePoint can do?
    Look for early conversations about users, information needs, and behaviours, not features or layouts.
  • Can they clearly explain their approach to information architecture and governance?
    If the answer sounds vague or overly technical, that’s often a red flag.
  • Do they talk about life after launch?
    Good partners plan for ownership, content upkeep, and adoption, not just go‑live day.
  • Are they honest about where they don’t specialise?
    Teams who readily collaborate with MSPs, internal IT, or other specialists tend to deliver stronger outcomes.
  • Can they describe a successful intranet without leading with visuals?
    If success is measured only by how it looks, usability and trust may be an afterthought.

You don’t need the biggest provider or the cheapest quote. Just a team whose main muscle matches the job you’re hiring them to do.

 

Are IT consultants bad at building intranets?

IT teams are excellent at keeping environments secure, stable, and supported. Intranets, however, sit at the intersection of information design, user behaviour, and organisational trust, which isn’t always their core focus. The issue isn’t capability, it’s specialisation.

What usually goes wrong with generalist‑built intranets?

Common patterns include:

  • Navigation designed around IT structures, not how people work
  • Little or no information architecture
  • No governance or ownership model
  • A “handover and hope” approach post‑launch

The result is often low adoption and quiet frustration rather than obvious failure.

Can SharePoint be a great intranet platform?

Absolutely, SharePoint is a powerful platform, but it doesn’t become a great intranet by default. Success depends on how it’s structured, governed, and aligned to real employee needs, not just features being turned on.

Should organisations avoid generalist IT providers for intranet projects?
Yes, if they don’t have specialist skills:

  • IT providers tend to focus on platform health, security, and support
  • Intranet specialists focus on structure, usability, governance, and adoption, all the ingredients needed for a great intranet.

What should we ask before choosing someone to build our intranet?

Instead of starting with price, ask:

  • Is intranet work a core part of what you do?
  • How do you approach information architecture and governance?
  • How do you design for adoption, not just launch day?
  • What happens after go‑live?

The answers to those questions matter more than the number on the proposal.

Sources