How we work
We study first. Then we build. Then we measure.
Three steps. Each one has a fixed time, a clear job for you, and something you keep at the end.
- 01
Study
1 to 2 weeks
We sit with your team and watch how the work actually moves, whatever the org chart says. We find the steps that are slow or leak money and put numbers on them.
What you keep
You keep the workflow map and the plan, whether or not we go on.
- 02
Build
4 to 12 weeks
We design the target workflow and a clickable prototype first. Scope and price are fixed for the first release. Then we build with weekly demos, and your team tests from week two.
What you keep
Code ownership and warranty are agreed with you and written into the statement of work.
- 03
Accelerate
Ongoing
We support go-live, measure the outcomes we agreed in Study, and take on the next bottleneck.
What you keep
You see the numbers move, or we hear about it first.
The small print, in plain words
- What we need from you
- One person who knows the work and can make decisions, about two hours a week.
- Changes along the way
- Small ones are part of the job. Bigger ones get a written estimate before we start them.
- What “done” means
- Your team is using it for real work, the data is in, and the numbers we agreed in Study are being measured.
- Handover
- Code, documentation and training are yours. Stay with us for improvements, or don't.
Questions people ask us
Can we stop after Study?
Yes. You keep the workflow map and the plan. Some people use it to fix things themselves or to brief another team. That's fine.
What if the workflow changes halfway?
We re-check the map, agree what changed, and give you a written estimate before we build the new part.
Do you work on site?
For Study, yes, wherever we can. Watching the work is the point. Build and Accelerate mostly run remotely with weekly demos.