By playing, you agree to uListen's Terms and Privacy Policy and YouTube's Terms of Service.

The Twenty Minute VC

Fabien Pinckaers, CEO @Odoo: The Billionaire Founder Who Doesn’t Care About Money | E1259

Fabien Pinckaers is the Founder & CEO of Odoo, one of the most incredible businesses that you might not have heard of.

Fabien PinckaersguestHarry Stebbingshost

Feb 12, 20251h 15mWatch on YouTube ↗

Summaries, chapters, transcripts, and FAQs on this page are made by uListen, not YouTube.

CHAPTERS

Jump to publisher timestamps

Chapter summaries

Fabien’s founder mindset: obsession, low prices, no IPO
Fabien opens with an unconventional founder philosophy: being obsessed with the product, keeping pricing low, and building long-term without IPO ambitions. He frames Odoo as a mission to commoditize business software rather than maximize short-term valuation.
- •Success requires obsession, not a “job” mentality
- •Deliberate preference for low pricing and broad adoption
- •Managers and Fabien continually buy shares; no share selling mentality
- •Clear stance: no IPO, no company sale—focus on long-term impact
Early hustles: from teenage software gigs to an art marketplace
Fabien recounts building management software for small businesses as a teenager and experimenting with many side projects through university. He highlights lessons from an art marketplace that scaled in volume but had weak unit economics.
- •Started coding and selling software at 13; motivation was building, not money
- •University years: e-commerce, antivirus, games, and a logistics-heavy T‑shirt business
- •Built a major Belgian art marketplace (outsold ebay.be in volume)
- •Learned that scale without a strong business model doesn’t create outsized value
Why Odoo was born: one integrated system instead of many tools
Fabien explains Odoo as the fusion of his passions—development and management—aimed at making a single, integrated suite for how companies actually operate. He intentionally stopped other projects to focus on management software as the “big problem.”
- •Chose to consolidate efforts into one management software vision
- •Started with early customers from auction-house/e-commerce work
- •Belief in solving a complex problem to build a big company (Paul Graham influence)
- •Emphasis on the “big picture” integration vs. disconnected tools
The “fat startup” approach: building everything first (and the bootstrapped struggle)
Instead of an MVP, Fabien built accounting, logistics, purchasing, and more upfront, taking two years for the first version. To fund progress, Odoo operated like a services company—growing to 100 people but repeatedly nearing bankruptcy.
- •Built a broad ERP suite from the start rather than a narrow MVP
- •Bootstrapped via services and custom development—cash-flow driven roadmap
- •Scaled to ~100 people on services despite poor scalability
- •Long periods close to bankruptcy shaped ruthless trade-offs and survival focus
2010 pivot: stop services, raise the first round, become a software company
Fabien describes the decisive shift to a true software vendor model, driven by dissatisfaction with UI and the need for recurring revenue. The pivot required Odoo’s first fundraising and a hard stop to services work.
- •Stopped services “from one day to another” to refocus on product and R&D
- •First fundraise: €3M at ~€10M post-money (painful dilution)
- •Built partner network globally to deliver implementations
- •Moved toward recurring revenue rather than project-based income
Open source monetization crisis: maintenance-only didn’t work
Odoo’s open-source model initially relied on maintenance/support contracts, but customers churned after year one when they felt they no longer needed support. The result was another cash crunch and the need for a new business model.
- •Open source + maintenance contracts led to weak retention of revenue
- •Customers could keep using software without paying (no license fee)
- •Partner model worked operationally, but economics broke down
- •Cash neared zero again, forcing another pivot
Open-core pivot and community backlash: fixing the model and rebuilding trust
Fabien explains the switch to open core—most features open source, some paid—which immediately improved monetization and stability. However, the shift triggered conflict with the open-source community due to earlier messaging, requiring a year to rebuild trust.
- •Adopted open-core: ~80% open source, ~20% paid
- •Went from survival mode to stable cash generation (~€15M revenue early on)
- •Major lesson: transparency with community about future monetization possibilities
- •Product strength helped partners and users stay despite criticism
Pricing as the biggest lever: one disastrous experiment and the 2022 breakthrough
Fabien details how frequent pricing changes created confusion and partner resistance, including a formula that scaled price too aggressively by users × apps. He contrasts that with the 2022 change that lowered prices for small customers and accelerated acquisition dramatically.
- •Bad pricing experiment lost ~1 year of growth due to partner backlash
- •Aggressive model (users × number of apps) made Odoo feel too expensive
- •2022 change: dropped entry pricing to ~€20/user for small customers, raised for larger
- •Result: ~2.8× more clients and stronger growth momentum
How Odoo grows: word-of-mouth, product-first speed, and surviving early hardship
Odoo’s growth engine is primarily customer advocacy—turning users into fans—rather than heavy paid marketing. Fabien ties long-term 50% annual growth to sustained product velocity and the grind of cash-stressed early years.
- •Primary acquisition channel: word-of-mouth from delighted users
- •Speed matters most in building product assets, not just revenue
- •Early hardship centered on payroll risk and difficult layoffs
- •Long-run compounding: ~50% yearly growth sustained over ~20 years
Management without “management”: no KPI culture, minimal budgets, internal promotions only
Fabien describes Odoo’s atypical operating system: avoid external managers, minimize planning rituals, and focus team leads on making teams better. He argues KPIs can distort reality and that responsible autonomy outperforms budget-driven behavior.
- •No external VPs/directors; leadership is internally grown
- •Teams don’t operate on shared budgets/forecasts; finance ensures cash health
- •Skepticism of KPIs—story of top expert scoring worst due to project selection bias
- •Bans recurring meetings; prefers direct collaboration and coaching
Recruiting and training young talent at scale (average age 26)
Fabien explains Odoo’s high-throughput hiring process centered on real work tests and fast decisions. He also outlines onboarding and coaching systems designed to develop young hires quickly and keep teams small and effective.
- •Hiring based on job simulations (build code, run a demo) rather than resumes
- •IQ test as a secondary predictor of performance; fast process (often <5 days)
- •Low “culture fit” failure rate claimed; most exits are competency-based
- •One-month onboarding + on-the-job coaching; small teams (~10)
Global expansion playbook: follow the leader, avoid tier-one cities, optimize retention
Fabien’s approach to geography is person-first: find the right director, then let them choose the location. He argues tier-two cities win on retention and cost-efficiency, which compounds productivity—especially in sales.
- •Location is secondary; the director quality determines success
- •Examples: Buffalo office success vs. San Francisco retention challenges
- •Preference for tier-two cities to reduce churn and improve loyalty
- •Retention drives productivity: experienced salespeople can sell ~2× over time
Competing with SAP, Microsoft, and point solutions: commoditizing management software
Fabien frames Odoo’s “competition” as a market gap: incumbents are broad but expensive and clunky, while point tools are great but fragmented. Odoo’s ambition is to become the integrated, affordable default—like Office suites did for productivity software.
- •Odoo’s wedge: integrated suite + simplicity + affordability
- •Incumbents: broad suites but ‘slow/expensive’; challengers: great single-purpose tools
- •Belief that mature management software will consolidate to a few global players
- •Strategy: be best by application quality, not vertical customization
Sales and enterprise motion: inbound-led scale, then industry apps and enterprise culture clash
Fabien details building sales through product demos and inbound leads, enabled by low ACV and heavy product-led momentum. As Odoo matures, it’s adding industry-specific packages and building an enterprise department with a distinct implementation approach.
- •Historically inbound-only; outbound only recently tested with a small team
- •Sales training emphasizes demos (high repetition) over scripts and outbound
- •Industry-specific ‘apps per industry’ launched to sharpen PMF and targeting
- •Enterprise expansion: minimize services, optimize implementation methodology, manage culture clashes
Valuation, secondaries, and governance: why Odoo won’t IPO or sell
Fabien explains why valuation is secondary to building and why Odoo prefers periodic secondary transactions to provide liquidity. He shares details of the large secondary at a $5B valuation and reiterates a firm “no IPO, no sale” stance to protect long-term focus.
- •Revenue disclosed (~$550M) and profitability; valuation seen as “on paper”
- •Secondary transaction: €500M at ~$5B valuation; major buyers include Sequoia/BlackRock/Mubadala/CapitalG
- •Founders/managers buying shares each round; Fabien retains ~57% ownership
- •No IPO to avoid short-termism and public-company complexity; liquidity via periodic secondaries
AI, Salesforce, and the next decade: problem-first innovation and consolidation thesis
Fabien shares a pragmatic AI philosophy: start from workflow pain, then choose AI or UX improvements accordingly. He predicts an eventual consolidation of business software similar to operating systems and office suites, aiming for Odoo to be one of the few winners.
- •AI is useful but often overrated; UX can beat agent experiences in many cases
- •Strong example: invoice recognition accuracy (~98.5%) transforming accounting workflows
- •Salesforce/SAP will persist, but challengers can grow faster; enterprise shifts create openings
- •Long-term view: management software will commoditize and consolidate to 1–3 global platforms

Publisher timestamps

Get more out of YouTube videos.

Read along on your phone, search it beside the video, or ask your favorite AI app what was said.