We work out what to build first, then build it, in an order where each stage pays for the next.
Which stage are you at?
Process first. Software later.
Get to one source of truth.
Make the back office talk to the programme.
Move from delivering to proving.
The stages above are the diagnostic. When you know where you are, the work itself runs like this.
A read of what you run today, what breaks, and which stage you are actually at. Often this ends with us telling you to buy less than you expected.
What to build in what order, sequenced so each stage pays for the next.
Systems configured or built, then adoption support: we train the teams who have to use it.
Support, iteration, and the next stage when you reach it.
Six things that outlast the engagement.
Instead of the field’s Excel, the office’s Excel, and the auditor’s Excel.
What funders ask for, produced from the system rather than a weekend of copying.
What you spent and what changed, in one place.
Finance, HR, and procurement systems that talk to each other.
The team still using it after we leave.
So the next build starts from where this one finished.
With the stage you are actually at. The diagnostic places you on the four-stage journey first, so the sequence follows your situation rather than a template.
Not usually. Most engagements connect and extend what exists. Replacement only earns its place when the current system is the actual constraint.
The same team. The people who write the sequence are the ones who implement it, so nothing is lost in a handover to another vendor.