The first 100 days of a fintech transformation

The first 100 days of a fintech transformation settle three things: what is actually true about the starting position, what the organisation has decided to do about it, and who will deliver it. Programmes that get into trouble usually settle them in the wrong order, building the delivery machine before the facts and the decisions are in place.

That holds whether the transformation is a bank replacing its core platform, an insurer launching a digital proposition or a high-growth firm turning a payments feature into a regulated business. The sequence we recommend is simple: days 1 to 30 to diagnose, days 31 to 60 to decide, days 61 to 100 to mobilise. The dates are a discipline rather than a law. What matters is that each phase produces something the next one cannot do without.

Why the order matters more than the speed

In our view, the most common failure in the first 100 days is not slowness. It is skipping ahead. A steering committee is formed, a delivery partner is appointed, workstreams are named and a plan appears with a go-live date on it, all before anyone has agreed what the organisation is starting from. The programme then spends its second and third quarters discovering facts it should have established in its first month and reopening decisions it thought it had made.

Earlier in this series we argued that transformation rarely fails because of technology. It fails on ownership, decisions, sequencing and governance. The first 100 days are where those are either settled or quietly deferred.

UK bank regulators draw a similar line. The Prudential Regulation Authority describes mobilisation as the period in which a newly authorised bank secures further investment, recruits staff, invests in IT systems and commits to third-party suppliers. Deposits are capped at £50,000 in total and the guidance treats 12 months as the maximum. It is also clear that mobilisation is not the stage at which to start building the bank; it is for completing work that is already well advanced. That is a useful principle well beyond banking.

Revolut: what a long mobilisation reveals

Revolut received its UK banking licence with restrictions on 25 July 2024 and entered mobilisation. More than 14 months later, in October 2025, the Financial Times reported that the PRA was still examining how Revolut's risk controls would work across its international operations. Revolut said at the time that it was in the final stages of mobilisation and that "getting this right is more important than rushing to meet a specific date" (as reported; the original Financial Times article was not read directly).

On 11 March 2026 the restrictions were lifted and Revolut launched as a UK bank, roughly 20 months after mobilisation began. Its migration plan was itself carefully sequenced: new customers first, then its 13 million existing UK customers moved from the e-money entity to the bank in phased batches, each with at least two months' notice, over a few months in total.

It would be wrong to present this as a failure. Revolut is now a UK bank, and neither Revolut nor the PRA has published the detail of what was discussed. Our reading is narrower. Mobilisation tests whether questions about control, ownership and scale have been answered before delivery starts. Where some remain open, mobilisation stops being a build-out and turns into an extended diagnosis, conducted with a regulator watching. For any organisation, that is the most expensive place to discover what should have been established at the start.

Nationwide: foundations first, and the patience to finish

In September 2018 Nationwide announced a £4.1bn technology investment over five years, £1.3bn of it incremental. Among its aims was to cut the society's data stores from 20 to two. In September 2026, in a feature published by Microsoft, one of its technology suppliers, CTO Paul Ballard said Nationwide had moved 15 million customers off its former core banking engine, replaced a 45-year-old customer data system and was preparing to integrate around five million Virgin Money customers. Nationwide acquired Virgin Money in October 2024, and Virgin Money's business transferred to the society on 2 April 2026 after court approval.

Two details from that account are worth dwelling on. The first is the gap between plan and reality. According to the same feature, when Nationwide's Chief Data and Analytics Officer arrived in 2023 the society was running 19 separate data stores. The two figures may not be defined identically, and the consolidation has since happened. But a programme that set out in 2018 to go from 20 stores to two was, five years later, still close to where it began on that measure. That is a reminder that a new leader should diagnose the starting position rather than inherit it. What you are handed is often the plan, not the facts.

The second is the decision rule. "You're doing it through the eyes of the customer," Ballard said. "How do we move you to Nationwide platforms in a way that you don't notice and you get better features?" A test that explicit makes the choices in the Decide phase faster, because it tells everyone what a good answer looks like before the options are on the table.

Days 1 to 30: diagnose

The purpose of the first month is an honest, evidence-based picture of the starting position that the people who will fund and run the programme accept as true. It is not a plan, and it should resist proposing solutions.

In practice that means establishing which customers, products, systems, contracts and data are in scope, and what condition they are in. It means listing the commitments that are already fixed, such as contract renewals, promises made to the board and regulatory deadlines. For EU financial entities, the Digital Operational Resilience Act has applied since 17 January 2025, and UK firms were required to be able to stay within impact tolerances for their important business services by 31 March 2025. A transformation changes the systems those regimes cover, so the diagnosis should show where the programme touches them.

It also means mapping who owns each decision today and who believes they do, and separating what the organisation knows from what it assumes. Interviews help, but data and walking a customer journey end to end usually help more. The outputs are short: a fact base, a list of the decisions the programme needs, each with an owner and a date, and a candid view of the main risks.

Days 31 to 60: decide

The second month is for the calls that are cheap to change now and expensive later. The central one is the build, buy, partner or kill choice we set out in an earlier article, applied to each major component. Around it sit the scope of the first release, the order in which things will happen, the outline operating model, the sourcing approach and the funding gates.

Two disciplines make this phase work. Each decision needs a single accountable owner rather than a committee, and the criteria need to be written down before the options are compared, as Nationwide's customer test illustrates. The kill decision deserves particular attention here. Stopping an existing initiative that competes for the same people and budget is often the most valuable decision the programme makes in its first 100 days, and the one most often postponed. The outputs are a decision log, an agreed sequence and a funded first release.

Days 61 to 100: mobilise

Only now does the programme stand up the machinery to deliver what has been decided. That includes governance proportionate to the risk, the accountable leaders and first critical hires (the subject of our previous article), contracts with the chosen suppliers, a delivery rhythm and a small set of measures that track outcomes rather than activity. Where a regulator is involved, it includes a plan for engaging with it.

The PRA's framing applies here too. Mobilisation completes what has been decided. If the programme finds itself debating scope or ownership in month three, it has not moved into Mobilise; it has gone back to Decide, and it should say so openly rather than let the plan absorb the delay.

Signs a programme has skipped ahead

A few patterns suggest the first two phases were rushed. The go-live date was set before anyone agreed the baseline. The main supplier was chosen before the scope was decided. The steering committee is still arguing about facts in month four. Workstreams exist without a named owner for the decisions they depend on. None of these is fatal on its own, but together they usually mean the programme is paying later for time it saved at the start.

Aulay's view

The first 100 days are where an outside perspective is worth most and costs least. A diagnosis carried out by people with no stake in past decisions is more likely to be believed. Decisions move faster when someone owns the process of making them. Mobilisation often needs experienced interim leaders in post before permanent hires arrive.

If you are a CEO, COO or transformation sponsor about to start a programme, or 60 days into one that still feels like day one, we would welcome a conversation at aulayco.com.

---