Sprint 01
Validation Sprint
2–3 weeksStarts at $7.5k
Validate the problem before budget or build.
Best for
Unclear idea or assumptions
You get
- Decision Memo
- Opportunity Brief
- User Interview Summary
Sprint paths
Choose the smallest sprint that creates signal.
Every Prakriya sprint is time-boxed, outcome-driven, and built to help you decide what should happen next.
Decision path
Start small. Move only when signal earns it.
Sprint 01
Validation
2–3 weeks
Most common
Prototype
3–5 weeks
Sprint 03
Pilot MBP
6–10 weeks
Sprint 04
Venture Pod
3–12 months
Validation
Sprint 012–3 weeks
Prototype
Most common3–5 weeks
Pilot MBP
Sprint 036–10 weeks
Venture Pod
Sprint 043–12 months
Decision-firstTime-boxedEvidence-backedNo roadmap drag
Choose by signal
Start with the sprint that answers the next question.
Each sprint has a different job. Pick the one that reduces the most important uncertainty first.
Swipe to compare
Sprint 02
Most commonPrototype Sprint
3–5 weeksStarts at $15k
Test the workflow before committing build effort.
Best for
Solution ideas that need proof
You get
- Clickable Prototype
- Workflow Map
- Usability Findings
Sprint 03
Pilot MBP Sprint
6–10 weeksStarts at $35k
Launch a buyable pilot with real users.
Best for
A buyable product test with real users
You get
- Pilot MBP
- Launch Plan
- Metrics Dashboard
Sprint 04
Venture Pod
3–12 monthsFrom $12k/mo
Keep shipping once signal is real.
Best for
Validated signal that needs execution
You get
- Operating Cadence
- Product Iterations
- Handoff System
Prices are USD starting points. Final scope is confirmed after a strategy call.Founding partner pricing is available for the first few sprint engagements.
Decision helper
Not sure where to start?
Start with the question you need answered.
Question 1 / Validation SprintIs this problem worth solving?
Question 2 / Prototype SprintWill this workflow work for users?
Question 3 / Pilot MBP SprintWill people buy or adopt this?
Start with Pilot MBP Sprint.
This sprint reduces adoption and willingness-to-pay uncertainty.
View sprintQuestion 4 / Venture PodSignal is real. Who keeps building?
Compare paths
Same decision system. Different signal depth.
Use the matrix to compare the next question, primary output, and best-fit moment for each sprint.
Validation Sprint2–3 weeks / Starts at $7.5k
- Timeline
- 2–3 weeks
- Investment
- Starts at $7.5k
- Main question
- Is this problem worth solving?
- Primary output
- Decision memo and scope direction
- Best when
- Unclear idea or assumptions
- What happens next
- Kill, refine, or prototype
Prototype Sprint3–5 weeks / Starts at $15k
- Timeline
- 3–5 weeks
- Investment
- Starts at $15k
- Main question
- Will this workflow work for users?
- Primary output
- Clickable concept and usability signal
- Best when
- Solution ideas that need proof
- What happens next
- Refine, build an MBP, or stop
Pilot MBP Sprint6–10 weeks / Starts at $35k
- Timeline
- 6–10 weeks
- Investment
- Starts at $35k
- Main question
- Will people buy or adopt this?
- Primary output
- Buyable pilot product and adoption evidence
- Best when
- A buyable product test with real users
- What happens next
- Handoff, continue, refine, or kill
Venture Pod3–12 months / From $12k/mo
- Timeline
- 3–12 months
- Investment
- From $12k/mo
- Main question
- Who keeps building after signal is real?
- Primary output
- Operating pod, releases, and handoff system
- Best when
- Validated signal that needs execution
- What happens next
- Continue with pod, handoff, or stop
Shared outputs
Every sprint ends with decision evidence.
The artifact set changes by sprint depth, but every engagement closes with a decision-ready trail.
Decision memo
Clear recommendation and rationale.
IncludedScope boundary
What is in, what is out, and why.
IncludedEvidence log
Research, tests, findings, and assumptions.
IncludedHandoff notes
What your team needs to continue.
IncludedNext-step recommendation
Kill, refine, handoff, or continue.
IncludedArtifacts are built to be shared with leadership, engineering, and product teams.
After the sprint
Every sprint ends with a clear next move.
The point is not more backlog. The point is knowing what should happen next.
Decision outcome
Kill
Stop with clarity and save resources.
Decision outcome
Refine
Potential is real, but the scope needs adjustment.
Decision outcome
Handoff
The internal team can own it with context.
Decision outcome
Continue
Signal is real. Keep building.
FAQ
Questions before you choose a path.
Use these to decide whether you need clarity, prototype signal, adoption evidence, or continued execution.
How do I know which sprint is right?
Start with the question you need answered. If the problem is unclear, validate. If the workflow is unclear, prototype. If adoption or purchase is unclear, pilot an MBP.
Can we start with validation and move to prototype?
Yes. The sprint path is designed to move only when the previous step creates enough signal for the next investment decision.
What if we already have research?
We use what you have, identify gaps, and scope the sprint around the highest-risk unanswered decision.
What makes a Pilot MBP different?
A Pilot MBP is the smallest real version users can buy, adopt, or commit to, scoped tightly enough to test real demand.
Do you build production software?
Yes, when the sprint requires it. The scope stays bounded around the decision, not a full product roadmap.
What if the sprint says we should kill the idea?
That is a valid outcome. Stopping with evidence protects budget, roadmap focus, and team energy.
Have a product bet that needs a decision?
Book a strategy call and we'll help you choose the smallest sprint that creates signal.
Need help choosing?
Book a strategy call