Step three · The build sprint
One decision, start to finish, in your accounts.
Four to six weeks, fixed price, on one decision. Your team learns the thing while it is being built, not after.
What it is
Built to the line, and nothing past it
Four to six weeks on one decision. Automation runs in your own environment under your own accounts, not on our server, and the workflows are yours. Your team gets trained on the thing while it is being built, not after. We measure the same steps again at the end and compare them to the map.
The note written at the line during the map, what the decider needs in front of them, is the build specification. Everything the system produces exists to satisfy that note and nothing more. The judgment call stays with the person accountable for the outcome, only now it arrives with the evidence already attached.
- Price
- $15,000 to $35,000
- Terms
- Fixed, per decision
- How long
- Four to six weeks
What you get back
- A working system that prepares the decision
- Runs on your infrastructure and credentials
- Team training during the build
- Before and after measurement against the map
Ownership
Nothing turns off when we leave
The workflows live in your environment, on your credentials, with the documentation alongside them. There is no licence to keep paying and no runtime of ours in the path. That is a property of how we build, not a promise about how we behave.
Measurement
We time the same steps again at the end
The line map produced timed baselines for each step of the preparation. At the end of the sprint we time those same steps and put the two numbers side by side. If the gap is smaller than the map predicted, you get that in writing too.
Questions
Before you ask
Where does the automation actually run?
In your accounts, on your infrastructure, under your credentials. Not on our server. The workflows are yours, so if we stop working together nothing turns off and nothing has to be handed back.
Why is the price fixed per decision?
Because the line map already measured the thing, so we are not guessing at scope. One decision, start to finish, for a number agreed before the work starts. If we were wrong about the scope that is our problem, not a change order.
What does the sprint actually deliver?
A working system that does the preparation in front of one decision and stops at the line, plus training for the people who will use it, delivered while the thing is being built rather than after. At the end we time the same steps again and compare them to the map.
Who owns the workflows when the sprint ends?
You do. They live in your environment on your credentials, and the documentation goes with them. There is no license to keep paying and no runtime of ours in the path.
Talk to us
Tell us which decision you would build first.
If you already know the decision and roughly what it costs to prepare, a sprint can start from that. If you do not, the line map is the cheaper way to find out which one is worth the four weeks.