Tell an evidence-led demo story
Objective. Run a demo that moves from a business question to the relevant screen, to evidence, to interpretation, to a next step - with two drill-downs and one explicit limitation.
Teaches the demo structure that wins technical and executive trust: start from the customer's question, land on one screen, show the evidence, interpret it honestly (including what it does NOT prove), and end on a decision. You will build and deliver a seven-minute demo that proves you understand value, not that you memorised a feature tour.
See it in the demo
The customer problem
The default demo is a tour: twenty screens, every feature, no question answered. Business impact: the buyer cannot connect any of it to their problem, the champion cannot re-tell it internally, and 'looks powerful' becomes 'no decision'. Revenue-cycle and operations buyers have seen slick dashboards before and been burned by numbers that did not hold up; a tour reads as 'another pretty tool'. What they actually need is to watch you answer one of their real questions with evidence on screen, and then watch you say what the evidence does and does not mean. The demo that wins is short, specific, and honest about its own limits - because honesty about a limitation is the strongest signal that the numbers you DO show are real.
The evidence-led structure
Five beats, every time: (1) BUSINESS QUESTION - state the customer's own question in their words ('you asked: are my busy claim teams actually clearing the expected work?'). (2) RELEVANT SCREEN - go straight to the one screen that answers it, not the home page (for an output question, https://work-output.demo.timechamp.io/#/overview then Transactions). (3) EVIDENCE - point at the specific data: the completed-work count, the complexity mix, the cost per clean unit, the quality standard. (4) INTERPRETATION - say what it means AND what it does not; this is where you drill down twice. (5) NEXT STEP - 'if this were your data, the next action would be X, owned by Y' - end on a decision, not a feature. Keep it to seven minutes for one question. The two drill-downs should answer the obvious follow-up ('why?') - e.g. from a low output number drill into complexity, then into a process step in Work Understanding (https://work-understanding.demo.timechamp.io/#/explorer).
What to say / do - the two drill-downs and the explicit limitation
Drill-down discipline: the first drill-down answers 'is this real or an artifact?' (e.g. from a utilization dip, show the denominator - what counts as available time - so they trust the number). The second answers 'so what do we do?' (e.g. from an output gap, drill into whether it is volume, complexity, quality or a stuck step). The explicit limitation is mandatory and you choose it deliberately per application: for Work Output, 'I am comparing these two teams, but I would only trust this comparison after aligning work type, complexity, period, tenure and quality - raw team-vs-team is misleading'. For Employee Monitoring, 'this application-activity label says non-productive, but that is not proof the person did no useful work - we use it as a prompt to investigate, not a verdict'. For Intraday Management, 'this is a simulated fix, not an executed action or an achieved service result'. For Value Leakage, 'this screen separates recovered capacity from recovered cash on purpose - do not add them'. Stating the limitation out loud is what makes the rest credible.
Choosing the screen per problem class
Match the screen to the question so you never wander: time-visibility question -> Time and Activity daily operations and attendance (https://time-activity.demo.timechamp.io/#/daily, /#/attendance), drill the utilization denominator. Output question -> Work Output Overview then Transactions and People (https://work-output.demo.timechamp.io/#/transactions, /#/people), drill complexity then quality/cost. Process question -> Work Understanding explorer then a friction finding, drill observed contribution vs proven cause. Planning question -> Real-Time Adherence control room (https://rta.demo.timechamp.io/#/control) showing schedule vs work vs output adherence, or Intraday Management control tower (https://idm.demo.timechamp.io/#/tower) showing the projected shortage and a simulated fix. Revenue-cycle executive -> RCM Operations Mission Control (https://rcm-ops.demo.timechamp.io/#/mission), move from a briefing signal to evidence to a proposed action with an outcome hypothesis. Prepare the exact click path before the call; never search for a screen live.
Objections and honest limits
'Can it do <feature>?' mid-demo - acknowledge, park it ('yes/confirm with product - let me finish answering your question first, then I will come back'), and protect the narrative; a demo derailed into feature ping-pong loses the thread. 'These are demo numbers.' - Agree plainly: 'they are - this is our demo lab, so treat the numbers as illustrative; the structure and the screens are real, and in a pilot these become your data.' Never pass demo figures off as a customer result. Honest limit of the demo itself: it proves the platform can answer the question and show evidence; it does NOT prove the magnitude of value for this customer - that requires their baseline (S08). End by naming that explicitly so you set up the pilot rather than over-promising. If any screen touches integration, security or packaging specifics, flag it to a specialist rather than asserting.
Interpretation check
A demo proves the platform can answer a question with evidence; it does not prove the size of the value for this customer. The explicit limitation is not a weakness to hide - naming what the evidence does not prove is what makes what it does prove believable.
In the field
KnackGlobal demo: question = 'are claim teams clearing expected work at a defensible cost per claim?'; land on Work Output Transactions and cost-per-clean-unit; drill-down 1 confirms the clean-unit definition and denominator, drill-down 2 splits the gap into complexity vs quality; explicit limitation = 'do not compare these two claim teams until we align complexity and tenure' - which is exactly the rigor that beats an incumbent's headline dashboard.
Practical task
Build and record a seven-minute evidence-led demo for one customer question: show the business question, go straight to the right screen, present the evidence, include two drill-downs (one proving the number is real, one driving to an action), and state one explicit limitation out loud. End on a concrete next step with an owner.
Self-check
What are the five beats of the evidence-led structure?
Business question, relevant screen, evidence, interpretation (what it means and does not), next step/decision.
What should the two drill-downs answer, respectively?
The first: 'is this real or a measurement artifact?' (e.g. show the denominator). The second: 'so what do we do?' (e.g. is the output gap volume, complexity, quality or a stuck step).
Give the mandatory explicit limitation for a Work Output team comparison.
You only trust a team-vs-team comparison after aligning work type, complexity, period, tenure and quality; raw comparison is misleading.
A prospect interrupts to ask if the product supports a specific feature. What is the disciplined move?
Acknowledge, park it (confirm with product if unsure), finish answering the current question to protect the narrative, then return to the parked item.
Why end on a next step rather than a final screen?
Executives buy decisions, not features. Ending on 'the next action would be X, owned by Y' makes the demo retellable internally and sets up the pilot.
Verified vs demo. The screens, drill paths and the interpretation limits are demo-shown and real; the numbers in the demo lab are illustrative, not customer results, and the magnitude of value for any customer must come from their own baseline in a pilot.