demo-tailor

---
name: demo-tailor
description: Turns discovery notes into a nine minute demo showing only the three things this buyer said they care about. Use before any demo or product walkthrough.
---

# Show only the three things this buyer cares about

A nine minute run sheet built from what the buyer said, with everything else cut.

## Claude does

1. Ask for the discovery notes, the capabilities you can genuinely show, and the date the buyer said something must work by. No notes, no demo.
2. Pull the business problems from the notes in the buyer's words. Gong's 519,000 call study finds good discovery surfaces three to four. Fewer than three means going back to discovery, not inventing the rest.
3. Rank them by the weight the buyer gave them, not by what demos best.
4. Keep the top three in that order, so if time runs short only the least important is lost. The rest goes to a written parking lot. Showing what never came up risks buying it back later.
5. Write a Situation Slide quoting the notes: overarching goal, current situation, pain and problems, capabilities sought, value desired, required timeline. Two minutes maximum, and no corporate overview, product intro, architecture or logo slide.
6. Open each topic on the finished result the buyer wants, then work backwards to the clicks.
7. Budget nine minutes for the main demo, no uninterrupted talking beyond 76 seconds, and a dated next steps block.
8. Refuse to guess named customers, ROI figures, savings percentages or integrations. Ask, or leave it out.

## Then Codex does

Codex expands the three approved topics into the run sheet: click paths, timing table, 76 second segment splits, parking lot and question prompts. Repetitive formatting across three near identical blocks, every judgement already made above.

```
codex exec --sandbox danger-full-access --skip-git-repo-check -C "<working folder>" - < CODEX.md
```

Fill in first: {SITUATION_SLIDE}, {TOP_THREE_TOPICS} (ranked, buyer's wording), {PRODUCT_STEPS} (clicks per topic), {CRITICAL_DATE}.

## Claude checks

1. Every topic traces to a line in the notes. One that does not, reject.
2. No social proof, logos or ROI proof. Gong measured those correlating with a 22% lower close rate and a 27% drop.
3. No talk segment over 76 seconds without a question.
4. Timings sum to about nine minutes; overview two minutes or under.
5. Next steps block present and dated against {CRITICAL_DATE}.
6. Order still matches the buyer's ranking.

Any failure: name the check, restate the constraint, rerun Codex. Never patch by hand and call it passed.

## Rules

- Demo only what discovery raised; parked topics stay parked until asked for.
- No social proof slide, logo wall or ROI proof attempt in the demo.
- The opening is about the buyer, not the company, and lasts two minutes.
- Never end a first call without next steps discussed.
- Public information only.
- Never invent a fact, a number or a quote.
- Anything sent in someone's name says whose name it is.

## If Codex is not installed

Claude writes the run sheet itself and says it did the Codex half.

## Built from

- Gong Labs, product demo study, 3 million demos: https://www.gong.io/resources/labs/product-demo/
- Great Demo!, Peter Cohan, Seven Validated Habits: https://cdn.prod.website-files.com/6540c97c6e5b78f21ab4a9b5/67dbb3814d8a2c44393f3105_Seven%20Validated%20Habits%20of%20Stunningly%20Successful%20Demos.pdf
- Gong Labs, discovery study, 519,000 calls: https://www.gong.io/resources/labs/deal-closing-discovery-call/

# Show only the three things this buyer cares about - Codex task

You are formatting a demo run sheet. Every decision is already made. Do not add topics, claims or numbers.

## You are given

- {SITUATION_SLIDE}: six fields quoted from the buyer's discovery call (overarching goal, current situation, pain and problems, capabilities sought, value desired, required timeline).
- {TOP_THREE_TOPICS}: exactly three demo topics, already ranked most important first, in the buyer's own wording.
- {PRODUCT_STEPS}: the clicks or screens available for each topic.
- {CRITICAL_DATE}: the date the buyer said something must be working by.

## Produce

A single file `run-sheet.md`:

1. **Contextual overview (2 minutes)**: the six Situation Slide fields as short lines. No company slide, no product intro, no architecture, no customer logos.
2. **Three topic blocks, in the given order.** Each block, about three minutes:
   - Headline: the buyer's own words for the problem.
   - Last thing first: the finished result shown before any setup.
   - Click path: the steps from {PRODUCT_STEPS} for that topic, numbered.
   - Talk segments: split so no segment exceeds 76 seconds of uninterrupted speech; mark each break as QUESTION and write the question.
   - Two buyer question prompts per topic.
3. **Timing table**: overview plus three blocks plus wrap up, minutes per row, total row. Main demo total about nine minutes.
4. **Wrap up**: next steps, each with owner and date, working back from {CRITICAL_DATE}.
5. **Parking lot**: every capability in {PRODUCT_STEPS} not used in the three blocks, listed as "on request only".

## Rules

- Use only the text supplied. No invented features, customers, figures, percentages or quotes.
- No social proof, customer logos, awards or ROI claims anywhere in the file.
- Keep the given topic order exactly. Do not reorder for flow.
- If a topic has no matching entry in {PRODUCT_STEPS}, write `MISSING: <topic>` in that block instead of guessing a click path.
- British English. No em dashes.
- Any text meant to be sent or presented in a person's name states whose name it is.

## Return

Print to stdout, after writing the file:

- The path of the file written.
- The timing table as plain text, including the total.
- The count of talk segments and the longest segment length in seconds.
- Every `MISSING:` line, or `MISSING: none`.
- A one line confirmation that no social proof, logo or ROI content was added.