Lyron
Microsoft 365

SharePoint Intranet Suite

Three to five coordinated web parts, a shared design system and a homepage your people actually open in the morning – rather than one forced on them as the browser start page.

Context

An intranet rarely fails on technology

Most intranets nobody uses are technically perfectly fine. They fail because the homepage answers not a single question somebody actually has in the morning: where is the form? Who is covering for my colleague? What happened to Tuesday's request?

So this project does not start with web parts but with a list of questions. Only once the five questions are clear does it become obvious which building blocks are needed at all – and which of them SharePoint already provides.

The second reason a suite differs from separate web parts is the foundation: shared components, shared spacing, one place for colours and type sizes. That costs a little more on the first block and makes every further one noticeably cheaper.

Use cases

What the homepage should answer

We start with the questions currently settled by shouting across the room. Everything else is kept for a second stage.

Biggest lever

What concerns me today

The block with the clearest benefit: open tasks, requests and deadlines – filtered to the signed-in person, not everyone.

My tasksOpen approvalsDeadlinesAbsences

Where do I find the form?

The most common question in any intranet. A quick access sorted by search term and department rather than folder structure.

FormsTemplatesPoliciesGuides

Who does what and who covers

A directory showing responsibility and cover – not just names and phone numbers.

ResponsibilityCoverLocationExtension

What matters

News sorted by relevance: mandatory reading at the top, nice-to-know below. With read receipts where they are needed.

Mandatory noticeDepartment newsRead receipt

What is coming up

Appointments, training, maintenance windows and absences in one view instead of four calendars.

AppointmentsTrainingMaintenanceLeave

For people without a desk too

Through Viva Connections the same homepage lands on a phone – for production, field service and shift work.

MobileViva ConnectionsMicrosoft Teams
Example

What the homepage looks like

A schematic of the finished composition. Marked in green is what gets custom-built – the rest comes from built-in features.

Greeting and searchPersonalised greeting, central search across documents and people.Built-in
What concerns meTasks, approvals and deadlines for the signed-in person, across several lists.Custom
NewsStandard news web part, sorted by audience.Built-in
Quick accessForms and templates, searchable rather than filed in folders.Custom
Dates and absencesFour calendar sources in one view, filtered by location.Custom
Who covers whomDirectory with responsibility and cover rules.Custom
Built-in Custom

Two of the six areas are built-in features. We make that split visible in the workshop before anything is built.

Illustrative layout. The ratio is the point: not every area needs custom development, and exactly that boundary determines the price.

How it works

How the suite comes together

  • Collect the five questions

    A workshop with people from different departments, not just communications. Which question do you ask yourself in the morning that you currently phone somebody about?

  • Separate built-in from custom

    News, search and document libraries are things SharePoint does. Anything joining several sources or depending on the sign-in becomes a custom web part. That split decides the price.

  • Design system first

    Before the first web part exists, components, spacing and colours are fixed. It sounds like a detour but noticeably saves time from the third block onwards.

  • Build the blocks and compose

    Three to five web parts, developed against your real data, then composed on the homepage. Interim versions are clickable.

  • Introduce rather than deploy

    An intranet that appears unannounced is ignored. We deliver a rollout plan, an editor handbook and training for the people who maintain it afterwards.

Impact

What changes day to day

Today

  • The homepage shows news and nothing else
  • Forms sit in a folder structure that grew over years
  • Responsibilities are clarified in the corridor or by chat
  • Four calendars, none of them complete
  • On a phone the intranet is practically unusable

With an intranet suite

  • The homepage answers the five most common questions
  • Forms are searchable rather than filed away
  • Responsibility and cover sit in one place
  • One overview of dates from several sources
  • The same homepage runs in Teams and on a phone
Limits

What a new intranet does not fix

