Value Leakage: Capacity ₹78 L
Objective. Open the Capacity category, read its findings as confidence-discounted sized leaks, and state what kind of value (capacity or cash) the category represents.
This screen answers 'how much value is leaking from unused or idle available capacity, and is that a capacity opportunity or a cash one?' It isolates one of the six leakage categories so a finding can be sized and owned.
See it in the demo
What this screen answers
The question here is 'how much available, paid capacity is not being turned into work, and what would freeing it be worth?' A Sales or CSM person opens this after the Overview to go one level deeper into a single category and pull out a specific finding to walk through.
The task
Open the Capacity screen at the cited route. Read its listed findings and the category magnitude (seeded in the demo around ₹78 lakh). Pick one finding and be ready to break its value into quantity x unit-cost x confidence. Do not quote the category figure externally - it is a seeded demo magnitude illustrating the method.
How to read it
Capacity leakage is measured in hours or FTE freed and then priced at the loaded rate. It is the clearest example of a capacity-type leak: the magnitude represents hours that could be released, not money in the bank. The misread to avoid: treating freed capacity as cash. Freed hours only become money if the customer actually redeploys those people to other work or removes the cost - that is the customer's decision, and the app is deliberately careful not to claim it for them. Remember the magnitude is already discounted by confidence, so it is a defensible estimate of a detected leak, not a theoretical maximum and not recovered money.
Honest limits
The screen proves the category is detected and sized on seeded data; it does not prove the figure for a real customer. The quantity basis (measured versus estimated), the unit-cost/rate, the recoverable share and whether this finding overlaps another category's hours are all customer-specific - validate them, and confirm detection method with product, before any number is quoted.
Interpretation check
Capacity leakage is freed hours/FTE, never cash recovered. The figure is a capacity opportunity priced at a rate; it becomes money only if the customer redeploys or removes the capacity, and it must never be summed with cash-type categories.
In the field
KnackGlobal (RCM, ~6,000 seats): idle capacity per seat is tiny, but across thousands of seats it sizes into a large capacity opportunity - still capacity, not cash, until they act on headcount or workload.
Practical task
Open the Capacity screen, pick one finding, and write it up as quantity x unit-cost x confidence with a one-line statement of whether it is a capacity opportunity or a cash one and who could own it.
Self-check
Is the Capacity category figure capacity or cash, and why does it matter?
Capacity - it is freed hours or FTE priced at a loaded rate. It matters because capacity is not cash until the customer redeploys or removes it, so it stays on its own line and is never added to cash recovered.
How would you break one finding on this screen into a defensible number?
Value = quantity x unit-cost x confidence. State the measured volume of the leak, the agreed money per unit, and the confidence discount for how certain the finding is - then it is a number finance can argue with rather than a vendor claim.
The customer wants to add this category to another category for a single total. What is the risk?
Overlap and mixing value types. Two categories can claim the same underlying hours (double-counting), and capacity leaks cannot be summed with cash leaks. Validate overlap and keep capacity and cash on separate lines.
What do you say about the ₹78 lakh figure on screen?
It is a seeded demo magnitude showing how the category is sized and ranked. The real figure depends on the customer's measured quantities, agreed rates and recoverable share - confirm with product and their finance.
Verified vs demo. Screen is live in the demo at /#/capacity; exact controls and figures are SME-validation-pending.