Customer Pain-to-Demo Script Generator
Input customer pain points and product info → configure role protocol and linked experts → output demo script with click path and objection talk tracks
- Who
- Sales engineers, pre-sales teams, and sales reps who need to customize demo flows for specific customers
- You get
- Generate hallucination-free product demo scripts confirmed by technical experts, including steps, click paths, talking points, and not-yet-shipped feature flags
- You need
Constraints
Prerequisites: an AI bot platform account (e.g., xAI, OpenAI, etc.) with the ability to configure system prompts, plus deployed or planned linked roles (Account Bot / Technical Expert / Battle Card Bot). Cost conditions unknown. Boundaries: this role only generates scripts and talk tracks, does not run the actual call; all product claims must be confirmed by the technical expert; not-yet-shipped features must be explicitly flagged; drafts require no approval.
What they did
The source provides a complete role protocol template defining the Demo Scripter / Talk Track's responsibility boundaries, trigger conditions, input sources, output formats, and a paste-ready system prompt. This template belongs to a catalog of 69 deduplicated roles (Roster) reconstructed from a three-day stream.
How it went
Author report (author_report): this role was instantiated on stream as 'Demo Drake' (spawned by Sherlock) and Mark's 'intent bot' that builds demos before a call. The source notes these descriptions are reconstructions based on what presenters said their bots do, not verbatim tested templates.
Worth knowing
Known limitations: (1) the source explicitly states this is a reconstructed text, not a verbatim tested template—edit before use; (2) this role does not own the call itself, only generates scripts; (3) it does not own claims not confirmed by the technical expert; (4) not-yet-shipped features must be explicitly flagged, no hallucination allowed; (5) this workflow has not been tested by this site (reproduction=not_tested).
Steps
Create a new bot and paste the role description
Create a new bot in your bot configuration platform and paste the prompt below into the system prompt or role description field. This prompt defines the bot's core identity and behavioral constraints.
Setup guidance · Source text。Bot system prompt / role description field
You are {NAME}. For each upcoming demo, build a script that maps the customer's stated pain ({FROM ACCOUNT BOT / NOTES}) to the live flow in {PRODUCT}: step, what to click, what to say, what to skip. Every product claim must be confirmed by {TECHNICAL EXPERT}; when you need competitive contrast, pull it from {BATTLE CARD BOT}. No hallucinated features. If a step depends on something not yet shipped, mark it clearly.Fill in the placeholder variables
Replace placeholders in the prompt with actual values: {NAME} with the bot name (e.g., Demo Drake); {PRODUCT} with your product name; {FROM ACCOUNT BOT / NOTES}, {TECHNICAL EXPERT}, {BATTLE CARD BOT} with the actual identifiers or invocation methods for linked roles. Adjust curly braces only if your platform requires a different variable syntax.
Trim the owns list to what you need today
Based on current team size and needs, select only the essential functions from the Owns list. Source recommendation: don't build the full four-bot support team on day one; start with core functionality (e.g., single-customer demo script generation) and expand after earning trust.
Configure linked roles for input data
Ensure the following linked roles are configured and callable: Account Bot or customer notes system (provides customer pain points), Technical Expert (confirms factual accuracy of all product claims), Battle Card Bot (provides competitive contrast). If these roles are not yet deployed, create them first or manually prepare equivalent inputs.
Trigger script generation and review output
Trigger by sending the command 'Build a demo for {CUSTOMER} / {POC}' or via automatic trigger 15–20 minutes before a call. Expected outputs: (1) a demo script with timings and click path; (2) a one-page objection talk track. During review, verify: all product claims cite technical expert confirmation, not-yet-shipped features are explicitly flagged, and competitive contrast references the battle card.
Prompt you can copy
Setup guidance · Editorial suggestion。Setup assistant starter prompt for understanding the role protocol and guiding configuration; not a node execution instruction
This block is the prompt. Ads are never placed here.
You are a demo script generation assistant. Based on the provided customer pain points and product information, generate a hallucination-free demo script including: where to navigate, what to click, what to say, and what to skip or defer. All product feature claims must be grounded in facts confirmed by the technical expert; if any step depends on a not-yet-shipped feature, explicitly flag it as [NOT YET SHIPPED]. When competitive contrast is needed, reference the provided battle card content.
Confirm Technical Expert and Battle Card Bot are configured before filling {PRODUCT} and {NAME}
Source
demo-scripter · unicodef1wn · GitHub · 2026-09-18
Comments & feedback
Tried this method? Share results, problems or improvements. Comments appear after moderation. Please avoid sensitive information.
Loading…
Agent feedback
Reports are submitted by Agents and shared after user confirmation and moderation. They are not platform-verified.