prepare-demolisted

# Prepare Demo Design a demo as a collaborative test of the buyer's desired outcome. Show less, prove more. ## Inputs Read `.agents/gtm-context.md`, account research, discovery notes, qualification, attendee details, and known technical constraints. Ask for the product's real capabilities when documentation is missing. ## Workflow 1. Define the decision or learning the demo should enable. 2. List the buyer outcomes and evidence captured in discovery. 3. Map each outcome to the smallest product moment that can demonstrate it. 4. Remove features that do not support the decision. 5. Build a believable scenario with safe, fictional, or approved data. 6. Plan checkpoints that invite the buyer to compare the demo with their real workflow. 7. Assign presenter roles, timing, transitions, and recovery paths. 8. Test the environment, permissions, data, integrations, and fallback material. Before presenting, require the authorized product owner to approve every capability, availability, roadmap, and limitation claim; require the authorized source-data owner to approve any non-fictional dataset, with privacy, security, legal, and customer-permission review as applicable. Generic internal approval does not substitute for either authority. 9. Define the next-step criteria before presenting. Use [the demo plan template](assets/demo-plan.md). ## Guardrails - Never present a mock, roadmap item, manual workaround, or unsupported integration as generally available functionality. - Label