Skip to content

We sell four things.

Each answers a different question. There is no order — start where you are.

01

Explore

AI Value Scan

Can we think this through first?

A few days. One conversation with the people who do the work.

You have a question, and you want a straight answer before spending real money on it.

Maybe you don’t know where AI fits in your business at all. Maybe you know what the problem is but not what to ask. Maybe your leadership needs to understand what’s realistic before anyone commits.

Or the question is specific and technical: which model to use, what it will cost to run, whether this needs agents at all.

Days are usually enough.

Typical outputs: A short list of what’s worth a closer look · where we’d start, and why · a straight answer to the question you came with · a short note you can pass around internally

This is for you if you want an answer, not a project.

02

Diagnose

AI Workflow Diagnostic

Is it worth rebuilding?

Two weeks with your people. One piece of work. One clear answer.

Something in your business isn’t working well. It’s slow, it’s manual, it eats your best people’s time, or it waits on someone who’s always busy. You think AI might help, and you want to know honestly whether it will.

Or you’ve already tried. There’s a pilot that never went anywhere, a tool nobody uses properly, or something live that costs more than it saves. Before you spend anything more on it, you want to know what’s actually wrong.

Either way, we take the work apart — how it really runs today, where the time and money go, and what would have to be true for AI to make a difference.

Then we tell you, in writing: go, fix first, or no-go.

Typical outputs: How the work runs today, and where it breaks down · what it costs you now, and what it would cost to run properly · whether AI can help, or why it hasn’t yet · what needs fixing first · the answer, in writing

A no-go is not a failed engagement. It is the answer.

This is for you if you want a straight answer about one piece of work — whether AI can help, or why it hasn’t.

03

Design

AI Solution Blueprint

How should it run?

The design, worked out properly, before anyone builds anything.

You’ve decided to go ahead. Now someone has to work out how it actually runs: what AI does, what your people still decide, and what happens to the cases that shouldn’t go through on their own.

That last part is where most of these go wrong. The routine cases are easy. It’s the urgent ticket sitting in an automated queue, or the claim that shouldn’t be settled without a person, that does the damage.

It doesn’t have to start from a manual process. If something is already running and the design is wrong — costing too much at volume, leaning on one big model where smaller ones would do, going out unchecked — we redesign that the same way.

Typical outputs: What AI does, and what a person decides · how the unusual cases get caught, and who they reach · which approach fits, and which models — one big one, several, or smaller ones closer to the work · enough detail for whoever builds it to price it and build it

This is for you if you know what you want to do, and need it designed before it gets built.

04

Guide

AI Programme Oversight

Who keeps it on track?

Someone senior stays alongside you the whole way.

Most of what goes in gets built by your own team, a vendor or an integrator. We help you pick, then stay with you through the build, reviewing at the points that matter and telling you honestly when it’s ready to go live.

After that, someone has to watch it: what gets checked, who’s allowed to change what, what happens when it breaks, and whether the benefit you were promised actually turned up.

That holds whether we were there for the build or not. If something is already live and you’d rather not carry it alone, we can pick it up from there.

Typical outputs: Help picking who builds it, and a plain read on their claims · reviews at the points that matter, including whether it’s ready to go live · how it gets watched once it’s live, and who owns what when it breaks · a regular read on whether the value showed up

This is for you if a build is under way, or already live, and you want your own person in the room.

Bring one workflow.

Tell us where work is slow, manual, expensive, exception-heavy or stuck. We will start there.