Software build budget & runway calculator
Set a budget and a target timeline, then add the people and services the build needs. The runway chart shows exactly when the money runs out relative to the plan.
- ~2 min
- Free · no sign-up
- Runs in your browser
How to use · 4 steps
- 01Enter budget and timelineYour total budget and how many months the build should take.
- 02Add the teamPick where the team is based, then use + and − to add each role you need.
- 03Choose infrastructure and AI usagePick the tiers that match your expected traffic and AI workload.
- 04Check the runwaySee how many months the budget lasts, whether it covers the plan, and a suggested budget with buffer.
Covered, no bufferagainst a 8-month plan · $1,200 left over
- Product engineers × 2$14k · 45%
- AI / ML engineers × 1$8.5k · 27%
- Product designers × 1$5.5k · 18%
- Infrastructure$900
- AI / API usage$1.2k
- Tools & overheads$1k
No black box.Every step, in plain words.
Results are estimates for planning, based on the figures you enter. They aren't financial advice or a quote.
- 01
Monthly burn = team cost + infrastructure + AI/API usage + a fixed allowance for tools and overheads.
- 02
Team cost = the number of each role × its monthly rate × the rate region multiplier.
- 03
Runway = budget ÷ monthly burn. Coverage compares runway with the timeline you've planned.
- 04
Rates are indicative monthly figures for planning, not quotes. Adjust the region to reflect where your team is based.
Good to know.
Burn rate is how much money a project or company spends each month. Runway is how many months the budget lasts at that rate.
Software timelines slip — usually because of scope that wasn't visible at the start. Planning for 20–30% more runway than the plan needs is common practice.
Yes, as a monthly usage tier. Model costs scale with volume, so treat the tier as a starting estimate and re-check it once you have real traffic.
Keep going.
AI vs human cost
Compare the monthly cost of a process run by people with the same process run by an AI system — and see the month it breaks even.
Automation ROI
Enter a task's frequency, handling time and error cost to see the hours and money you'd recover in a year — and when the build pays for itself.
AI readiness score
Twelve questions across data, processes, systems, team, ownership and risk. See where you're ready for AI and what's holding you back.
Tell us the job thatkeeps coming back.
We'll tell you whether it's worth automating, and what it would take. A founder or senior engineer replies within one working day.
