Software estimation tool
Software estimation that tells you how sure you are.
Estimate each part of a feature as a range. The tool adds the ranges up over 10,000 simulated runs and gives you a date at the confidence you choose, so you see which parts carry the risk before anyone commits.
Free, no sign-up. Nothing you type is saved.
Why ranges
A single number hides the risk.
“Two weeks” sounds like an estimate. It’s really three problems the team hasn’t had time to solve yet.
It sizes the whole feature at once
Nobody can hold twelve parts in their head. The number ends up being a feeling about the feature, not a sum of its work.
It doesn’t say how sure it is
“Two weeks” might mean “probably” or “if nothing goes wrong”. Whoever hears it can’t tell which, and plans as if it were a promise.
The missing work isn’t in it
Seat limits, bounced emails, users who already have an account. The parts nobody listed turn up mid-sprint, and the date slips.
How it works
How SprintProof estimates software.
- 01Break it into partsThe AI planner drafts the frontend, backend, data and rollout work. You edit, merge and split the parts.
- 02Three numbers per partBest case, likely and worst case, in dev-days. Small parts get narrow ranges; risky ones get honest ones.
- 03Add what the plan missed“Did you think of…?” questions from the check library become parts with their own ranges, or written decisions.
- 04Simulate, then pick a confidence10,000 runs of the plan give a date at 50% for planning, 80% for a commitment, or 90% for a launch. Parts tend to overrun together, so each run shares part of its overrun across the parts, and dates assume engineers work in parallel about 70% of the time.
Methods
Software estimation methods, compared.
Each method answers a different question. Only ranges answer the one your stakeholders ask: when will it ship, and how sure are you?
| Method | Shows uncertainty | Gives a date | Finds missing work |
|---|---|---|---|
| One number for the feature | No | Yes, with unknown odds | No |
| Story points | Partly, through the gaps in the scale | Only through average velocity | No |
| T-shirt sizes | Partly | No | No |
| SprintProof ranges | Yes, a range for every part | Yes, at the confidence you choose | Yes, from the check library |
FAQ
Software estimation questions
What is software estimation?
How does three-point estimation work?
Can we keep using story points?
Does it work with Jira and Linear?
Is the estimator on this page free?
Team
Your next estimate deserves error bars.
Create your account and name your workspace. Your first feature plan is free. To keep planning, subscribe to Team: the 14-day money-back guarantee applies.
Want to hear when the ChatGPT and Codex plugin ships? Leave your email.