AI Software Development
Prototype Sprint
Two to three weeks from workflow to a working prototype on your own process language and sample data
- Duration
- 2 to 3 weeks
- Ladder stage
- Proof
- NATIVE stages
- Target, Integrate
The situation
When this engagement is the right one
A prototype exists to make a decision possible. Ours runs on your process language and your sample data, and it ends with a recommendation that may be: do not build this. That is a successful outcome, and it is cheaper than the alternative.
You are probably seeing
- A workflow keeps being discussed and never specified.
- Two teams disagree about feasibility and neither has evidence.
- The business case cannot be written because nobody has seen the thing work.
What we do
The work, in the order it happens
- 01Map the workflow end to end with the people who do it.
- 02Agree the decision the prototype must make possible, in one sentence.
- 03Build a working prototype on sample data, in your terminology.
- 04Test it against the hard cases, not the clean ones.
- 05Deliver a build-or-stop recommendation with a named decision owner.
What you get, and keep
- A working, clickable prototype you keep.
- A before-and-after workflow map on one page.
- A build-or-stop recommendation with the evidence behind it.
- A value map if the recommendation is to build.
Prerequisites
- A named decision owner who will act on the outcome.
- Sample data, anonymised if necessary, that represents the hard cases.
Not included
- This is not production software. No authentication hardening, no integration with a system of record, no audit trail.
- We will not run a sprint with no named decision attached to it.
Where this sits in the method
Commercially this is a Proof engagement on the Proof, Product, Platform ladder.
FAQ
Questions we get asked
- What if the answer is do not build?
- Then the engagement succeeded. You spent three weeks instead of two quarters to find out.
- Can the prototype become the product?
- Sometimes the interaction design survives. The code is rewritten to production standards in the First Workflow Build.
- Who owns the output?
- You do, from day one, including prompts and evaluation sets.
Related engagements
Work that usually sits either side of this
Next step
Ready to scope prototype sprint?
Bring the pilots you already have running. The first call is a scoping conversation, not a pitch.