Know what you spend.
Building societies and mutuals

Cost discipline in a mutual is a member interest.

In a shareholder-owned bank, money saved on infrastructure becomes margin. In a mutual it becomes rate, or branch hours, or the capacity to absorb the next piece of mandatory change.

That is a different argument to make internally, and it is a better one.

Why this is harder in a society than in a bank

The core
Much of the estate sits with a platform supplier, so the spend in your own cloud accounts is only part of the picture, and the invisible part is the part under contract.
Migrations
Societies moving between core banking platforms run two estates for a period, and the duplicate cost is nobody's line item until somebody counts it.
Small teams
Cost sits with a CTO or IT director alongside a great deal else, and there is rarely a dedicated FinOps function to hand it to.
AI on cards
Document processing, summarisation and generative tooling get bought on expenses by people solving a real problem, and none of it appears in any technology budget line.
Mergers
Consolidation means combined entities carrying two of most things for longer than anyone intended.

The March 2027 register, and where this overlaps

From 18 March 2027, societies have to maintain a register of material third party arrangements and submit it annually to the regulator through RegData. The register asks what each third party provides, whether it supports an important business service, where it is performed, and how providers rank in the supply chain.

What it does mean is that every society is going to spend part of the next year building a complete and defensible inventory of who supplies what. These engagements build that inventory from the billing and contract side, and produce the cost picture alongside it. If you have to enumerate your suppliers anyway, doing it once and getting the spend answer at the same time is cheaper than doing it twice.

Two honest limits. The arrangements the register cares about are the material ones, and most of those you already know about. And the register wants risk and supply chain information a spend review does not produce, so this is a head start on the discovery, not a completed submission. Where it genuinely helps is completeness: the subscriptions nobody logged, the departmental AI spend nobody classified as a supplier arrangement, and the fourth parties sitting behind your platform provider.

What we do not need

This matters more in a regulated mutual than anywhere else, so it is worth being explicit.

Never requested

  • Production system access
  • Customer, member or personal data
  • An agent or collector installed in your estate
  • Software to buy, install or integrate
  • A procurement exercise
  • An internal project team or steering group

What we work from

  • Billing and usage exports
  • Invoices and contract summaries
  • Four conversations of an hour each
  • Two weeks of application or usage logs
6hours

Your organisation's total involvement. And no ongoing data flow, no persistent access, and nothing left behind in the estate when the engagement ends, so this does not become a third party arrangement of its own to assess, register and report.

What you get

The total
Spend across cloud, AI and software, reconciled against your invoices.
The breakdown
Attributed to teams and products, with confidence labelled where tagging is incomplete.
The savings
Ranked by annual value against days of effort, each traced to something your team can verify.
The plan
Ninety days of dated actions with named owners, written so your own team can run it.

And a number you can take to a board that is asking what the technology estate actually costs.

Questions

"We are too small for this."+

Possibly. The fees are set by the size of the estate and smaller organisations pay less. But the societies that benefit most are usually the ones without a dedicated cost function, not the ones with the largest bills.

"Our core is outsourced, so we barely have any cloud."+

Then the cloud number will be small and the report will say so in week one. The subscription and AI picture is usually where the surprise is, and the supplier contract is where the largest single number sits. Knowing what each of the three is worth is the point.

"We are mid-migration. Should we wait?"+

No. Mid-migration is when duplicate running cost is highest and least visible, and it is the moment a baseline is worth most, because it gives you something to measure the migration against afterwards.

"Will you talk to our platform supplier?"+

Only if you want us to, and only with you in the room. We have no relationship with any of them to protect.

More at the questions page.

Independent means independent. Nivaan sells no cloud, no tooling, no licences and no managed services, and takes no commission from any vendor. What that means. In a sector with heavy supplier concentration, that is the whole point.

Start with a question, not a contract.

Twenty minutes, no deck. Bring your last cloud invoice if you have it to hand.

Book a 20-minute call