How an Odoo implementation runs with us
ODOO IMPLEMENTATION
A programme in phases
You know at any moment what is open, who is working on it and what still has to be decided.
BeyondERP implements Odoo for companies in Belgium and the Netherlands. The phases below are the ones we run today.
OUR APPROACH
The seven phases of an implementation
Every phase ends with something you can look at: a list, a plan, a working environment or a script.
01
Analysis and scope
We come to your site and let your people talk. Then we go through, process by process, what standard Odoo handles and where it pinches. The result is a fit-gap list: every gap with a proposal and a price, so you choose yourself what goes into phase one.
02
Project plan
Phases, dates, who takes part on your side and how much time that asks. We plan your involvement explicitly, because an implementation without people from the company in it gets stuck.
03
Configuration and development
We build in short rounds, with a test environment next to the production environment. Every two weeks you see working functionality instead of a progress percentage.
04
Master data
Items, customers, suppliers, price lists, bills of material, locations. This is the phase that makes projects fail when it starts too late, so we start early and appoint one owner per data set together.
05
Test scenarios
Your people test their own work with scenarios we write down together: an order from request to invoice, a production order from bill of material to completion. What fails goes on the defect list, with a priority.
06
Cut-over
An hour-by-hour script: when the old system closes, which balances move over, who is standing by and what we do when something does not work. We agree beforehand at which point we would go back to the old situation.
07
Running along and evaluating
After the go-live we deliberately let it run alongside daily operations for a number of weeks. Then we sit down together again: which improvements surface now, and what do we pick up next?
PROJECT CONTROL
How we run a project
All activities sit in a project management environment where we plan and follow up. The functional requirements are analysed and documented per module, and that documentation stays available to your users after delivery.
We work with workshops per module, once or twice a week with your key users, depending on their availability. Every two weeks the project leads from both sides sit together and we review scope, planning and budget. Changes go past the management team before they are carried out.
Your key users test themselves, with test scenarios we write down together, and they give the end-user training as well — with us alongside when that helps. People who explain it themselves use it better afterwards.
What an implementation with us includes
Preparation and kick-off, the final planning, the functional analysis workshops and their write-up, training for your key users, preparing your master data, setting up and configuring the modules, drawing up and following up the test scenarios, support with the data migration, follow-up of the acceptance tests, support at the go-live, a project meeting every two weeks and the project management.
What we don’t do
We don’t start an implementation without an analysis. When that analysis shows Odoo is not the right system here, we say so, even when it costs us a project.
We don’t do a big bang without a test round with your own people, and we don’t put custom work into production that nobody on your side owns.
CUSTOMER STORY
What it brought Festicup
Festicup rents out reusable cups to events and washes them in its own washing centre. In three months they moved from SAP Business One to Odoo.
The implementation has led to significant time savings, particularly from quotation to invoice, and has improved Festicup’s operational efficiency.
Festicup
Thinking about an Odoo implementation?
In a 30-minute conversation we go through your processes and say what an analysis would look like for you.