The implementation journey
How we implement Odoo
Four phases: process design, gap-fit analysis, AI development with tests and documentation, and go-live. You choose how much you outsource. Everything we promise, you can read below — without a form.
What you will find here
No brochure behind a form
We simply put our approach, our checklist and our pitfalls on this page. You do not have to leave anything behind to find out how we work. If you want to know what an app costs, see €1,000 per app. If you are looking for a heavier project with its own architecture and project governance, you can read about that on custom project. And if your current implementation is stalling, then Odoo rescue is your starting point.
The four phases
From process to production
Process design
Together with your team we record how your business works: from order to invoice, from purchase to delivery. The result is a blueprint that drives the next three phases, not a document that disappears into a folder.
- AI structures your processes and suggests industry patterns.
- You decide how your business works and where you want to go.
Progress of the project
Gap-fit analysis
We set your designed processes alongside standard Odoo and name every difference. Before anything is built, you see what works as standard, what needs configuration and where customisation genuinely adds value. That makes the quote a substantiation rather than an estimate.
- AI matches your requirements against the standard apps and reports the gaps.
- You decide which gaps are worth closing.
Progress of the project
AI development with tests and documentation
Configuration and customisation follow from the blueprint, and every component gets its tests and its documentation in the same flow. No implementation where the documentation is still to come: what has been built has been tested and described.
- AI builds, tests and documents in a repeatable and verifiable way.
- Our consultants safeguard architecture and quality.
Progress of the project
Go-live
Data migration, training and go-live, carried out in a controlled way because everything has already been tested against your own processes from phase one. Where it helps, we run in parallel with your old system for a period. After go-live we stay on board for support and further development.
- AI runs the migrations, validations and regression tests.
- We do the training, the go-live coordination and the aftercare.
Progress of the project
Per phase
What is on the table at the end of each phase
| Phase | What you get | Who decides |
|---|---|---|
| 01 Process design | A blueprint of your processes on our platform | You |
| 02 Gap-fit analysis | A gap report plus a substantiated quote | You |
| 03 AI development | Working configuration with tests and documentation | Together |
| 04 Go-live | A live environment, trained key users and a support agreement | Together |
Ungated checklist
Are you ready for an Odoo implementation?
Twelve points that determine whether a project runs smoothly. Go through them with your team. There is no form and no download — the whole list is below.
- 1. One decision-maker has been appointed. Someone who makes the call without first scheduling three meetings.
- 2. Management is involved, not just informed. An ERP project touches every department.
- 3. You know which processes are genuinely unique. And which ones you only do that way because the old system forced you to.
- 4. Your master data is in order. Products, contacts, prices and stock locations without duplicates and dead records.
- 5. Key users have had time freed up. Genuinely freed up in the diary, not squeezed in after five.
- 6. You know which systems have to stay. Webshop, WMS, PIM, bank or BI: name what stays and what goes.
- 7. Your current processes are written down somewhere. Even if it is rough — something beats knowledge that lives only in people's heads.
- 8. There is a budget, not just a wish. Including room for the things you discover along the way.
- 9. You have a reason with a date. An expiring contract or a growth spurt keeps the pace up.
- 10. Your team knows something is changing. Surprises at go-live cost more than the build itself.
- 11. You are willing to accept the standard. Every piece of customisation is a commitment you maintain for years.
- 12. What happens after go-live has been agreed. You arrange support and further development before go-live, not after.
Go through the list with your management team
The points that remain open are exactly the points we tackle first in the process design.
Support models
You choose how much you do yourself
The same four phases, three ways to go through them. You can switch along the way: many customers start guided and continue autonomously after go-live.
Guided
We take the lead on the entire project. You provide knowledge and decisions, we do the rest. Suited if your team is busy or if this is your first ERP implementation.
What you do yourself
- Taking decisions in the four phases
- Making key users available for sessions
- Supplying and approving master data
What we do
- Process design and gap-fit analysis
- Build, tests and documentation
- Migration, training and go-live coordination
Hybrid
You take on the parts you do well and we fill in where it gets specialist. In practice your team often does the configuration and data, while we safeguard the architecture, integrations and tests.
What you do yourself
- Configuring the apps you know well
- Cleaning and importing master data
- Internal training of colleagues
What we do
- Architecture and gap-fit analysis
- Integrations, customisation and tests
- Review of your configuration before go-live
Autonomous
You run the project yourself and we stand alongside as a sounding board and safety net. Suited to organisations with their own application manager or a team that already knows Odoo.
What you do yourself
- The full process design and configuration
- Migration, testing and go-live
- Administration and further development
What we do
- Input on the architecture
- Go-to contact for sticking points
- Safety net if things unexpectedly stall
Honest about the hard part
What usually goes wrong
We have seen enough projects to know where the friction is. These are the recurring patterns — and what we do about them. If your project is already stuck, read how we take over stalled implementations.
Dirty master data
Duplicate products and dead contacts only surface during the migration. We check your data as early as phase two.
No real decision-maker
If every choice has to pass four people, the pace stops. Before we start, we ask for a single point of contact with a mandate.
Rebuilding the old system
Customisation that only exists because that is how it used to be gets maintained for years. We challenge every request in the gap-fit analysis.
Key users without time
Sessions that keep getting rescheduled stretch out every project. We fix the session dates in the diary up front.
Integrations too late
The webshop, WMS or bank only turns out to be a problem late on. We map all integrations as early as phase one.
What does work
Start small, go live quickly with one app and expand from there. That is exactly why the app route exists.
Frequently asked questions
About our implementation approach
Which route suits you?
The Business Scan gives you an indicative proposal straight away. A conversation follows in which we make the route, the form of guidance and the price concrete.