Free Odoo project diagnostic
Is your Odoo project drifting, or genuinely failing?
Answer nine questions and get an immediate risk score across your technical build, timeline and budget, governance, and user adoption.
- Takes two minutes
- No email required
- Your answers never leave your browser
How many times has your official go-live date been pushed back?
Scored in your browser. Nothing is sent until you choose to share it.
Reading your score
The score is a weighted diagnostic index from 0 to 100, not a probability. It answers one question: how many of the patterns we see in failed Odoo projects are present in yours.
- 0 to 30Low riskNormal project friction. A slipped date or a cautious team on its own is ordinary. Keep the cadence and re-run the grader if something changes.
- 31 to 60Medium riskWarning signs worth reviewing. The project is drifting, and a targeted review of the code and the plan is usually enough to correct course.
- 61 to 100High riskThe pattern is consistent with a failing implementation. An independent technical review is recommended before committing more budget.
Backed by real migrations
The delivery record behind every service
Migration work is our publishable proof, three engagements where the projection became operational reality on Odoo. The same senior team stands behind every service, and the full case studies are on the migration page.
- ManufacturingV12 → V17
Industrial Manufacturer, Texas
12custom modules carried over, zero data lost
- DistributionV14 → V18
Wholesale Distributor, Quebec
30%faster page loads once the upgrade shipped
- Professional ServicesCE → Enterprise
Consulting Firm, Brussels
0hproduction downtime during cutover
Implementation, migration and audit counts span our senior consultants' careers, including work delivered before Octura was founded in 2024. Go-live weeks and retention are measured on Octura engagements.
Methodology and limits
Nine weighted questions cover the four causes of ERP failure: the technical build, timeline and budget, process and governance, and people and adoption. Technical and budget signals carry more points than user friction, because a team grumbling about a new interface is normal and basic workflows breaking after handover is not. The worst case is 172 raw points, normalized to a score out of 100.
How the weights work
| Category | Questions | Max points | Weight |
|---|---|---|---|
| Technical build | 2 | 50 | 29% |
| Timeline & budget | 2 | 45 | 26% |
| Process & governance | 3 | 42 | 24% |
| People & adoption | 2 | 35 | 20% |
| Max points | 9 | 172 | 99% |
Percentages are rounded, so the four weights sum to 99.
The overall score is the sum of all nine answers divided by 172. Each category score is that category's points out of its own maximum, so the overall score is the weighted average of the four category scores.
What the score does not do
It reads nine answers, not your database, your configuration or your source code. It cannot identify a specific code defect, and it cannot estimate what stabilising the project will cost. Both take reading the code and the data.
A low score is a real answer. If your answers show no red flags, do not buy an audit: the friction you are feeling is normal for an ERP rollout.
How this calculation is made
The Octura Project Rescue Risk Score is calculated by scoring nine weighted questions across four causes of ERP failure, the technical build at 29 percent of the scale, timeline and budget at 26, process and governance at 24, and people and adoption at 20 (rounded), for a worst case of 172 raw points normalized to a score out of 100. A score of 0 to 30 is normal project friction, 31 to 60 shows warning signs worth reviewing, and 61 to 100 is consistent with a failing implementation; it is an indicator, not an audit.
Frequently Asked Questions
Is the diagnostic free?
Yes, completely free and no email. Your score and diagnosis appear immediately on screen. The scoring runs in your browser, and your answers are never sent to a server.
Will my current partner find out?
No. Your nine answers stay in your browser and are never stored by Octura. Like every page on this site, anonymous usage statistics may be recorded, such as how many questions were completed and which risk band came out, but they never contain your answers. You can diagnose your project privately before you raise it with anyone.
How is the score calculated?
Nine weighted questions, 172 points at worst, normalized to a score out of 100. Technical and budget red flags (slipped dates, hourly billing over estimate, bugs in basic workflows, no rollback plan) outweigh mild user friction. The per-category breakdown is shown alongside the result, and the weights table sits in the methodology section.
What do the three bands mean?
0 to 30 out of 100 is normal project friction, and no rescue is indicated. 31 to 60 means the project shows warning signs worth reviewing, and a targeted review is recommended to correct course. 61 to 100 means the pattern is consistent with a failing implementation, and an independent technical review is recommended before committing more budget.
My Odoo project is behind schedule and over budget. Is that enough to call it failing?
Not on its own. A slipped date is common and an overrun on hourly billing is recoverable; together they are two of the nine signals this grader weighs, and they carry 45 of the 172 points between them. What turns being behind schedule and over budget into a failing project is what sits underneath: custom code breaking standard workflows, no rollback plan for the data migration, and no way to see the state of the work. Score all nine and you will know which of those you have.
What if my score is high?
Get an outside read before committing more hourly budget. Our Triage package (From $4,500) is a 5-day audit: we read your code and git history, measure the state of the database, and deliver a risk map with three priced options. If the project can be saved you leave with a fixed-price roadmap. If it cannot, we tell you exactly why.
Does this replace an audit?
No. Nine answers are not a substitute for reading your code, your data and your configuration. This tool tells you whether the failure pattern is present; an audit tells you exactly what is broken and what fixing it costs.
Do you take over projects from other partners?
Yes, it is most of what our rescue practice does. We do not need your current partner's cooperation to audit what has been delivered, provided you own the code repository, which is the most common case.
Project rescue
Taking over an Odoo project that has drifted
Audit first, then stabilize, then deliver the remaining scope. We read the git history, the custom modules and the database state before writing a line of code, and you keep the report whether or not you hire us.
See Odoo project rescue