Case study
£19 million was the plan. Up to £216 million was the damage.
Birmingham's Oracle story is not a technology story. The software was ready to change. The way of working wasn't.

Rujuta Singh
3 min read
Birmingham City Council is the biggest local council in Europe. In 2022, it moved finance, HR and payroll onto Oracle. The idea was to use it out of the box. Then came the customisations.
One of them was the bank reconciliation. It didn't work. The council couldn't produce auditable accounts. Fraud checks were switched off for more than 18 months. About £2 billion of transactions landed in the wrong year.
In 2023, alongside its equal pay liabilities, the council effectively went bust. The project is now forecast to cost £144 million. Auditors put the total losses at up to £216.5 million.
Now the fix
They're rebuilding Oracle from scratch, with standard processes this time. And in January they delayed the relaunch again, to give staff more time to learn the standard way of working. Not because of the tech.
The software was ready to change. The way of working wasn't.
Birmingham is just the one that made the news. I hear "we're different" in a lot of transformations. Sometimes it's true. Often it's an old process asking for a bodyguard.
Change the system and you've spent money. Change how people work and you've changed the business.