Freed capacity
The hours saved — how many people is that, and what does it become?
Hours given back by AI as full-time equivalents, then the three honest readings of the same number: capacity, growth, or a saving bounded by attrition.
- ≈ 2 min
- Free calculation · AI commentary on request
- You leave with: Hours saved as FTEs, and the three ways to read them
The hours given back
Gross, as claimed. The model then applies adoption and realisation.
The pace at which a payroll saving is even possible: through unreplaced departures.
Enables the growth reading. Set 0 to ignore.
2.2 full-time equivalents freed. What that number becomes — capacity, growth or saving — is a management decision, not a calculation result.
A business case that books these FTEs as a year-one saving without saying through which departures loses the trust of the people who have to sign it.
The three readings
The figures above are computed and free. If you also want them read back to you — what they mean, what is specific to your sector, where to start — that is produced on request.
The detail
| Line | Estimate |
|---|---|
| Risk | |
“Cost” reading — bounded by attritionoften omitted A payroll saving exists only through unreplaced departures. At 10% attrition, at most 12.0 FTE in year one. | €260,000 €91,000 — €550,000 |
| Return | |
Gross hours claimed 120 people × 8 h/month × 12. | €11,520 |
Hours genuinely recoverable After 60% active users and 50% realisation. The rest evaporates into less hurried days — not nothing, but not a euro. | €3,456 €1,210 — €7,344 |
“Capacity” reading The hours are redeployed to work that was not getting done. Valued at loaded cost. This is growth or quality, not a saving. | €260,000 €91,000 — €550,000 |
“Growth” reading Hours redeployed to revenue-generating work at the organisation's current revenue per hour. Assumes the demand exists to absorb it. | €390,000 €140,000 — €830,000 |
The assumptions
Every figure above rests on these. The ones marked “assumption” have no external source: they are modelling choices, labelled so they can be argued with rather than mistaken for measurements.
- Hours per FTE 1600 h/anPublished
- Effective annual hours in France, net of leave.
- Attrition 10 %/anAssumption
- The pace at which a cost reading is even possible. An organisation at 5% attrition takes twenty years to realise one FTE through natural departures.
- Active users 60 %Published
- Active use as a fraction of seats bought. Enterprise assistant deployments routinely report 30–60% sustained active use; the top of this range requires deliberate enablement, which is what the change-management line above pays for.
- Realisation 50 %Assumption
- The gap between hours saved and value realised. Twenty minutes saved across a fragmented day is often not recoverable as anything. This is the single biggest reason AI business cases overshoot, and it is why the tool never quotes raw hours × rate as a benefit.
What the calculation does, what the AI does
Every figure on this page comes from a deterministic algorithm running in your browser: the same input always gives the same result, and nothing is sent to produce it. AI runs only afterwards, to write the commentary from those figures. It produces none of them — the format it fills has no numeric fields — and any sentence quoting a value the calculation did not produce is removed before display.
Where to go next
See all 19 tools →- Roadmap
In what order, and over how long?
≈ 3 min · Quarterly phases and what each one delivers - Training sizer
How many sessions, over how long, for what budget?
≈ 3 min · Session count, real duration and the full budget - Carbon footprint
How much does our AI use emit, and where should it run?
≈ 2 min · kWh and kg CO₂e, by hosting region - Cost calculator
What does our AI transformation actually cost, and when does it break even?
≈ 3 min · A line-by-line budget, the return and the break-even month - Pitfall radar
What is going to go wrong in our programme, and what will it cost?
≈ 2 min · Detected pitfalls, their weighted cost and the fix for each - AI usage policy
Our teams already use AI: what rules do we give them, in writing, this week?
≈ 4 min · A complete AI usage policy, ready to sign