Jérôme Paquot

🚨 How do you scale Belgium’s biggest SaaS company at 40% per year—without losing control, culture, or clarity? 🎙️ In this new episode of De CFO podcast, I sit down with Alessandro Mazzocchetti, CFO of Odoo — the €5B+ Belgian tech powerhouse with over €500M in ARR and clients in 175+ countries. But this isn’t your typical growth story. It’s a rare look behind the numbers: 👉 How Odoo builds pricing discipline in a fast-moving market 👉 Why the CFO should own the liquidity events — not just report on them 👉 What it takes to scale a finance team inside a product-led organization 💬 Alessandro shares how he’s helped steer Odoo from a small ERP disruptor to one of Europe’s most successful SaaS players — side by side with founder Fabien Pinckaers. If you're a CFO in tech, growth, or scale-up mode… this episode is pure gold. 👇 Listen to the full conversation in the comments. #DeCFOPodcast #CFO #SaaS #Odoo #FinanceLeadership #ScaleUp #TechGrowth #ARR #StartupToScaleup

150

12 Comments

🔎 Deep Dive: search_fetch() in the Odoo ORM ⚡ As Odoo developers we often use .search() plus .read() or rely on fields loading on demand. When performance is critical, though, search_fetch() is a cleaner option — it reduces round-trips and loads exactly what you need. 🧠 What search_fetch() does Model.search_fetch(domain, field_names[, offset=0][, limit=None][, order=None]) • Runs a domain search • Retrieves the specified fields in a single step • Prevents additional SQL caused by lazy field access • Keeps results cached for better performance Think of it as a faster, single-query alternative to .search() followed by .read(). 💡 When it’s the right tool Reach for search_fetch() when: • ⚡ You need lower latency — e.g., API responses, dashboards, or server-side routines • 📉 You want to cut down on SQL queries • 📋 You only need a subset of fields (read-only) • 🛑 You don’t plan to alter the returned records 🧪 Example products = self.env['product.template'].search_fetch( domain=[('sale_ok', '=', True)], field_names=['name', 'list_price', 'currency_id'], limit=50, order='name ASC' ) This pulls 50 saleable products and preloads the requested fields in one efficient call. ⚠️ Quick caveats • Returns a standard recordset. • The listed fields are fully loaded into memory (no later lazy fetches). • Will raise AccessError if the user lacks read permission for the model/fields. 🛠️ Good scenarios to adopt it • REST or JSON endpoints • Reporting and analytics code • Custom dashboard backends • Any flow that’s read-heavy and sensitive to DB round-trips 💬 Have you tried search_fetch() in your Odoo apps? Drop your tips or experiences — let’s swap notes and optimize together!

159

At the age of 13, Fabien built his first software product. Now, he’s scaled Odoo into a €5.26 billion global powerhouse. You might think Odoo is an Indian brand - because it’s being used everywhere in our country now. But the founder Fabien Pinckaers is a Belgian entrepreneur - and here’s his story! 1. Coding at 13 Fabien’s tech journey started early. He taught himself coding as a teen, built a logistics management software, and sold it to a local company, Les Transports Verts. 2. Started innovating in college As he entered university to study Computer Science, Fabien’s coding skills evolved into business ideas. One such project was Auction-in-Europe, an online auction platform that outperformed eBay in Belgium’s art market. 3. The birth of TinyERP After graduation, Fabien saw SMEs struggling with expensive, complex ERP systems. In 2002, he launched TinyERP - an affordable, open-source solution to simplify their operations. 4. Rebranding to Odoo As TinyERP grew, Fabien realised businesses needed more than just an ERP, they needed a flexible solution. In 2010, he rebranded TinyERP as Odoo, adding modular apps that could scale with business needs. 5. Odoo goes global After rebranding to Odoo, the company went from a one-man operation in Belgium to a global powerhouse. It became a go-to solution for businesses worldwide looking to streamline their operations. 6. Expanding into India Fabien saw huge potential in India’s tech talent and growing SME market. In 2016, he opened Odoo’s Indian headquarters in Gandhinagar, Gujarat, capitalising on the opportunities in Tier 1&2 cities. - Today, Odoo is a €5.26 billion company, with over 7 million users in 180+ countries and 150+ partners globally. Fabien’s success came from rapid experimentation, and his ability to solve, simple universal problem statements. His journey goes to show that the world is full of opportunities - just waiting for the right solution. Be observant, take risks, and always focus on solving real problems! What part of Fabien’s journey inspires you the most? #odoo #entrepreneurship #success

40

1 Comment

💡 Implementing #Odoo on your own – or teaming up with a partner? Between “We’ll figure it out somehow” and “This is running like clockwork” lies just one key decision. If you’re introducing Odoo, your goal is to streamline processes – not create more chaos. Yet many companies underestimate what a successful ERP implementation truly requires: 👉 Data migration 👉 Choosing the right modules 👉 Mapping business processes 👉 Staff training 👉 Post go-live support Our latest blog post explores: 🔍 When self-implementation might actually make sense 💪 Why an experienced Odoo Partner often makes all the difference 💸 And how the “cheaper” route can quickly become the more expensive one Curious? Dive into the blog here: https://lnkd.in/eF6hHTF3 #OBSSolutions #Odoo #ERP #WhyOdoo #WhyOdooPartner #OdooImplementation #ERPImplementation

39

1 Comment

🚨 Why Odoo ERP NEVER crashes in a live demo… but suddenly does after Go-Live? 🤔 Suspicious, right? Because during demos, you're shown a polished sandbox — not the reality of your business operations. No real load. No complex workflows. No integrations. Just a shiny, smooth preview. 🔍 But after Go-Live — when real data, users, processes, and expectations hit the system — it breaks. And the reason isn’t Odoo itself… It’s who implemented it. 💡 A good service provider: ✅ Configures for scale ✅ Aligns workflows with your business logic ✅ Doesn’t just install, but architects the ERP 🚨 A scammer: ❌ Shows demo data ❌ Skips documentation ❌ Disappears after deployment 👉 So before blaming Odoo, look closely at who’s behind your ERP journey. ERP is not a software purchase — it's a partnership. Choose your Odoo partner wisely. Your business deserves more than a crash course. #Odoo #ERPImplementation #BusinessGrowth #DigitalTransformation #BewareOfScammers #OdooServiceProviders #ManufacturingSolutions #ConstructionERP #HealthcareERP #MediaManagement #HospitalAutomation #SmartFactory #ProjectManagement #HospitalERP #ConstructionTechnology #MediaTech #ERPForSME #MakeInIndia

320

28 Comments

In #Odoo AI, a new feature allows for the addition of properties to any record, including customers, using an AI field that auto-completes based on your input. Discover how AI enriches customer data in Odoo.

1,311

55 Comments

Revenue recognition isn’t an invoice, it’s progress. If your long-term projects close the month from billing schedules and spreadsheets, forecasts drift and reconciliation gets noisy. At this year’s Odoo Experience in Brussels, Benoît Le Goff will share his insights in the session «Revenue Recognition & Long-Term Project Tracking in Odoo». What you’ll see: 🔸 Start in CRM: each deal spins up a structured project 🔸 Log monthly progress and recognize WIP inside Odoo 🔸 Generate clean accounting entries via a lean posting engine 🔸 Keep resource planning and phase statuses in one place 📅 Friday 19 September, 11:00 📍 Hall 11.D For more details about the talk: https://lnkd.in/dhs-dPzm #OdooExperience2025 #Odoo #RevenueRecognition #ERP #Camptocamp

22