Read up on the 10 takeaways from the episode:
1) The real problem wasn’t spending - it was how decisions were made
Before Spendesk existed, Rodolphe had already lived through the problem inside fast-growing companies. Teams were encouraged to move quickly and take ownership. That autonomy was essential to growth. But the moment money entered the equation, everything slowed down.
Finance, understandably, needed control. Visibility over cash, approval processes, compliance. The result was a system where every expense had to be validated and justified - often manually. And as the company scaled, that system became heavier and heavier.
At some point, the contradiction became obvious.
“I was rebuilding the exact bureaucracy I had hated before, just to regain control.”
That’s where the real insight came from. The issue wasn’t that employees were spending too much, or that finance lacked tools. It was that companies were trying to operate in a modern, decentralized way with systems designed for centralized control.
Spendesk was conceived as a way to resolve that structural mismatch: to give teams the ability to act, while allowing finance to keep a clear, real-time view of what was happening.
2) The first version failed and clarified everything
Like most early-stage products, the first version of Spendesk was far from what it would eventually become. The initial idea was to solve a very specific pain point: the sharing of company cards.
The solution they built was simple. A browser extension that allowed employees to access a shared company card, while logging who used it and when. It worked, technically speaking. But it didn’t solve the core issue.
Finance teams didn’t trust it. Security concerns remained. And most importantly, the product sat on the surface of the problem rather than addressing its root.
That failure turned out to be decisive. It forced a realization that would shape everything that followed: you can’t build a meaningful finance product if you don’t control the transaction itself.
In other words, visibility without control isn’t enough.
3) Building under constraints and learning faster because of it
At that stage, nothing was in place to make things easier. There were no obvious payment partners in Europe, no infrastructure readily available to issue cards, and no fully formed technical team to build the product quickly. Rodolphe himself went back to coding to push things forward, even though he hadn’t done it in years.
“I would spend four days building what a good engineer would do in one hour.”
From the outside, this looks inefficient. But in practice, it created something far more valuable than speed: proximity to the problem.
Eventually, they found a partner that allowed them to issue virtual cards. It wasn’t perfect, and the setup introduced friction that would normally kill adoption. But it was enough to test the next hypothesis.
4) The first real signal: customers taking irrational risks
The early product allowed companies to generate virtual cards for online purchases. To use it, however, customers had to pre-fund accounts - through a structure that was far from reassuring.
They had to wire money to Gibraltar.
And yet, customers did it.
That moment revealed something fundamental: the pain was strong enough that companies were willing to accept friction, uncertainty, and risk to solve it.
When users behave in ways that seem irrational on paper, it’s often because the problem you’re solving is much bigger than you thought.
5) The second signal: usage that grows instead of fading
If the first signal proved that the problem existed, the second showed that the solution was working.
Typically, early SaaS products see a burst of activity followed by decline. Users test, explore, and then slowly disengage when the product doesn’t integrate deeply enough into their workflows.
That didn’t happen here.
Week after week, usage increased. More transactions, more teams involved, more use cases emerging organically inside companies. What started as a tool for marketing teams quickly expanded to other departments, without any push from the product itself.
“Normally usage declines. For us, it kept increasing.”
6) The final signal: willingness to pay - without friction
Up to that point, everything had been free. Which meant one critical question remained unanswered: would companies actually pay for it?
When they introduced pricing, the expectation was cautious. Losing a significant portion of users would have been normal, even healthy. Instead, almost all customers converted.
Out of around a hundred companies, only a handful chose not to continue.
“We thought we would lose half. Almost everyone stayed.”
7) When investors don’t believe what customers already know
With these signals in hand, fundraising should have been straightforward. It wasn’t.
For several months, the response from investors was largely negative. The core idea — giving employees direct access to company spending — went against deeply ingrained assumptions about financial control.
“Companies will never give cards to employees.”
The breakthrough came when they changed their approach. Instead of trying to convince traditional venture capital, they turned to people who understood the problem directly: founders, operators, and early customers.
Within three weeks, the round was closed.
8) Building in Europe means building complexity from day one
Spendesk’s early development was rooted in Europe, largely because that’s where the founders had access to their first network and customers. But this choice came with a structural challenge that shaped the company’s trajectory.
Unlike the US, Europe is not a single market. Expanding means navigating multiple countries, each with its own regulations, behaviors, and operational constraints. What works in one market doesn’t automatically translate to another.
“You end up duplicating your effort in each country.”
This makes growth slower and more complex, but it also creates a different kind of strength. Companies that succeed in this environment build resilience early, and develop systems that can handle fragmentation.
9) The role of intuition when everything becomes less clear
Looking back, one of the most striking lessons doesn’t come from the early product decisions, but from how decisions evolve as the company grows.
In the beginning, founders rely heavily on instinct, simply because there are no established rules to follow. As the company scales, that instinct is often diluted by external input — advisors, investors, benchmarks, best practices.
That shift can be dangerous.
“Every time I ignored my intuition, it was a mistake.”
The challenge isn’t to reject advice, but to avoid overfitting to it. The ability to filter signal from noise becomes a critical skill, especially when navigating uncharted territory.
The takeaway
What makes Spendesk’s early story interesting isn’t just the outcome, but the sequence of signals that shaped it.
A problem that felt operational turned out to be structural. A failed MVP clarified what truly mattered. Customers validated the product not through feedback, but through behavior — by taking risks, increasing usage, and ultimately choosing to pay.
Behind it all, there’s a consistent pattern: progress didn’t come from perfect planning, but from continuously testing assumptions against reality, and adjusting quickly when they didn’t hold.
In the end, building a category isn’t about having the right idea from the start.
It’s about recognizing, early enough, when you’re onto something real and having the discipline to follow it all the way through.
