I lead platform, data, and AI infrastructure at Pleo.

Fifteen years scaling European fintech. Most of what I do is the work nobody else wants to own — the migrations, the cleanups, the org designs that decide whether a company scales or stalls.

5 → 15
European markets, 11 months
Engineering throughput, flat headcount
70%
Card scheme cost reduction
20pp
Margin uplift on a processor migration

The path here

I joined Pleo in 2019 at around 100 people, looking to get hands-on after five years advising banks at McKinsey. My first job was migrating 20,000 customers to a new payment processor and unlocking a 20-point margin uplift. That turned into building the entire payments platform from scratch. We went from five European markets to fifteen in eleven months.

As the platform matured, the scope grew. I took on data, developer experience, infrastructure, security, eventually leading 100+ people through a period where we tripled engineering throughput without adding headcount. The unlock was removing friction and treating platform teams as product teams with real users and real outcomes.

Today I lead ~70 people across platform engineering, data, AI infrastructure, and regulated entities. The recent win I'm proudest of: a 70% reduction in card scheme costs through direct negotiation in a duopoly market where you have almost no leverage.

Before Pleo: McKinsey, advising Tier 1 European banks on payments and regulatory strategy. Before that: a PhD in physics at the University of Copenhagen, building atomic clocks beyond the quantum limit.

Full experience →

About

I lead platform, data, AI infrastructure, and our regulated entities at Pleo — about 70 people. I joined in 2019 to migrate the payments stack and ended up building the platform that runs the company.

Most of what I've owned at Pleo started as something nobody else wanted to own — a payment-processor migration, a regulatory deadline, a market launch with weeks of runway. The pattern: go in, ship the unsexy thing, leave a team that doesn't need me anymore. Before Pleo: McKinsey advising Tier 1 European banks, and a PhD in physics building atomic clocks.

Where I'm strongest

European payments, end-to-end
Built Pleo's payments platform from scratch, scaled it from 5 to 15 markets in 11 months, and took 70% out of card scheme costs in a duopoly through direct negotiation. The work no one wants to own and that determines whether the company can scale at all.
Traditional companies going AI-first
I'm in the middle of this transition right now: rearchitecting data pipelines, compliance automation, and internal tooling at a company that started as a card programme. Not the chatbot layer — the work that decides whether AI becomes the default way an organisation operates or stays a side project. Most of it isn't sexy.
Platform organisations crossing 50 → 200 engineers
Tripled engineering throughput on flat headcount in the last cycle. The unlock was treating platform teams as product teams with real users and real outcomes — and being willing to sit in the org-politics rooms nobody else wanted to be in. This is the threshold where org structure starts driving the product roadmap, and where most companies break.
Building product organisations through growth-stage
Joined Pleo at 100 people; helped take it past 850. Six years inside the product engine of a Series C fintech, plus five years at McKinsey before that advising European banks on payments and digital transformation. Product at growth-stage isn't the discovery loop — it's pricing, packaging, regulatory readiness, market launches with weeks of runway, and saying no to the things that don't compound. The companies that get this right keep momentum past Series B; the ones that don't, stall.
"Stefan is one of the strongest colleagues I have ever worked with. He navigates gnarly migrations, is an excellent org designer, and is a leader everyone wants to follow — because he genuinely cares for every individual on his team."
VP Engineering, Pleo

Writing

Latest
01
Designing an Organization When Every Framework Says Something Different
Every org design framework is right, and they each point you somewhere different. What to do when the answers don't match.
Leadership May 2026 9 min read
The Unglamorous Core of Payments
Apr 2026
The smooth checkout is an illusion. The unglamorous infrastructure work behind it is where payments actually live.
FinTech 6 min read
The Best Tech Is Not the Best Partner
Apr 2026
Why partner selection in FinTech comes down to compliance posture and relationship depth, not which integration looks cleanest.
Leadership 5 min read
What I Listen To
Mar 2026
From my father's vinyl to Sufjan Stevens on headphones. The thread is music that doesn't hedge.
Personal 1 min read
Goal Setting Doesn't Need Another Framework
Mar 2026
OKRs, SMART, BHAGs, V2MOMs. The framework isn't the point. A goal needs a clear achievement, a baseline, an owner, tangible work you can point to, and a cadence you keep.
Leadership 3 min read
Approximate Correctly: What Physics Taught Me About Business Decisions
Feb 2026
A physicist's case for approximation as a deliberate tool, and why back-of-envelope thinking beats false precision in business decisions.
Leadership 4 min read
What Setting a High Bar Requires
Feb 2026
The bar is a contract, not a demand. What it takes to hold high standards and actually help people meet them.
Leadership 4 min read
How We Kept the Payments Platform from Becoming a Bottleneck
Feb 2026
Every payments platform reaches the same crisis point: you become the team everything routes through. How we committed to APIs-only and held the line.
Payments 4 min read
The Physicist's Path to FinTech Leadership
Feb 2026
The connection between quantum physics and FinTech leadership isn't obvious. But the instincts transfer: systems thinking, order-of-magnitude reasoning, finding the right frame.
Leadership 5 min read
Support Meetings, Not Status Meetings: How Naming Changes Culture
Feb 2026
A 'status meeting' says your job is to account for yourself. A 'support meeting' says our job is to help you succeed. Same calendar slot, different culture.
Leadership 4 min read
From Twelve Options to One Command: How We Transformed Platform Engineering
Feb 2026
Our platform teams wrote thousands of lines of documentation. Engineers read almost none of it. Here's what we changed.
Leadership 7 min read
Why 'Do You Support Faster Payments?' Is the Wrong Question
Jan 2026
We asked the bank if they supported Faster Payments. They said yes. Then we tested it at 9pm on a Saturday.
FinTech 4 min read
Your Leadership Scorecard: What to Own When You Lead Beyond a Single Team
Jan 2026
Five dimensions I track when I'm responsible for more than a single team. Not from a book — from doing the same thing in different areas and watching what moved.
Leadership 5 min read
Five lessons I wish someone told me before about building in payments
Dec 2025
Payment systems look simple until you hit production. The learning curve is expensive, and most of the lessons live in the gaps between what documentation says and what APIs do.
FinTech 4 min read