Stack Review
The diagnostic comes first.
Two days of structured discovery. One written report. One honest recommendation.
How it runs
We follow a real process end to end. Not the designed version, the one that actually runs. We talk to the people doing the work, because they are the ones who know where it catches.
Then we run a four-way test on every friction point we find. Only two of the four answers are candidates for software. The other two are governance, and a tool will not fix them.
The four-way test
Every friction point lands in one of four boxes. Which box it lands in decides whether software is even the right conversation.
Governance
A tool will not fix these. Buying one is how they get more expensive.
Nobody owns the decision
The work stops while it waits for someone to say yes, and no one is sure who that is. A tool built on top of this just adds a queue nobody owns.
Nobody agrees on the number
Two teams report the same measure and get different answers, and both are defensible. Automating it makes the disagreement faster, not smaller.
Candidates for software
These are the ones worth costing. Not all of them will clear the bar, but they are the right conversation.
The information exists elsewhere
Someone has it. It is in another system, another inbox, or another person's head, and getting it costs a phone call every time. That is an integration problem.
The information does not exist
Nobody is capturing it, so the decision is made on instinct. That is a build problem, and it is usually the one worth doing first.
What you get
The report names the top three friction points by value, with rough estimates. It tells you where technology helps, where it does not, and what the next move is.
If the answer is a meeting and a spreadsheet, you will have that in writing. We would rather tell you that in two days than sell you six months of the wrong thing.
Fixed price. You own the report on delivery.
If the friction is AI
AI Firebreak
A Stack Review looks at a process. AI Firebreak looks at how consistently AI is already being used across the organisation, against how far the controls have got past paper.
Get in touch
It starts with a short conversation about the process that is costing you. The scope and the price are fixed before anything begins.
Get in touch
Tell us what process is giving you trouble. We'll come back to you about whether a Stack Review is the right first move.