Free tools for product and delivery teams
Six calculators I use in real engagements, rebuilt so you can use them too. No sign-up, no email wall, nothing sent anywhere: every calculation runs in your browser and disappears when you close the tab.
The tools
Story point estimator
A shared reference for what 1, 2, 3, 5, 8 and 13 points actually mean, plus a calculator that turns a sized backlog into working days including a regression buffer. The table is the half most teams skip.
Open the toolRICE backlog prioritiser
Score initiatives on reach, impact, confidence and effort, and get a ranked backlog you can defend in a room full of people who each want their item first. Export the ranking as CSV.
Open the toolRelease date forecaster
"When will it be done?" deserves a range. Backlog, velocity, variability and scope growth become best, likely and worst-case dates, with the point at which new scope outruns delivery made obvious.
Open the toolSprint capacity planner
Turn team size, sprint length, ceremonies, holidays and focus factor into the capacity you actually have, in hours and story points. The gap between gross and net is usually why sprints miss.
Open the toolFeature cost & delivery risk estimator
The real cost of a feature once discovery, design, code review, QA, rework, release and first-year support are counted, and a risk score that shows how much of the estimate is guesswork.
Open the toolMeeting cost calculator
What that recurring meeting costs per session, per month and per year, plus what you'd save by cutting fifteen minutes or two attendees. Useful evidence for a conversation you've been avoiding.
Open the toolNothing is collected. These tools have no backend, no analytics on the inputs, no cookies and no storage. Whatever you type stays in your browser. Use real numbers, because that's the only way the output is worth anything.
The arguments these tools end
"That's a 3, not a 5." Points only work when everyone means the same thing by them. A written reference scale turns sizing from a negotiation into a comparison, and moves the conversation to where it belongs: what makes this risky, not how many hours it takes.
"Everything is a priority." RICE doesn't make the decision for you, but it forces the four things that matter into the open, where they can be argued about honestly.
"When will it be done?" A single date is a promise made with information nobody has. A forecast with a range is defensible, and it survives the sprint where everything goes wrong.
"We should be able to fit that in." A team of five in a two-week sprint does not have four hundred hours. Planning as though it does is how commitments quietly become fiction.
"It's a two-week build." The build is two weeks. Discovery, design, review, QA, the rework after the demo, the release and the first three months of support are the other half.
"It's only an hour a week." An hour a week with eight people in the room is a five-figure annual line item. A number turns a preference into a budget decision.
Something isn't shipping. Let's find out why.
Send me three sentences about what's stuck, or take the free 30-minute call. Either way you'll get an honest read - including if the answer is that you don't need me.