Value Leakage concepts - the mental model and the words that make the number honest
Objective. Give Sales and CSM the mental model Value Leakage is built on and the key terms, so they can explain the app precisely and defend its numbers. The core idea: a leak is a quantified, confidence-discounted, owned loss tracked from Open to Verified, with capacity and cash kept separate.
Value Leakage turns 'we are leaking value' into a defensible, owned, trackable number. Its mental model is a chain: observed work is detected as a candidate leak, sized as quantity x unit-cost x confidence, routed to one of six categories, ranked, attributed to an owner, and tracked through states to Verified recovery - with recovered capacity and cash recovered never summed. This module defines the terms plainly and shows how they chain, so the formula and the capacity-vs-cash rule become second nature.
See it in the demo
The core concept the app is built on
The core concept is the honest ledger of lost value. Every other app finds a problem; Value Leakage puts a defensible money number on it, says who can act, and tracks whether it was actually recovered. What makes it a ledger rather than a slide is discipline in three places: findings are sized with a confidence discount so soft findings are marked down rather than hidden; findings are owned so a leak is a plan and not a statistic; and recovery is tracked to a Verified state with evidence, with recovered capacity and cash recovered kept as separate lines that are never summed.
The mental shift to teach: the value of this app is not a big number, it is a defensible number. A theoretical maximum impresses no one in finance; a confidence-discounted, owner-attributed, overlap-checked figure labelled capacity or cash is something a CFO can fund. The app is deliberately built to resist its own inflation.
Key terms defined plainly
- Leak / finding - a specific, sized instance of lost value surfaced from observed work (idle hours, a process wait, a quality rework loop, an unbilled outcome).
- Quantity - the measured volume of the leak: hours, touches, units. The term that should be measured, not guessed.
- Unit-cost - the agreed money per unit: a loaded hourly rate, a cost per claim. Agreed with the customer's finance, not assumed by the app.
- Confidence - a discount between a directional guess and a well-evidenced fact. The term that stops the number inflating.
- Value - quantity x unit-cost x confidence. The sized, defensible figure for a finding.
- The six categories - capacity, process, system, quality, AI and outcome: the buckets every finding is routed into.
- Recoverable share - how much of a theoretical leak is realistically recoverable, as opposed to the theoretical maximum.
- Attribution / owner - the named, accountable person who can act on a finding.
- Recovery states - the lifecycle from Open (sized, not acted on) through action and measurement to Verified (recovery confirmed with evidence).
- Recovered capacity vs cash recovered - two separate recovery lines: hours or FTE freed versus money actually collected. Never summed.
- Overlap - two findings describing the same underlying hours, which must not be double-counted.
How the concepts chain together
The concepts form one pipeline, and understanding the chain is understanding the app:
Observed work -> Workflow detection surfaces a candidate leak. -> Sizing applies value = quantity x unit-cost x confidence, so the candidate gets a defensible figure. -> Category routes it to one of the six buckets. -> Top value leaks ranks it among all findings by confidence-discounted value, so effort follows value. -> Attribution gives it a named owner, turning the number into assignable work. -> Recovery tracks it from Open to Verified with evidence, reading recovered capacity and cash recovered as separate lines.
Each link constrains the next: a candidate with no agreed rate cannot be sized honestly; a finding with no owner cannot recover; an Open finding is not a recovered one. The chain is why a single screen's number is never the whole story - you read a finding along the chain, not in isolation.
The one concept people most often get wrong
The single most-misunderstood concept is the capacity-vs-cash separation, and it is deliberately the hardest discipline in the app. People want one impressive total, so they add recovered capacity to cash recovered. That is wrong because freed capacity is hours or FTE, not money - it only becomes cash if the customer redeploys or removes that capacity, which is their decision, not the app's claim. The app keeps the two on separate lines on purpose, and summing them is exactly the inflation the whole confidence-discounted model exists to prevent.
A close second is confusing a sized or detected finding with a recovered one. Detection produces a candidate; Open is a sized opportunity; only Verified-with-evidence is recovered. If you can hold two ideas firmly - capacity is not cash, and sized is not recovered - you have the honest core of the app.
Interpretation check
A leak is a quantified, confidence-discounted, owned loss tracked from Open to Verified. Value = quantity x unit-cost x confidence; there are six categories; and recovered capacity and cash recovered are separate lines that are never summed. Sized or detected is not recovered.
In the field
KnackGlobal (RCM, ~6,000 seats): the concept that wins the account is 'defensible, not big' - a small per-claim or per-hour leak multiplied across thousands of seats is a large number only when it is confidence-discounted, owner-attributed and kept as separate capacity and cash lines that finance will back.
Practical task
Write a 90-second plain-English explanation of Value Leakage for an operations leader that uses, in order: leak, the value formula, the six categories, owner, and the capacity-vs-cash separation. Then pick one demo finding and label it with every term in the chain - quantity, unit-cost, confidence, category, owner, recovery state, and whether it is capacity or cash.
Self-check
Define value in Value Leakage terms and say what each factor protects against.
Value = quantity x unit-cost x confidence. Quantity is the measured volume (guards against guessing), unit-cost is the finance-agreed money per unit (guards against made-up rates), and confidence is the certainty discount (guards against counting a directional finding as proven). Together they make the number defensible.
Name the six categories and what kind of loss each buckets.
Capacity (idle or under-used available time), process (friction and waiting in how work flows), system (waits or losses caused by tools/systems), quality (rework and quality failures), AI (missed automation or AI opportunity), and outcome (lost business outcomes such as denials or unbilled value).
Walk the concept chain from observed work to verified recovery.
Observed work is detected as a candidate, sized by quantity x unit-cost x confidence, routed to one of six categories, ranked in Top value leaks, attributed to a named owner, and tracked on Recovery from Open to Verified with evidence - reading capacity and cash as separate lines.
What is the one concept people most often get wrong, and why is it wrong?
The capacity-vs-cash separation: people sum freed capacity and cash recovered into one total. It is wrong because freed capacity is hours, not money - it becomes cash only if the customer redeploys or removes it. Summing them is the inflation the whole model exists to prevent.
Distinguish recoverable share from value and from verified recovery.
Value is the sized figure (quantity x unit-cost x confidence). Recoverable share is how much of that theoretical leak is realistically recoverable. Verified recovery is what evidence confirms was actually recovered. Theoretical leak, recoverable value and verified recovery are three different numbers.
Verified vs demo. The six-category model, the value formula, the ranking, attribution and the recovery states with the capacity-vs-cash separation are demo-shown on seeded data with illustrative magnitudes (for example Capacity ~78 lakh, Process ~1.12 crore). The real rates, recoverable-share assumptions, detection method and verification evidence are customer-specific - confirm with product and the customer's finance.