Leading a Multi-Entity SaaS Platform Across 14 Countries

One platform, many truths

A multi-entity SaaS platform has to be a single point of solution for everyone, sales teams, back-office users, dealers, brokers, and end customers, yet each country has its own rules, its own regulators, and its own idea of "normal." The temptation is to fork the product per market. The discipline is to find the shared core and isolate the variation.

The value of getting this right is real: the lending platform I led targeted more than 50 million EUR of new business value and cut manual operations by 20-25%. None of that comes from clever features. It comes from a platform architecture that lets one product flex across many entities without splintering.

You manage product through people, not tickets

At that scale you don't ship by writing the best ticket. I was driving nine feature teams across Bangalore and Paris, which means the real work is product vision, prioritisation, budgeting, recruitment, and keeping transversal activities aligned. The roadmap only moves as fast as the teams understand the "why" behind it.

I learned to over-invest in shared context. When nine teams in two cities all understand the same vision, they make a thousand small decisions correctly without me. When they don't, I become a bottleneck, and a bottleneck is the most expensive thing on a multi-country platform.

Stakeholder management is the actual job

Strategic vision sounds glamorous; most of it is stakeholder management. Sales wants speed, back-office wants control, dealers want simplicity, customers want clarity, and leadership wants the number. My job is to hold all of those in one roadmap without quietly betraying any of them.

I treat that as a translation problem. Every group is optimising for something legitimate; my role is to make the trade-offs explicit instead of letting them get re-litigated in every meeting. Change and relationship management isn't soft skill decoration, at this scale it *is* the product process.

What scale taught me

Coherence beats customisation. Shared context beats heroics. And a platform that serves many masters survives only if you make the hard prioritisation calls out loud. Leading across 14 countries didn't make me want simpler products, it made me better at finding the simple core hiding inside a complicated one.