Time to outcome and value
Objective. Explain how Time Champ value is actually realised - the chain from activity to a verified business result - and keep capacity value and cash value separate so every business case you build or defend survives a CFO's scrutiny.
This is the honesty engine of the whole programme. It teaches the difference between capacity released and cash recovered, why a finding is not yet a result, and how to express value as a testable hypothesis the customer owns rather than a vendor promise.
See it in the demo
The customer problem
Customers have been burned by value stories that did not materialise. A tool shows '2,000 hours of potential savings' and twelve months later nobody can point to a line in the budget that moved. The reason is almost always that the vendor collapsed two different things into one number: the capacity that could be released if an opportunity were acted on, and the cash that actually changed hands. They are not the same, and treating them as the same destroys trust - usually at the first business review, which is exactly when you need the customer to believe you. The business impact is stark: inflated expectations at sale, a credibility collapse at the QBR, and a renewal conversation poisoned by a number that was never real. The discipline of separating capacity from cash, and finding from result, is not caution for its own sake - it is what lets value compound across a renewal rather than evaporate.
How value is realised - the chain
Value in Time Champ moves along a chain, and each link can break:
- Signal - a metric or finding surfaces (an exception, a friction point, a leakage finding).
- Evidence - the signal is validated: right denominator, scope, source, freshness (F06).
- Owner and action - someone who can act takes a specific action.
- Capacity value - time or capacity is released (e.g. hours no longer lost to rework). This is real but it is a potential - it does not become money until it is redeployed or removed.
- Cash value - the released capacity is actually converted: headcount avoided, overtime cut, more work done with the same team, a denial recovered. This is what finance recognises.
- Verification - the result is measured against a baseline the customer agreed before the change.
Value Leakage makes this explicit: its recovery screen distinguishes recovered capacity from cash recovered, and tracks baseline, action, measurement and verification as separate states. That product behaviour is your model for every value claim.
Capacity value vs cash value
Capacity value answers 'how much time or throughput could we free up?' It is the right number for a pilot hypothesis and for sizing an opportunity. It is honest only if you label it as capacity, not cash.
Cash value answers 'what did finance actually recognise?' It requires a decision to convert the freed capacity - avoid a hire, reduce overtime, absorb more volume, recover a specific denial. Without that decision, capacity value stays theoretical.
The RCM world sharpens this further: recoverable value, billed value, collected cash and capacity value are four distinct things (per RCM Operations' own interpretation rule). Confusing recoverable with collected is the fastest way to lose a revenue-cycle executive's trust.
Practical rule: in any model, show capacity value and cash value in two separate columns, state the conversion assumption between them in the customer's words, and let the customer own that assumption. If they will not commit to the conversion, the cash number is yours, not theirs - and a value story the customer will not sign is not a value story.
What to say / do
Frame value as a hypothesis, not a promise. Talk track: 'Based on what we have seen, there looks to be roughly X of capacity tied up in [rework / idle / over-staffing]. I am not going to tell you that is Y in savings, because that depends on a decision only you can make - whether you redeploy it, avoid a hire, or absorb more volume. What I would propose is a baseline we agree now, a small change we test, and a measurement after. If it converts, we have a number we both trust.'
For sales, this becomes the pilot charter (S08): customer-owned baseline, testable hypothesis, explicit capacity-vs-cash split, success criteria.
For CSM, this becomes the QBR spine (C08): compare suitable baselines, name the confounders, and report capacity and cash as separate lines with verification status. Never present a projected number and a realised number in the same font without labelling which is which.
Measurement and honest limits
Measurement is the point, not the footnote. For any value claim, you should be able to state: the baseline, when it was agreed, the scope and denominator, the action taken, the owner, and whether the result is verified or still projected. Value Leakage's states - open, verified, recovered (capacity vs cash) - are the vocabulary to borrow.
Honest limits: the demo shows the model and the vocabulary for separating capacity from cash. It does not prove a specific savings figure for a specific customer - those come only from a baseline and verification in that customer's data. Overlapping findings cannot simply be summed (Work Understanding's rule): two improvements that both claim the same hour double-count. And a simulated or projected improvement is not an executed action or an achieved result (Intraday's rule). When a customer asks 'what will we save?', the honest answer is a method and a hypothesis, with the cash number owned by them - escalate to a specialist before committing a figure (F09, F10).
Interpretation check
Recovered capacity and recovered cash are different states and the product shows them separately; a finding or a simulation is a hypothesis, not a realised result. Never present capacity value as if it were money finance has recognised.
In the field
KnackGlobal's business case lives on this distinction: output-per-FTE and cost-per-claim describe capacity and unit economics, but the cash story (headcount avoided, denials recovered) is only real once KnackGlobal commits to converting the freed capacity - so the proposal separates the two and lets the customer own the conversion.
Practical task
Take one capacity finding from the Value Leakage demo and write a two-column value statement: capacity value on the left, cash value on the right, with the single conversion assumption named in plain language and a note on who owns it and how it would be verified.
Self-check
A prospect asks 'so what will Time Champ save us?' What is the honest shape of your answer?
A method and a hypothesis, not a guaranteed figure: an estimate of capacity that appears tied up, an explicit statement that converting it to cash is the customer's decision, and a proposal to agree a baseline, test a change and measure the result - with any cash figure owned by the customer.
Why can't you add two Work Understanding friction findings together to size savings?
They may overlap and claim the same released time, so summing them double-counts. Overlapping findings must be reconciled before any savings claim.
In RCM, name the four values that must stay separate and give the trust risk of confusing them.
Recoverable value, billed value, collected cash, capacity value. Presenting recoverable as if it were collected cash inflates the result and destroys a revenue-cycle executive's trust at the first review.
What makes a value number 'the customer's' rather than 'yours', and why does it matter?
The customer owns the baseline and the conversion assumption (e.g. that freed capacity becomes an avoided hire). It matters because a number the customer will not commit to cannot be defended at a QBR or a renewal.
Verified vs demo. The capacity-vs-cash model and the finding/verified/recovered states are shown in the Value Leakage demo; any specific savings figure for a real customer needs their baseline and verification and should not be asserted from the demo.