How it works
Three stages, and we do most of the work
Working with us has three stages: a free scorecard that ends in a plan you keep, a fixed-scope build measured in days, and a monthly arrangement where we run what we built.
The scorecard and the walkthrough
You answer seven questions about how your operation actually runs today. The score appears on screen straight away, with a level for each of the seven areas and the one that is costing you the most right now.
If you book the walkthrough, we go through the score area by area, show you what fixing the top one would involve, and give you a plan. The plan is written so another team could pick it up. You keep it either way — that is not a figure of speech, it is the whole point of doing it this way round.
What we need from you
- Seven honest answers. Optimistic ones make the score useless.
- Twenty minutes from whoever actually knows how the work flows.
What you get
- A score out of 21 with a level for each of the seven areas.
- The one area to fix first, and what fixing it involves.
- A written plan you keep, with no obligation attached.
The build
We build one system first — usually the area that scored lowest — rather than trying to change six things at once. One working system beats six half-finished ones, and it lets you judge us on something real before committing further.
Week one
- We watch the current process end to end, on real work.
- We write down the rules you already follow, including the exceptions.
- You sign off on scope. Nothing is built from an assumption.
Week two, and sometimes three
- We build and connect it to the tools you already have.
- We run it alongside your existing process, not instead of it.
- You test it on real cases while the old way is still there.
Nothing goes live until it has handled real work correctly with your old process still running behind it. Cutover is a decision you make after seeing it work, not a date in a plan.
We run it
Automation is not a thing you install. Vendors change their forms, platforms change their exports, your own rules change when a state changes its notice periods. Something upstream breaks roughly every few months, and somebody has to notice and fix it.
That is the part we keep doing. Monitoring, repairs, and the next improvement — a tech team without the hire.
What running it includes
- Monitoring, so a break is found by us rather than by a tenant.
- Repairs when something upstream changes.
- Rule changes as your process or your states change.
- The next system, when you are ready for it.
What it is not
- Not a contract you are locked into. It is month to month.
- Not a licence. There is nothing to keep paying for if you leave.
- Not a black box — you can see what it does and what it did.
- If a month does not move your operation forward, that month is refunded.
Questions
What people ask about the process
How much of our team’s time does a build take?
A few hours in week one, mostly from whoever runs the process today, and some testing in week two. We watch real work rather than sitting your team in a workshop, because the described process and the actual process are rarely the same thing.
What does it cost?
It depends on what you actually need, which is what the free scorecard works out. You’ll get exact numbers on the call, with nothing hidden afterwards.
Can we start with more than one system?
You can, and we usually advise against it. One finished system changes a week; three half-finished ones change nothing and make it hard to tell what helped. Once the first is running, the second is faster.
What happens if we stop?
You keep the documentation, the rules and the process map. What we run on your behalf stops running, and we will tell you plainly which parts your team can keep operating themselves and which parts would need someone technical.
Start with the free scorecard.
Seven questions, two minutes, and your score appears on screen.