Skip to Content

Diagnosis before design.

Five stages. The same five on a two-week assessment and on an eighteen-month programme — the depth changes, the sequence does not.

A method is only useful if it survives being written down. Ours is published here in full, including the gate at the end of each stage and the artefact it produces.

01

Discover

We walk the operation with the people who run it. Two to ten days on site.

Gate: an agreed map of how the work is done today.

02

Diagnose

We quantify where time, margin and control are lost, and rank by payback.

Gate: a diagnosis the client's own numbers confirm.

03

Design

Target operating model first. Platform, data and integration decisions follow it.

Gate: an operating model the sponsor will sign.

04

Deploy

Phased against operational milestones. Each phase changes one measurable thing.

Gate: the operating metric moves, in production.

05

Defend

Day 91 onward: adoption, controls, and handover to the team that will own it.

Gate: your team runs it without us in the room.

We do not skip Diagnose to shorten a proposal. An engagement that starts at Design is a configuration job with a consultancy invoice attached.

Start a conversation.

Start a conversation.

Choose the one that fits where you are. None of them is a sales call. Each is an advisory conversation calibrated to a specific question.

60 minutesExecutive briefingFor a CEO, COO or CFO deciding whether the question is worth pursuing.Begin →
Two weeks, on siteTransformation assessmentFor an organisation that knows something is wrong and wants it named precisely.Begin →
One weekERP readiness assessmentFor a board or sponsor about to approve an ERP investment.Begin →