Best for
- Complex enterprise product demonstrations
- Industrial software and digital manufacturing demos
- Multi-stakeholder buying committees
Build a buyer-centered demo spine with role-specific branches, trigger questions, proof cues, show and do-not-show rules, fallback paths, timing, and evidence capture.
A rehearsed demo system with narrative spine, stakeholder branches, decision cues, proof points, timing, handoffs, fallback routes, and post-demo evidence fields.
Quick view
Check the audience, core tools, and access before you start the detailed steps.
Best for
Core tools
4 tools used across the workflow.
Access
Preview the open steps, then unlock the remaining implementation details and prompts.
Why this works
A strong technical demo is a controlled conversation, not a fixed tour. The workflow establishes one narrative spine while preparing branches for stakeholder priorities, evidence gaps, technical depth, time pressure, and unexpected questions, allowing the team to stay relevant without improvising unsupported capability.
Expected results
Narrative focus
One demo spine
The team can explain the business and technical journey without defaulting to module order.
Branch readiness
3-8 stakeholder paths
Role and objection branches support relevance while preserving approved claims.
Timing control
Planned cuts and fallbacks
The team knows what to skip if the meeting shortens or a branch consumes time.
Evidence capture
Every key reaction logged
Post-demo outcomes feed requirements, proof plans, risks, and next actions.
Step-by-step workflow
The first 2 steps are open. Pro unlocks the remaining steps, copy-paste prompts, pro tips, tool-by-tool setup guidance, and implementation details.
45-60 min
45-60 min
Use Google Slides and Gong to set the decision the demo supports, audience, hypotheses, scope, time, environment, claims, prohibited content, success evidence, and owners. Create or update the exact fields `demo_id`, `opportunity_id`, `decision_supported`, `audience`, `beliefs_tested`, `scope`, `time_limit`, `environment_id`, `approved_claims`, `prohibited_content`, retaining the native account, opportunity, contact, site, program, requirement, and source IDs instead of matching on display names alone. Apply the operating rule that the demo cannot show unapproved roadmap, customer data, unstable features, or fit assumptions as facts, and write every proposed change to a dated change log rather than replacing the prior approved value. Validate the work by checking audience, time, environment, claims, and decision-owner attendance; assign each warning or exception an owner, severity, due date, and evidence link, and hold records that fail the check. The completion gate is the account executive, demo lead, and product owner approving the charter; document the rollback or fallback path if the source is unavailable, the connector fails, or the buyer disputes the record.
An approved demo charter tied to a buyer decision.
If the team cannot name the decision, the demo will become a feature tour.
45-60 min
45-60 min
Use Claude and Google Slides to package narrative rules, branch schema, role modules, environment inventory, approved proof, examples, tests, and changelog. Create or update the exact fields `skill_name`, `folder_path`, `version`, `owner`, `backup_owner`, `instructions_file`, `branch_schema`, `environment_inventory`, `test_suite`, `changelog`, retaining the native account, opportunity, contact, site, program, requirement, and source IDs instead of matching on display names alone. Apply the operating rule that the Skill folder contains `SKILL.md`, instructions, role modules, environment inventory, tests, approved examples, and changelog, and write every proposed change to a dated change log rather than replacing the prior approved value. Validate the work by running regression tests against known good and unsafe demo scenarios; assign each warning or exception an owner, severity, due date, and evidence link, and hold records that fail the check. The completion gate is the Skill owner and demo governance lead approving release; document the rollback or fallback path if the source is unavailable, the connector fails, or the buyer disputes the record. Run this template in Claude within the approved demo narrative Claude Skill workspace after attaching the source records named for this step; store the returned JSON beside the source register before any downstream action.
A reusable demo Skill with versioning, tests, and maintenance ownership.
Pro workflow preview
Previewing 2 of 13 steps
Get the remaining 11 steps, copy-paste prompts, pro tips, tool-by-tool setup guidance, and ongoing workflow and prompt releases.
$9/month
Include tests for unexpected security, integration, roadmap, and pricing questions so the Skill learns when to defer.
ROLE
You are the governed sales-execution analyst supporting a sales engineer or demo lead. You work inside the “Create a demo narrative with branching technical talk tracks” operating system, where source traceability, stable CRM identifiers, buyer-safe language, and human authority are more important than producing a polished but unsupported answer.
OBJECTIVE
Complete workflow step 2, “Create the versioned demo Claude Skill,” and produce this operational outcome: A reusable demo Skill with versioning, tests, and maintenance ownership. Execute only this step; do not silently broaden the task, fabricate buyer facts, or make external changes.
INPUTS
1. APPROVED SOURCE RECORDS: {{create_the_versioned_demo_claude_skill_source_records}}
2. FIELD DICTIONARY AND ALLOWED VALUES: {{create_the_versioned_demo_claude_skill_field_dictionary}}
3. ACCOUNT, OPPORTUNITY, OR PROGRAM CONTEXT: {{create_the_versioned_demo_claude_skill_deal_context}}
4. OPERATING RULES, PERMISSIONS, AND APPROVAL MATRIX: {{create_the_versioned_demo_claude_skill_operating_rules}}
5. PRIOR APPROVED VERSION OR CURRENT STATE: {{create_the_versioned_demo_claude_skill_prior_state}}
6. DEADLINES, OWNERS, AND REVIEW CADENCE: {{create_the_versioned_demo_claude_skill_approval_context}}
WORK TO PERFORM
1. Perform the exact job described by “Create the versioned demo Claude Skill” using the supplied IDs and field names.
2. Separate observed facts, direct buyer statements, operator-entered decisions, calculations, and model inferences.
3. Preserve account_id, opportunity_id, contact_id, site_id, program_id, requirement_id, source_id, owner, and effective_date whenever supplied; do not merge records merely because names look similar.
4. Populate the requested fields, identify missing values, and flag contradictions, stale evidence, duplicate entities, unsupported claims, permission issues, and dependencies.
5. Return records that can be copied into the declared system of record without renaming identifiers, flattening one-to-many relationships, or overwriting an approved value.
6. Provide a compact change summary, exception queue, approval request, and next-action list with owner and due date.
7. Apply the step-specific instructions: package narrative rules, branch schema, role modules, environment inventory, approved proof, examples, tests, and changelog.
OUTPUT SCHEMA
Return valid JSON only with this exact top-level structure:
{
"workflow_slug": "demo-narrative-branching-talk-track-builder",
"step_number": 2,
"step_title": "Create the versioned demo Claude Skill",
"run_status": "pass|warning|hold|fail",
"source_register": [{"source_id":"string","source_type":"string","captured_at":"ISO-8601|null","authoritative":true,"notes":"string|null"}],
"records": [{
"skill_name": "value|null",
"folder_path": "value|null",
"version": "value|null",
"owner": "value|null",
"backup_owner": "value|null",
"instructions_file": "value|null",
"branch_schema": "value|null",
"environment_inventory": "value|null",
"test_suite": "value|null",
"changelog": "value|null",
"evidence_source_ids": ["string"],
"confidence": "high|medium|low",
"review_status": "approved|needs-review|held"
}],
"exceptions": [{"record_id":"string|null","exception_type":"string","severity":"low|medium|high|critical","evidence":"string","owner":"string","required_action":"string"}],
"changes_from_prior_state": [{"record_id":"string","field":"string","prior_value":"value|null","proposed_value":"value|null","reason":"string","source_ids":["string"]}],
"review_summary": {"facts":["string"],"inferences":["string"],"open_questions":["string"],"next_actions":[{"action":"string","owner":"string","due_date":"YYYY-MM-DD|null"}]},
"qa": {"schema_valid":true,"ids_preserved":true,"evidence_complete":true,"human_approval_required":true}
}
GUARDRAILS
- Treat the supplied field dictionary, approval matrix, security policy, commercial rules, and prior approved state as binding.
- Do not invent quotes, dates, metrics, relationships, customer permissions, product capabilities, legal positions, security answers, pricing authority, or approvals.
- Do not perform, simulate, or claim an external write. Return proposed records or actions for the named operator or governed automation to apply.
- Do not collapse conflicting evidence into one confident statement. Preserve each source and route the conflict to the exception queue.
- Do not expose confidential margin, personal data, security detail, or contract language to an audience not authorized in the inputs.
- Mark any record that could change scope, price, legal obligations, security posture, implementation effort, or buyer commitment as human-approval-required.
EVIDENCE REQUIREMENTS
- Every material claim must cite one or more supplied source_id values and include the source date when available.
- Direct buyer statements must remain distinguishable from seller interpretation and model inference.
- Calculations must show inputs, units, formula, and rounding rule; relationships must show the evidence supporting the match.
- A record without adequate evidence must be marked needs-review or held, never approved by default.
UNCERTAINTY HANDLING
- Use high confidence only for current authoritative records or direct, corroborated buyer evidence.
- Use medium confidence for a plausible interpretation supported by one credible source, and low confidence for hypotheses requiring validation.
- When two sources disagree, list both values, explain the conflict, and name the person who must resolve it.
- If required inputs are absent, return run_status “hold” and state exactly what is missing instead of guessing.
HUMAN REVIEW
The named operator must review the source register, exceptions, inferred fields, proposed changes, and audience permissions. Require explicit approval before any CRM write, buyer-facing publication, pricing or scope commitment, legal or security response, pilot promise, or external notification. Return the approval decision, reviewer, timestamp, rejected items, and required revisions in the final review summary.Related workflows
Continue with workflows that share a similar GTM motion, category, or tool stack.
A sequenced proof plan with stakeholder belief, proof method, evidence, owner, acceptance criterion, cost, dependency, decision milestone, and fallback.
A governed solution-fit register with requirement links, evidence, assumptions, dependencies, validation owners, scope impact, and buyer-confirmation status.
A champion-ready internal deck, decision memo, forwarding email, stakeholder FAQ, proof library, implementation summary, objection guide, and coaching plan.