Customer simulation and certification
Objective. Run a full cycle end to end - discovery, workflow selection, demonstration, objection handling and agreeing a next step - and produce the supporting discovery, pilot and handover artifacts.
The capstone that certifies a new AE is call-ready. You run a realistic customer simulation that chains every prior lesson - problem-led discovery (S02), fit and scope (S03), an evidence-led demo (S04), honest objection handling (S07), a pilot proposal (S08) and a clean handover (S09) - and you are scored against the certification gate: practical score >=80, no critical error, manager review.
See it in the demo
The customer problem (what this simulates)
A new AE can pass each skill in isolation and still fail a real call, because the real call demands them in sequence under pressure: you discover, and what you hear must change which workflow you demo; you demo, and the objection that comes back must be handled without abandoning the value or over-claiming; you propose a pilot whose scope must match what discovery actually surfaced; and you agree a next step that is real, not a polite 'we will circulate internally'. Business impact of getting the chain wrong: a technically competent AE who demos the wrong thing, over-promises under one objection, or lets the call end without an owned next step - which is most lost deals. This simulation exists to catch those failure modes before they cost a live account.
How the simulation runs
You are given a seeded customer (operations leader or revenue-cycle executive, a staffing or output problem). The flow, timed: DISCOVERY (fill the six-slot frame from S02 - current process, cost, evidence, owner, urgency, constraints - with real questions, not a checklist recited). FIT AND SCOPE (classify the problem - time-visibility, output, process or planning - per S03, and name the smallest useful starting scope, or a no-fit if warranted). DEMONSTRATE (a focused evidence-led story per S04: business question -> right screen -> evidence -> interpretation with two drill-downs -> one explicit limitation, using the correct demo URL for the problem class). OBJECTIONS (handle at least two of the five from S07 with acknowledge -> reframe -> condition, no universal promises). PILOT (propose scope, baseline and a testable hypothesis per S08, keeping capacity separate from cash). NEXT STEP (agree a specific, owned, dated advance). Then produce the artifacts: discovery notes, a one-page pilot charter, and a seven-field handover.
What to say / do - the critical-error list
Certification is pass/fail on critical errors regardless of style. A CRITICAL ERROR is any of: inventing a metric or customer result; asserting a packaging, integration or security fact that should have been escalated to a specialist; demoing the wrong application for the discovered problem; making a universal promise under an objection ('we always deliver X%'); blending freed capacity and cash into one ROI number; selling monitoring-for-monitoring's-sake or dismissing a works-council/comms concern; or ending the call with no owned, dated next step. Avoid these and you clear the gate's 'no critical error' bar. To score well above 80: tailor the narrative to the buyer (S01), let discovery genuinely redirect the demo, state the explicit limitation out loud without being prompted, handle the ROI objection with a baseline-owned method rather than a number, and produce artifacts clean enough that a CSM could act on the handover with no clarifying questions.
Self-assessment before you submit
Score yourself against the rubric before the manager review, because a reviewer-surprise is itself a signal you are not yet calibrated. Discovery: are all six slots filled from what the customer actually said, with unknowns written as follow-ups not guesses? Fit: did you scope to the smallest useful start and could you have called a no-fit if needed? Demo: did the business question drive the screen choice, were there two real drill-downs (one proving the number, one driving action), and did you name a limitation? Objections: condition not promise, every time? Pilot: customer-owned baseline, falsifiable hypothesis, capacity and cash separate? Handover: seven fields, no open-unscoped promise? Next step: specific, owned, dated? If any answer is weak, fix it before submitting. The certification is not a hoop - it is the rehearsal that makes your first ten real calls safe for the pipeline and the brand.
Objections and honest limits
'The simulation is artificial, real customers are messier.' - True, and that is why the gate scores judgement (did you escalate, did you avoid the critical errors) over polish; messiness is handled by the escalation discipline, not by knowing every answer. 'Can I just show I know the product?' - No - product knowledge without the value-led chain is exactly the generic feature-tour this curriculum exists to prevent; you are certified on customer value and honest judgement, not feature recall. Honest limits: passing certifies you are safe to run real calls with support, not that you are a closer; it does not replace manager review on live deals, specialist involvement on packaging/integration/security, or the real customer's own baseline for any value claim. A pass means your judgement under the chain is sound - the market is where mastery is earned.
Interpretation check
Certification scores judgement over polish. A fluent demo with a critical error (invented metric, bluffed security answer, blended capacity-and-cash, no next step) fails; a less slick call that escalates honestly, avoids the critical errors and ends on an owned next step passes. You are certified on customer value and honest judgement, not feature recall.
In the field
A KnackGlobal-style simulation is the sternest test: revenue-cycle executive, output/cost problem, active incumbent displacement, hard objections on existing tooling and soft ROI, and pointed integration/security questions - passing it means tailoring the narrative, demoing Work Output/Value Leakage to the discovered problem, answering ROI with a baseline-owned pilot number (capacity separate from cash), escalating integration/security cleanly, and leaving with an owned next step.
Practical task
Run and record a full customer simulation - discovery, workflow selection, evidence-led demonstration, at least two objections, a pilot proposal and an agreed owned next step - and submit it with the three artifacts (discovery notes, one-page pilot charter, seven-field handover). Target the certification gate: practical score >=80, no critical error, manager review.
Self-check
List four critical errors that fail the certification regardless of style.
Any four: inventing a metric/result; asserting a packaging/integration/security fact that needed escalation; demoing the wrong application for the discovered problem; a universal promise under an objection; blending capacity and cash into one ROI number; selling surveillance or dismissing a comms/works-council concern; ending with no owned, dated next step.
How should discovery affect the demo in the simulation?
What you hear in discovery must redirect which workflow/application you demo. Running a pre-planned demo regardless of discovery is a scored failure - the demo must answer the problem class you actually found.
What makes a 'next step' acceptable at the end of the call?
It is specific, owned by named people on both sides, and dated. 'We will circulate internally' is not an owned next step and counts against you.
Why does passing NOT mean you no longer need specialists or manager review?
A pass certifies sound judgement under the chain and that you escalate correctly - it does not replace specialist answers on packaging/integration/security, manager review on live deals, or the customer's own baseline for any value claim.
What are the three artifacts you must produce alongside the recorded simulation?
Discovery notes (six slots), a one-page pilot charter (baseline, testable hypothesis, scope, success criteria, capacity vs cash), and a seven-field sales-to-CSM handover with no open-unscoped promise.
Verified vs demo. The demo screens and the value chain are demo-shown; everything that would be a customer fact - metrics, packaging, integration, security, baseline - must be handled in the simulation exactly as in a real call (approved fact or named escalation), and inventing any of them is a critical error.