Tool
Estimate Your Odoo Implementation Scope and Cost
Answer ten questions and get an indicative scope class, a delivery effort range and the three things driving it. No email required, no form in the way, and the whole model is published below so you can check our arithmetic.
Model reviewed by Bhavesh Selarka on . This is an estimate for planning, not a quote.
The calculator
Reading the result
The Four Scope Classes
The class matters more than the number. It tells you what kind of project this is, which decides how it should be planned and who needs to be involved.
Focused
One or two workflow families, a single entity and little custom work. Usually a single phase with a short discovery in front of it.
Multi-function
Several connected families across one or two entities. Phased go-live, real data migration and a handful of integrations.
Complex
Deep operational workflows, multiple entities or significant custom engineering. Design decisions matter more than configuration speed.
Transformation
A multi-entity or multi-country programme with custom development, integrations and change management. Planned as a roadmap, not a project.
Honesty about precision
Why the Range Is Wide
Anyone giving you a single number before discovery is guessing, and they're doing it with more confidence than the information allows.
- Nobody has seen your data yet. Master-data quality moves migration effort by a factor of three or more.
- A workflow family is a container, not a specification. "Manufacturing" is two weeks or two months depending on what you actually make.
- Integrations vary enormously. A maintained connector is days; an undocumented legacy API is weeks.
- Custom requirements are discovered, not declared. Some appear only when people see the system with their own data in it.
- Your team’s availability changes the elapsed time even when the effort is identical.
How the model works
- Each workflow family carries a baseline effort in person-days, taken from our own delivery history on the projects published on this site.
- The baselines are added, then multiplied by an entity factor (more legal entities means more configuration and reporting) and a fit factor (how far your process is from standard Odoo).
- Data migration, integrations, edition, hosting, rollout and training effort are added on top as flat amounts, because they do not scale with the number of workflow families.
- A timing factor is applied last, because a hard deadline costs effort in parallel working and risk management.
- The result is expressed as a range. The range starts at plus or minus 25 per cent and widens for each answer you marked as undecided.
- Elapsed weeks assume a small dedicated team working alongside your people, not the effort divided by a fixed team size.
Scope boundary
What the Number Includes, and What It Does Not
The most misleading thing about implementation estimates is usually what has been quietly left out of them.
Included in the effort range
- Discovery workshops and the written design decisions that come out of them
- Configuration of the workflow families you selected
- Data migration: mapping, loading, reconciliation and sign-off
- Integration build and testing for the systems you counted
- Custom module development where the fit answer implies it
- User acceptance testing, training and go-live support
- Project management across the phases
Not included
- Odoo licence subscriptions, which are set by Odoo S.A. and vary by country and user count
- Hosting and infrastructure costs, whether Odoo.sh or your own cloud account
- Third-party app or connector licences from the Odoo Apps marketplace
- Hardware: tills, scanners, label printers, fiscal devices
- Your own team’s time, which is usually the second largest cost in an ERP project
- Post go-live support and enhancements, which we quote as a separate retainer
- Statutory, tax and audit advice, which stays with your accountant
The published model
Every Weight This Calculator Uses
These are the exact figures behind the result, taken from our own delivery history and reviewed on 23 September 2026. The base range is plus or minus 25 per cent, widened by each undecided answer.
Legal entities and countries in scope
| Answer | Effect on the estimate |
|---|---|
| One entity, one country | × 1 on the workflow subtotal |
| Two or three entities | × 1.35 on the workflow subtotal |
| Four or more, or multiple countries | × 1.8 on the workflow subtotal |
Internal users who will work in the system
| Answer | Effect on the estimate |
|---|---|
| Up to 10 | 2 person-days |
| 11 to 30 | 5 person-days |
| 31 to 100 | 12 person-days |
| More than 100 | 25 person-days |
Which parts of the business go into Odoo
| Answer | Effect on the estimate |
|---|---|
| Sales and CRM | 12 person-days · Pipeline, quotations, pricelists, order hand-off |
| Finance and accounting | 18 person-days · Invoicing, bills, payments, reconciliation, reporting |
| Inventory and purchasing | 16 person-days · Warehouses, receipts, replenishment, deliveries |
| Manufacturing and quality | 25 person-days · BOMs, routings, work orders, traceability |
| Point of sale or retail | 14 person-days · Tills, cashier workflow, hardware, fiscal rules |
| eCommerce or customer portal | 15 person-days · Catalog, checkout, portal, fulfilment link |
| Projects, services or field work | 14 person-days · Projects, timesheets, planning, helpdesk |
| HR and payroll | 16 person-days · Employees, leave, attendance, appraisals, payroll boundary |
Data to migrate
| Answer | Effect on the estimate |
|---|---|
| One clean source, or a fresh start | 4 person-days |
| Two or three sources, reasonably clean | 12 person-days |
| Several sources, or known data-quality problems | 28 person-days |
Systems to integrate
| Answer | Effect on the estimate |
|---|---|
| None for now | 0 person-days |
| One or two, common platforms | 8 person-days |
| Three to five | 22 person-days |
| Six or more, or bespoke APIs | 45 person-days |
How close is your process to standard Odoo?
| Answer | Effect on the estimate |
|---|---|
| We can adopt standard ways of working | × 1 on the workflow subtotal |
| Mostly standard, configured to fit | × 1.25 on the workflow subtotal |
| Several processes need custom modules | × 1.7 on the workflow subtotal |
| Our core process has no standard equivalent | × 2.3 on the workflow subtotal, widens the range by 10% |
Edition
| Answer | Effect on the estimate |
|---|---|
| Odoo Community | 4 person-days · Extra effort where OCA or custom fills an Enterprise gap |
| Odoo Enterprise | 0 person-days |
| Not decided yet | 2 person-days, widens the range by 8% |
Hosting
| Answer | Effect on the estimate |
|---|---|
| Odoo Online | 0 person-days · No custom code possible on this plan |
| Odoo.sh | 3 person-days |
| Self-hosted cloud or on-premise | 8 person-days |
| Not decided yet | 3 person-days, widens the range by 5% |
Rollout pattern
| Answer | Effect on the estimate |
|---|---|
| One site, single go-live | 4 person-days |
| One site, phased by workflow | 8 person-days |
| Several sites or entities in sequence | 18 person-days |
Timing
| Answer | Effect on the estimate |
|---|---|
| No fixed external deadline | × 1 on the workflow subtotal |
| A target date we would like to hit | × 1.05 on the workflow subtotal |
| A hard deadline (fiscal year, contract, system shutdown) | × 1.15 on the workflow subtotal, widens the range by 5% |
Spotted a weight that does not match your experience? Tell us. The model changes when our delivery data says it should, and the reviewed date above moves with it.
Next step
Turn the Estimate Into a Scope
Send us the result and the workflows behind it. You get a written scope with the phases, the assumptions we would test first, and the decisions that would move the number, from an engineer rather than a salesperson.