Customer simulation and certification
Objective. In one end-to-end simulation, diagnose an account, train a user, present value and qualify a next step - producing reviewed training, success plan, adoption diagnosis and QBR artifacts that meet the certification gate.
This is the capstone: a single simulated account run start to finish, assembling the skills from C01-C11 into the artifacts a real CSM produces in their first quarter. It certifies that you can not only explain the method but run it under observation, with the honesty disciplines intact - because the certification gate is practical score 80 or above, no critical error, and manager review.
See it in the demo
What this simulation proves
A CSM who can discuss each lesson separately may still fall apart when an account needs diagnosis, training, a value story and an expansion decision in sequence, under the pressure of a sponsor who pushes back. This simulation proves you can run the whole arc coherently: that your success plan (C01) and your QBR (C08) use the same baseline; that your adoption diagnosis (C07) names a specific layer; that your training (C04) produces a user who can perform; and that at no point do you cross an honesty line - inventing a metric, conflating capacity with cash, promising unconfirmed roadmap, or escalating to nobody. The certification is not a quiz; it is evidence that you can be trusted with a real account this quarter without a senior CSM re-doing your work.
The simulation structure
Run a chosen account - KnackGlobal (RCM) or OVO (contact-centre) - through four acts. Act 1, diagnose (C01, C02): take the contracted scope, state the sponsor's outcome in their words, establish or flag the baseline, run the readiness checklist, and produce a mutual success plan with a measurable milestone and a named dependency. Act 2, train (C04): deliver a 20-minute manager session on one routine with a performed learner task and a check-understanding question that surfaces an interpretation trap. Act 3, present value (C05, C06, C08): run a short QBR against the baseline with confounders named and capacity kept separate from cash, and show the operating routine and action log feeding it; handle one disputed-metric challenge with the investigation order, not a defence. Act 4, qualify a next step (C09, C10, C11): qualify an expansion or a renewal action against the five tests, log any risk with a named owner, and state what you would hand to sales. Use the demo apps throughout so every act rests on real screens.
What to say / do - the assessment artifacts
Produce and submit four artifacts for manager review. (1) Success plan: outcome, baseline, one measurable milestone with a date, named dependency and owner, three-role stakeholder map. (2) Training package: the 20-minute session plan, the learner task, facilitator notes with the interpretation trap and model answers. (3) Adoption diagnosis: the five-layer assessment for the key capabilities, the first-broken layer per capability, and matched interventions. (4) QBR: the validated value story against baseline, confounders named, capacity vs cash separated, honest gaps, next-quarter plan. Each must be specific to the chosen account and internally consistent - the QBR's baseline must be the success plan's baseline, the adoption diagnosis must explain any thin outcome. Inconsistency across artifacts is itself a finding; a real account will expose it.
The certification gate and critical errors
The gate is a practical score of 80 or above, no critical error, and manager review. A critical error is an honesty or safety failure, and any one of them fails the simulation regardless of polish: inventing a metric or customer result; conflating recovered capacity with cash recovered; presenting an unvalidated number as fact in the QBR; promising roadmap or entitlement you did not confirm with product; escalating a risk to no named owner; or crossing the specialist boundary by attempting setup beyond CSM literacy. These are exactly the mistakes that lose real accounts, so they are disqualifying. The reviewer also checks the softer bar: are the discovery questions and talk tracks specific to the account and the data, or generic enough that any SaaS CSM could have written them? Generic is a fail on the quality bar even if nothing is factually wrong.
Objections and honest limits
During the simulation the reviewer will push: 'make the QBR number bigger', 'just promise them the feature', 'skip the baseline, we are short on time', 'win the metric argument'. Each is a planted critical-error trap, and the correct move is the disciplined one from the relevant lesson - claim less and prove it, confirm with product, establish baseline as milestone zero, agree the definition rather than win. Honest limits of the certification itself: it proves you can run the method on a simulated account with demo data; a real account adds live data quality, real stakeholders and real commercial stakes, so your first real accounts still get senior review. The certification is a licence to drive, not a claim that you no longer need a map. Where the simulation surfaces something you genuinely do not know, the certifiable answer is 'I would confirm with product', not a confident guess.
Interpretation check
Certification is about coherence and honesty across the whole account arc, not polish on any one act. A single critical error - an invented metric, capacity sold as cash, an ownerless escalation - fails the simulation no matter how good the rest looks.
In the field
A KnackGlobal run is the sternest test: diagnose the output/FTE and cost-per-claim outcome, train an RCM lead to read it, present a baseline-anchored QBR that survives a ProHance-style challenge, and qualify either a renewal defence or an expansion - all without a single critical honesty error, because the real account would not forgive one.
Practical task
Run one account (KnackGlobal or OVO) through all four acts and submit the four artifacts - success plan, training package, adoption diagnosis, QBR - plus a qualified next-step brief and any risk/escalation record. Artifacts must be internally consistent (shared baseline), account-specific, and free of the listed critical errors. Submit for manager review against the gate (score >=80, no critical error).
Self-check
Name three critical errors that fail the simulation outright.
Any of: inventing a metric or customer result; conflating recovered capacity with cash recovered; presenting an unvalidated number as fact; promising unconfirmed roadmap/entitlement; escalating to no named owner; or attempting setup beyond CSM literacy. Each is an honesty or safety failure that loses real accounts.
Why must the QBR's baseline be the same baseline as the success plan's?
Internal consistency is scored. If the QBR measures against a different baseline than the one the success plan established, the value story is not credible and the inconsistency is itself a finding - a real account would expose it immediately.
The reviewer says 'skip the baseline, we're short on time'. What is the certifiable response?
Refuse the shortcut - establish the baseline as milestone zero, because without it no later value claim is defensible. The prompt is a planted critical-error trap; taking it would undermine the entire value arc.
Your discovery questions could have been written by any SaaS CSM. Why does that fail even if nothing is wrong factually?
The quality bar requires specificity to the account and the Time Champ data. Generic material is exactly what the curriculum was built to prevent - it signals the CSM does not actually understand the customer's value, only the method's shape.
Verified vs demo. Everything rests on demo data and demo screens. The simulation certifies method and honesty, not production-account readiness; real accounts add live data quality and commercial stakes, so first real accounts still get senior review, and any uncertain production fact is answered 'confirm with product'.