HOW WE WORK

One method, run the same way whether it is a launch, a migration, or a rescue.

Six stages, a clear owner at each one, and AI used to accelerate the parts that used to take weeks, not to replace the judgment calls that still need a person.

The six stages, at a glance

The same six stages whether this is a new implementation, a migration, or a rescue.

01

Diagnose

Full inventory of process, data, and integrations before anything is designed.

AI: process mining
02

Design

A solution mapped to your actual workflows, not a generic template.

AI: gap mapping
03

Data

Master data and history migrated, cleaned rather than just copied.

AI: cleansing & matching
04

Build

Configuration and any required customisation, reviewed against the original design.

05

Prove

Testing against real scenarios, not a generic checklist.

06

Land

Go-live timed around your calendar, with support through the first close.

AI: in-app help agent
Each stage, in more detail

What actually happens at each of the six stages.

01 · Diagnose

A full inventory of how the business actually runs today, not how the org chart says it runs.

  • We talk to the people doing the work, not just their managers
  • AI-assisted process mining maps system logs and transaction patterns
  • Judgment on what is load-bearing still comes from a person

02 · Design

Every place your process and the system's own default behaviour genuinely differ, written down explicitly.

  • Differences get flagged before testing, not during it
  • Some differences should change your process, not the system
  • This is the single biggest lever against scope creep

03 · Data

Master data and history migrated, not just exported and reimported.

  • Duplicate and inconsistent records get cleaned first
  • Dead vendors and old units of measure do not make the trip
  • The new system starts with data worth trusting

04 · Build

Configuration against the signed-off design, with every addition checked against it.

  • "Just one more field" gets tracked against the original scope
  • Nothing gets built that was not actually agreed to
  • This is where most uncontrolled projects quietly drift

05 · Prove

Testing against real transaction scenarios pulled from your business.

  • Not a generic script that ships with the methodology
  • If your busiest month is unusual, we test against it
  • Defects get caught here, not after go-live

06 · Land

Go-live timed around your calendar, with support through the first close.

  • Legacy system kept read-only for a period, not switched off
  • Support continues through the first full close cycle
  • That is when the questions that matter most tend to surface
GO DEEPER ON HOW WE WORK

The mechanics behind the method, spelled out one topic at a time.

Each of these covers one specific part of how an engagement actually runs, in detail, rather than a single paragraph on this page trying to cover all of it.

Where AI actually compresses the timeline

Stage by stage, what genuinely speeds up and what still needs a person.

Governance & who decides what

Decision rights, steering cadence, and how conflicting input actually gets resolved.

Change control in practice

How a scope change gets raised, costed, and approved mid-project, without silent creep.

What we need before Diagnose starts

A practical readiness checklist, so you can tell how prepared you actually are.

Communication & reporting cadence

The real weekly rhythm: status updates, steering meetings, and how issues escalate.

What happens after Land

Hypercare specifics, first-close support, and the formal handover to managed support.

Who's actually on the team

The roles behind an engagement, and how much of each is dedicated versus shared.

Standard first, custom only when it earns it

Why most clients end up with a fraction of the customisation they expected.

Common questions

What people usually ask about how we run a project.

Q.Do all six stages happen for every engagement?

Yes, though the depth varies. A rescue engagement spends more time in Diagnose reconciling what already exists.

Q.Where does AI actually get used, and where doesn't it?

AI accelerates pattern-matching work: scanning customisations, mapping data gaps, cleansing records, answering routine questions after go-live. Judgment calls stay with a person.

Q.What if we already have most of the Diagnose work done?

We review what exists rather than redo it, though we will tell you honestly if something looks incomplete.

Q.How do you handle scope changes mid-project?

Every change is logged and priced against the original design before it is approved.

Considering an engagement

Get a straight read before you commit.

Tell us what you are trying to get done. We will walk you through how this method would apply to your situation.

Book a 30-minute call

With someone who has run this before.

Run the situation diagnostic

Four minutes, no email required.