Method
Assess. Decide. Pilot. Transfer.
The same four movements on every engagement, at whatever size the problem justifies. What changes between a two-week review and a twelve-week pilot is depth, not method.
- 01
Assess
2 to 6 weeks
We inventory what exists rather than what the documentation claims. Every finding names the artifact it came from, so it can be re-checked instead of argued about.
An evidenced baseline you could hand to an auditor.
- 02
Decide
1 to 2 weeks
Findings become a sequenced roadmap. Where we recommend one option over another, the trade-off and the reversal cost are written down next to it.
A roadmap with owners, sequence, and the decisions made explicit.
- 03
Pilot
6 to 12 weeks
We take the first path end to end. A plan that has never been executed once is an estimate, and estimates are where migration programmes lose their credibility.
One path working in production, with a runbook you can repeat.
- 04
Transfer
Throughout
Transfer is not a closing meeting. Your engineers work alongside ours from week one, and the handover checks that they can re-run the work rather than that they attended a walkthrough.
Runbooks, training, and a named internal owner.
A week during an assessment
What it feels like from your side
If the plan will not survive your constraints, you hear it in week one. We would rather lose the follow-on work than deliver a roadmap nobody can execute.
- Monday
- A 30-minute stand-up with your sponsor. Blockers named, no status deck.
- Tue to Thu
- Working sessions with the teams who own the systems, plus evidence collection.
- Friday
- A written update: what we found, what changed in our view, and what we need from you next week.
What we ask of you
- A sponsor who can unblock access, available for 30 minutes a week
- Read access to the systems in scope, granted in week one rather than week three
- One named engineer per system area, part time
- Permission to write down what we actually find
How engagements end
- A handover session where your team re-runs the work, not one where they watch us
- Every artifact delivered in an editable format you own
- A named internal owner recorded against each deliverable
- An honest list of what we did not get to, and what it would take
Commercial model
Priced so you can judge us on the first engagement
We take no reseller commission from any vendor we recommend, and that clause is in the engagement letter rather than only on this page. Indicative pricing is shared during the briefing once the scope is roughly known.
| Engagement type | Basis | Exit |
|---|---|---|
| First engagement | Fixed scope, fixed price | Complete at delivery, no commitment beyond it |
| Assessment | Fixed scope, fixed price | Complete at delivery |
| Advisory retainer | Monthly | 30 days notice, either side |
| Delivery work | Milestone based, with acceptance criteria agreed up front | At any completed milestone |
Data handling
What happens to your data while we hold it
Security buyers read this before they read the service pages. It is stated here rather than held back until the contract stage.
- We work in your environment wherever the work allows it, so the data never leaves your control.
- Where we must hold data, it is the minimum needed for the finding, held for the engagement only.
- Client data is not used to train any model, and is not sent to a third-party model without your written agreement.
- Access is limited to the named engagement team. There is no shared consultancy-wide access.
- At the end of the engagement we return or destroy what we hold, and confirm which in writing.
- Any subprocessor we use for an engagement is named before the engagement begins.
Next step