Value Leakage - where is value lost, who can act, and what has actually been recovered?
Objective. Teach the customer value of Value Leakage: the application that quantifies lost value in money terms (value = quantity x unit-cost x confidence), attributes each finding to an owner, and tracks it from baseline through action to verified recovery. Learn to make the formula concrete and to keep recovered capacity strictly separate from cash recovered.
Value Leakage is the money layer of the platform. Every other app finds a problem; this one puts a defensible number on it, says who can act, and tracks whether it was actually recovered. The discipline that makes it credible: each finding is quantity times unit-cost times confidence (so soft findings are discounted, not hidden), and the recovery screen keeps recovered capacity and cash recovered as separate lines that are never summed.
See it in the demo
The customer problem
Operations leaders know they are leaking value - idle capacity, process friction, system waits, quality rework, missed AI opportunities, poor outcomes - but they cannot put an agreed, defensible number on any of it. So improvement initiatives compete on anecdote and volume, not on money. The biggest leak and the loudest leak are rarely the same, and without quantification the business funds the loudest.
When numbers do get produced, they are usually inflated and un-owned: a consultant's slide claims a huge 'savings opportunity' that is really a theoretical maximum, with no owner, no confidence discount, and no way to verify it later. Finance learns to distrust operations' numbers, and genuine recovery goes unfunded because every claim looks like the inflated ones. The core problem is the absence of an honest, trackable, owned ledger of where value is lost and what was actually won back.
Business impact
Unquantified leakage means mis-allocated improvement effort - teams chase visible annoyances while the largest recoverable value sits untouched because no one sized it. In an RCM operation like KnackGlobal across thousands of seats, even a modest per-unit leak multiplies into a very large number, but only a quantified, prioritised view turns that into a fundable programme.
The inflation problem has a specific, damaging consequence: when capacity freed is reported as if it were cash collected, leaders over-claim, finance writes down the credibility of the whole programme, and the next improvement budget is harder to win. A recovery story that cannot distinguish 'we freed 200 hours' from 'we collected this much cash' is not a business case; it is a liability. The impact Value Leakage addresses is both the lost value itself and the lost trust from measuring it dishonestly.
How Time Champ addresses it
Value Leakage (https://leakage.demo.timechamp.io/) organises findings into categories - capacity, process, system, quality, AI and outcome - with workflow detection surfacing them, a Top value leaks view ranking them, attribution naming who can act, and a recovery view tracking status. In the demo the category tiles carry real magnitudes (for example Capacity around 78 lakh and Process around 1.12 crore), which makes the point that leaks are sized and ranked, not just listed.
The quantification model is value = quantity x unit-cost x confidence. Quantity is the measured volume of the leak (hours, touches, units). Unit-cost is the agreed money per unit (loaded hourly rate, cost per claim). Confidence is a deliberate discount for how certain the finding is - a well-evidenced leak counts near full, a directional one is marked down. That confidence factor is what stops the number inflating. The recovery screen then explicitly separates recovered capacity (hours or FTE freed) from cash recovered, and tracks each finding Open to Verified. Confirm with product the rate sources and detection methods for a given customer; the demo shows the model and magnitudes on seeded data.
What to say / do
Sales - one finding, the formula, and the recovery status. Open the Overview, pick one finding from Top value leaks, and break it down live: 'This number is quantity - the hours we measured - times unit-cost - your loaded rate - times confidence - how sure we are. The confidence factor is why this is a number your CFO can argue with, not a vendor fantasy.' Then open recovery and show the finding's status, and crucially separate the two lines: 'This part is capacity we could free; this part is cash actually recovered. We never add them together.' Qualify: 'When you pitch an improvement internally today, how do you size it, and does finance believe the number?'
CSM - validate the inputs before you trust any leak number. The number is only as honest as its inputs, so check: the time basis (is the quantity measured or estimated), the rates (are the unit-costs agreed with the customer's finance), the recoverable share (how much of the theoretical leak is realistically recoverable), overlap (are two findings double-counting the same hours), and the owner (is a real person accountable). Then track each high-value finding through baseline, action, measurement and verification. The adoption outcome is a living leakage ledger with owners and verified recoveries - not a one-time sizing exercise that ages on a slide.
Measurable value
Value here is literally the quantified, verified recovery - this is the app whose output is money. Measures to agree and baseline:
- Verified recovery with evidence - recoveries confirmed against evidence and reaching Verified status, labelled as capacity or cash. This is the headline that must stay honest.
- Owner coverage - the share of high-value findings with a named, accountable owner (an un-owned leak is not a plan).
- Time to verification - how long a finding takes from Open to Verified.
- Unresolved high-value findings - the biggest leaks still sitting Open.
The formula makes the value defensible: because every finding is discounted by confidence and findings are checked for overlap, the aggregate is a number the customer can take to finance. State value as 'a defensible, owned, verified recovery ledger' - and never let the capacity line and the cash line be summed into a single impressive total, because that is exactly the inflation the app exists to prevent.
Objections and honest limits
'These leakage numbers are made up.' This app is the answer to that cynicism, not an example of it. The confidence multiplier discounts uncertain findings, overlap checks prevent double-counting, and recovery is tracked to a Verified status with evidence. Walk a sceptical buyer through one finding's inputs and the capacity-vs-cash separation - the honesty is the pitch.
'So this tells us the cash we'll save?' Not directly. It sizes recoverable value with a confidence discount and tracks what was actually recovered, keeping capacity and cash separate. Freed capacity only becomes cash if the customer redeploys or removes it - that is their decision, and the app is deliberately careful not to claim it for them.
Honest limit - the interpretation check: the recovery screen explicitly distinguishes recovered capacity from cash recovered, and overlapping findings cannot simply be summed. The numbers depend entirely on the time basis, agreed rates and recoverable-share assumptions - confirm these and the detection methods with product and the customer's finance before any figure is quoted externally.
Interpretation check
The recovery screen explicitly distinguishes recovered capacity from cash recovered - they are never summed. And overlapping findings cannot simply be added together. Freed capacity is not cash until the customer acts on it; presenting a blended 'total savings' is the exact inflation the app exists to prevent.
In the field
KnackGlobal (RCM, ~6,000 seats): a small per-claim or per-hour leak multiplied across thousands of seats is a very large, fundable number - but only a confidence-discounted, owner-attributed, capacity-vs-cash-separated ledger turns it into a business case finance will back, which is exactly what is needed to defend the account against the incumbent on hard ROI rather than claims.
Practical task
On the demo, pick one finding from Top value leaks and produce a one-page recovery case: the finding, its value broken into quantity x unit-cost x confidence, the named owner, its current recovery status, and - as two clearly separate lines - the recoverable capacity versus any cash recovered. Then list the five input validations (time basis, rates, recoverable share, overlap, owner) you would run before taking the number to a customer's finance team.
Self-check
Write out the value formula and explain what each term protects against.
Value = quantity x unit-cost x confidence. Quantity is the measured volume of the leak; unit-cost is the agreed money per unit; confidence is a discount for certainty. The confidence factor is what stops a directional finding being counted as if it were proven - it keeps the number defensible.
A leader adds the 'capacity freed' line and the 'cash recovered' line into one total to show the board. Why do you stop them?
Because capacity and cash are different things and the app keeps them separate on purpose. Freed capacity only becomes cash if the customer redeploys or removes it. Summing them inflates the result and destroys the credibility the confidence-discounted model was built to protect.
Two findings each claim savings from reducing the same idle hours. What is the risk and where is it handled?
Double-counting - overlapping findings summed would overstate recovery. The CSM validates overlap before trusting the aggregate; findings that share the same underlying hours cannot simply be added.
Before trusting any leak number for a customer, what five inputs does a CSM validate?
Time basis (measured vs estimated quantity), rates (unit-costs agreed with finance), recoverable share (how much is realistically recoverable), overlap (double-counting), and owner (a real accountable person). The number is only as honest as these.
Why is Value Leakage the natural money layer on top of the other apps?
The other apps find problems - friction, idle capacity, quality gaps, denials; Value Leakage puts a confidence-discounted money value on them, attributes an owner, and tracks verified recovery. It converts findings into a defensible, owned financial ledger.
Verified vs demo. The category model (capacity/process/system/quality/AI/outcome), workflow detection, Top value leaks ranking, attribution, the quantity x unit-cost x confidence model, and the recovery view with the capacity-vs-cash separation are demo-shown on seeded data with illustrative magnitudes (for example Capacity ~78 lakh, Process ~1.12 crore). Real rate sources, detection methods, recoverable-share assumptions and verification evidence are customer-specific - confirm with product and the customer's finance.