Cardiff is one of the few UK cities that actually runs the back-office machinery of consumer insurance and finance at scale, and that is the grouping worth writing for. The FTSE 100 motor and home insurer Admiral is headquartered in Tŷ Admiral on David Street; Legal & General’s Welsh HQ handles pensions administration for thousands of schemes; Principality Building Society (the largest mutual in Wales) sits in the city centre, with Pepper Money’s specialist lending operation in Capital Quarter and a price-comparison cluster (Confused.com, Go.Compare) nearby. Invest Cardiff designates the central business district a Financial & Professional Services Enterprise Zone, and insurance employment in the city sits well above the UK average. What defines the place is operational: claims, servicing, reconciliation, regulatory reporting and customer portals, not capital markets.
The Operations Behind Cardiff’s Consumer Finance, Not the Headline Names
The temptation is to write to the big names. They are the wrong audience. Admiral, Legal & General and the Admiral-owned Confused.com all run substantial in-house data and engineering teams. They build their own systems, and they will never be a client. They are evidence, not a market: proof of how deep Cardiff’s consumer-finance talent pool and operations base run.
The firm that searches for a Cardiff software developer is the tier underneath them. It is the independent insurance broker or MGA running Acturis or Open GI. It is a regulated mutual like Principality on a legacy savings-and-mortgage core. It is a specialist lender such as Pepper Money, or a claims-handling and FS-support operation somewhere in the Enterprise Zone. These firms run capable, packaged platforms and employ no developers to make those platforms behave as one system. That gap is the entire job.
The Legacy Core Is the Real Cardiff-Specific Problem
The most distinctive software problem in Cardiff sits on the mutual and lending side, because that is where the oldest, most central platform meets the newest customer expectation. A building society or specialist lender runs its whole business on a savings-and-mortgage core that has been hardened over decades. For many that is an SBS (Sopra Banking) Mortgage & Savings Suite-class platform, the family of core software that today underpins lenders managing roughly one in five UK mortgages. At the centre, that core is dependable and not going anywhere. The trouble is everything modern that has to attach to it.
A live-balance member portal, an online savings application, a document a customer expects to download on demand: none of that was contemplated when the core was specified, and the core does not expose it cleanly. So the connective work falls to a firm with no engineers to do it. Migrations don’t dissolve the problem either; they relocate it. Some societies move origination onto Finova (formerly DPR) Apprivo or shift the core toward cloud-native platforms such as Mutual Vision, and each of those moves is itself an integration project: origination has to talk to the core, the core has to feed self-service, and the legacy ledger usually has to keep running alongside the new piece for a long handover. The platforms exist; the wiring between them does not.
Where the Servicing and Reconciliation Day Actually Goes
On the insurance and broking side the pain is less about one ancient core and more about a day spent reconciling money the systems will not reconcile themselves. A Cardiff broker on Acturis transacts alongside hundreds of insurer partners on a platform that handles a very large share of UK general-insurance premium; an Open GI intermediary sits inside a comparable network. The placement platform is rarely the weak link. What it does not do is settle the back office.
- Premiums, commissions and client money have to be matched daily across the policy platform, the bank feed and the finance ledger. It is a deadline-bound job that grows with volume and absorbs more of the operations desk each month.
- A claim or a servicing case moves between the policy platform, a claims tool, a document store and the ledger, and the same case details, payments and correspondence get retyped at each crossing because nothing carries them across.
- Client-money rules turn every one of those manual handoffs into a control point, not just a delay. A mistyped figure between systems is a CASS exposure as well as a slow afternoon.
The work here is not a new placement platform. It is the layer that makes premium, claim and money data settle once, with the reconciliation breaks surfaced for a person to clear rather than hunted for in spreadsheets.
Consumer Duty Turned Reporting Into a Standing Data Problem
The FCA’s Consumer Duty has been in force for open products since 31 July 2023, and it changed what reporting has to do. Firms must now produce accurate, board-level management information evidencing good customer outcomes (complaints, fair value, satisfaction) and review it at least every twelve months. The data exists, but it is scattered across systems that were never built to feed a regulator.
So the outcomes report gets stitched together by hand: complaints from one platform, fair-value evidence from another, servicing and claims data from a third, reconciled in a spreadsheet before it goes to the board. That is slow, fragile and hard to defend if the FCA asks how a number was reached. The fix is an integration that pulls the underlying outcomes data from the source systems on a schedule, into a board-ready view that traces back to where each figure came from.
What We Build Around Your Policy, Core and Claims Systems
We integrate the platforms a Cardiff firm already depends on, rather than asking it to replace anything. The same problem recurs whether the centre of gravity is a building-society core or a broker’s placement platform: capable systems that hold authoritative data and will not hand it to each other. The build is shaped to whichever of those a firm is living with:
- Core and origination integrations that connect a legacy savings-and-mortgage platform (or an Apprivo / Mutual Vision migration in progress) to the member-facing layer, so a live balance, a document or an application status is read from the core rather than re-entered beside it. This is our core API integration work.
- Policy-to-ledger connectors linking Acturis, Open GI or a legacy core to the claims tool, document store, payments and finance ledger, so case and money detail crosses each handoff once.
- Reconciliation automation that matches premiums, commissions and client money daily, surfaces the breaks for a human to resolve, and keeps month-end from owning the operations desk.
- A bespoke member or customer portal built on the core platform’s API, drawing balances, documents, claims status and applications from the live record.
- Consumer Duty outcomes reporting assembled automatically from the source systems into a board-level view, every figure traceable to its origin.
This is custom software development for a regulated sector that has no developers and no intention of hiring any. It is slow, central, compliance-bound integration work, better held by a standing partner than handed to a contractor and lost when they leave, and the gap the in-house teams at Admiral and L&G prove is real.
Working in Cardiff’s Financial Services Sector?
A good first scope is to pick the single process that costs the most certainty: the daily reconciliation if you are a broker, the member portal that cannot see the core if you are a society. Wherever a figure is copied between systems, or a customer is held while someone checks three screens, there is a cost and, under Consumer Duty and the client-money rules, an exposure sitting in plain sight. Show us where your operations desk is rekeying data between systems and we will build the join that removes the most risk first. Consumer finance is one half of the city’s story; drama production is the other, covered on the Cardiff page.
