Custom Intranet vs SharePoint: What's Right for Your NZ Business?

SharePoint is the default answer when NZ businesses start talking about intranets. It's included in most Microsoft 365 plans, which means a lot of businesses already technically have access to it. The pitch is hard to argue with: "We're already paying for it."

But there's a big gap between "technically have access to" and "actually get value from." SharePoint is powerful — genuinely powerful — but it comes with real complexity, a significant learning curve, and a design philosophy that suits large enterprise environments more than small businesses. Understanding that gap is the starting point for making the right call.

What SharePoint Actually Is

SharePoint is Microsoft's enterprise content management and collaboration platform. It's been around since 2001, and the modern cloud version (SharePoint Online, part of Microsoft 365) is a serious piece of enterprise software. Thousands of large New Zealand businesses — banks, government departments, corporates — use it as their intranet backbone.

At its best, SharePoint is deeply integrated with the rest of the Microsoft 365 stack. It connects seamlessly with Teams, Exchange (Outlook), Azure Active Directory, and the rest of the Microsoft ecosystem. If your business runs entirely on Microsoft tools, SharePoint can be genuinely excellent.

At its worst, SharePoint is a complex platform that requires real expertise to configure well, produces interfaces that feel dated and unintuitive, and generates a lot of "why can't I find anything in here?" from staff who didn't choose it and weren't trained on it.

The Real Cost of "Free" with SharePoint

"It's included in our Microsoft 365 subscription" is technically true, but it's worth unpacking what you're actually getting for that.

A default SharePoint installation is essentially an empty container. To turn it into a working intranet, someone needs to design the information architecture, configure permissions, build the homepage, create the navigation structure, set up document libraries with sensible naming conventions, and then populate all of it with your actual content.

That work takes time — typically from a few weeks for a simple setup to months for something genuinely comprehensive. Either your team does that work (which means it's not free; it's just internal cost), or you hire a Microsoft partner to do it (which in NZ typically runs $5,000–$20,000+ depending on scope).

Then there's maintenance. SharePoint requires ongoing administration — managing permissions, updating the structure as your business changes, dealing with Microsoft's regular interface updates. Larger organisations have dedicated SharePoint admins. Small businesses often don't, which means it either gets neglected or falls on whoever is "best with computers."

None of this means SharePoint is the wrong choice — just that "it's included" understates what it actually takes to get value from it.

Where SharePoint Works Well

SharePoint is a strong choice when:

You're deeply embedded in the Microsoft ecosystem. If your team lives in Teams, uses Outlook for everything, and signs in with Azure AD, SharePoint's integration is seamless. Single sign-on, Teams tab integrations, and file sharing with OneDrive all work together naturally.

You have IT support. Whether that's an internal IT person or a managed service provider who handles Microsoft 365 for you, having someone who knows SharePoint reduces the ongoing friction significantly.

Your primary need is document management. SharePoint's document library functionality is mature and well-built. If your main requirement is a well-organised, searchable place to store files with proper permissions, SharePoint handles that well.

You have standardised processes that fit Microsoft's model. SharePoint has strong built-in functionality for news posts, pages, lists, and document management. If your intranet needs map closely to what these features do out of the box, you may not need much customisation.

Where Custom Intranets Win

A custom intranet starts from your requirements, not from a platform's capabilities. That distinction matters in a few specific situations:

You use a mix of tools, not all Microsoft. Many NZ businesses use Xero (not Microsoft accounting), Google Workspace (not Office), a non-Microsoft job management system, and so on. A custom intranet can integrate with all of these. It can pull job status from your service management system, show outstanding invoices from Xero, and display calendar events from Google Calendar — all in one place. That kind of cross-platform integration is awkward to build in SharePoint.

You need custom tools alongside the content. A leave request form, a maintenance issue tracker, a staff rostering view, a health and safety incident log — these are things a custom intranet can include as first-class features. In SharePoint, you'd build these with Power Apps and Power Automate, which are capable but have their own complexity and licensing considerations.

User experience matters to you. Custom intranets can be designed to be fast, clean, and genuinely pleasant to use. SharePoint can look polished, but it often requires significant design effort to get there, and the underlying UX can feel clunky compared to a purpose-built interface. If your goal is an intranet your team actually uses — not one they tolerate — the user experience difference often justifies the investment.

You want to own your platform. With SharePoint, you're dependent on Microsoft's decisions about features, pricing, and interface changes. Microsoft 365 plans have changed significantly over the past decade, and there's no guarantee they won't change again. A custom intranet is yours — no vendor lock-in, no licensing renegotiations, no surprise changes to features you rely on.

The Honest Cost Comparison

Let's put some rough NZD numbers on it.

SharePoint path: Microsoft 365 Business Standard costs around $22/user/month (mid-2026 pricing). For a 15-person team, that's ~$330/month or ~$4,000/year — but this covers email, Teams, Office, and more, not just SharePoint. Initial SharePoint configuration from a Microsoft partner: $5,000–$15,000. Ongoing admin time (internal or external): variable. Three-year total for the intranet-specific work: roughly $10,000–$25,000, plus staff time.

Custom intranet path: Build cost: $15,000–$35,000 for a small business intranet. Hosting: $50–$150/month. Maintenance: $500– $1,500/year. Three-year total: $18,000–$42,000, depending on scope.

The numbers aren't as far apart as people expect, especially once you factor in the real cost of SharePoint configuration and ongoing admin. For businesses where SharePoint is the right fit, it's a solid choice. For businesses where it isn't, paying a bit more for something that actually works for your team is often the better investment.

How to Decide

Ask yourself a few honest questions:

Does your team primarily use Microsoft tools? If yes, SharePoint is worth exploring seriously. If your stack is mixed, custom is probably better.

Do you have someone who can configure and maintain SharePoint? If yes, great. If not, the "free" option becomes expensive in staff time or consultant fees.

Do you need custom tools and integrations alongside your intranet content? If yes, custom gives you much more flexibility.

How important is user adoption? If your team needs something intuitive to actually use it, a custom-designed interface often wins.

If you're genuinely unsure, the best next step is a conversation with someone who can look at your specific situation — not a Microsoft salesperson or someone who only does custom development, but someone who'll give you an honest read on what fits your business. Sometimes the answer is SharePoint. Sometimes it's custom. Sometimes it's an off-the-shelf intranet tool that's neither. The right answer depends on your team, your tools, and what you actually need it to do.