Duration: 52:59
PART 1 — Analytical Summary
Context and why it matters 💼
In this session, Greg (head of Odoo’s MMC implementation team) and Charlotte (sales leader for MMC) explain how Odoo evolved from a challenger to a credible game-changer for medium and large organizations. They outline what changed across product, platform, go-to-market, and delivery methodology to address higher complexity, scale, and governance needs. The talk also clarifies how Odoo now wins and delivers larger projects through a dedicated MMC team spanning sales, project directors, business analysts, developers, experts, and a newly formalized security function. This matters because it signals Odoo’s ambitions beyond SMEs—without abandoning its DNA of simplicity, speed, and standardization.
Core ideas and innovations ⚙️🧠
The narrative is twofold: Odoo matured both the product and the way it sells and implements. On product, R&D addressed finance depth (including an equity app, new bank reconciliation, audit reporting, e‑invoicing compliance, OCR, consolidation, and enhanced analytic plans), broadened localizations (accounting and payroll), and streamlined logistics (planning with MPS, smarter purchasing, and faster dispatch). With AI in v19, Odoo focuses on practical assistance—generating reports and graphs, enriching data, and removing low-value tasks—rather than novelty. Additional additions include an ESG app, stronger security (e.g., auto-logoff), invoice control options, and mass edit for large data updates.
On platform, Odoo.sh evolved into a fully integrated, scalable hosting option for larger volumes and high transaction throughput. It supports direct BI connections and, crucially, now provides EU data residency: new European customers’ data and backups are hosted in Europe, with full rollout targeted by the end of Q2 next year.
The commercial journey was also overhauled. Odoo now invests more in pre-sales: understanding context, handling RFP/RFQ processes with detailed, honest responses, and running “way of working” sessions to model the future state using the customer’s own data. Demonstrations are customized (without custom development) to reflect real products, customers, and flows. Before signature, Odoo tackles strategic topics head-on—security and compliance, hosting performance and scalability, governance and RACI, and change management—then aligns on legal terms with a dedicated team.
To de-risk delivery, Odoo uses a paid Discovery Analysis as a structured bridge between pre-sales and implementation. It combines As-Is and To-Be workshops, a solution blueprint (including standard vs. development choices), phased rollout and budget, risk mapping, and change impacts. The outcome reduces uncertainty, builds internal alignment (sponsors to key users), and validates feasibility before committing to execution.
Throughout, Odoo insists on its DNA: challenge requirements, stay as standard as possible, deliver fast, and maintain transparency. The method is common across company sizes but adapted for large-scale governance: steering and project committees, stakeholder management beyond a single point of contact, formal risk management, robust training plans, and multi-wave go-lives. A shared project portal consolidates tasks, tickets, and communications; simple, actionable KPIs (budget vs. consumed, change requests, bug counts, schedule drift, Kanban bottlenecks) guide decisions. Change management is treated as essential—pragmatic tactics (videos, roadshows, “Lab’Odoo” on-site demos, early key-user involvement) help drive adoption. One case shows how turning a skeptical key user into an ambassador came down to listening and involvement.
Impact and takeaways 🚀💬
The practical effect is a higher hit rate on larger opportunities and more predictable delivery at scale. Larger customers get a single, integrated platform that’s easier to use and train, with lower TCO and fewer moving parts to maintain. The Discovery Analysis makes scope, cost, and risks tangible early, while governance and data residency enhancements address enterprise due diligence. Odoo remains candid about trade-offs: start standard, challenge complexity, then add targeted developments only when they truly add value. Collaboration between sales and services is now by design, not exception—experts join early to craft feasible offers that the delivery team can stand behind. Big projects vary (and can easily exceed 100 consulting days), but the philosophy is consistent: ship value fast, phase sensibly, and keep stakeholders aligned.
In Q&A, “large” is framed by users/complexity rather than revenue (often 250+ employees), Odoo’s largest known user base cited is around 5,000 users, clients can stop after Discovery if needed, and comparisons to SAP emphasize usability, cost, and flexibility—while acknowledging SAP’s historical depth. The team expects more large-enterprise migrations as Odoo’s breadth and governance mature and as new leadership cohorts prioritize UX, integration, and total cost.
PART 2 — Viewpoint: Odoo Perspective
Disclaimer: AI-generated creative perspective inspired by Odoo's vision.
When we started Odoo, our obsession was usability and integration—make business software people actually like to use. That doesn’t change whether the company has five users or five thousand. What’s new is our discipline around governance, risk, and scale: keep the product simple, but raise the bar on how we sell, plan, and deliver.
The Discovery Analysis is crucial here. It preserves our DNA—standard first, challenge politely—and gives large customers the confidence to move. With EU data residency, deeper localizations, and meaningful AI in v19, we’re closing the last-mile gaps without compromising on simplicity. The community and our partners remain central: together, we learn faster, build faster, and keep the product honest.
PART 3 — Viewpoint: Competitors (SAP / Microsoft / Others)
Disclaimer: AI-generated fictional commentary. Not an official corporate statement.
Odoo’s strengths in usability, speed, and TCO are undeniable. The investment in pre-sales rigor, governance, and EU data residency makes them harder to disqualify in the upper mid-market. Their “standard-first” posture, backed by an integrated platform, resonates with customers trying to escape integration sprawl and legacy complexity.
The challenges ahead are typical of the enterprise: sustaining performance at extreme scale, broad and evolving compliance (audit, segregation of duties, e‑invoicing regimes), and deep vertical capabilities. Methodology and change management maturity must keep pace across multi-country rollouts. We should expect Odoo to keep climbing—differentiation for incumbents will depend on enterprise depth, advanced compliance tooling, and global delivery consistency, while matching Odoo’s UX and cost expectations.
Disclaimer: This article contains AI-generated summaries and fictionalized commentaries for illustrative purposes. Viewpoints labeled as "Odoo Perspective" or "Competitors" are simulated and do not represent any real statements or positions. All product names and trademarks belong to their respective owners.