SharePoint intranet redesign services for the intranet you already have

What this engagement covers

A redesign starts from the intranet you already have. The tenant, the sites and much of the content stay; what changes is how it is organized, how it looks, how people find things and why they would come back. Deliverables are a written diagnosis of the current intranet, a restructured set of hubs and navigation, a rebuilt home page and news setup, page templates with written standards, a content clean-up with an approved archive list, search tuning for the queries staff actually run, named owners for each site, and a relaunch plan. Work is done remotely by senior US-based engineers from our Orange County, CA base, serving every US state, at one fixed price agreed after your free consultation.

The typical buyer launched an intranet a year or three ago, sometimes with an agency, sometimes in-house. It looked good on day one. Since then news stopped being posted, department pages went out of date, the navigation grew by accretion, and staff now ask colleagues where a policy lives instead of looking. Nothing is broken in a way a support ticket would catch. It simply goes unused.

Redesign, new build or ongoing support

Three different jobs get called “fixing the intranet”, and choosing the wrong one wastes the budget. If there is no intranet yet, or the existing one is built on classic pages that cannot be modernized, you need a new build, and our guide to launching a SharePoint intranet in 30 days lays out that plan week by week. If the intranet works and people use it but small things keep breaking, that is SharePoint support and maintenance. A redesign sits between them: the platform is sound, the experience is not.

If you need all of it, a full build with document libraries, migration and training, our SharePoint intranet and document management consulting engagement covers the whole platform, and redesign work can be folded into it.

What the diagnosis usually finds

Every unused intranet has its own history, but the causes repeat. The first week is spent confirming which of them apply to yours, so the fixed fee pays for the problems you actually have rather than a generic rebuild. The table shows the symptoms we look for, what usually sits behind them, and what the redesign changes in response.

Restructuring hubs and navigation without moving everything

Structure is the layer most redesigns have to touch, and the one most likely to disrupt people if it is done carelessly. Microsoft’s guidance on planning SharePoint hub sites (opens in new tab) describes the model we work to: a flat set of sites grouped by hubs, each hub carrying shared navigation, branding and a common search scope. Because hub association is a setting rather than a location, regrouping sites changes what people see without changing any URL they have saved.

So the order of work is deliberate. New hubs, hub navigation and site associations go first, because they move nothing underneath. Content clean-up and site consolidation follow one department at a time, with the owner confirming each step. Where the problem runs deeper than the intranet, into document libraries, content types and metadata, that work belongs to SharePoint information architecture consulting, the structure layer of a redesign, and the two are often scoped together.

Page standards, search and the home page

Once the structure holds, the pages themselves are brought into line. A page standard is a short written document: which templates exist, what every page must include, how long a news post should be, and who approves what. The templates enforce most of it automatically. The home page is rebuilt last, because it should point at a structure that already works rather than paper over one that does not.

Search improves mostly as a side effect of the clean-up. When superseded pages are archived and the remaining ones have clear titles and descriptions, the current version stops competing with three outdated copies. We then check the queries staff most often type and fix what still lands badly. Microsoft documents how to request a recrawl of a site or library (opens in new tab) after large changes, which we use so the results reflect the new structure rather than the old one.

Planning the relaunch

A redesigned intranet that nobody is told about stays unused. The relaunch plan is a deliverable, not an afterthought: a short announcement from leadership, the intranet pinned where people already work in Microsoft Teams, a first month of news already drafted so the home page is not empty on day two, and training for site owners on the templates and standards they now own. Putting the home site inside Teams is done with Viva Connections, and Microsoft’s Viva Connections documentation (opens in new tab) covers what it adds and what it requires.

Who this fits

The usual fit is a small or mid-size organization on Microsoft 365 with a modern SharePoint intranet that stopped earning its keep. Common triggers are a new internal communications lead who inherited it, a merger that doubled the number of department sites, a leadership team asking why the intranet costs time and delivers nothing, or a Copilot pilot that surfaced how much outdated content is sitting in it.

It is a poor fit in two cases, and we will say so during the consultation. If the intranet is built on classic SharePoint pages and subsites, redesigning in place costs more than building fresh, so a new build is the honest recommendation. And if staff do use the intranet but a few things need fixing, you need support work rather than a redesign.

Delivery in three phases

The table shows scope and timeline rather than prices, because an honest fee depends on how many hubs, sites and pages are involved. Our fixed-fee process explains how the fee is set and what is agreed before any work starts.

Everything produced belongs to you from day one. The diagnosis, the page standards, the templates and the configuration all live in your own Microsoft tenant, never in ours.