| name | demo-thesis |
| description | Create a Demo Thesis brief for a software product video. Use when defining the target viewer, before/after belief change, demo promise, proof requirements, CTA, positioning frame, or first station of Damien's demo process before Story Spine, scripting, or Demo Path work.
|
Demo Thesis
Produce the strategic brief that all later demo-video work depends on.
Read references/demo-thesis-process.md unless the user explicitly asks for a
very quick pass. If product context is missing, make the smallest useful
assumptions and label them.
Workflow
- Gather the available source material: product context, Raven knowledge,
launch goal, customer objections, competitor frame, and product capabilities.
- Define one target viewer precisely enough that the video can make tradeoffs.
- Write the before/after belief change in one sentence.
- Choose one demo promise and no more than 3-5 proof requirements.
- Mark each proof requirement as product-visible, evidence-backed, or
explanation-only.
- Define the primary CTA and the scope boundary: what this demo is not trying
to prove.
- Run the quality checks from the reference before presenting the brief.
Output
Use this structure:
Demo Thesis Brief
Product:
Target viewer:
Viewer context and pain:
Current alternatives:
Category frame:
One-sentence demo promise:
Viewer belief before watching:
Viewer belief after watching:
Primary CTA:
Scope boundary:
Proof requirements
| proof | why it matters | burden | current support | risk |
Terms to use:
Terms to avoid:
Open questions / assumptions:
Hand-off notes for Story Spine:
Keep the output decision-ready. Do not drift into a full script, shot list, or
product click path; those belong to Story Spine and Demo Path.
