# Sales Demo Narrative Designer

Design a customer-specific product demonstration around business decisions, realistic workflows, proof points, and controlled recovery from demo risks.

## Prompt

You are a solution consulting lead who specializes in buyer-centered sales demonstrations and technical proof.

Inputs:
1. Buyer audience, roles, and decision stage: {{audience}}
2. Confirmed problems, desired outcomes, and use cases: {{buyer_needs}}
3. Product capabilities, environment, and available data: {{demo_context}}
4. Meeting length, decision criteria, and required proof: {{session_requirements}}
5. Product limitations, technical risks, and prohibited claims: {{constraints}}

Do the following:
1. Prioritize the buyer outcomes and questions the demonstration must prove, separating confirmed needs from seller assumptions.
2. Build a narrative arc from current-state friction through a realistic future-state workflow to measurable outcome, using only capabilities available in the demo environment.
3. Create a timed run-of-show with audience relevance, setup, action, proof, discovery question, and transition for each segment; cut features that do not support a decision criterion.
4. Define realistic sample data, role-specific moments, interaction points, objection branches, failure recovery, backup assets, and explicit handling of unavailable functionality.
5. Produce a demo storyboard, presenter script, environment checklist, rehearsal test cases, backup plan, and post-demo commitment question. Avoid feature dumping, fake customer data presented as real, and unapproved roadmap promises.

## Best for

Account executives and solution consultants preparing focused product demonstrations for a specific buying group and decision.

## Compatible tools

- Claude
- ChatGPT

## How to use

- Start from buyer decisions and use cases, not the feature menu.
- Use synthetic or approved demonstration data.
- Rehearse failure states and backup assets.
- Label simulated integrations and unavailable functionality clearly.

## Customization tips

- Assign a purpose and time limit to every segment.
- Create one relevant moment for each attendee role.
- Use discovery questions during the demo.
- End with a specific mutual next commitment.

## Example input

Audience: Operations vice president, dispatch manager, IT architect, and finance analyst at a 600-vehicle delivery company. Needs: reduce manual route exceptions, show dispatcher control, integrate with existing telematics, and estimate savings. Context: 45-minute web demo using a sandbox with synthetic Berlin routes. Requirements: 30 minutes demo, 10 minutes discussion, 5 minutes next steps. Constraints: live telematics connector is unavailable; predictive weather routing is roadmap only and must not be shown as current.

## Example output

The narrative follows a dispatcher from a morning exception through review, override, driver notification, and operational reporting. Each segment ties to a role: control for dispatch, API evidence for IT, and exception-cost reporting for finance. The connector is demonstrated with a recorded sandbox payload and labeled as a simulation; roadmap weather routing is excluded. The plan includes seeded route failures, a static backup recording, proof questions, rehearsal checks, and a final request for a technical validation workshop.