Know first,
estimate after
A fixed price is not a sales trick but a consequence. Whoever looks properly first can name a figure. Whoever skips that has to bill by the hour. We look first, with twenty-five years of experience in business processes and the engineering to build it ourselves.
From introduction to aftercare
Six steps. The first costs nothing, the second makes the third possible. If a project is too big for two people, we scale up through our network of Odoo Gold partners.
Introduction
We want to know what you are trying to achieve and where it goes wrong today. At the end of that hour you get an honest picture of whether Odoo fits, and whether we fit. Including when the answer is no.
Scan
We walk through your processes, look inside your current systems and work out what has to move across. This is the work that makes a fixed price possible: we only estimate once we know.
Proposal
Scope, planning and price on paper. What is in it, and just as important: what is not. If the project lends itself to it, there is a single figure underneath.
Setup in sprints
No half a year of silence followed by a surprise. Every two weeks you see running software and steer within the agreed scope.
Data and testing
A test migration on a copy, test scenarios your own people walk through, and a dress rehearsal. Only once that goes well do we go live.
Live and aftercare
We are there when you switch over and stay close in the weeks after. Then we remain reachable for questions and further development.
On that fixed price
In the Odoo landscape, billing afterwards is the norm. Understandable, because implementations run over. But it does mean the client carries the risk of an estimate they cannot make themselves.
We turn that around where we can. After the scan we know enough to name a figure that stands. If it runs over within that scope, that is our problem.
- When it works: when the scope can be drawn clearly and your processes are known.
- When it does not: for open-ended research, or when no decision has been made about the processes themselves.
- Extra work: always possible, but it gets its own price up front. Never afterwards on the invoice.
- What you get back: a scope on paper both of us can be held to.
What we need from you
An implementation rarely fails on the software. It fails on availability.
One decision maker
Someone who is allowed to cut knots without calling three meetings first.
Key users with time
A few hours a week from the people who will use it. Without them we configure on assumptions.
Honesty about the process
How it really goes, not how the handbook says it goes. That is usually where the difference sits.
Curious what your Odoo project would cost?
An hour of introduction costs nothing and always yields something: at the very least an honest picture of what is and is not possible. If the project lends itself to it, you get a proposal with a single figure underneath.