Home › The Garage › Capacity modelling & cost-benefit analysis
Capacity & Value

Capacity Modelling & Cost-Benefit Analysis

Before you spend a dollar changing a process, you should be able to say what it will return. Capacity modelling turns time and headcount into throughput and cost; cost-benefit analysis turns a change into a number leadership can sign off.

By LeanBean · Updated November 2026 · 8 min read
What's in this guide
  1. What capacity modelling is
  2. Finding the bottleneck
  3. Throughput, labour cost and lead time
  4. Cost-benefit analysis of a change
  5. The six types of value
  6. The double-counting guard
  7. Common questions
Intake120 / day Assessment70 / day ← bottleneck Approval200 / day The whole process can only move 70/day — the slowest stage sets the pace. Adding staff anywhere but Assessment changes nothing.
Capacity is governed by the bottleneck. Model it, and you know exactly where a change pays off — and where it doesn't.

What capacity modelling is

Capacity modelling works out how much a process can actually produce, given the time each step takes and the people assigned to it. It converts the soft language of "we're stretched" into hard numbers: units per day, the limiting stage, the labour cost to run it, and the lead time a unit experiences. Once you have that model of the current state, you can model a future state — more automation, different staffing — and read off the difference.

Finding the bottleneck

Every process has one stage that is slower than the rest. That stage — the bottleneck — sets the throughput of the whole flow, no matter how fast everything else runs. The arithmetic for each lane is simple:

Lane capacity
capacity per day = (staff × working minutes per day) ÷ (effective minutes per unit)
where effective minutes per unit = time per unit × (1 − automation %).

Run that for every lane; the smallest result is the process throughput, and the lane that produced it is the bottleneck. This is the single most important number in the model: improving any other stage is wasted effort until the bottleneck moves. It is the capacity equivalent of the Theory of Constraints — and the reason "add more people" so often changes nothing.

Throughput, labour cost and lead time

A complete model carries three figures, because an improvement can show up in any of them:

Model the current state honestly first — actual times, actual staffing — then change one thing and compare. That delta is the raw material for the cost-benefit case.

Cost-benefit analysis of a change

A cost-benefit analysis (CBA) weighs what a change costs against what it returns, annualised so it's comparable across options. The discipline that makes a CBA credible to a CFO is simple: never type a dollar figure in directly. Every dollar of benefit should be the arithmetic consequence of a modelled change — a before-and-after capacity delta — not an estimate someone asserted. If freeing 30 minutes a unit removes the need for one full-time assessor, the benefit is that role's loaded cost across the working year, derived, not guessed.

  1. Model the future state — the same process with the proposed change (automation %, staffing).
  2. Read the deltas — throughput up, labour cost down, lead time down.
  3. Convert each delta to an annual figure using the loaded rate and working days.
  4. Net against the cost of making the change — tooling, build, run cost.

The six types of value

A freed half-hour is not automatically "savings." Classifying the benefit correctly is what makes the number honest:

TypeWhat it is
Opex reductionHeadcount or spend actually removed — cash out the door, gone
Capacity releaseFreed time, staff retained and redeployed — potential, not cash
RevenueMore throughput sold at a known margin per unit
Risk / complianceIncidents or penalties avoided × their cost
Working capitalFaster lead time releases cash tied up in the process
Cost avoidanceA hire you didn't have to make as volume grew

The double-counting guard

One freed hour is one type of value, never two
The most common way a business case loses credibility is counting the same freed labour as BOTH an opex saving AND a capacity release. It is one or the other: either the role is removed (opex) or the person is kept and redeployed (capacity). Decide which, and claim it once. A CFO will find a double-count in seconds, and it costs you the whole case.

This is exactly how LeanBean's capacity and value engine works: you model the before and after on the map, it proposes the value type from what physically changed, you confirm it, and the guard stops the same hour being claimed twice — so the number that reaches leadership is defensible.

Describe a process. Get the whole analysis.

LeanBean turns a plain-language description of any process into a professional map — with Lean waste, SIPOC, design-thinking, AI-readiness and capacity analysis built in, and a Transformation Coach that sequences the fixes. Free to start.

Build your first map free →

Keep learning in the Garage

Short, practical lessons on Lean, process mapping and AI-ready operations — the same thinking that powers LeanBean, in two minutes or less. Follow along and build the habit.

Common questions

What is capacity modelling?

Working out how much a process can actually produce, given the time each step takes and the staff assigned. It converts 'we're stretched' into numbers: units per day, the limiting (bottleneck) stage, the labour cost to run it, and the lead time a unit experiences.

How do you find the bottleneck?

Calculate each lane's capacity — (staff × working minutes) ÷ effective minutes per unit — and take the smallest. That lane is the bottleneck and it sets the throughput of the whole process. Improving any other stage changes nothing until the bottleneck moves.

How do you do a cost-benefit analysis for a process change?

Model the future state with the change, read the deltas (throughput up, labour cost down, lead time down), convert each to an annual figure using the loaded rate and working days, then net against the cost of making the change. Crucially, derive every dollar from a modelled delta rather than asserting it.

Why shouldn't freed time be counted as both savings and capacity?

Because it is one freed hour, not two. Either the role is removed (an opex saving) or the person is retained and redeployed (a capacity release). Counting both double-counts the same hour and destroys the credibility of the business case.

Related guides: Process Cycle Efficiency · Transformation roadmap · What is AI readiness?