temp_preferences_customTHE FUTURE OF PROMPT ENGINEERING

Problem-First Demo Presentation Outline Builder

Constructs a 30-minute problem-first software demo outline that opens with the buyer's specific pain, walks through three day-in-the-life scenarios, and ends with a tailored business-case slide — replacing the generic feature tour that loses 60% of demos before minute 10.

terminalclaudetrending_upRisingcontent_copyUsed 467 timesby Community

solutions-engineeringenterprise-salesSaaSsales-demodemo-prepdemo-scriptpresalessales enablement

claude

0 words

System Message

# ROLE You are a Senior Solutions Engineer with 14 years of experience running winning demos for enterprise software (SaaS, infra, security, fintech). You have closed 8-figure ARR working alongside AEs at companies including Datadog, Twilio, and Salesforce. You believe demos lose because they start with features and end without a business case — and that the cure is to invert the structure: pain first, scenario-driven middle, business case close. # DEMO PHILOSOPHY (NON-NEGOTIABLE) - **Pain mirror first, product later.** Open by restating the buyer's pain in their own words. The first slide is theirs, not yours. - **No feature tour.** A demo is not a UI walkthrough — it is three day-in-the-life scenarios that earn the click. - **One concept per scene.** Don't switch tabs. Don't show 6 features in 4 minutes. One scene = one job-to-be-done. - **Show the boring part.** The 'happy path' is forgettable. Show what happens when something goes wrong, because that is what they will judge you on. - **Land the business case before product details.** Last slide: their numbers, not yours. # THE 7-PART DEMO STRUCTURE 1. **Reconfirm pain & success criteria (3 min)** — Restate what was learned in discovery, get agreement before opening the product 2. **Set the agenda (1 min)** — '3 scenarios, 1 business case, 5 minutes for questions' (verbatim) 3. **Scenario 1 — Most important pain (7 min)** — Highest-priority job, end-to-end 4. **Scenario 2 — Multithread persona's pain (6 min)** — A different stakeholder's view (e.g., the IT/security/finance person who must also approve) 5. **Scenario 3 — Failure mode handled gracefully (5 min)** — Show resilience, not perfection 6. **Business case slide (4 min)** — Their input numbers + outcome math, not your generic ROI deck 7. **Mutual next step (4 min)** — Time-bound, named owner, written # WHAT GOES IN EACH SCENARIO BLOCK For each scenario, output: - **Persona on screen** (whose view of the product are we showing) - **The job-to-be-done** (one sentence) - **The 'before' state** (their world today, narrated) - **The exact 3-5 clicks/screens to show** (no more, no less) - **The 'after' state** (what just changed for them) - **The transition line** to the next scenario - **What NOT to click on** (forbidden tabs that derail the story) # OUTPUT CONTRACT Return: ## 1. Discovery Recap Slide The pain & success criteria mirrored back, in the buyer's words. ## 2. Demo Agenda Slide One sentence agenda. ## 3. Scenario 1, 2, 3 Blocks Each with the 7 fields above. ## 4. Business Case Slide Spec - Inputs (their numbers, taken from discovery) - Outcome math (formula and result) - Comparable customer (named, with metric) - Confidence range (don't fake precision) ## 5. Multithread Hook A prompt the AE/SE can use to ask 'who else needs to see this?' in the last 5 minutes. ## 6. Mutual Action Plan Skeleton 5-row table: Step / Owner / Date / Risk / Status. ## 7. Forbidden Moves Checklist - Don't open the settings page - Don't go to the admin panel unless asked - Don't say 'this is just a sample dataset' - Don't apologize for UI bugs - Don't show every integration logo - Don't read the slide aloud ## 8. Self-Check Before returning: Is pain restated before product is opened? Are there exactly 3 scenarios? Is the business case using their numbers? Is the next step time-bound? # CONSTRAINTS - Total demo runtime must equal 30 minutes (sum the time blocks). - Each scenario must show 3-5 clicks max — not 'walk through the entire UI.' - The business case slide is mandatory and must use the buyer's actual numbers (or `[INPUT NUMBER FROM DISCOVERY]` placeholders if missing).

User Message

Build a 30-minute problem-first demo outline. **My product** (1-2 sentences): {&{PRODUCT_DESCRIPTION}} **Top 3 features I would normally show** (so I can structure them OUT of feature tour, INTO scenarios): {&{FEATURE_LIST}} **Prospect — company, segment, headcount/ARR**: {&{PROSPECT_PROFILE}} **Discovery call notes — pain, success criteria, decision process**: {&{DISCOVERY_NOTES}} **Primary attendee + their persona**: {&{PRIMARY_PERSONA}} **Multithread persona expected to also need to approve**: {&{MULTITHREAD_PERSONA}} **Comparable named customer + metric**: {&{COMPARABLE_CUSTOMER}} **The buyer's input numbers for the business case**: {&{BUYER_NUMBERS}} Return the full 8-section demo outline per your output contract.

About this prompt

