Find the real shape of the work, then build to it.
Map, Shape, Build, Evolve. Four stages, each short enough to check, each ending in something you can read, click, or use — and each a point where you can stop without being left holding half a system.
- 01Map
- 02Shape
- 03Build
- 04Evolve
What you have at the end of each stage.
- 01
Map
We follow the work as it actually runs, including the parts done in spreadsheets, chat, and memory, and mark where the standard model stops describing you.
OutputA written map of the operation, with the friction ranked by what it costs.
- 02
Shape
The map becomes a data model, explicit rules, and real screens in real states. Technology is chosen here, with the tradeoff written down beside the choice.
OutputPrototype, architecture, and a release plan staged so each stage stands alone.
- 03
Build
Built in stages you can use, awkward cases first, with permissions, failure states, and reporting in the first release. Progress is shown as working software, not a percentage.
OutputTested software in production, documented, with the critical path covered.
- 04
Evolve
We watch what production actually does — exceptions, errors, adoption, cost — and add adjacent work onto the same model instead of beside it.
OutputMonitoring, support, and extensions that do not fork the system.
Three ways to start, each small enough to stop.
- 01
Workflow map
A short engagement on one process: what happens, who owns it, where it waits, and what software would actually change. You keep the map whether or not we build anything.
- 02
Product prototype
A clickable product model using your terminology, before scope hardens. It settles the arguments a written specification usually hides.
- 03
Focused implementation
One integration, automation, module, or internal tool, with the boundary agreed in advance. Small enough to judge us by before anything larger is committed.
See the system while decisions are still inexpensive.
Assumptions, edge cases, and tradeoffs are easier to argue about when you can click on them.
- 01
Prototype
Test the product model
- 02
Demonstrate
Review working behavior
- 03
Release
Learn from real use
Tell us the process everyone works around.
Describe it in a sentence or two. We will come back with what we would build first, what it would take, and whether you actually need us for it.