Methodology

Odoo implementations fail in predictable ways. The scope balloons, the data isn't ready, key users get cornered into a tool nobody asked them about, and somewhere around week eight the project loses its champion. We built our methodology to head off each of these.

We work in four phases. Each has explicit entry criteria, deliverables, and a written sign-off before the next phase starts. If you want to stop at the end of any phase, you can — you'll have something useful in hand either way.

Phase 1 — Discovery

One to four weeks, depending on size. We run process-mapping workshops with the people who'll actually use the system. We document the as-is, the to-be, and the gap. We hand you a written scope and a fixed quote before any code or configuration starts.

Phase 2 — Design & Build

The bulk of the project. Configuration in a sandbox, data migration with reconciliation reports, any custom modules built and tested. We demo working software weekly — not Powerpoint — so problems surface early.

Phase 3 — Train & Go Live

Role-based training delivered in your office or remote. User acceptance testing with sign-off. A written cutover plan with a rollback option. We're on-site or on-call through go-live week.

Phase 4 — Stabilize & Support

Three months of post-launch hypercare bundled into the project price. Daily check-ins for the first two weeks, weekly thereafter. At the end of hypercare you transition to ongoing support, or take it in-house.

Typical timeline

Small deployments (five to ten users, standard processes): eight to twelve weeks. Mid-size (ten to thirty users, some customization or integrations): three to six months. Large or regulated (fifty-plus users, GMP, government, multi-entity): six to twelve months. We'll give you a realistic estimate in discovery, not before.

How we price

We quote fixed-fee for discovery and for each delivery phase, with time-and-materials for change requests. Hypercare is bundled. Hosting, licenses and third-party services are passed through at cost. No retainers required to start.

What we won't do

We don't quote ERP projects sight unseen. We won't agree to "agile, we'll figure it out as we go" with no scope. And we won't take on a project where the team doesn't have a real internal champion — those projects don't succeed, and we'd rather say no.

What you take away

  • Process maps and a written scope of work
  • A configured, tested Odoo environment
  • Migrated data with reconciliation reports
  • Role-based training materials and recordings
  • A cutover plan with rollback procedures
  • Three months of hypercare support
  • Source code (for any custom modules) with documentation

Common questions

Do we have to host on Odoo.sh? No. We support Odoo.sh, your own cloud (AWS / GCP / Azure), or on-premise. We'll help you choose based on size, compliance posture, and team capability.

Can you work with our existing IT or in-house developers? Yes — we frequently work alongside in-house teams, with clear handover and code-review practices.

What if we already started an implementation that's stalled? We do project recoveries. Get in touch with the current scope, the issues you're facing, and any prior vendor's deliverables. We'll tell you honestly whether we can help.

Next step

Tell us about your project.

A 30-minute scoping call to find out whether we're the right fit. No commitment, no sales pressure.

Book a consultation