Map it. Build it. Keep tightening it.
Three phases, in order. The first one is sold on its own, so you can stop after it and still be better off than when you started. That is deliberate. Nobody should be asked to commit to a build before anybody has seen the operation.
The Redprint
We map how work actually moves through the business, write it down, lean it out, and score every automation opportunity in it. You end the week with your operation documented and a ranked, costed list of what to build.
What we need from you
- Thirty to sixty minutes each with the people who do the work, not their managers
- Read access to the systems the work passes through
- One person who can answer “why do we do it that way”
What you get
- Every process documented as it runs today
- The leaned-out version of each one next to it
- The automation map, ranked, with a build spec per opportunity
- A written business case with the numbers behind it
The build
We start at the top of the map and work down. One workflow at a time, live and stable before the next one starts, because nothing we ship is allowed to interrupt the work you are already doing.
How a workflow ships
- Built against the spec you already approved in the map
- Run alongside the manual process first, so you can compare outputs
- Switched over once it has handled the exceptions cleanly
- Watched for two weeks afterwards, with the fallback still in place
What does not happen
- No system replacement. Your team keeps the tools they know
- No big bang. There is no day when everything changes at once
- No training program. The work simply stops arriving on their desk
- No decision handed to a machine that should have been yours
Tighten
Operations move. You add a service line, a customer wants something done differently, a platform changes underneath you. The retainer keeps the system matched to the business instead of slowly drifting away from it.
What the retainer covers
- Monitoring, and fixing what breaks before you find out it broke
- New workflows from the map as you decide to turn them on
- Changes to existing ones when the process changes
- The documentation kept current, so the app stays true
Terms
- Month to month. Cancel anytime
- Everything we build stays yours, running in your systems
- 30-day satisfaction guarantee on the work
Slow enough that nothing breaks. Fast enough that you feel it in a month.
The first workflow is usually live in week two, and it is deliberately one where the payback is obvious: the thing your team complains about most. Once people see one job stop arriving on their desk, the rest of the map gets a lot easier to agree on.
Two ways in, and the first one does not commit you to the second.
The Redprint
A fixed-scope week, priced and sold separately from any build. Your operation documented, leaned out and mapped, delivered as an app your team can use from the day it lands. Buying it obliges you to nothing else, and the build specs are yours either way.
Build and retainer
We build down the map in the order you choose, then hold the system steady as the business changes. Month to month, cancel anytime, and priced against the hours it gives back rather than against a page count.
Pricing depends on the size of the operation and how much of the map you want turned on. We quote after the discovery call, in writing, against a scope you have read.
What owners ask before they start.
How long until we see something working?
How disruptive is this to the people doing the work?
Who owns what you build?
What if we want to build it ourselves?
What does the guarantee actually mean?
- 01How the work actually moves through your business today
- 02What you have already tried, and where it came apart
- 03Whether there is enough here to be worth building
You will be talking to the people who would actually build it. If there is something worth doing, we will tell you what it would look like. If there is not, then we build a relationship.