Trust Is the Product: Leading Product and Technology in Regulated Fintech

In most software, you optimise for growth and treat everything else as a constraint to loosen later. In regulated fintech, that instinct gets you fined, shut down, or — worse — trusted by people you then let down. For thirteen years I led product and technology in financial services: at HSBC, Shieldpay and Zopa, across payments, lending and open banking. The lesson running through all of it is plain. Trust is the product. Everything else is packaging.

What "regulated" actually changes

A regulated product carries constraints that are not negotiable down the line. Risk, Legal, Compliance and Architecture are not stakeholders you manage around — they are co-authors of the roadmap. Every decision has to survive an audit. "Move fast and break things" is a liability when the things that break are people's money or their data. The craft of product leadership here is delivering real momentum inside those constraints, rather than pretending they are someone else's problem. The teams that win are the ones that treat compliance as a design input from day one, not a gate bolted on at the end.

Scale: HSBC

At HSBC I ran technical product management for a global digital-banking estate serving millions of customers across more than twenty countries, progressing into a manager-of-managers role leading a product and technical-product organisation of fifty to eighty people. The work I am proudest of was not a flashy feature — it was the internal mobile platform: a shared component library that let engineering teams across twenty-plus markets compose their own banking apps without rebuilding the foundations each time. That platform thinking improved engineering efficiency by around twenty-five percent and made the difference between markets shipping in parallel and waiting in a queue. Orchestrating the launch of the new HSBC UK app, then the US, Canada and beyond, meant aligning Risk, Legal, Architecture and regional leadership on every release. At that scale, leadership is mostly the work of making it safe for many teams to move at once.

Risk: Shieldpay

At Shieldpay I was Head of Technical Product on a regulated payments platform clearing five to eight billion pounds a year, serving more than forty of the UK's top-100 law firms across escrow and disbursement. I owned the rules engine and introduced third-party ML-based risk scoring for KYC and AML decisioning — moving the platform from manual review to automated, auditable risk workflows. In a regulated context, "auditable" is doing as much work as "automated": a decision you cannot explain to a regulator is a decision you cannot ship. We delivered a two-hundred-percent improvement in integration throughput on complex cross-border payments and cut enterprise onboarding queries and meetings in half by making integration genuinely self-serve. Less friction for clients, more defensibility for the business.

Data: Zopa

At Zopa, an FCA-regulated neobank with more than 850,000 customers, a £2.1B loan book and £2.9B in deposits, I led product across mobile, web and APIs and owned the open-banking data product — spend categorisation, credit-score explanations and personalised financial nudges built on connected-account data. Open banking is a trust contract in miniature: customers hand you a window into their entire financial life, and every feature has to earn that access by being genuinely useful and visibly safe. We validated decisions with an A/B testing programme across the full user base rather than shipping on opinion — because at that scale, intuition is expensive and evidence is cheap.

The technical product leader

The throughline across all of it is a particular kind of leader, and it is rarer than it should be: someone who can hold a board-level conversation about strategy in the morning and review a diff for an authorisation hole in the afternoon. I started as a software engineer and never put the keyboard down. In regulated fintech that hybrid is not a vanity — it is leverage. It means you can tell when an architecture decision is quietly creating compliance debt, when an estimate is fiction, when "it's secure" is a hope rather than a fact. The constraints that make fintech hard are exactly the constraints that reward technical product leadership. Build for trust first, and growth turns out to be the easier half.