Process
From opportunity to measurable impact
Four stages, each producing something you can review before the next begins. You can stop after any of them.
Discover
Understand how work actually moves, not how the diagram says it should.
We follow a real workflow from the moment something arrives to the moment it is finished. Who touches it, where it waits, what gets re-typed, and which steps exist because of a decision nobody remembers making. Most of the useful findings are in the waiting and the re-typing.
- What you get
- A written description of the current workflow and where the time goes.
- What we need from you
- An hour or two with the people who do the work, and access to look at the systems.
Prioritize
Rank opportunities by measurable impact and by how confidently a project could start.
Two things decide the order: how much a change could matter, and how sure we can be about it today. A large opportunity nobody can measure ranks below a smaller one with a clear baseline, because the second can be proved and the first cannot. We pick one and write down why.
- What you get
- A ranked shortlist, one recommendation, and the metric that would settle it.
- What we need from you
- A decision on whether the recommended metric is one you actually care about.
Build
Build the narrowest useful version, integrated with the tools you already run.
Scope is written down before development, including what is excluded. The first version does one thing against one workflow, with human review retained wherever judgement matters. Your existing CRM, help desk and spreadsheets stay where they are; we connect to them.
- What you get
- A working system in your environment, and documentation of its boundaries.
- What we need from you
- Access to the relevant systems, and someone available to review edge cases.
Measure
Compare against the baseline agreed before development, over a defined period.
The metric was baselined before anything was built, so the comparison is real rather than reconstructed afterwards. We run for a defined period, look at what moved, and decide together whether to expand it, adjust it or stop. Stopping is a legitimate outcome.
- What you get
- A before-and-after against the agreed metric, and a recommendation on what next.
- What we need from you
- Patience for a defined observation period rather than a verdict in week one.
Commitments
What holds this together
Four rules that decide how the work runs, including the ones that occasionally cost us the project.
The metric comes before the build
If we cannot agree what would count as success and how to measure it today, that is a reason to wait, not to start.
We will tell you when AI is the wrong answer
Sometimes the fix is a process change, a setting in a tool you already pay for, or nothing at all. Saying so costs us a project and keeps the advice worth having.
Scope is written down, including exclusions
You should be able to read what is not being built as easily as what is. Ambiguity in scope is where projects go wrong.
No estimate before the workflow review
Implementation projects typically start at $3,000. That is an indicative starting point, not a quote, and we will not pretend to price work we have not examined.
Before you commit to anything
The audit is stage zero
The free AI Opportunity Audit is a compressed version of Discover and Prioritize, run from your own answers. It cannot see your systems or your volumes, and it says so plainly in the result. It is a way to find out whether a conversation is worth having.
Where is your business losing time or opportunity?
Tell us what you are trying to improve. We’ll help you identify whether there is a realistic AI opportunity—and tell you honestly if there isn’t.
No prepared brief required. Tell us what you’re trying to improve, and we’ll help you identify the next step.