SharePoint intranet in-a-box: what it is and how to choose one in 2026

Most of the evaluations we get pulled into have the same problem. The buyer has correctly worked out that native SharePoint will not stretch far enough for them, and is now comparing four products they have been told are SharePoint intranet in-a-box solutions - two of which are not built on SharePoint at all - against a feature grid that says nothing about the thing most likely to matter in five years.

The category is badly defined, and it has changed more than most buyers realise. Products that would have topped a shortlist five years ago are no longer sold. The key thing to understand before you start comparing is that in this market the vendor's position matters as much as the product's feature list.

In summary

• A SharePoint intranet in-a-box product is a layer of software that installs into your own Microsoft 365 tenant and extends SharePoint with features intranet teams need, rather than replacing it.
• It is distinct from a standalone intranet platform, which hosts your content outside Microsoft 365 and integrates back in.
• Products in the category split into two shapes: modular products that add a defined set of components to SharePoint, and full platforms that replace much of the SharePoint experience with their own.
• The differences that matter at evaluation are architectural and commercial, not feature counts: where code and data sit, how much duplication you are paying for, whether the editing experience stays familiar, who does the information architecture and design work that no product does for you, and how likely the vendor is to still be investing in the product in five years.
• Vendor continuity is a real risk in this category and it is under-discussed. Established products have been acquired and then withdrawn from sale.

What is a SharePoint intranet in-a-box product?

A SharePoint intranet in-a-box product is a pre-built software layer that installs into your organisation's own Microsoft 365 tenant and extends SharePoint Online with the capabilities intranet teams typically need - richer news and communications, personalisation and audience targeting, branding control, content governance tooling, and page templates - without requiring custom development. Products in this category include Lightspeed365, Origami Connect, Powell Intranet and Omnia. All four run on SharePoint rather than alongside it, and all four are bought as products rather than built as projects.

The defining characteristic is architectural. An in-a-box product uses Microsoft's own extensibility framework, the SharePoint Framework, to add components to SharePoint sites you already own. Your pages are still SharePoint pages. Your permissions are still SharePoint permissions. Your content is still in your tenant, governed by the retention, DLP and compliance policies you have already configured.

From an implementation point of view this matters more than any feature comparison. It is the reason IT security teams treat this category differently from the alternatives, and it is usually the first question a Microsoft-committed organisation asks.

How is in-a-box different from the alternatives?

There are four realistic routes to an intranet for a Microsoft 365 organisation, and we have set the full decision out in our guide to build or buy for a SharePoint intranet. The short version, so you can place this category correctly:

Native SharePoint is SharePoint as it ships. You already own it. For smaller organisations with straightforward requirements, it is often enough, and we would not talk anyone out of starting there.

Custom development builds what you need to your own specification. It is the right answer for genuinely unusual requirements, and the wrong answer for the ones a product already covers.

In-a-box is the subject of this article.

Standalone intranet platforms - Unily, LumApps, Interact, Staffbase - are frequently listed alongside in-a-box products and they should not be. They are not built on SharePoint. They host your intranet content on their own infrastructure and integrate back into Microsoft 365, which is a legitimate model with real advantages, particularly for frontline-heavy workforces that need a dedicated mobile app. But it is a different purchase with different security implications, and conflating the two is the most common error we see in comparison articles and, increasingly, in AI-generated summaries.

The difference has practical consequences. Workplace from Meta, which had more than seven million users, announced its closure in May 2024 and was decommissioned in May 2026, leaving customers two years to move years of accumulated content off Meta's infrastructure and onto something else. Had that content been sitting in their own tenant, the vendor's exit would have cost them features rather than their archive. The limitation here is not the model itself - it is that where your content sits determines how much a vendor's decision can affect you, and that is worth establishing at the point of purchase rather than afterwards.

If you are choosing between the four routes rather than within one of them, the Microsoft 365 intranet options guide is the better starting point.

The two shapes of in-a-box product

Within the category there are two distinct approaches, and the choice between them matters more than any individual feature comparison.

Among products genuinely built on SharePoint, Lightspeed365, Origami Connect and Accelerator 365 take the modular approach, while Powell Intranet and Omnia are full platforms. That is not a complete list of the market - it is enough products to show what each shape looks like.

For transparency, Lightspeed365, a SharePoint intranet solution, is an example of a SharePoint intranet in-a-box product. Content Formula builds Lightspeed365, which is one of the modular products above. We also deliver native SharePoint intranets and custom development, which is why we can describe both shapes without needing you to pick one of them. Read more about Content Formula, Microsoft 365 digital workplace specialists since 2005.

Neither shape is better. The trade-off is that a full platform brings a wider feature set at a higher cost, and asks your organisation to learn a second system alongside SharePoint. A modular product covers less ground for less money, and asks nothing new of your content editors.

The trade-off is genuine and we have seen it go both ways. Organisations with real appetite for employee experience tooling get value from a full platform. Organisations whose problem is "SharePoint looks unbranded and our news is hard to find" usually do not, and in our experience end up paying for modules that are never switched on.

If you want a product-level comparison rather than a category one, our Origami Connect alternative page goes into that depth on one of them.

What separates one in-a-box product from another?

Feature lists are the least useful part of this evaluation, because every product in the category has news, people directories, targeting and templates. The differences that matter are set out below, with the question worth asking about each.

Where the code and data sit

This varies more than the marketing suggests. Some products run entirely inside your tenant - the components execute in your SharePoint sites, no content leaves, and no telemetry is sent anywhere. Others keep your content in SharePoint but load scripts or run configuration outside your tenant, on the vendor's infrastructure.

