Glow CloudKit Get the kit

Comparison

Build it yourself, or buy the kit?

A competent SPFx developer can build you a decent org chart. That is not the question worth asking. The question is who keeps it working through the next five years of SharePoint Framework versions, Node upgrades, Fluent UI changes and Graph API deprecations, long after the person who wrote it has moved on to something more interesting.

Side by side

The maintenance figures are counted from our own repositories, not estimated. No day rate is quoted, because yours is not ours to guess.

Glow Cloud Kit Building in-house
Getting the first one Installed and configured this afternoon Weeks of a developer's time, then testing
Getting the other 17 Included. They are already built Each one is another project
Keeping up with SPFx Ours to do. All 18 are on SPFx 1.23 Yours, permanently. Every version, every Node bump
What that upkeep looks like 765 commits across our repositories in the year to August 2026 The same shape of work, on your team's time
Accessibility, dark mode, mobile, theming Done, and re-done when SharePoint moves Yours to build and yours to keep working
When it breaks Reported to us, fixed in a release Whoever wrote it, if they still work there
A genuinely bespoke requirement We will not build your internal process into a product This is exactly what building is for
Control of the code Configuration is yours; the source is ours Complete. You own every line
Cost £99/mo for all 18, flat, cancel anytime Developer time to build, then to maintain, at your rate

Honest about the difference

Sometimes building is plainly right, and we would rather say so than win the argument.

Build it if…

  • The requirement is genuinely yours - it wires into your systems, your data or a process no product will ever model.
  • You already employ SPFx developers with real capacity, and this is a good use of it.
  • Policy forbids third-party code in the tenant. That is a legitimate constraint and no comparison table beats it.
  • You want to own the source outright, and you are prepared to own it for as long as it runs.

Buy the kit if…

  • What you actually need is an org chart, a directory and a calendar - things thousands of intranets need identically, which is precisely what a product is for.
  • You do not want to own the upgrade treadmill. SharePoint keeps moving whether or not anyone is funded to follow it.
  • The requirement is not one part, it is 18, and building them in sequence would take a year.
  • Your developers' time is better spent on something only your company needs. Nobody was ever promoted for rebuilding a staff directory.

The short version: the build is the cheap part and the visible part, which is why it is the part that gets estimated. The expensive part is the five years afterwards, and it does not appear on the business case at all.

In the twelve months to August 2026 we made 765 commits across these 18 apps. The header web part alone took 141 of them and is on its twenty-eighth revision. None of that was new features anybody asked for - most of it was keeping working software working. That is the bill you are quietly signing up for, and £99 a month is us signing it instead.

Try it before you scope a build

£99/mo for all 18, or £29/mo per part. 14-day free trial, a card is required to start, cancel anytime, no licence keys.

Other comparisons

Weighing something else up? These cover the other ways teams solve this.

Maintenance figures counted from Glow Cloud Solutions' own source repositories on 27 August 2026, covering the preceding twelve months across all 18 apps. They describe that period and are not updated continuously. Build effort varies enormously with scope, team and existing SPFx experience, so no estimate of it is offered here.