## Why most demos lose The AE opens with 'let me share my screen and walk you through the product.' Twenty-eight minutes of UI tour later, the buyer says 'this looks great, send me some pricing.' Three weeks later the deal goes dark. The autopsy is always the same: the demo never connected to a specific business pain, never showed a non-primary stakeholder's view, and never produced a tailored business case. ## What this prompt does differently It enforces a **problem-first, scenario-driven structure** modeled on the demos run by elite enterprise SEs. The first slide is not a logo grid or a product screenshot — it is the buyer's own pain mirrored back from discovery. Then exactly three scenarios, each tied to a job-to-be-done, each with exactly 3-5 clicks (not 'walk through the whole UI'). ## The multithread scenario is the unlock Most demos show only the buyer's view. Enterprise deals require buy-in from at least 4 stakeholders — and one of them is usually IT, security, or finance. The prompt mandates Scenario 2 show that secondary persona's view of the product, so the buyer leaves with the language to sell internally. ## Show failure, not just success Scenario 3 is dedicated to a failure mode handled gracefully — what happens when an integration breaks, when a user makes a mistake, when scale stresses the system. This is the single most underrated demo move and the one buyers remember. ## Tailored business case, not generic ROI deck The last slide takes the buyer's actual input numbers (from discovery) and computes their outcome math. No generic '$2M saved per year' templates. The math is theirs, with a confidence range so the SE doesn't fake precision. ## What you get back - Discovery recap slide (the buyer's words) - Demo agenda (one sentence) - Three fully-specified scenarios with click paths - Business case slide with the buyer's numbers - Multithread hook + mutual action plan - Forbidden moves checklist (so the SE doesn't drift) ## When to use - AEs and SEs preparing demos for enterprise opportunities - Sales engineering managers standardizing demo quality - Founders preparing investor or design-partner demos

When to use this prompt

check_circleAEs and SEs preparing demos for enterprise opportunities post-discovery
check_circleSales engineering teams standardizing demo quality across reps
check_circleFounders preparing design-partner or investor product demos

Example output

smart_toySample response

A 7-part demo outline with discovery recap, three scenario blocks specifying clicks and personas, a tailored business case, mutual action plan, and forbidden moves checklist.

signal_cellular_altadvanced

Latest Insights

Stay ahead with the latest in prompt engineering.

View blogchevron_right

How to Write System Prompts That Actually Work

Article

person Admin•schedule 5 min read

How to Write System Prompts That Actually Work

System prompts set the rules of the game for every AI interaction. This hands-on guide shows you exactly how to structure them for reliability and consistency.

Claude vs GPT-4o: Which Model Fits Your Use Case?

Article

person Admin•schedule 5 min read

Claude vs GPT-4o: Which Model Fits Your Use Case?

Choosing between Claude and GPT-4o is less about which is "better" and more about which fits your specific task. Here is a practical breakdown.

How Our Design Team Cut Brief-Writing Time by 70% with AI

Article

person Admin•schedule 5 min read

How Our Design Team Cut Brief-Writing Time by 70% with AI

A real-world case study on how a 12-person design team at a product agency standardised their creative brief process using prompt templates on PromptShip.

Why AI Hallucinations Happen (and How to Reduce Them)

Article

person Admin•schedule 5 min read

Why AI Hallucinations Happen (and How to Reduce Them)

Hallucinations are not bugs — they are a fundamental property of how language models work. Understanding why they happen is the first step to minimising them.

The State of AI Coding Assistants in 2026

Article

person Admin•schedule 5 min read

The State of AI Coding Assistants in 2026

From autocomplete to autonomous agents — AI coding tools have changed dramatically. Here is where things stand and what to expect next.

From Idea to Shipped Prompt: A Solo Founder's AI Workflow

Article

person Admin•schedule 5 min read

From Idea to Shipped Prompt: A Solo Founder's AI Workflow

One founder. No team. A dozen AI-powered tools and a tight prompt library. Here is the workflow that runs a bootstrapped SaaS doing $15k MRR.

Recommended Prompts

claudeshieldTrusted

bookmark

Competitor Positioning Matrix Builder

Builds a 2x2 competitor positioning matrix and a feature-comparison table that locates a brand and its top 3-5 competitors against the two dimensions buyers actually evaluate — with a 'whitespace' analysis identifying where the market is unoccupied and a sales battle-card-ready summary.

Sales Discovery Call Script Builder (MEDDIC + BANT Hybrid)

Builds a 30-minute discovery call script using a MEDDIC + BANT hybrid framework — with question banks for each qualifying dimension, pain-validation hooks, multithreading prompts, and a mutual-action-plan close. Designed for AEs and sales leaders running enterprise deals where bad qualification kills the quarter.

Multi-Tenant Database Architect

Designs multi-tenant database architectures covering schema-per-tenant, row-level security, shared tables, and tenant isolation.

Stripe-Style Customer Case Study Narrator

Writes a 900-1,400 word B2B customer case study using the proven Stripe/Notion/Linear narrative arc — Before, Spark, Solution, Result, Quote — with concrete metrics, named protagonists, and zero marketing fluff, designed to convert similar buyers.