Fabien Pinckaers, CEO @Odoo: The Billionaire Founder Who Doesn’t Care About Money | E1259
Summary
- Odoo’s €550 million in revenue is the product of roughly 50% annual growth sustained for 20 years, not one breakout year. Fabien says the company is now “extremely profitable,” has not raised primary capital since 2014 and generates more cash than it can sensibly spend. The harder years meant prolonged near-bankruptcy, late salaries and financings completed when Odoo had little leverage.
- The decisive inflection was business-model fit: services financed product breadth, open-source maintenance failed to renew, and an 80/20 open-core model finally monetized Odoo’s product and community. With roughly two weeks of cash remaining, Odoo shifted to a model in which 80% of features remained open source and 20% were paid. Breaking its promise of permanent openness cost about a year of trust, but the resulting revenue let it expand its development team tenfold and contribute more to open source.
- Fabien treats low pricing as a strategic moat, not foregone monetization. An unsuccessful formula of €10 × users × applications provoked a partner revolt and cost roughly a year; in 2022 Odoo cut small-customer pricing across applications from around €120 to €20 per user per month while charging larger customers more, subsequently attracting 2.8 times as many clients. “If I can decrease the price, I would do it right away.”
- Odoo is explicitly betting that horizontal management software becomes a commodity controlled by one to three integrated platforms. Its suite replaces fragmented CRM, accounting, commerce and logistics products, with application quality taking precedence over industry-specific positioning. Fabien’s long view: as with operating systems and office suites, “everybody will use the same CRM, the same accounting, the same website builder.”
- The operating model rejects standard scale-up orthodoxy: no externally hired VPs, internal promotion only, few recurring meetings, and leaders who remain their teams’ strongest practitioners. Work samples plus IQ testing support offers within roughly five days; a 5,000-person workforce averaging 26 years old operates in small teams, while coaching and retention reduce reliance on layers of management and formal KPI systems.
- Go-to-market economics are unusual even for efficient SaaS: Odoo reached €550 million in revenue through predominantly inbound demand and word of mouth at roughly €3,500 in ARR per customer. Salespeople become product experts through two demos per day; only recently did around 30 people begin testing outbound around 50 industry applications. Enterprise expansion keeps services at 18% of revenue and deliberately removes implementation heaviness.
- Control and time horizon are the cap-table strategy: Fabien owns 57%, buys shares alongside managers, rejects both an industrial sale and an IPO, and provides liquidity through secondaries every three to four years. The latest transaction moved €500 million of shares at a €5 billion valuation, mainly from Summit Partners to Sequoia Capital, CapitalG, BlackRock and Mubadala. He welcomed low transaction prices because “in every transaction I was purchasing shares.”
- Fabien’s AI position is selective: agents are useful where they solve workflow problems, but conventional UX often remains faster. He contrasts an Agentforce help-desk conversation with simply clicking a portal button, while invoice recognition at 98.5% genuinely changes accounting by turning data entry into validation. On a possible AI winter, his answer is deliberately unresolved: “I don’t know.”
Deep dive
1. Odoo began as an anti-MVP built around the whole problem
Fabien started building management software at 13, motivated less by money than by seeing people use something he made. As a student he tried e-commerce, antivirus, games and Linux merchandise; physical shirts taught him that logistics was a poor fit for someone who also wanted to “drink beer.”
His art marketplace reached 15,000 objects per month and sold more items than eBay Belgium, yet generated only about €5,000 monthly. The lesson embedded in that contrast: substantial usage did not rescue a bad business model.
Odoo unified his interests in development and management. Instead of an MVP, he spent two years building accounting, logistics and purchasing simultaneously—the “complete opposite” of lean startup orthodoxy. Paul Graham’s argument that a large company must solve a large problem supplied the logic: everything a business needs was difficult enough to matter.
2. Services created the product—and recurring survival crises
Odoo initially built whatever customers requested, using services to finance feature after feature until the company employed 100 people. That breadth eventually became an advantage: the suite was designed with everything working smoothly together, “not a patchwork of different software,” even though services produced weak economics.
Near-bankruptcy was not one dramatic evening but “months and months” without sleep. Cash pressure corrupted decisions: Odoo accepted customers because they paid quickly, dismissed people Fabien liked and optimized for the next payroll rather than the best contract.
In 2010, Fabien stopped services “from one day to another” to repair a comprehensive product with a poor interface and pursue recurring software revenue. The transition required Odoo’s first round: €3 million at a €7 million pre-money valuation, leaving investors with 30% at €10 million post-money. He received around 10 offers and chose Sofinnova Partners, which led the round.
Open-source maintenance then failed because customers paid for the first year and concluded they did not need support afterward. With perhaps two weeks of cash left, Odoo shifted to open core: 80% remained open source and 20% became paid. Once monetization worked, survival stopped being the company’s organizing motivation.
3. Breaking the open-source promise was costly but ultimately additive
Fabien’s deepest regret is the story he told the community: Odoo was open source, would always remain so and opposed proprietary software. When financial reality forced open core, partners left, critics attacked and trust took roughly a year to rebuild—negative comments persist even now.
His concession is unusually direct: the community had been “built on another story.” Had he said Odoo was open source today but might eventually need monetization, he believes the company could have avoided much of the conflict without misrepresenting the product.
The irony changed his view of the trade-off. Moving from 100% open source to 80% enabled Odoo to expand its development team roughly tenfold, so it now contributes far more open-source software than when the company could barely pay salaries. “It was a bad calculation on my part.”
4. Pricing mistakes destroyed a year; a price cut unlocked demand
During the unstable years, Odoo repeatedly changed product, services, business model and pricing. Its worst formula charged roughly €10 multiplied by both users and applications, causing the price to rise too aggressively as customers adopted more of the suite; partners effectively refused to sell it.
The hard part was distinguishing resistance to change from evidence that the price was wrong. Fabien spent about nine months insisting partners did not understand the value before restoring the old model, damaging trust and losing approximately one year of growth.
The 2022 change inverted that failure. When inflation pushed others to raise prices, Odoo reduced pricing for small customers across applications from around €120 to €20 per user per month while increasing larger-account pricing. Acquisition accelerated, producing 2.8 times more clients; happy users and word of mouth remain the principal lead source.
5. The horizontal suite is a deliberate commoditization wager
The host’s vertical-SaaS challenge—narrow markets offer clearer customer profiles and messaging—meets Fabien’s application-level answer. Odoo aims to build the best CRM, accounting product and website builder, arguing that mature applications increasingly resemble one another across industries.
Small and midsize businesses still combine spreadsheets, Slack, email tools, WordPress and other products that integrate poorly and cost too much to maintain. Microsoft, SAP and NetSuite tried broader platforms, yet Fabien places market adoption below 10%; Odoo’s opportunity is to make one integrated suite simple and affordable.
His analogy moves from phones to operating systems and office suites: many early products eventually consolidated around a few mature standards. Management software adds business complexity to technical and UX complexity, but Fabien expects the same endpoint—“one, two or three players” serving most of the world.
6. Product focus substitutes for managerial scale
Fabien argues that Odoo’s product is years ahead because complex software made simple requires “a few genius people,” not an army of 10,000 developers. He credits unusually strong developers, good management and relentless focus on one product rather than superior access to capital.
Odoo never recruits VPs, managers or team leaders externally. A leader’s sole objective is to make the team better, which means the leader must remain its best practitioner: an outside manager cannot improve developers if the existing developers already surpass that manager technically.
Team leaders do not receive budgets, forecasts or most formal goals; the CFO and finance team control the company budget, including hiring capacity and spending, without sharing it with teams. Sales targets are an exception. For ordinary purchases, Fabien says approval processes can cost more than the item itself, so employees can buy a $30 or $50 scanner and get reimbursed immediately.
The company also forbids recurring meetings and resists proliferating products and departments. Fabien calls organizational complexity “a dark force” that managers continually create; keeping Odoo near three major departments and roughly 400,000 lines of code requires constant intervention.
7. Work samples beat résumés, while KPIs can invert reality
Hiring centers on doing the job: developers develop, sales candidates demonstrate and pitch, and résumés carry little weight. An IQ test is Odoo’s second-best predictor after demonstrated job ability; Fabien retrained recruiters who overweighted résumé discussion simply because it consumed more interview time.
The process is one meeting, largely automated and typically completed within five days: applicants book directly into an interviewer’s calendar and receive an offer the next day. Fabien’s claim is categorical—after watching a developer work for three hours, it is usually clear whether the person is good.
A US director once insisted on satisfaction, delivery-time and application-deployment KPIs. After three months, Odoo’s best Belgian consultant ranked last because he had received every difficult, troubled project. The whole team knew he was strongest while the dashboard said the opposite: “Things are very subjective.”
Cultural mismatch is, in Fabien’s estimate, exceptional—probably less than 1% of the time—and more than 90% of dismissals concern competence. His recurring error is waiting too long because entrepreneurial optimism expects improvement: once he starts thinking negatively about working with someone, the decision is probably already late.
8. A young workforce scales through purpose, coaching and asymmetric talent
Odoo’s 5,000 employees average 26 years old. Fabien rejects the claim that young Europeans will not work: they will work intensely when they have purpose, passion and visible impact, as demonstrated by a young organization building software for millions of users.
Everyone receives one month of structured onboarding with e-learning, exercises and certification, followed by on-the-job coaching in teams of roughly ten. Team leaders work beside people daily rather than managing through weekly meetings, formal plans or detached performance systems.
Recruiters look for someone world-class at one thing and accept weaknesses that fit the context. Selecting for multilingual, technical, socially polished all-rounders produces people “average at everything”; transformative talent may be weak elsewhere, and some departments can accommodate even low sociability.
9. Geographic expansion starts with the leader, not the market map
Odoo chooses a trusted internal director first and lets that person determine location. Its Buffalo office exists because an exceptional employee wanted to move there; Fabien would rather back that person in a secondary city than hire an average director in Silicon Valley and spend heavily around Google, Microsoft and Apple.
Tier-two cities support the metric he considers decisive: retention. A salesperson with five to seven years’ experience may sell twice what the same person produces during the first two years, so high turnover in prestigious markets quietly destroys operating efficiency.
India illustrated intervention without replacement. A strong early employee had remained near 200 staff for seven years; Fabien relocated there for a year, retained the entire management team, grew employment to 800 and raised signed clients from 16 to roughly 800 per month.
His stage model is simple: one to ten people is about constructing product and business; ten to 100 shifts the founder’s culture into middle managers’ behavior; beyond 1,000, scalability and frictionless repetition dominate. Smart early employees can evolve across all three stages.
10. Inbound efficiency funds an enterprise push without service dependence
Odoo reached €550 million in revenue with an average contract near €3,500 ARR and, until recently, essentially no outbound sales. Demand came inbound, largely through word of mouth; representatives learn the broad suite through two product demonstrations per day until repetition creates expertise.
Outbound began only months before the interview, with roughly 30 people against an approximately 1,800-person sales organization. The catalyst was product maturity: Odoo packaged applications for 50 industries, starting with areas where existing customers already proved product-market fit.
Fabien says Odoo has “plenty of competitors” yet feels it has none. Large suites such as SAP and Microsoft offer breadth but are slow, expensive and disliked; point products such as Slack, Mailchimp and Asana deliver simplicity but only one function. Odoo’s wager is breadth, usability and pricing near €20 for small customers.
Enterprise required a separate department, sales motion and implementation methodology, but services remain only 18% of revenue. Large customers initially love the demos, then experience one or two months of culture clash with Odoo’s direct pace; projects become smoother once both organizations adjust.
11. Private control protects the long-term product cycle
Odoo’s second primary round raised €7 million at a €23 million pre-money valuation after receiving only one offer, from XAnge. Investors saw repeated pivots, limited profitability and merely regular—not exceptional—growth. Fabien calls both primary rounds poorly priced, yet raising only twice preserved majority ownership.
The recent €500 million secondary valued Odoo at €5 billion. Summit Partners supplied most of the shares, while Sequoia Capital, CapitalG, BlackRock and Mubadala bought; Fabien and managers sold nothing, having historically borrowed to purchase more shares whenever transactions occurred. He still owns 57%.
There will be “no industrial exit” and “never an IPO.” Investors accepted liquidity through secondaries every three or four years; the latest had more buyers than sellers. Fabien wants neither quarterly earnings pressure nor public-company complexity, preferring the freedom to build across 10- or 20-year competitive cycles.
12. AI is one tool inside a culture of autonomy and obsession
Fabien finds Salesforce’s Agentforce help-desk example unconvincing: calling, potentially failing recognition and answering identity questions can be less efficient than clicking a portal link. His rule is to begin with wasted time, then choose UX, AI or another algorithm—not begin with “I want to do AI.”
Accounting provides the counterexample: Odoo reaches 98.5% recognition on invoices and bills, which Fabien says exceeds humans and changes accountants from data-entry operators into validators. He expects disruptive use cases even if an AI winter arrives, but refuses to predict whether that winter will happen.
Odoo’s cultural triad is autonomy, responsibility and evolution. If a salesperson asks permission to buy a €50 barcode scanner, a manager should return the decision: “You’re smart…decide.” The same logic lets employees choose their own titles and avoids controls that would cost more than the purchase.
Fabien spends roughly half his time on product and half improving internal functions, sometimes relocating for a year. Investors can challenge and offer a point of view, but he says the solution must come from the founder; the people doing the work challenge him more than the board. Sustaining 50% growth requires focus, continued innovation and preservation of the culture—alongside the obsession he considers necessary to build such a company.