Value Leakage: System ₹54 L
Objective. Open the System 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 system waits, latency and tool downtime, 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 is 'how much working time is lost waiting on systems - slow screens, latency, downtime, tool switching - and what is that 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 System screen at the cited route. Read its listed findings and the category magnitude (seeded in the demo around ₹54 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
System leakage is time lost to the tools rather than the process, priced at a rate. Read it as capacity lost to waiting, sized and confidence-discounted. The misread to avoid: assuming the figure is money IT will save by fixing a system. It is capacity lost to waiting, priced and discounted - realising it depends on removing the wait and using the freed time, and it can overlap with process leakage on the same hours. 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
System-wait leakage is lost capacity (people waiting on tools), not cash and not a guaranteed IT saving; it becomes value only if the wait is removed and the freed time is used, and it may overlap with process findings.
Practical task
Open the System 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 System category figure capacity or cash, and why does it matter?
Capacity - time people lose waiting on systems, priced at a rate. It is not cash and not an automatic saving; the wait has to be removed and the freed time put to use, which is the customer's action.
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 ₹54 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 /#/system; exact controls and figures are SME-validation-pending.