The Pattern
Every major UK fintech runs a modern web stack. Revolut: Next.js. Wise: custom modern. Monzo: modern. Starling: modern. Not a single one chose WordPress, Drupal, or any legacy CMS.
This isn't coincidence. It's selection pressure. FCA-regulated companies face security scrutiny that makes legacy CMS architecturally unsuitable. The plugin model creates compliance scope that fintech compliance teams won't accept.
The FCA Factor
The Financial Conduct Authority requires regulated firms to demonstrate operational resilience — including technology infrastructure. A WordPress site with 25 plugins, each an independent codebase, presents a change management and audit challenge that modern frameworks avoid entirely.
This regulatory pressure is a feature, not a bug. It forced UK fintechs to make infrastructure decisions that are objectively better — and the performance, cost, and security benefits followed.
The Lesson for Other Sectors
UK healthcare (NHS), education, and local government don't face the same regulatory pressure on framework choice that fintech does. The result: they default to WordPress and Drupal. The lesson from fintech is that when you're forced to evaluate properly, you never choose legacy.
