What is a sprint actually costing you? Cost per sprint, cost per story point, cost per ticket — calculated from team size, salaries, sprint length, and velocity.
Adds 30% overhead to salary (employer NI/tax, benefits, equipment, software). Assumes 220 working days per year.
SprintFlint computes velocity per sprint and cycle time per ticket — the inputs to this calculator. Free for the first 300 tickets.
Start FreeSalary is roughly 70% of what an engineer actually costs the business. The other 30% covers employer tax (e.g. NI in the UK, FICA in the US), benefits (health, pension, equity), equipment, software licenses, office space, and recruitment amortised over tenure. Standard approximation across most industries.
It's the most concrete answer to "how much does this feature cost?" If a feature is estimated at 13 points and your cost-per-point is £2,000, that feature costs £26,000 to ship. CFOs and product directors find that conversation easier than "20 engineering days."
Yes, but be careful. Cost-per-point is a useful budgeting number for management. If you push it down to engineers as a productivity metric, they'll inflate point estimates to make the number look better. Use it for board conversations, not standup pressure.
Order-of-magnitude accurate. The 30% overhead assumption is industry-standard but varies by location (UK overhead is closer to 25%, US closer to 35% with healthcare). 220 working days assumes reasonable PTO. Adjust salaries to fully-loaded figures if you have a more precise rate from finance.
For a UK product team: £1,500-£3,000 per point is typical. US: $2,500-$5,000. The number itself matters less than the trend — if it's rising sprint over sprint, your team is shipping less per pound. Look at *why* (process bloat, tech debt, oversized stories) before reacting.