Scoped engagements
These are starting points for a conversation, not products to add to a cart. We agree the question, boundaries and outputs together before any engagement begins.
Where to begin
Choose the question closest to yours. The scope shown is indicative: access, constraints and the decision at hand determine the actual brief.
A bounded discovery for organisations that know change is needed but do not yet have a shared account of the problem.
See the indicative scopeThe decision behind it
What is actually holding the estate back?
Useful when the challenge is real but the brief is still too broad to commission a detailed solution.
A focused review of a product’s technical shape and operating dependencies before a consequential investment or change.
See the indicative scopeThe decision behind it
Can this product support the next decision?
Useful before a significant technical commitment when the team needs clearer options, not another generic scorecard.
A scoped assessment of one prospective AI use case and the architecture, data and operating conditions around it.
See the indicative scopeThe decision behind it
Is there a responsible path from AI interest to use?
Useful when a specific AI opportunity has a sponsor but its viability and guardrails are not yet clear.
A decision-oriented blueprint for organisations with an understood starting point that need to sequence change across technology and operations.
See the indicative scopeThe decision behind it
What sequence of change is defensible?
Useful when enough discovery exists to move beyond a list of opportunities, but detailed delivery has not yet been commissioned.
A considered next step
Bring the decision you are trying to make, even if the brief is not yet formed. We can discuss whether a scoped engagement is appropriate, or whether a different first step would be more useful.