The most common disappointment comes from an intranet project raising expectations it cannot meet. We state four of them up front:

  • It does not replace an editor. A good homepage needs somebody maintaining news and keeping forms current – one to two hours a week. Without that role you have a prettier intranet with the same outdated content a year later.
  • Disorder becomes more visible, not smaller. If documents sit in fifteen libraries with contradictory permissions, a search block shows exactly that. Sometimes the first project is the clean-up – we say so when we see it.
  • Not everything belongs on the homepage. The strongest lever in any intranet project is leaving things out. If every department gets a tile, the page ends up answering no question at all. We will be uncomfortable on this point.
  • Custom blocks need maintenance. Microsoft ships SPFx roughly quarterly and the move to React 18 is under way. A suite of five web parts is five times the maintenance of one – plan for it, with us or in-house.
Systems

Runs inside your Microsoft 365 environment

SharePoint OnlineViva ConnectionsMicrosoft TeamsMicrosoft GraphEntra IDPower AutomateMicrosoft 365 Copilot
Scope and price

Scope and price

The entry price covers three to five blocks including the design system and homepage. What moves the price, we say before the quote.

from €5,900 one-off
  • Workshop: which questions should the homepage answer?
  • Separating built-in features from custom development
  • Design system with reusable components
  • Three to five custom-built SPFx web parts
  • Building and composing the homepage
  • Surfacing through Viva Connections on Teams and mobile
  • Rollout plan, editor handbook and training (up to 2 hours)

What increases the price

  • More than five blocks or several homepages per location
  • Connection to systems outside Microsoft 365
  • Multilingual with separate editorial content per language
  • Migrating content from an existing intranet
  • Third-party accessibility audit against WCAG

Several homepages per location or multilingual editions typically land in the range of our Workflow Enterprise package from €5,900 upwards. We quote the binding fixed price after the workshop.

All prices excl. VAT · maintenance and the React 18 migration optionally via a support package

Included

What you get

  • Complete web part suite

    All blocks signed, deployed to the app catalog and composed on the homepage

  • Design system as a foundation

    Reusable components that make every later block cheaper

  • Editor handbook

    How content is maintained and blocks configured – without developer knowledge

  • Rollout support

    Introduction plan plus 60 days of support during the phase that decides whether it gets used

Questions & answers

Frequently asked questions about the intranet suite

Because of the foundation. Separate projects mean three sets of styling, three build pipelines, three implementations of permission logic. In a suite that happens once. At three blocks the cost is roughly equal; from the fourth the suite is noticeably cheaper – and it looks like one product rather than a collection.
Usually fewer than the first workshop asks for. Our experience: three well-made blocks answering real questions beat seven that each satisfy one department. We prioritise together and keep the rest for a second stage once the first runs.
Yes, and often that is the better route. If the structure and permissions hold up, we replace only the homepage and add blocks. A full rebuild mainly pays off when the site structure itself is the problem.
That is what Viva Connections is for: the same homepage appears in Microsoft Teams and on a phone. What matters is planning for it from the start – blocks designed for a large screen rarely shrink sensibly after the fact.
Your editors, and that is deliberate. Whatever experience says will change sits in the property pane of the blocks or in ordinary SharePoint lists. For the technology behind it – SPFx versions, the React 18 migration – there are our support packages.
Considerably less than the first, because the design system and build pipeline exist. Another web part on an existing foundation typically comes in below the entry price of a single web part at €1,900.
Related solutions

These solutions fit alongside

SharePoint Web Parts with SPFx

The entry point with a single block, when the homepage is not the priority yet.

SharePoint Copilot Apps

The same data additionally as an agent in Microsoft 365 Copilot.

SharePoint Migration

When the move off SharePoint Server comes before the new intranet.

Automated Employee Onboarding

The most common process behind an intranet homepage.

Which five questions should your homepage answer?

In the free intro call we collect them together. In our experience two of them can already be solved with built-in features – and that is exactly what we will tell you before quoting.

Book a free intro call
arrow_back Back to all products