The Twenty Minute VCFabien Pinckaers, CEO @Odoo: The Billionaire Founder Who Doesn’t Care About Money | E1259
CHAPTERS
Obsessed founder mindset and Odoo’s long-game stance (no IPO, low price, sorrysap.com)
Fabien opens with his worldview: obsession is required to win, and Odoo is built for long-term impact rather than maximizing short-term valuation. He frames Odoo’s unusual choices—never selling shares, keeping prices low, and rejecting an IPO—as consistent with that mission.
- •Success requires obsession; treating it as “just a job” won’t build hypergrowth
- •Managers and Fabien repeatedly buy shares; the company hasn’t been built to cash out
- •No IPO and no sale: public markets push short-term behavior
- •Deliberately low pricing aligns with commoditizing business software
- •Early competitive ambition symbolized by buying the “sorrysap.com” domain
Early entrepreneurship: teenage software gigs, side projects, and the painful logistics of physical products
Fabien recounts starting to build management software for his father’s network as a teenager, driven more by building than money. He continued stacking projects through university—from e-commerce to security software to a Linux T‑shirt store—learning what scales and what doesn’t.
- •First paid software work began at 13; motivation was impact and usage, not cash
- •University years filled with experiments: e-commerce, games, antivirus, more
- •Linux merchandise e-commerce worked but exposed fulfillment/logistics pain
- •He describes prioritizing building (and having fun) over traditional schooling
- •These experiments set up the desire to unify everything into one platform
From Belgium’s biggest art marketplace to the idea of Odoo
Before Odoo, Fabien built a high-volume online art marketplace that outsold ebay.be in item volume, but struggled with a weak business model. The experience reinforced that building something big isn’t enough—you need a monetization model that works.
- •Art marketplace moved ~15,000 items/month and worked with auction houses
- •Became one of Belgium’s largest in the category, but monetized poorly
- •Revenue (~€5k/month) didn’t match the effort and scale of what he built
- •Lesson: distribution and scale don’t fix a broken business model
- •Catalyst to focus on a single, meaningful product category: management software
Building Odoo “the fat way”: tackling the whole ERP suite from day one
Fabien describes intentionally rejecting MVP minimalism to solve a “big problem” end-to-end: everything a business needs in one integrated system. He argues this early “build it all” approach is what later made Odoo cohesive rather than a patchwork of tools.
- •Started by consolidating his passions: development + management into one product
- •Built accounting, logistics, purchasing, etc. all at once (took two years)
- •Inspired by Paul Graham’s idea: big companies solve big problems
- •Acknowledges risk: slower monetization and higher complexity early on
- •Belief: the integrated big-picture architecture became Odoo’s moat
Bootstrapping via services to 100 people—and months near bankruptcy
Odoo initially grew as a services-heavy business, building whatever customers asked for to generate cash. That enabled headcount growth but created repeated periods of existential cash stress, forcing painful trade-offs and nonstop survival mode.
- •Professional services funded development; features were customer-driven
- •Scaled to ~100 people but endured prolonged “near bankruptcy” periods
- •Cash stress distorted decisions: choosing deals that pay faster vs. best deals
- •Bootstrapping kept Fabien as primary shareholder but increased hardship
- •The experience shaped later focus on recurring revenue and sustainable monetization
2010 pivot: raise €3M, stop services overnight, and try open-source maintenance revenue
Fabien explains the first major pivot: transitioning from services to a software vendor model, funded by a €3M round. Odoo remained open source, with monetization through support and maintenance contracts—and a growing partner ecosystem—but churn undermined recurring revenue.
- •Raised €3M at ~€10M post (he calls it a poor valuation)
- •Stopped services abruptly to refocus on R&D and UI/recurring revenue
- •Open-source model: sell maintenance/support, bug fixes, maintenance contracts
- •Built a global partner network to deliver implementations
- •Problem: customers stopped paying after year one because software kept working
Second pivot under pressure: open-core monetization and the community backlash
When maintenance revenue failed and cash hit near zero again, Odoo shifted to an open-core model (80% open source, 20% paid). The pivot unlocked strong growth, but created a trust crisis with the open-source community due to earlier messaging that Odoo would ‘always’ be fully open source.
- •Cash nearly ran out (weeks left), forcing decisive monetization change
- •Open-core model: most features free, premium features paid
- •Once monetization worked, growth became smooth and cash constraints disappeared
- •Major challenge: community felt betrayed; partners threatened to leave
- •Key learning: communicate optionality early (“open today, may monetize later”)
Scaling pains and the ‘product wins’ philosophy—why marketing only buys time
Fabien argues that in slow-moving markets like ERP, product quality eventually beats marketing and brand, though distribution can accelerate timelines. He also connects the open-core controversy to a broader belief: a great product retained partners despite conflict.
- •In ERP, product quality compounds over time; legacy systems remain ‘shitty’ for decades
- •Marketing can accelerate growth by years, but cannot overcome a weak product long-term
- •Odoo survived partner/community conflicts largely because the product was strong
- •Word-of-mouth remains the dominant acquisition channel because users become fans
- •Speed matters most in building durable assets (especially product), not just revenue
Pricing as a growth lever: the disastrous partner backlash vs. the 2022 breakthrough
Fabien shares that pricing changes were both his worst and best decisions. An earlier pricing experiment multiplied cost by users and number of apps, triggering partner revolt and costing roughly a year of growth; in 2022, lowering entry price for small customers dramatically boosted acquisition while raising price for larger customers.
- •Frequent historical pricing experiments created confusion and partner resistance
- •Bad model: price = €10 × users × apps, ramping too aggressively
- •Partner network refused to sell; trust took months to rebuild; eventually reverted
- •2022 change: lower price for small customers (to ~€20) and raise for larger ones
- •Result: ~2.8× more clients acquired after the pricing shift
Operating without shared budgets: internal promotions, minimal KPIs, and the ‘team leader as best practitioner’ model
Fabien describes Odoo’s unconventional management system: few formal processes, budgets controlled centrally, and leaders expected to elevate team craft rather than manage via metrics. He illustrates KPI pitfalls with a story where the best consultant looked worst on paper because he took the hardest projects.
- •Odoo avoids hiring external VPs/managers to protect culture and working norms
- •Team leaders are expected to be the best in the team, improving others’ skills
- •Budgets/forecasts exist for finance, but aren’t used to ‘run’ teams day-to-day
- •KPIs can mislead; context matters (hard projects distort performance metrics)
- •Recurring meetings are discouraged; coordination happens through daily work
Hiring at scale: job auditions, IQ testing, extreme speed, and training young teams
Fabien explains how Odoo hires and develops young talent at scale—prioritizing practical on-the-job tests and fast decisions over resumes. With an average employee age of 26, Odoo emphasizes onboarding, coaching, and purpose as key drivers of performance and retention.
- •Candidates are tested on the core action (build code, run a demo) rather than resumes
- •IQ test is used as a secondary predictor (after job performance in the audition)
- •Hiring is highly automated and fast—often within ~5 days from application to offer
- •Culture issues are rare; most failures are competency-related and seen within 6 months
- •Structured onboarding: ~1 month training + ongoing coaching; teams ~10 people
Relocating to fix growth: the India year and lessons from scaling stages
Fabien recounts moving with his family to Gujarat for a year to unblock India’s growth, helping the team scale from 200 to 800 employees and dramatically increase new client signings. He also outlines how the founder’s role changes from 1→10, 10→100, and 1000+ scales: building the business, transmitting culture, then driving scalability.
- •Fabien relocated to India for a year to accelerate growth; family joined
- •India went from ~16 new clients/month to ~800/month after operational changes
- •He emphasizes helping strong local leaders rather than replacing them
- •Scaling stages: 1→10 build product/business; 10→100 culture via managers; 1000+ scalability
- •Founder time split: ~50% product/R&D, ~50% internal improvements across functions
Global expansion strategy: director-first, tier-two cities, and retention as the scaling engine
Odoo expands internationally by selecting the right leader first, then letting that leader choose the location—hence offices like Buffalo. Fabien argues tier-two cities improve employee retention and efficiency, which compounds productivity over time, especially in sales.
- •Location matters less than the director; leadership quality determines success
- •Odoo sells largely online, enabling non-obvious hubs (e.g., Buffalo)
- •Prefers tier-two cities to avoid talent wars with Big Tech and reduce turnover
- •Retention is framed as the key scaling lever—experienced people become far more productive
- •Managers/directors are promoted internally; external leadership hires are avoided
Competition and commoditization: why Odoo thinks it can outlast SAP/Microsoft and unify the SMB stack
Fabien positions Odoo as solving what incumbents and point solutions haven’t: a simple, integrated suite that’s affordable. He predicts business software will commoditize like operating systems and office suites—consolidating into a handful of dominant platforms—driving his insistence on low pricing and tight focus.
- •Odoo aims to combine breadth (suite) with usability and affordability—rare in ERP
- •Sees incumbents as expensive/slow; point tools excel but don’t integrate well
- •Mission: commoditize management software so most companies run the same platform
- •Pricing strategy supports mass adoption, akin to Office/Workspace models
- •He expects consolidation: from many vendors today to 1–3 major players long-term
Capital strategy and incentives: profitable growth, secondaries at $5B, and ‘never IPO’
Fabien explains Odoo’s investor strategy: no fundraising since 2014, only secondary transactions for liquidity, with clear alignment that there will be no IPO or acquisition. He also reveals Odoo insiders intentionally bought shares in earlier rounds and prefers lower valuation pricing when purchasing.
- •Reports ~€550M revenue with ~50% growth; profitable and self-financing
- •$500M secondary at ~$5B valuation involved Summit selling to major institutions
- •Fabien and managers bought shares in rounds (even using loans) and rarely sell
- •No IPO: avoids short-termism, compliance burden, and constraints on communication
- •Liquidity handled via periodic secondaries every ~3–4 years when investors want to sell
Sales and enterprise motion: inbound-led GTM, demos as training, and culture clash in big-company deployments
Odoo built to half a billion in revenue primarily through inbound demand and product-led word-of-mouth, with a sales process centered on frequent demos. Moving upmarket requires a distinct enterprise department and implementation methodology that minimizes services, but early phases with large customers often create cultural friction.
- •Average contract is low (~$3.5k ARR), historically making outbound unattractive
- •Sales reps improve via repetition: ~2 demos/day; product fluency is core
- •Outbound only recently tested (~30 people vs ~1,800 sales total)
- •Enterprise requires different methodology and a new department, while keeping culture
- •Biggest enterprise challenge: culture clash with large clients before alignment
AI pragmatism and quick-fire: start from problems, skepticism on hype, and education as a societal lever
Fabien takes a pragmatic view on AI: many demos are hype when UX would solve better, but narrow applications like invoice recognition are truly transformative. In the quick-fire, he downplays investor value relative to operators, discusses pay practices, and argues education (especially in Europe) underemphasizes entrepreneurship and computing.
- •AI is a tool, not a goal—start from inefficiencies and choose best solution (UX, AI, algorithms)
- •Skeptical of agent hype (e.g., call-center scenarios) vs. good self-serve portals
- •Strong AI wins exist: ~98.5% invoice recognition, shifting accountants to validation
- •Investors can challenge but rarely provide solutions; operators matter most
- •If “CEO for a day,” he’d reform education (more IT/entrepreneurship/leadership)
