The Sprint
We build it first.
You decide after.
Two weeks, a fixed fee, and a working prototype pointed at your real workflow. At the end you keep it and stop, or take it to a production build and the sprint fee comes off the top.
What you end up with
- 01A mapped workflow
Every step, handoff, system, and decision in the process as it runs today, not as the org chart says it should. Where the time goes, where things break, and which piece is actually worth building.
- 02A working prototype
Not a mockup or a slide. Working software, pointed at the real workflow and narrow on purpose, so you can put it in front of the people who’d use it and find out what you actually think.
How it runs
Two weeks is the ceiling,
not the plan.
Before any of it: a short intake call, then a fixed number for the sprint. You know the fee before you commit to anything, and if we can’t see a prototype worth building in two weeks, we’ll say so then instead of selling you one.
Two weeks is the outside edge. We box it there so the work can’t sprawl to fill the calendar, and plenty of sprints finish inside it. The fee is the same either way, agreed up front.
- Step01
We map
We sit with the people who do the work and trace the process end to end, as it actually runs. However the sprint ends, the map is yours.
- Step02
We choose
We agree together on the one piece worth prototyping. Narrow beats broad here. The goal is something real in your hands, not a demo of everything.
- Step03
We build
We build that piece and put it in front of you with time still on the clock, then spend what’s left reacting to what comes back. You end the sprint holding something that runs.
At the end of the sprint,
you decide.
Take it as is
Some prototypes are already enough. If the piece we built solves the problem at the size it is, keep it and run it. There’s no retainer trailing behind it and no version two you have to buy to make version one work.
Take it to production
If it needs to be real infrastructure, hardened and integrated and handed to everyone instead of a few people, we quote the production build off something we have both now watched work. Start that build, or one connected to it, within 30 days of the sprint ending and the entire sprint fee is credited against it.
When a sprint
is the right call.
- You need to see it working before you commit to building it
- The process crosses several systems, and no two people describe it the same way end to end
- There’s a workflow the whole team works around, but nobody has ever drawn it
- You already suspect the requirements will change the moment people touch a real version
- Someone else has to see it run before they’ll fund the rest of it
Start a sprint
Tell us about the workflow you’d put through it. A few fields is all we need. We read every one personally, and we’ll tell you if a sprint isn’t what you need.