Skip to content
Walid Redwan

Method

Seven phases, no surprises

Each phase ends with something you can review and sign off. If a phase says the project should stop or change shape, you hear it then, not three months in.

  1. Discovery & scoping

    Interviews with the people who do the work, not only management. Current processes documented as they actually run, volumes measured, pain points ranked, and the systems that must be integrated identified.

    Process document + prioritized scope

  2. Fit-gap

    Every requirement mapped to standard Odoo, a configuration change, a workflow change, or genuine custom development — with an estimate and a recommendation for each gap.

    Fit-gap matrix + budget range

  3. Configure & build

    Standard configuration first, demonstrated to you early on real data. Custom modules built in parallel, each in its own branch, reviewed against the module standards before it merges.

    Working staging environment

  4. Data migration

    Master data cleaned and imported, opening balances reconciled with your accountant, historical transactions loaded where they earn their keep. Every import is repeatable and scripted.

    Reconciled staging database

  5. UAT & training

    Your team runs their real month on staging with test scripts per role. Issues are logged, fixed and retested. Training is recorded so new joiners are not a fresh cost.

    Signed UAT + training recordings

  6. Go-live

    A cut-over plan with a named owner per step, a freeze window agreed weeks in advance, and a documented rollback. Go-live happens on a date chosen for your business calendar, not mine.

    Production system + cut-over log

  7. Hypercare

    Intensive support through the first full close cycle, when the real problems surface. Then a deliberate handover to a support retainer or to your internal team.

    Stabilized system + handover pack

What you own at the end

  • A git repository containing every custom module, with commit history
  • Module documentation: what it does, why it exists, what it depends on
  • Deployment runbook — how to update, restart and restore the system
  • Tested backup and restore procedure, with the restore actually performed once
  • Recorded role-based training for onboarding new staff
  • A written list of the deliberate compromises made, so future decisions have context

Considering Odoo, or trying to fix one?

A short call is usually enough to tell whether this is a configuration problem, a process problem or a project problem.

Book a discovery call