Know before you commit.

Where should we start with AI and our transformation?

The pressure to do something with AI is real. But the right starting point isn't the technology. It's the outcome. We start by agreeing what needs to change in your business, whether that's growth, margin or risk, and where it stands today.

Then we find where AI will genuinely move it, and what has to be true first. Typically two to four weeks.

Sound familiar?

• Everyone wants AI. No one agrees where to start.
• You're not sure your data and systems are ready for it.
• Processes and architecture are fragmented across the estate.
• There's no business case yet to justify the spend.

What we do

• Define the outcomes that matter most, in business terms: growth, margin or risk.
• Agree how each will be measured, and record where it stands today.
• Review the health of your data, integrations and platforms.
• Identify the AI use cases that move those outcomes, ranked by value and feasibility.
• Define the return, and how you'll track it.

What you walk away with

• Agreed priority outcomes, each with a measure and a starting point.
• A ranked list of AI use cases, each tied to an outcome.
• A clear view of what has to be fixed first.
• A roadmap to an AI-ready platform.
• A return on investment case you can hold the work to.

A blueprint before the build.

You know the outcome you want. Now you need to know how it will work, and what it will take. We design it with you before a line of code is written. Typically four to six weeks.

Sound familiar?

• The goal is clear. The solution isn't.
• Legacy processes don't map cleanly to modern platforms.
• The big design decisions need expertise you don't have in-house.
• The investment won't be approved without a blueprint.

What we do

• Kick off with your team walking us through how the work runs today, in your own systems.
• Map and validate how your processes actually run, building on what you already have.
• Run discovery workshops by theme: vision and success measures, the current landscape, each area in scope, architecture and data, and AI.
• Design the solution, prioritise the backlog, and work through the risks with you.
• Play it all back, agree the plan, and either hand over or continue into build.

What you walk away with

• Process maps showing how the work runs today, validated with the people who do it.
• A vision for the change, with agreed success measures across financial, customer and technical value.
• A high-level solution design: architecture, integrations, data and the key customer journeys.
• A prioritised, sized backlog at agreed level (normally Epics), with a clear line on what's in and what's deliberately out.
• Roles and responsibilities for both teams, through delivery.
• A phased delivery plan.
• A live log of risks, assumptions, issues and decisions.

Yours to keep. Every output is issued in open formats and owned by you, ready to use with any delivery partner.

A reset for an in-flight programme.

The programme has stalled, or the value isn't landing. We give you an independent view of what's really happening, and a plan to recover it. Typically around four weeks.

Sound familiar?

• The programme has slipped, stalled or lost the confidence of the business.
• Delivery is moving. Value isn't landing.
• Technical debt and early design decisions are slowing everything down.
• A deadline is coming, and the current plan won't meet it.

What we do

An independent review across three areas.

• Product and platform. Is what's being built aligned to the outcome you need?
• Engineering. Architecture, solution design, technical debt and delivery practice.
• Delivery. How work flows from idea to production, how it's planned, and how it's governed.

What you walk away with

• An independent view your board can trust.
• A costed recovery plan, designed with your team, that you can act on immediately.
• A plan to deal with technical debt.
• Governance built into the way forward.