We, the Self-ERP team, often hear business owners and managers say something like this: “Why waste time and money on Discovery? We already know we want ERP!”
In small companies, this logic sometimes works, because the standard functionality of Odoo Enterprise “out of the box” really covers key processes, including sales, warehousing, and accounting. But when it comes to medium or large businesses, holding structures, manufacturing, or utilities, the “set up and run” approach no longer works. Here, it is important to consider the specifics of processes, interrelationships between departments, regulatory reporting, and integrations.
In this case, the Discovery phase becomes not just useful, but critical to ensuring that ERP implementation is successful the first time around. In this article, we explain in detail what Discovery is and what tasks it covers, what is included in the final documentation, what benefits it brings to the business, and how much it costs.
What is Discovery in the world of Odoo?
Discovery is a pre-project study of a company that lasts from 80 to 100 hours. Upon completion, the business receives answers to the following key questions:
- Which business processes need to be automated?
- Which of them are covered by Odoo's standard functionality?
- Where are the gaps and where are customizations or integrations needed?
- What should the architecture of the future system be?
- What budget and timeline are realistic for such a project?
In the official Odoo methodology, GAP analysis for small projects is usually integrated into the Kick-off (start-up meeting or official launch). But for medium and large companies, this is a separate phase that can last from a few days to a month, depending on the complexity.
This approach is consistent with the practices of other ERP vendors. For example, in NetSuite, the first stage of the life cycle is called Discovery & Planning and includes requirements gathering, scope estimation, and risk analysis.
US market experience and research findings
- According to a study by TechSci Research, the ERP market in the US is estimated at $14.62 billion in 2023 and is expected to grow to approximately $18.14 billion by 2029, with an average annual growth rate of about 3.5%.
- The main challenges cited by companies are high initial costs, the complexity of adaptations and data migration, and integration with existing systems. TechSci Research notes that SMEs (small and medium-sized enterprises) are particularly hesitant due to budget and technological complexity.
- There is a noticeable trend toward using cloud-based ERP solutions — they require less proprietary infrastructure but often need customization and flexible integrations. Companies are looking for solutions that can be adapted to their unique business processes.
- According to a 2023 report by Panorama Consulting Group, many ERP implementations in the US cost more than initial estimates and sometimes exceed the planned timeline. The reason is precisely an underestimation of complexity and insufficient analysis of processes at the outset. (Although direct studies labeled “Discovery” are less common, generalized conclusions confirm that preparation is critical.)
- Research shows that projects that start with a clear plan, architectural blueprint, and understanding of integrations and risks are significantly more likely to succeed. In the US, companies that invest in pre-project analysis (similar to Discovery) have better ROI and fewer cost overruns.
In international projects, the Discovery stage has long been the standard. For example, MetaOption notes that the typical scope of 80–100 hours pays for itself many times over, as it avoids months of rework and thousands of dollars in losses.
What do BIM models and Discovery have in common?
If we compare them, according to modern construction standards, no one starts work without a BIM (Building Information Modeling) model anymore. It is a digital twin of the future building, which clearly shows: where the walls, communications, and technical areas will be; how the load is distributed; how much it will cost; and what risks may arise before work begins.
Discovery for Odoo is your BIM, but in the ERP world. In other words, it is a detailed design of the system before implementation, which includes:
- creating a digital model of your business processes;
- determining which modules work “out of the box” and which need refinement or integration;
- calculating the scope of work, budget, and deadlines.
Instead of starting “construction without blueprints,” you get a clear and realistic plan that is technically sound and agreed upon by all parties. This reduces risks, avoids chaos, and saves on rework.
Discovery documentation: what's included in the package
It is important for business owners to understand what they are paying for. Discovery documentation is a detailed diagram of the future ERP system that allows you to plan implementation without surprises.
What is included in the documentation package:
- A business process map (BPMN/flowcharts) that shows how processes work.
- GAP analysis determines what Odoo covers as standard and where additional customization is needed.
- System architecture diagram — modules, integrations, and data flows.
- List of integrations and assessment of their complexity.
- Risk analysis, including time, financial, and technical risks.
- Roadmap, which outlines all stages of implementation and the estimated budget.
- Implementation options — minimum viable product (MVP) versus full rollout.
- Assessment of work, including the amount of time and resources required for implementation.
Each of these elements helps the owner make informed decisions and see the full picture of the future ERP system.
Customer participation in the Discovery process
Discovery involves not only the integrator's work, but also the active participation of the customer, as the business team is well versed in internal processes and knows the details.
Usually, 3–5 key managers from different areas are involved on the customer's side. Each of them spends 6–10 hours on interviews, workshops, and reviewing materials.
Approximately 40–60 hours of the customer's team's time will be required.
If the customer does not participate, Discovery may be superficial, fail to take into account the real needs of the business, and lead to additional problems during implementation.
Practical examples from customer experience
Real-life examples show the risks of ignoring Discovery and the opportunities that its proper implementation opens up. Below are two anonymous cases that illustrate the difference.
Success thanks to Discovery
A municipal enterprise decided to undergo Discovery before implementing Odoo. As a result, they received: a map of business processes, a detailed plan of stages, and a clear budget calculation.
As a bonus, they received documentation that they used as the basis for an international grant application. Discovery became not only a technical but also a financial tool for the company's development.
Mistakes without Discovery
A retail company decided to “save money” and immediately start implementing Odoo. During the work, they had to study in detail the architecture and business processes that were not described at the start. This led to additional costs and delays. In essence, Discovery still had to be done, but during the implementation process and at a higher cost.
Key benefits of Discovery for owners or top managers
What are the benefits for your business if you go through Discovery? Here are three key points to consider.
- Risk reduction. You can see all the “pitfalls” before you start implementation and avoid them.
- A clear vision of the result thanks to a detailed plan with step-by-step stages and responsible parties. This way, you know exactly where you are investing your time and resources.
- Budget and deadline control. Investing in 80-100 hours of Discovery saves hundreds of hours of work and thousands of dollars in the future, making implementation predictable and effective.
These benefits allow the owner or manager to maintain control over the ERP implementation and minimize unforeseen costs and risks. Next, it is worth considering how much Discovery costs and how to plan its budget.
How much does Discovery cost?
Duration and cost for medium-sized companies:
- Time — 60–100 hours
- Approximate cost of Discovery — €3,000–€5,000
For large holding companies or manufacturing companies:
- Time — 150–250 hours, with several teams working in parallel
- Approximate cost — €7,500–€12,500
By investing these hours at the start, the company receives a clear implementation plan and a predictable budget. It also minimizes risks, which in the long run saves hundreds of hours of work and significant funds.
For comparison: overspending on implementation without Discovery usually eats up 20–40% of the budget. For an average ERP project, overspending amounts to €15–30 thousand.
Checklist — do you need Discovery?
Discovery is recommended if your business:
- is medium or large;
- is a holding company or consists of several legal entities;
- has non-standard processes or its own IT solutions;
- plans to integrate with CRM, accounting, logistics, or manufacturing;
- involves the migration of large amounts of data;
- seeks to attract grants or investors — Discovery documents are ideal for applications.
For small businesses with standard processes, a short GAP analysis during Kick-off is usually sufficient, without a full Discovery phase.
Cost or benefit? Discovery results
In summary, Discovery for Odoo Enterprise is a BIM model of ERP implementation that transforms chaos into predictability, provides a clear plan, budget and deadline control, and minimizes risks.
Our experience and customer practice confirm that investing in Discovery always pays off, helping to avoid unforeseen costs and ensuring “first-time” implementation of the system.
Here's a question for you: when was the last time you invested in a clear plan rather than fighting chaos?
Valentyn Mekhno, SelfERP Project Manager (ERP)
Not sure if Discovery is right for your business? Leave a request or your contact details and we will work with you to assess the scope, risks, and complexity of implementation.