Skip to Content
Odoo Gold Partner Delivering to clients in 14 countries +94 777 626 222 info@nerosoftsolutions.com

/how-we-work

Process before configuration.

Five stages, each with a written deliverable. If a stage isn't signed off, the next one doesn't start.

  • 98% Live on the agreed date
  • 5 Median modules in phase one
  • 90 Days of hypercare

/why-it-is-ordered-this-way

Implementations fail on process, not software.

Odoo will do what you configure it to do. That is the whole difficulty. A configuration is a set of decisions about how your business runs, and if those decisions have never been written down, the implementation becomes the place where they get made — badly, at speed, by whoever is in the room.

So the gap between how you operate and what Odoo does natively is mapped in writing first. You approve that document. It becomes the scope, and the scope is what the date is built on — which is why the date holds.

/the-five-stages

Each stage ends in something you can read.

  1. 01

    Requirement analysis

    Two weeks mapping how the business actually runs, before anyone opens Odoo. Deliverable: the current-state process map.

    2 weeks

  2. 02

    Gap analysis against standard Odoo

    Every requirement marked standard, configurable or custom — with the cost of each option printed beside it. Deliverable: the signed scope.

    1–2 weeks

  3. 03

    Implementation

    Two-week sprints, demoed on your own data. Nobody signs off on a blank database. Deliverable: a configured system you have already used.

    6–12 weeks

  4. 04

    Training and go-live

    Role-based training, a rehearsed cutover, and the date we put in writing at the start. Deliverable: written SOPs your team owns.

    2 weeks

  5. 05

    Support and improvement

    Ninety days of hypercare with a named engineer, then a backlog you prioritise. Deliverable: the handover pack and the escalation path.

    90 days

/we-do

What we are responsible for

  • Mapping the process and writing the scope
  • Configuration, data migration and testing
  • Training, SOPs and the rehearsed cutover
  • Telling you when a request will cost more than it returns

/you-do

What we need from you

  • One decision-maker who can settle a disagreement between departments
  • People who do the work, in the mapping sessions — not only their managers
  • Your data, in whatever state it is actually in
  • Sign-off at each stage, or a reason it is being held

/next

Tell us what you are running today.

Thirty minutes, no slides. We will tell you straight if Odoo is not the answer.