Skip to content

The challenge

ERP projects fail more often than they succeed, usually for the same reason. Everything is replaced at once. The team is trained on a system that does not match how they work, and the old way quietly continues alongside it.

By the time that is visible, the budget is spent and the organisation is running two systems.

How we approach it

A1

Phase by department

Not by whichever modules the vendor bundles together.

A2

Run in parallel

Through one full cycle, until the numbers agree.

A3

Configure first, customise last

Customisation only where it demonstrably earns its cost.

A4

Train the trainers

The people who will support the rest of the organisation.

How delivery runs

The same four phases, whatever we are building.

  1. 012–3 weeks

    Discovery

    We map your current process, users and constraints, then define scope in writing.

  2. 022–4 weeks

    Design

    Interface and data design, reviewed with the people who will use the system daily.

  3. 036 weeks+

    Build

    Delivery in two-week increments, each one testable, with progress visible throughout.

  4. 04Ongoing

    Launch & support

    Deployment, training and documentation, then optional support at a level you choose.

What you get

Rollout plan
Module sequence with a usable system at each phase.
Master data
Chart of accounts and reference data set up and verified.
Parallel run
A defined period with reconciliation at the end.
Training
Role-based, using your own data rather than samples.
Cutover
A checklist with named owners and a rollback position.
Support
An agreed period of hands-on support after each phase.

What changes

No big-bang cutover

Each phase is live before the next begins.

Verified before trusted

Parallel running proves the numbers first.

Training that holds

Staff learn on their own data, not a demo set.

Reversible

Every phase has a defined way back.

Questions

About this work specifically.

General questions about scope, ownership and timelines are answered on the resources page.

A first phase covering one department is typically three to four months including the parallel run. A full multi-department rollout runs across a year or more. Anyone quoting a full ERP in six weeks is describing an installation, not a rollout.

Both are legitimate. Licensed products can be the right answer when the process is standard and support matters more than flexibility. We will give you the comparison including the five-year cost, not just the first invoice.

Tell us what you need built.

We reply within two working days with honest scope and next steps — including when we are not the right fit.