Free tool · no signup
Software project estimate calculator
List the tasks, give each one a best case, a likely case and a worst case in hours, and get the expected total, a likely range, and a safer price to quote. Then turn it into a proposal or a payment schedule.
| Task | Best case | Likely | Worst case | Expected | |
|---|---|---|---|---|---|
| 4.5 h | |||||
| 12.7 h | |||||
| 25.3 h | |||||
| 11 h | |||||
| 8.7 h | |||||
| 9 h |
Expected
71.2 h
$6,764 at $95 an hour. Likely between 65.9 and 76.5 hours.
What to quote
| ExpectedRight about half the time | $6,764 |
| Safer quoteCovers the work about 5 times in 6 | $7,268 |
The maths (PERT): each task's expected hours = (best + 4 × likely + worst) ÷ 6, and its spread = (worst − best) ÷ 6. Expected hours add up; spreads add as variances, so the project's range is narrower than the sum of every worst case. The safer quote is expected + one spread.
Questions people ask
How do I estimate the cost of a software project?
Break it into tasks you can picture doing, estimate each one in hours, add them up and multiply by your rate. Estimating each task three ways (best case, likely, worst case) gives you a realistic total and a range instead of one number you'll probably miss.
What is a three-point estimate?
For each task you give a best case, a likely case and a worst case. The expected time is (best + 4 × likely + worst) ÷ 6, which leans towards the likely case but lets the risky tasks pull the total up. It's the PERT method, and the calculator shows the maths under the tool.
How much buffer should I add to an estimate?
Developers report anything from 1.25× to 4× in practice, which is why a single multiplier is a poor guide. Worst-case hours per task show where the risk actually is; quote the safer figure, or put a visible contingency line in the proposal instead of padding every task.
Should I quote the expected price or the safer one?
The expected total is right about half the time, so quoting it means overrunning about half the time. The safer quote (expected plus one standard deviation) covers the work in roughly five cases out of six; many developers quote that and show the likely range so the client sees the reasoning.
How should I estimate work nobody has done before?
Split it out. Quote a short, paid discovery or prototype phase first, then estimate the rest once the unknowns are known, or bill the uncertain part by the hour. Wide gaps between best and worst case in the calculator are the tasks to treat this way.
Can I share an estimate with a client or a colleague?
Yes. “Copy a link to this estimate” puts every task and number in the link itself, so it opens with the same figures. Nothing is stored on our side.