- What happens
- You take the ninety-second check and see your score across people, process, data and systems. Then thirty minutes with us. You name the process that eats the week; we put a yearly cost on it and show the working: volume, minutes per item, the loaded cost of the person doing it, the delay it causes downstream.
- What you leave with
- A written sequence for your constraint, the items we would tell you not to do yet and why, and what fixing it in-house would take against what it takes with us. All in writing, yours to keep whether or not we speak again.
- What it costs you
- Ninety seconds, then thirty minutes. No fee.
- Where it can end
- Here, often. If we cannot name something worth doing in the first fifteen minutes, we say so and give you the other fifteen back.
- 02
Decide
Decide what gets built, and what does not.
- What happens
- Every recurring process gets two numbers: what it costs to fix and what it costs to leave alone for a year. We rank by payback and hand you a twelve-month sequence with a one-page version your board can read in five minutes. Alongside it, if you want it, your leadership team learns to do this costing themselves, so the next vendor pitch, including ours, gets priced rather than trusted.
- What you leave with
- A costed, ranked list. The reasons behind each ranking. The list of things we crossed off. Ground rules for what AI may and may not touch in your business, with a named owner.
- What it costs you
- A fixed fee, agreed before we start, and credited against the first workflow we build for you.
- Where it can end
- With a plan you run yourself. Some clients take the roadmap and the training and do not need us for the build.
- What happens
- One workflow at a time, in payback order. The work is built into the systems your team already uses, so nobody learns a new tool; the work simply stops arriving. Where nothing off the shelf fits, we build the software that does the job, and only after we have shown you it pays for itself. Your people are the owners from the first day, not after a handover.
- What you leave with
- Working software in your own accounts. The written rules for when it stops and asks a person. A team that can judge its output. Nothing that depends on us staying.
- What it costs you
- Per workflow for automation, against what it saves. Scoped and quoted for a custom build, gated on the payback we showed you.
- Where it can end
- After one workflow, if that is where the maths stops. There is no minimum.
In every phase
What stays true throughout.
- 01
The first step is free and stays free.
- 02
Nothing gets built unless it pays for itself, and you see the maths first.
- 03
No new tool for your team to learn.
- 04
Everything in writing, and everything you keep.
- 05
We name what we would not do, before you ask.
Who this works for
Businesses of 50 to 500 people, usually in one of three situations.
- 01
You keep being told you are behind on AI.
Every week someone says adopt it. Nobody has told you what it would save, or whether it is anywhere near your biggest leak.
- 02
Money is leaking and you cannot name the line.
You can feel the business dragging. You cannot point at the process doing it, and guessing costs more than measuring.
- 03
Your team does what software should do.
Copy, paste, reconcile, chase, repeat. Nobody was hired for that, and somehow everyone does it. You want it gone, not explained.
The one ask on this page
Ninety seconds now. Thirty minutes if it is worth it.
Take the check, see your score with no email asked for, and decide whether the thirty-minute review is worth your time. If you already know the process, skip the check and tell us.