# Product demo review checklist

## Before the meeting

- [ ] The meeting has one buyer-relevant job, not a tour of every feature.
- [ ] Every customer-specific statement has a dated source and evidence status.
- [ ] Assumptions are written as questions, not declarations.
- [ ] The product version, account, permissions, and integrations were rehearsed.
- [ ] Demo data is synthetic, sanitized, or explicitly approved.
- [ ] No production secret, other customer's data, or private note can appear.
- [ ] Every claimed result is visible in the product or supporting record.
- [ ] Known limitations have plain-language wording.
- [ ] A screenshot, recording, or alternate environment exists for likely failures.
- [ ] The next-step question names an owner and a date without inventing urgency.

## During the meeting

- [ ] Reconfirm the starting condition before opening the product flow.
- [ ] Stop when the buyer corrects the premise.
- [ ] Show one complete job before optional features.
- [ ] Distinguish current behavior from roadmap work.
- [ ] Say “I do not know” when evidence is missing and assign an owner to follow up.
- [ ] Record the buyer's wording instead of asking an LLM to infer sentiment live.

## After the meeting

- [ ] Separate confirmed facts, corrections, open questions, and assumptions.
- [ ] Send only the material promised in the call.
- [ ] Verify every answer before it enters CRM or a follow-up email.
- [ ] Record environment failures without blaming the buyer or hiding the limitation.
- [ ] Move feature requests to the product process; do not promise them in the recap.
- [ ] Keep a versioned run sheet when the demo becomes a repeatable team asset.