How it works
Each step pays for the decision about the next one.
No system gets sold before a diagnostic says it should exist. And after every step you keep something useful — whether or not you take the one after it.
Seven numbers you already know — revenue, three day-counts, how the chasing gets done — turned into a directional estimate of what your cycle is holding. Every figure shows its math, because you'll want to check it.
What you keep
A rough dollar figure on each leak, and the equation behind it. Run it twice a year even if you never talk to us.
Exit 1 · where you can stop
If the numbers come back small, stop here. Not every shop has a cash problem worth an engagement — the Snapshot is how you find out without spending anything.
Cash Conversion Diagnostic
Fixed fee · four phases, typically 4–6 weeks · at risk until the readout
Read the full diagnostic scopeThe same questions, answered from your actual financials instead of estimates — then taken to the people who run the work. Four phases: your cycle baselined, four interviews, two workshops to validate the leaks and design the target state, and a readout. One entity, trailing-12-month data, remote-first.
What you keep
The written report — baseline, leak map, opportunity map, target-state workflows, and fix sequence. Yours either way, including the fixes tagged “do it yourselves.”
Exit 2 · where you can stop
If the fix list says your team can handle it internally, the report is a working plan and we said so in writing. And if what we found wasn't worth the fee, you don't pay it — that's decided at the readout, by you.
We install what the fix sequence calls for — the pricing, billing, purchasing, and follow-up processes and the automation behind them — then run and improve it with you. You're buying a known result from your own diagnostic, not a project with an open end.
What you keep
A system your business owns and your people run — starting with the included build, up to ten days on a fix your own map named. The point is infrastructure that outlasts the engagement, not a dependency on us.
Exit 3 · where you can stop
The retainer continues only while it earns its keep on the two numbers we report: working capital freed and cash flow from operations.
This is the path for finding out where cash is stuck. If you already know — you can name the process and just lack the hands — the Targeted Diagnostic verifies it — typically one to two weeks — and skips the rest.
“Run” means it keeps working after the consultants would have left.
Where it runs
It runs in your tenant, not ours.
If you have an IT function, this is the first thing they’ll ask. Here’s the whole arrangement in one picture — and the detail, in their words, below it.
- Whose account does it run in?
- Yours. The automation sits in your own cloud tenant, under a service account your business owns and we administer — on licenses you most likely already own, and we check yours before we scope. If you have no cloud capability to build on, we run a single-tenant environment for you instead, with the exit and portability terms written into the agreement rather than discussed later.
- Where does our data go?
- It doesn't. Customer names, invoice amounts, aging and job costs are born and die inside your boundary. We build against a synthetic manufacturer — the same fictional company these walkthroughs run on — never against an extract of your books. What reaches us is whether a job succeeded or failed and on which record, never what was on it.
- Does anyone train a model on our numbers?
- Where you have a cloud model service of your own, the model runs inside your subscription and your region, and the call never reaches an account of ours. Where you don't, the no-training terms get named in writing per vendor and checked current before anything runs — not asserted from memory. If your contracts forbid data leaving at all, the honest answer is open models on your own hardware, and we'll tell you what that costs you in capability.
- What happens if we stop?
- You keep it. Every automation is handed over with its workflow export, configuration, secret references, test fixtures, runbook and rollback procedure. There's nothing hosted here to switch off, and nothing that needs us in the room to keep running.
The short version: we hold the access, you hold the data. Running and improving the system is what the retainer is for — sitting on your financials is not.