Three packages, one timeline
The agreed scope determines the schedule, within the framework of the chosen package.
| Package | Scope | Time to go-live | Post-go-live support | Price |
|---|---|---|---|---|
| Quick Start | 1–3 modules, standard process | 4–6 weeks | 30 days | from €8,900 |
| Implementation | 4–8 modules, up to 40 hours of development, one interface | 8–16 weeks | 60 days | from €22,000 |
| Transformation | Company groups, several legal entities, complex migration | 3–9 months | 90 days | on quote |
Projects generally begin two to three weeks after contract signing. At Rauschenberger, three months separated the March 2026 project start and the June 2026 launch. Seven entities then began using CRM, sales and invoicing in Odoo, with accounting following in a second phase.
The five phases, using a 16-week implementation as the example
1. Analysis and specification (weeks 1–2)
We review current processes with management and the relevant departments, drawing on your requirements document if one is available. We then assess the requirements against Odoo and record the modules, customisations and acceptance criteria in the specification.
2. Configuration and development (weeks 3–9)
We configure master data, posting rules, warehouse routes and sales processes in a test environment. Development follows the customisations agreed in the specification; the Implementation package includes up to 40 hours for this work.
3. Data migration and testing (weeks 10–14)
We map the exported legacy data to the appropriate Odoo fields. A test migration lets us reconcile balances and open items. Your team then tests its working processes and signs them off.
4. Training, organisational rollout and go-live (by week 16)
Training and organisational rollout follow a separate plan with specific deliverables:
- Key-user concept: You name key users per department. They test, sign off and later train new colleagues.
- Roles and access rights: We define per role who may see and post what, and sign it off with you.
- Training plan: One session per role with content and duration, on your own data, on site or by video.
- User documentation: Guides per process, stored in the system. At Prantl this was complemented by 11 video lessons for the team.
We agree the cutover date together, often at month- or quarter-end, and support your team through the switch.
5. Post-go-live support (60 days)
During the post-launch period, we respond promptly to questions and review progress each week. Ongoing support then continues under a plan starting at €490 per month.
Project governance
Before work starts, we agree decision-making responsibilities, acceptance procedures and change handling in writing.
- Steering committee: Your management or project sponsor, our project lead and our management. The committee decides on scope, dates and budget and meets at the milestones. In transformation projects it is a fixed part of the setup.
- Fixed project lead: You have a fixed project lead with a named deputy and an escalation path straight to management.
- Milestone sign-offs: You sign off the specification, the configured test instance, the test migration and the go-live release in writing. The yardstick is the acceptance criteria in the specification.
- Status report and risk log: Every week you receive a status report with progress, open items and pending decisions. The risk log names the impact, the measure and the owner of each risk.
- Change request procedure: We describe any change to the agreed scope in writing, with effort and impact on date and price. It is implemented only after your approval. On a fixed price the agreed scope stays binding; extra effort within the specification is at our expense.
- Customisation documentation: Every customisation is documented: requirement, technical description, affected modules and a user guide. You receive the documentation with the sign-off. It is the basis for every version upgrade.
This gives management a common basis for decisions on scope, schedules and budget. Finance can trace each price change to its approval. IT receives the documentation needed to review customisations during an upgrade.
What you contribute
Your key users need time allocated for workshops, testing and acceptance. Keeping to the agreed schedule also depends on receiving data and decisions from your business on time.
The next step
For Quick Start and Implementation, we prepare a binding fixed-price quote within five business days of the free initial call. Transformation projects require a preliminary assessment first, which we also recommend for implementations from €30,000. All packages and prices are on the pricing page.