Just shipped: mcu.im is live →Accepting 2 engagements · Q3 2026 / Isle of Man · UK · EU / v 2026.04
Case study · Manx Credit Union · Live in production

The credit union that runs end to end
on software we built.

The Manx Credit Union serves its members on a platform we built and now operate: loans, savings, treasury, audit, and a member portal, live at mcu.im.

Bank statement in, board pack out. The same system MCU runs today, in two and a half minutes.

There is also a 90-second cut and a 40-second cut.

100+
Screens in production
±£1
Reconciled vs the treasurer's reports
12
Staff & member roles
4
Apps, one platform
01 The engagement

One team behind everything the credit union runs.

How a community credit union got modern software without hiring a software department.

The Manx Credit Union is the Isle of Man's community credit union: savings accounts and affordable loans, run by a small team who know their members by name. When MCU decided to invest in better tools for members and staff, they asked us to deliver all of it.

Delivering it meant running the project as well as writing the code. We planned the build, designed each screen with the staff who would use it, shipped working software week after week, moved the member records across, trained every role, and ran the go-live. When the front desk needed something changed, we usually had it live within days.

Today we are MCU's software provider. Members apply for loans and check their balances online; staff work their queues in the staff app. The treasurer reconciles the bank statement in the treasury module, and the credit committee meets every Tuesday inside the same system.

02 The journey

We didn't copy the data across. We rebuilt it.

The delivery looked nothing like the plan. The honest version is the better story.

The historical book arrived as fragments: one export of 3,680 records with the names stripped, two membership spreadsheets, the weekly benefits file, and the credit union's own paper till books. No dates of birth, no contact details, no documents, no transaction history for savings. Balances, and little else.

So we rebuilt it. Eight import pipelines, one per source, each deriving what it loaded: balances computed from ledger history rather than read from a field, instalments recovered from the payment schedules themselves, duplicates merged, and every row the arithmetic couldn't yet prove parked visibly, with a written note of what would resolve it. The book went live frozen: repayments open, outbound money locked until each member re-verified their identity, then opened one member at a time.

Then we let the arithmetic judge the result. Recomputing every loan's life day by day surfaced what no inspection could. The old model only calculated interest when a payment arrived, so a loan nobody paid simply froze; one had sat at the identical balance for thirteen and a half months. The rebuilt book reconciles against the credit union's own treasurer reports to within one pound, and its interest income decomposes to the penny with no unexplained remainder.

Most of the system as it exists today was designed and built in the final ninety days before launch, with the staff who use it: four out of five commits in the entire history land in that window. That pace comes from how we build. Every change passes an independent review and an automated test suite that grew from nothing to more than five thousand checks in the same ninety days. Inside those controls, AI agents write much of the code and we direct them. The map of the early prototype survived. The territory was replaced.

Going live on a real loan book meant rehearsing like it mattered: three full rehearsals on exact copies of the live book, identical figure for figure. Production ran one day after the final rehearsal, so every payment-tied figure had to match to the penny, and every calendar-tied figure had to move by exactly one day's interest. Both did. Mid-run, a safety check refused to write, and nobody overrode it: the cause was fixed, the untouched book restored from snapshot, the run repeated clean. The credit union then corrected its own migrated book by pressing six buttons in one legal order, each step verified, each step reversible.

And where rebuilding the truth changed what members owed, the change went in their favour: the family loan's pricing moved onto a daily basis that works out cheaper per year, applied retroactively.

03 The platform

Everything a credit union needs to serve its members.

One codebase behind the member portal, the staff app, and a desktop build for the office.

01

Member portal

Members sign in to apply for a loan, check balances and repayments, read their documents, and keep their details current. No trip to the office needed, and passwordless login means no forgotten passwords either.

02

The full loan lifecycle

Application, interview, affordability, credit checks, agreement signing, committee decision, payout, repayment, arrears. One system, one history per loan.

03

Committee decisioning

Weekly sessions with attendance and quorum, structured questions for every case, and every decision recorded with its reasoning.

04

Front-desk cashier

Cash deposits and loan repayments taken at the counter. Tills balance at close, and corrections need a second pair of eyes.

05

Treasury & accounting

Bank statement imports with automatic payment matching, payout confirmation, benefit payment routing, an expense register, income dashboards, and dividend modelling for the AGM.

06

Audit & compliance tooling

Review queues for KYC, due diligence, and payments. Screening inboxes, four-eyes corrections, and an inspection pack the team can generate on demand.

07

Reporting & analytics

A catalog of financial, member, and compliance reports, plus a self-serve analytics studio for the questions the catalog doesn't cover.

08

The working day

Role-aware dashboards, staff messaging, a shared calendar synced with Microsoft 365, document signing, and a help centre with guided tours built in.

04 In the product

What staff and members actually see.

Captured from the live build on our staging environment. The names are fictional; the software is not.

app.mcu.im / loans
MCU staff app: a loan detail screen with outstanding balance, repayment progress, original terms, and documents
The staff app. A loan mid-lifecycle: balance, repayment progress, terms, and the documents behind it.
app.mcu.im / member-dashboard
MCU member portal home showing the membership journey, next payment due, and savings
The member portal. Savings, the next payment, and the path to full membership.
app.mcu.im / reporting
MCU reporting catalog with financial and compliance reports, each exportable as PDF or Excel
The report catalog. Financial and compliance packs, exported on demand.
05 The delivery

Writing the software was half the job.

Project management, data migration, and training came from the same team that wrote the code.

i / Manage

Project management

We ran the plan from kickoff to go-live and demoed working software every week. MCU's team stayed focused on members while the build moved.

ii / Build

Development on the fly

Feedback from the counter and the back office went straight into the build. The platform grew around how the team actually works, screen by screen.

iii / Migrate

Data onboarding & migration

Member records, loan histories, and documents came across through an import centre we built for the purpose. Every batch was checked and signed off before go-live.

iv / Train

Training & handover

We trained every role on its own screens before launch. The platform now carries its own training centre, so new staff learn inside the tool they will use.

06 Under the hood

Boring technology, carefully arranged.

The same stack we run everywhere, tuned for a financial operator.

An Angular front end and a Spring Boot API on PostgreSQL, hosted on AWS. A dedicated authorisation server handles sign-in, trusted devices, and passwordless login, and a gateway keeps tokens out of the browser entirely. Bank statements arrive over open banking, credit checks run through TransUnion, the calendar syncs with Microsoft 365, and loan statuses update live over WebSockets. The same build ships as a signed desktop app for the office machines, and a Playwright suite walks the money paths before anything reaches production.

Angular 19Spring Boot 3.2Java 21PostgreSQLSpring Authorization ServerOAuth2WebSocketsYapily open bankingTransUnionMicrosoft 365ElectronPlaywrightAWS
07 The numbers

For the engineers: the numbers.

Counted straight from the repositories at the July 2026 launch.

870k+
Lines of code
3,700+
Commits
781
API endpoints
281
Database migrations
5,000+
Automated tests
99.98%
Uptime
08 Your build

Tell us how your operation runs.
We'll build the platform it runs on.

A 30-minute call with a senior engineer that goes straight into the technical detail. You'll leave with a point of view on how to ship, whether you hire us or not.

Phone / WhatsApp+44 (0) 762 440 3021
JurisdictionIsle of Man · UK · EU