Our Approach to AI Consulting & Implementation
One team, from workshop to handover.
Five steps, a realistic first 90 days, four ways to start, and straight answers. Use the tabs to jump.
Five steps, then the first 90 days
From the first workshop to more engineers when you need them. Open any step for a short explainer.

Consulting
We pin down the business problem, find where value hides and agree what success looks like before anyone writes code.
- Leadership interviews and workshops
- Process and data walk-throughs
- A written definition of success

Creation
We design and build solutions made for your business. If it is technical, we can solve it.
- Solution design with your team
- Iterative builds in short sprints
- Testing with real users

Collaboration
We sit with your people so the know-how stays with you after we leave.
- Joint working sessions
- Pairing with your engineers and analysts
- Champions in each team

Consolidation
We move from pilot to production and then to numbers that matter: revenue, cost and speed.
- Production hardening
- Rollout and training
- Tracking against targets

Codework
When you need more capacity, Codework engineers and specialists join the same team.
- On-demand engineering capacity
- Specialists for niche needs
- Continuity with the original team
The first 90 days
Four phases, one team, a decision at the end of each. Open any phase for a short explainer.

Discover
Interviews, process walk-throughs and a review of systems and data.
How it works →
Decide
A ranked list of use cases. You choose the first to prove.
How it works →
Build
Build the pilot with a real team and prepare people in parallel.
How it works →
Measure
Results against targets and a clear call: scale, adjust or stop.
How it works →Four ways to start
Each ends with a decision gate, so you commit more only when the evidence supports it.
Diagnostic
Interviews, a review of systems and data, and a scored view of where you stand.
- Best for
- Teams not sure where to begin.
- You receive
- Readiness score
- ranked use cases
- 90-day plan
- Decision gate
- You decide which use case to prove first.
Pilot
One strong use case, built and run with a real team against agreed targets.
- Best for
- Teams ready to test one idea for real.
- You receive
- Live pilot
- measured results
- go / no-go case
- Decision gate
- You decide to scale, adjust or stop.
Programme
Delivery across strategy, engineering and adoption by one blended team.
- Best for
- Teams rolling AI out across the business.
- You receive
- Production systems
- trained teams
- governance
- Decision gate
- Each phase ends with a funding decision.
Advisory
A senior adviser for your executives, board and vendor decisions.
- Best for
- Teams that need guidance, not a build.
- You receive
- Steering
- vendor reviews
- AI policy
- Decision gate
- Rolling monthly, stop any time.
Why act now
Waiting is a decision, and it compounds.
of large transformations miss their goals
Plans that ignore how people work, and training that comes too late, sink most programmes.
is when small head starts become large leads
Businesses that invest in digital, AI and adoption pull steadily ahead of those that wait and patch.
Change management decides how deep it goes
With it, performance dips briefly and ends above today. Without it, the dip is deeper and ends lower.
How ready are you?
Six questions, one minute. Tick what is true today and watch the gauge move.
Explore
Early days, which means you can set direction before buying tools piecemeal.
Suggested next step: A 2–3 week diagnostic.
Get the full report →Frequently asked questions
Straight answers to what leaders ask us most. Still unsure? Ask us directly.

We are not a tech company. Is AI relevant to us?
Usually, yes. The best early wins are ordinary: searching documents, drafting replies, tidying data, routing requests. We start from your biggest cost or delay and only then pick a tool.
How are you different from a big consultancy?
You work with senior people who also build. There is no hand-off from a pitch team to a junior team, and the same group stays through adoption.
What does it cost?
A diagnostic is a fixed fee, a pilot is scoped against a target, and larger programmes are priced per phase. We share a range on the first call.
Is our data safe?
We work inside your environment where possible, apply least-privilege access, and agree data handling in writing before anything is touched.
Who owns what you build?
You do. Code, prompts, models, documentation and dashboards are yours from day one.
How quickly can we start?
Most diagnostics start within two weeks of the first call.
Ready to start?
Talk to us for thirty minutes. You leave with a written view, whether or not you hire us.
Book a discovery call →