Skip to Content
METHOD

Our Odoo deployment method: scope, build, deploy, sustain.

Five phases, named deliverables and an exit criterion at every step. This framework is what allows us to commit to a scope, a schedule and a budget before we start.

Thirteen years and 350+ projects have taught us one thing: an ERP rarely fails on technology, almost always on scoping and adoption. Our method tackles both. It applies to all our business solutions, whatever the industry, and relies on the Karizma One platform to prototype fast and deploy without surprises.

The five phases

From diagnosis to continuous support

1

Scoping & audit

Understanding of processes, the existing system and the stakes. Scope arbitration, module selection, data migration plan.

Deliverables: scoping note, functional scope, schedule, firm budget, RACI.

Exit criterion: scope, schedule and budget signed.

2

Design

Workshops per domain, prototyping on Karizma One, specification of custom developments and interfaces.

Deliverables: design file, mock-ups, business rules, test plan.

Exit criterion: design validated by key users.

3

Build & acceptance

Configuration, developments, data migration, integrations. Functional acceptance by key users, fixes, re-testing.

Deliverables: accepted environment, migrated data sets, acceptance report.

Exit criterion: acceptance signed, migrated data validated.

4

Deployment & training

Role-based training on the real configuration, cut-over preparation, Go-Live — a contractual milestone — then reinforced hypercare.

Deliverables: training materials, cut-over plan, Go-Live report.

Exit criterion: production open, autonomous users.

5

Run: support & maintenance

Corrective and evolutionary maintenance, version upgrades, new needs. Unlimited bug fixing for Karizma One clients.

Deliverables: SLA, steering committee, evolution roadmap.

Exit criterion: never ends: that is the service.

Governance

Sponsor and project manager on the client side, project director and consultants on the Karizma side. A regular steering committee that decides; roles written down from scoping.

What does not change

The scope, schedule and budget fixed at scoping. Any change goes through an explicit committee decision — never through silent drift.

What we measure

Progress per phase, acceptance rate, adoption after Go-Live, resolution time in support. The project is steered by numbers, not by feelings.

FAQ

Your questions about the method

Because it is the only way to hold a budget and a deadline. Scoping fixes the scope, schedule and budget before the first configuration; anything outside the scope goes through an explicit decision, not drift.

Scoping takes two to four weeks. Design and build make up most of the project — 6 to 25 weeks in total depending on scope. Deployment takes one to two weeks. Run starts at Go-Live and never stops.

A sponsor and a project manager on the client side, mirroring our project director and consultants. A steering committee decides on trade-offs; roles are formalised from scoping.

A hypercare period, then support and maintenance: corrective and evolutionary maintenance, version upgrades, and unlimited bug fixing for Karizma One clients.
See also:ERP glossary →