2 min lesson
Demo & presentation rep
Rebuild the sequence in "Demo & presentation rep" from memory, ending with the check that proves the outcome.
Step 1 of 3
Same product, two completely different rooms. The principals want to see real engineering survive their standards. The CTO wants to see a strategic bet pay off. A single demo that tries to serve both serves neither.
Tailoring is the whole grade here. You earned the right to demo specific things in discovery, so demo those. Northwind's payments cycle time and the principals' merge conditions are your script, not a generic feature tour.
Learn more
Full explanation
Stage two versions of the repo
Field SAs keep two copies of the same demo scenario. One is behind the curtain: it carries a demo narrative in Markdown - the natural-language beats (here's what we're looking at, here's what we're going to do) plus the exact prompts you plan to run. The other is a cleaned-up repo with the narrative and prompt references stripped out, and that's the one you actually share on screen. You paste the prompts in live so it never reads like you're reciting them from inside the repo. Have the agent build the demo narrative for you as part of your first prompt - it drafts the script while you stage the scenario.
“I'll have one that's behind the curtain. It'll have a demo narrative. It'll have the prompts that I want to run. And then I'll actually share my screen showing a kind of cleaned up version.”