# Buyer-specific product demo run sheet

Copy this file for one meeting. Delete prompts that do not apply.

## 1. Meeting contract

- Buyer organization:
- Date and time:
- Attendees and roles:
- Decision or next step this meeting can support:
- What this demo will not cover:
- Demo owner:
- Note taker:

## 2. Evidence ledger

Record the source behind every buyer-specific claim. Use `observed`, `buyer-stated`,
`inferred`, or `unknown` in the Status column.

| Claim or constraint | Source and date | Status | Safe wording in the demo |
| --- | --- | --- | --- |
|  |  |  |  |
|  |  |  |  |
|  |  |  |  |

Do not present `inferred` or `unknown` rows as facts. Turn them into questions.

## 3. Product state

- Product version or release:
- Demo environment:
- Account and permissions:
- Dataset: synthetic, sanitized, or buyer-approved:
- Integrations available:
- Known limitations relevant to this buyer:
- Data that must not appear on screen:

## 4. One narrative

- Starting condition confirmed by the buyer:
- One job to complete:
- Product actions to show:
- Observable end state:
- Evidence the buyer can inspect:
- Assumption that still needs confirmation:

## 5. Live sequence

Times are editable agenda placeholders, not performance benchmarks.

| Segment | Screen or action | Claim supported by evidence | Question to ask | Fallback |
| --- | --- | --- | --- | --- |
| Reconfirm context |  |  |  |  |
| Show starting state |  |  |  |  |
| Complete the job |  |  |  |  |
| Inspect the result |  |  |  |  |
| Discuss limits |  |  |  |  |
| Agree next step |  |  |  |  |

## 6. Stop rules

Pause the script and ask a question when:

- the buyer corrects the starting condition;
- a required permission or integration is absent;
- the demo environment differs from the promised version;
- an outcome would require an unverified ROI, timing, or adoption claim;
- a screen exposes data that was not approved for the meeting.

## 7. Close the meeting

- What the buyer confirmed:
- What the buyer corrected:
- Open technical or commercial questions:
- Owner and date for each answer:
- Agreed next step, owner, and date:
- Evidence to send after the meeting:

## 8. Post-demo record

- Did the environment behave as rehearsed?
- Which claim lacked enough evidence?
- Which question changed the narrative?
- What should be removed before the next demo?
- What belongs in the product backlog rather than the sales script?