SharePoint

What a SharePoint intranet in 30 days really looks like

By Edward Pinela — Microsoft-certified consultant · August 5, 2026

A working SharePoint intranet in 30 days is achievable — if you define “working” honestly. In one month a small or mid-sized organization can launch a home site, a news framework, four to six department sites, and Viva Connections in Teams. What you cannot do in 30 days is migrate every file share, build custom applications, and reach full adoption. This article separates the two, week by week, so you can commit to a launch date without setting yourself up to miss it.

What fits inside the first month — and what does not

A 30-day intranet build covers structure, branding, core content, and the Teams experience: a home site with global navigation, a news publishing model, department hubs, a policies library, and a Viva Connections dashboard. It deliberately excludes bulk file migration, custom web part development, and multilingual publishing, which are scoped as follow-on phases with their own timelines.

The distinction matters because most stalled intranet projects die from scope, not technology. SharePoint Online provisions sites in minutes; what consumes calendar time is deciding the structure, gathering content from busy department heads, and getting sign-off. Cap the launch scope and hold the line: a lean intranet that ships beats a comprehensive one that is perpetually 80% done.

The week-by-week plan

Here is the schedule we use for a typical 20–500-employee organization. Each week has a hard exit criterion — if you have not met it, fix that before moving on, because slippage compounds:

Why Viva Connections belongs in the launch scope

Viva Connections puts your intranet inside Microsoft Teams as a dashboard, feed, and resource list, and its core experience is included with Microsoft 365 plans — no additional license for a standard launch. Including it in the first 30 days is the single highest-leverage decision in the plan, because it removes the “remember to visit the intranet” problem entirely.

Configuration is genuinely fast once the home site exists: designate the home site, build the dashboard cards, and pin the app in Teams via a policy. Microsoft's Viva Connections documentation (opens in new tab) covers the setup steps and requirements. Worth noting for planning: Microsoft continues to fold Viva Connections management into the SharePoint admin center through 2026, so administration keeps getting simpler. If your staff live in Teams all day — and in most SMBs they do — publishing news where they already are is the difference between an intranet people read and one they forget exists.

What honestly takes longer than a month

Three things reliably outlast the 30-day window, and pretending otherwise is how launch dates die. First, file migration: moving a decade of shared-drive content deserves its own project with inventory, cleanup, and wave planning — our file server to SharePoint migration guide walks through that timeline separately. Second, adoption: deployment frameworks in wide use treat 30 days as the foundation phase and 90 days as the realistic adoption horizon; organizations that skip champions and role-based training routinely see usage plateau at a fraction of staff. Third, governance maturity: naming standards and a provisioning process should exist at launch, but retention policies and content lifecycle rules are refined over the following quarter — and because staff will create teams faster than they create sites, the rules for Teams sprawl, naming, and guest access deserve their own pass rather than being folded into the intranet build. Well-governed content pays off again later, too — it is the foundation a Copilot deployment depends on, as we cover in our Copilot data governance article.

The five decisions that decide your launch date

Almost every delay traces back to an unmade decision rather than an unfinished task. Settle these five in week one and the rest of the month is execution: who owns the intranet after launch; whether news is published centrally or by each department; which three tasks staff must be able to complete on day one; what the top-level navigation says, in plain language, in seven links or fewer; and who has final say when two departments disagree about placement.

Write the answers down and circulate them. The document is short — a single page — but it is the artifact that lets you say no in week three without reopening the debate. Teams that skip it end up relitigating navigation during content loading, which is precisely when a 30-day plan becomes a 90-day one.

Doing it in-house versus bringing in help

An in-house build on this plan is realistic if someone on your team has built a SharePoint information architecture before and can protect a quarter of their time for a month. If nobody has, the usual failure mode is not a broken intranet but a six-month one. This is exactly the shape of project we deliver as a fixed-fee SharePoint consulting engagement: senior US-based engineers, a scope agreed before work starts, typical 2–4 week delivery, and 30 days of hypercare after launch while habits form. Pricing is scoped after a free consultation — here is how the fixed-fee process works, and what drives the cost of a SharePoint intranet covers the scope, content, and governance variables behind that number. Either way, the plan above is the same one we would run; the only variable is who runs it. Plan for month two as well: whoever owns the intranet after launch inherits permission drift, version and storage growth, search that needs reindexing and flows that fail quietly, all of which our SharePoint support and maintenance engagement handles as scoped work rather than a retainer.