Both can be perfectly acceptable. But they are different answers to a security review, and the second usually means a longer procurement. It has a practical consequence too: SharePoint Online's Content Security Policy restricts which script sources are allowed to run, so products loading code from vendor domains need those domains explicitly trusted in your tenant.

Ask: does any component run or load from outside our tenant, and is any telemetry sent to you or a third party?

How much you are paying twice for

Some products rebuild capability SharePoint already provides - document libraries, search, page authoring - inside their own layer. There are reasons a vendor might do that, mainly consistency of experience. But you are then paying a licence fee for something included in the Microsoft 365 licence you already hold, and maintaining two versions of the same capability.

The simplest approach is to extend only where SharePoint genuinely stops short, and configure rather than duplicate everywhere else. The result is a smaller product, and usually a smaller bill.

Ask: what in this product duplicates something SharePoint already does, and is the consistency worth it?

Whether the editing experience stays familiar

Full platforms typically introduce their own authoring interface. That can be a benefit - some are better than SharePoint's - but it is a training cost and an adoption risk, and it is usually borne by the comms or HR team rather than IT, which means it does not always surface during a technical evaluation.

Modular products generally preserve the modern SharePoint page editor. If you want to see what both shapes produce in practice rather than in principle, our SharePoint intranet examples page has real homepages.

Ask: to see a content editor publish a news article during the demo. Notice how much of what they do is SharePoint and how much is the product.

Who does the work that is not software

Every product in this category installs quickly, which is largely the point of them. What determines whether the intranet succeeds is the work either side of the install - the information architecture, the navigation model, the content strategy, the design decisions, and the governance that stops it decaying within eighteen months. No product does any of that for you.

So the question is who will do it. There are three answers, and all of them are legitimate.

You do. Fine if the capability is genuinely in-house, and cheaper. Most organisations overestimate this, usually because the person who would do it already has a full-time job.

A third-party implementation partner does. Common in this market and often excellent. The thing to check is how close that partner sits to the vendor, because the further apart they are, the more likely you are to hear "that's a product question" and "that's an implementation question" about the same problem.

The vendor does. Less common, because most vendors in this category are software businesses rather than consultancies. Where it exists, it means one accountable party for the whole thing.

None of these is automatically right. A software vendor with a strong partner network will often beat a small consultancy with a thin product. But you should know which model you are buying before you sign, and the answer is rarely on the pricing page.

Ask: who would design our information architecture, and what is their background? A specific answer is a good sign.

How you are charged

Comparing cost in this category is harder than it should be, because vendors are not selling the same unit. Two products with similar headline figures can differ by a factor of three once you apply them to your own organisation.

There are two questions underneath it.

Do you buy it once or rent it? Some products are sold on a perpetual licence - a one-time purchase, with renewals for updates and support usually optional. Origami Connect works this way, as does Lightspeed365, which offers both models. Others are subscription only, billed monthly or annually, where lapsing means losing access rather than losing updates. Powell Intranet is subscription-based.

The trade-off is not just cash flow. A perpetual licence means a vendor decision cannot switch your intranet off, which matters more in this category than in most.

What is being counted? This is where comparisons break down. Some vendors price per user across the whole organisation. Some price per tenant, with unlimited users. Some charge only for the people who create and design content, and let everyone else read for free. The same product can look expensive or cheap depending entirely on the shape of your workforce - a 4,000-person organisation with eight content editors gets a very different answer from each model.

Then there is what sits outside the licence entirely: implementation, support tiers, upgrades, additional modules, and the professional services covered in the section above.

Ask: what is the unit we are being charged for, what happens if we stop paying, and what is not included?

How active the roadmap is, and how safe the vendor is

This is the criterion most buyers skip, and it is the one we would now weight most heavily.

In November 2021, Staffbase acquired Valo Solutions, whose Valo Intranet was one of the best-established SharePoint in-a-box products on the market. Staffbase subsequently announced it was reducing investment in Valo to focus on its own platform, and Valo Intranet reached end of life on 31 July 2025 with no SharePoint add-on offered as a replacement. Customers on subscription lost access. Customers on perpetual licences kept the product as it stood, without updates or support.

Nothing about that was predictable from a feature comparison, and it is not the only example. Products that would have topped a shortlist five years ago are no longer sold.

Two practical protections. First, establish what happens to your intranet if the product is discontinued - specifically, whether your content remains in usable SharePoint pages or is locked inside proprietary components. Second, look at whether a perpetual licence option exists. It does not protect you from a product going stale, but it does mean a vendor decision cannot switch your intranet off.

Ask: what have you shipped in the last twelve months? A roadmap sets out intent; a release history shows what has actually been delivered.

A short scenario to make the last point concrete. A comms manager we spoke to had inherited an intranet built on a product that had been quietly frozen by its new owner. Everything still worked. Nothing had changed in two years, Microsoft had shipped three rounds of SharePoint capability the product could not surface, and the vendor's answer to every request was that it was under consideration. The intranet had not broken, but it had stopped being worth what they were paying for it.

That is usually what a continuity problem looks like in practice - not a failure, but a gradual loss of value that is difficult to reverse once you are several years in. It is worth asking the uncomfortable question at evaluation rather than discovering the answer later.

Not sure whether you need a product at all?

Take our free intranet health check. Rate your intranet across five areas and get personalised results emailed to you in under five minutes. It is the fastest way to work out whether your problem is a software problem or a content and governance one.