What we look at
We start with how work moves through your company, not with software screens: how a quote becomes an order, how goods arrive and leave, how an invoice gets to the customer and the numbers get to the accountant. Alongside that we take the quantities that decide sizing — orders per day, articles, users, companies, currencies.
Then every requirement is checked against standard Odoo, in a fixed order: standard first, community modules second, custom code last. We tell you which tier each requirement landed in and why. Most of what arrives as "we need custom development" turns out to be a setting, a pricelist rule, or a different way of running the process.
What you get
A written target picture: which Odoo apps in which order, what your data migration involves, which integrations are needed, where custom work is genuinely justified, and a phased plan with an effort range. It is specific enough that you could take it to another partner — that is deliberate. Advice you can only use with us is not advice.
If Odoo is the wrong fit for your case, the document says so. That has happened, and it is cheaper to learn it in scoping than in month four of a project.
How a scoping runs
Four steps, in order
Process mapping
interviews with the people who do the work, and a walk through your real document flows.
Gap analysis
every requirement sorted into standard, community module or custom, with the reasoning written down.
Target picture
apps, data, integrations, sequence, effort range. Reviewed with you, not presented at you.
Decision
you proceed with us, with someone else, or not at all. The document works in all three cases.
Asked before every scoping
Do we need Odoo licences before a scoping?
No. Scoping needs access to the people who know your processes and, if one exists, a look at your current system. Licence questions — including Community versus Enterprise — are an outcome of scoping, not a precondition.
We already run Odoo. Is consulting still relevant?
That is where it is most concrete. For running systems the same method produces a migration and rollout plan: what moves to the new version as-is, which customisations get retired because the standard caught up, and in what order the jump happens.
What if the answer is that Odoo does not fit?
Then the document says so, with the reasons. We only earn on the work after scoping if there is work worth doing.
Who conducts the scoping?
The person who would lead the project afterwards. There is no handover from a consulting team to a delivery team, because there is no separate consulting team.
Get in touch
Tell us what isn't working
Send a short description of where your processes hurt. You'll get a reply from the person who would do the work, not a sales team.