Engagement shape · typical timeline
Stages
Typical span
Approval gates
After launch
STAGE
WK 0
WK 4
WK 8
WK 12
WK 16
WK 18+
01
Discover
1-2 wks
02
Assess
1-2 wks
03
Design
1-3 wks
04
Configure & Build
3-8 wks
05
Test & Launch
1-2 wks
06
Improve
→
The journey
Every engagement follows a defined delivery route, adapted to the scale and complexity of the work. You know what stage you are in, what decisions are required and what is delivered before we move forward.
01
Discover
Understand the business, objectives and current operating model.
02
Assess
Review processes, platforms, data, integrations and constraints.
03
Design
Define the target process, solution architecture and delivery plan.
04
Configure & Build
Configure, integrate, automate and develop what has been agreed.
05
Test & Launch
Validate with users, migrate where required, train and move into production.
06
Improve
Measure adoption and outcomes, then optimise as requirements evolve.
Why it’s built this way
01
Nothing significant is configured, migrated or changed without an agreed reason, defined scope and appropriate approval.
02
You know what stage you are in, what decisions are required and what will be delivered next.
03
Technology decisions trace back to an operational, commercial or governance requirement identified during discovery and assessment.
Where are you now?
Start where you are.
Choose the closest stage. We will confirm what is already complete and continue from there.
Stage by stage
Select a stage to see what we need from you, what our team does and what you have in hand before it closes.
01
Discover
1-2 WEEKS
02
Assess
1-2 WEEKS
03
Design
1-3 WEEKS
04
Configure & Build
3-8 WEEKS
05
Test & Launch
1-2 WEEKS
06
Improve
ONGOING
Stage 1 · 1-2 weeks
We interview the people who use the systems, understand how work actually moves, identify pain points and establish the business outcomes the programme needs to achieve.
You provide
Relevant stakeholders, process context, existing documentation and access to the information required for discovery.
We do
Map workflows, identify constraints, review the current technology landscape and document the operational requirements.
You get
An agreed view of the current state, priority problems and the basis for the next-stage decision.
STAGE 1 OF 6
Next: Assess →
The working relationship
What we ask of you
Stakeholder time in Discover, and admin access where agreed
A decision-maker who can approve scope and sequence
Nominated testers, and feedback on each build iteration
Ownership of the system once it’s live
What you can expect from us
Findings before recommendations, and costs before commitments
Platform-neutral advice. We work with the stack you already run
Documented designs, managed change control, and progress reporting
Support that carries on well past go-live