Measured
- +33% more successful sprints. A sprint counts as successful when the sprint goal is met as committed. Measured before and after Performalise on the same teams, aggregated across customer engagements 2024 to 2025.
- +45% growth in stakeholder satisfaction. Measured by stakeholder survey at review, before and after; the practical effect is that status meetings become decision meetings.
- Delivery forecast range from ±4 to 6 months to ±4 to 6 weeks across a portfolio. The width of the range within which delivery dates land, measured on the forecasts Performalise issues against what shipped.
- 26,000+ improvement ideas from a single team in one year through Team Voice, counted, not sampled.
- +4.2% sprint-over-sprint improvement rate, the average compounding gain on the team's own baseline.
Arithmetic
Two figures appear in leader-facing material: £750k of engineering spend a year that lands instead of slipping, across ten teams, and £3.7m of business value that recovered capacity carries. Neither is a measurement. Forecast and satisfaction are measured. The money is arithmetic: 10 teams at £37.5k per team per month, a third more sprints landing from a 50% baseline, value at 5x cost. Wherever those two figures appear on this site they carry that sentence.
How the signals are produced
Performalise builds two timelines per work item, what was said about it and what happened to it, from the four streams (standup, tracker, code and deploys, product analytics). The divergence between the two, scored against the sprint goal, is said versus did. Goal confidence is a band, not a point: the team's judgement wearing its evidence, pre-filled from real usage where it can be measured. Forecasts are ranges with the confidence behind them, extrapolated from the team's own history, never from a cross-company benchmark.
What we do not measure
Individual productivity. AI coding-tool adoption or token cost. Software capitalisation. Velocity as a target: velocity is a planning signal for the team that owns it and is never turned into a KPI or compared across teams.
Methodology
Aggregated across customer engagements, 2024 to 2025. Before-and-after on the same teams where the measure allows it. Methodology available on request to josef@performalise.com. Where a page states a number without its basis, that is a defect; tell us.
Frequently asked questions
Are the £750k and £3.7m figures measured?
No. They are arithmetic: 10 teams at £37.5k per team per month, a third more sprints landing from a 50% baseline, value at 5x cost. Forecast range and stakeholder satisfaction are measured.
What counts as a successful sprint?
A sprint whose goal is met as committed. The +33% is measured before and after on the same teams, aggregated across 2024 to 2025 engagements.
Do you benchmark teams against other companies?
No. Forecasts and drift are extrapolated from each team's own history. Cross-company benchmarks are deliberately not used.
Part of How Performalise works, the public record of how the product is built to behave. Last reviewed 27 August 2026. Corrections: josef@performalise.com.