@rubytech/create-realagent-code 0.1.255 → 0.1.256

package/payload/platform/plugins/slides/skills/deck-system/STORYTELLING-product-launch.md

@@ -0,0 +1,579 @@
+# Storytelling: Product Launch
+
+How to build a product launch deck that makes people want what you've made.
+
+Product launches are performances. The deck is the pacing mechanism. Every section is a reveal. The audience should feel like they're unwrapping something, layer by layer, each one more exciting than the last. The moment you show the product before you've built anticipation, you've lost the plot.
+
+This guide is the narrative framework for launch decks. It works for keynotes, press events, internal product reviews, customer webinars, and "here's what we built" moments. The Slides template was built to support this arc.
+
+---
+
+## The nine-beat structure
+
+Every product launch has a shape. This is ours:
+
+```
+Start ──────────────────────────────────────────────────────── End
+│ Setup │ Problem │ Reveal │    Demo    │ Specs │ Proof │ OMT │ CTA │ Close │
+```
+
+Nine beats. Some launches skip one or two. The "one more thing" is optional. The rest are load-bearing.
+
+| Beat | ~Share | Purpose |
+|------|--------|---------|
+| The Setup | 10% | Build the world |
+| The Problem | 10% | Name the friction |
+| The Reveal | 15% | Drop the product |
+| The Demo | 25% | Show it working |
+| The Specs | 10% | Give the details |
+| Social Proof | 10% | Show who's in |
+| One More Thing | 5% | Surprise (optional) |
+| Availability & CTA | 10% | Tell them how to get it |
+| Close | 5% | Land the line |
+
+---
+
+## Beat 1: The Setup
+
+### Purpose
+
+Why are we here today? What's the context? You're setting the stage for the world the product enters. You're orienting the audience before opening the curtain.
+
+The audience should feel oriented. They should understand the landscape, the momentum, the stakes. By the end of this beat, they should be leaning forward, anticipating something.
+
+### Pacing
+
+Slow. Deliberate. You're building a room before you turn on the lights. Let the context breathe so it earns the reveal.
+
+### Example headlines
+
+> **The way we work** <span class="dim">changed forever.</span>
+> **$4.2 trillion market.** <span class="dim">Still running on spreadsheets.</span>
+> **Every team ships faster now.** <span class="dim">Except for one bottleneck.</span>
+> **Three years ago** <span class="dim">we made a bet.</span>
+
+### Best components
+
+- **Quote slide:** A single provocative statement to open. No subtitle.
+- **Eyebrow + headline + subtitle:** Context with a category tag ("THE MARKET", "THE SHIFT", "2024 → 2025").
+- **Two-column:** Then vs now. Old paradigm vs new forces.
+
+### Common mistakes
+
+- Starting with your company history. Nobody cares yet.
+- Showing the product logo on slide 2. You've killed the anticipation.
+- Making the setup too long. Ten percent means 2–3 slides.
+- Being vague. "The world is changing" says nothing. Be specific about *what* changed.
+
+---
+
+## Beat 2: The Problem
+
+### Purpose
+
+What's broken, missing, or hard? The gap in the market. The friction everyone lives with. Make the audience *feel* the problem before you show the fix.
+
+This is empathy work. If you skip it, the product reveal lands flat because the audience hasn't felt the pain you're solving.
+
+### Pacing
+
+Build tension. Each sub-point should make the problem feel worse. Stack frustrations. End with a line that closes the chapter, the "surely there's a better way" moment.
+
+### Example headlines
+
+> **The old workflow** <span class="dim">has 14 steps.</span>
+> **Teams wait 3 days** <span class="dim">for what should take 3 minutes.</span>
+> **Everyone hates it.** <span class="dim">Nobody fixes it.</span>
+> **Good enough** <span class="dim">stopped being good enough.</span>
+
+### Best components
+
+- **Step stack** (in two-column): Show the painful old workflow with its blockers and friction points.
+- **Capability list:** Rows of problems. Left: the task. Right: what's wrong with the current state.
+- **Dark slide:** One gut-punch line that captures the whole problem. "Your team spends 40% of their time on work about work."
+
+### Common mistakes
+
+- Describing problems the audience doesn't recognize. If they don't feel it, they won't care about the fix.
+- Straw-manning competitors. Describe the *category* problem, the systemic friction.
+- Making it too abstract. Use numbers, timelines, real scenarios.
+- Spending too long here. You need enough pain to motivate the reveal, and enough restraint that the mood stays productive.
+
+---
+
+## Beat 3: The Reveal
+
+### Purpose
+
+The product. Name, positioning, one headline. This is the "one more thing" moment, the *main* thing. Let it land. Pause.
+
+The reveal is a name and a promise. One sentence that captures what this thing *is*. The details come later. Right now, the audience just needs to understand the shape of what you've built.
+
+### Pacing
+
+**Slow down.** This is the most important transition in the deck. The slide before should end on a question or a tension. Then: click. The product appears. Give it a full beat of silence. Let the name sit on screen for two seconds before you say anything else.
+
+### Example headlines
+
+> **Introducing Arc.** <span class="dim">Design at the speed of thought.</span>
+> **Meet Relay.** <span class="dim">One inbox for every team.</span>
+> **This is Prism.** <span class="dim">Your entire pipeline, one command.</span>
+> **We call it Drift.** <span class="dim">And it changes everything.</span>
+
+### Best components
+
+- **Product slide** (showcase style): Big product name on the right. Tagline and one-line description on the left.
+- **Dark slide:** Product name, large type, nothing else. Maximum dramatic weight.
+- **Collage slide:** Full-bleed product image or hero screenshot immediately after the name slide. The one-two punch: name then visual.
+- **Art overlay:** The product rendered against a beautiful full-bleed background. Creates an aspirational, premium feeling that pure screenshots lack.
+
+### Common mistakes
+
+- Burying the reveal in a list of features. The reveal is *one* slide. One name. One line.
+- Clicking past the reveal without letting it breathe. Give it a full pause.
+- Weak naming. "Introducing our new analytics dashboard" is forgettable. Give it a proper name.
+- Showing the reveal too early. If you haven't earned the tension, the drop doesn't hit.
+
+---
+
+## Beat 4: The Demo / Walkthrough
+
+### Purpose
+
+Show it working. This is the longest section, and the most important. The reveal promised something. The demo proves it. Feature by feature, each with its own mini-narrative.
+
+### Pacing
+
+Each feature follows the **setup-show-impact** pattern:
+
+1. **Setup** (text slide): What was hard before. One sentence of context.
+2. **Show** (collage slide): Screenshot, video, live demo. The product doing the thing.
+3. **Impact** (text slide or stat): What this means. The result. The number.
+
+Alternate between text slides and full-bleed visuals. This creates rhythm: read, see, feel, read, see, feel. Three to five features is the sweet spot. More than that and you lose momentum.
+
+### Example headlines
+
+> **Search that actually works.** <span class="dim">Across every source, in milliseconds.</span>
+> **One click to deploy.** <span class="dim">No config. No waiting.</span>
+> **Real-time collaboration.** <span class="dim">See changes as they happen.</span>
+> **From 14 steps** <span class="dim">to one.</span>
+
+### Best components
+
+- **Eyebrow + headline + subtitle:** Setup slide for each feature. Eyebrow tags the category ("SEARCH", "DEPLOY", "COLLABORATION").
+- **Collage slide:** Full-bleed screenshot or video after each setup. This is the "show" beat.
+- **Two-column:** Old way vs new way, side by side.
+- **Product slide:** For hero features that deserve the showcase treatment.
+- **Dark slide:** One mid-demo moment where you step back and say something big. "This is what three years of R&D looks like."
+- **Feature card row:** Break down a complex capability into three or four cards, each with an icon, title, and one-line benefit. Ideal for showing feature breadth at a glance.
+- **Code slide:** For developer-facing products, show a real snippet of the API or CLI in action. Nothing builds trust faster than seeing the actual interface.
+- **Spec block:** Input/process/output layout. Show what goes in, what the product does, and what comes out. Effective for AI, data, or automation features.
+
+### The setup-show-impact pattern
+
+For each feature:
+
+```
+Slide A: "Teams used to wait 3 days for deploy previews."     [text: setup]
+Slide B: [full-bleed screenshot of instant preview]           [collage: show]
+Slide C: "Deploy time: 3 days → 12 seconds."                 [stat: impact]
+```
+
+Vary the pattern across features:
+- Feature 1: setup → collage → stat
+- Feature 2: dark slide (big claim) → collage → two-column comparison
+- Feature 3: eyebrow setup → video → quote from a beta user
+
+Variation keeps the audience alert.
+
+### Common mistakes
+
+- Too many features. Pick three to five. The rest go in a blog post.
+- Describing features in text without showing the product. Use screenshots, videos, anything visual.
+- Showing features without context. "Here's feature X" means nothing. "You used to do Y, now you do X" means everything.
+- Same layout for every feature. Monotony kills attention. Vary your components.
+- Rushing. Give each feature its own breathing room. The demo section should feel generous.
+
+---
+
+## Beat 5: The Specs
+
+### Purpose
+
+The details. Performance benchmarks, pricing, availability dates, compatibility, technical requirements. The audience has seen what it does. Now they need to know the specifics.
+
+This beat serves the analytical buyers. The people who were nodding during the demo but need numbers before they commit.
+
+### Pacing
+
+Faster. This is information delivery. Be crisp. Use grids and lists. Get in, give the facts, get out.
+
+### Example headlines
+
+> **The numbers.** <span class="dim">Under the hood.</span>
+> **Built for scale.** <span class="dim">Here's the proof.</span>
+> **Pricing that makes sense.** <span class="dim">No surprises.</span>
+> **What's included.** <span class="dim">Everything you need.</span>
+
+### Best components
+
+- **Capability list:** Rows of specs. Left: the metric. Right: the value. Clean, scannable.
+- **Three-column:** Pricing tiers or plan comparison.
+- **Stack grid:** Categories of capabilities with checkmarks or feature lists. Also works well for grouping features into thematic columns.
+- **Two-column:** Technical details on one side, what it means for the user on the other.
+- **Update row:** Release timeline showing what shipped, what's in beta, and what's next. Gives analytical buyers a sense of velocity and roadmap confidence.
+
+### Common mistakes
+
+- Burying the price. If there's a price, say it clearly.
+- Too many specs. Pick the 5–8 that matter. The spec sheet lives on your website.
+- No context for numbers. "99.99% uptime" means more when you say "That's 52 seconds of downtime per year."
+- Making this section too long. It's 10% of the deck. Two to three slides.
+
+---
+
+## Beat 6: Social Proof
+
+### Purpose
+
+Who's already using it? Who believes in it? Testimonials, logos, case studies, beta results. This answers the unspoken question: "Am I the first idiot to try this, or is it safe?"
+
+### Pacing
+
+Confident but measured. Let the names do the talking. A wall of logos says more than a paragraph of self-congratulation.
+
+### Example headlines
+
+> **Teams already shipping with it.** <span class="dim">Thousands of them.</span>
+> **Hear it from them.** <span class="dim">Real teams, real results.</span>
+> **In production** <span class="dim">since day one.</span>
+> **Trusted by the teams** <span class="dim">that move fastest.</span>
+
+### Best components
+
+- **Logo bar:** A clean horizontal row of recognizable customer logos. High density, zero friction. The fastest way to establish credibility.
+- **Testimonial grid:** Multiple quotes arranged in a grid layout. Each cell: photo, name, role, and a one-line quote. Conveys breadth of adoption at a glance.
+- **Stack grid:** Logo grid. Four columns of customer logos. No captions needed.
+- **Capability list:** Testimonial rows. Left: company name. Right: quote.
+- **Quote slide:** One powerful testimonial, large type. Attribution below.
+- **Two-column:** Case study format. Left: the challenge. Right: the result with the product.
+
+### Common mistakes
+
+- Fake-sounding testimonials. "This product is amazing!" means nothing. Specific results beat generic praise.
+- Too many logos with no context. One case study beats twenty anonymous logos.
+- Putting social proof before the demo. The audience needs to understand the product before they care who else uses it.
+- Skipping this entirely. Even in an internal launch, showing who's been piloting it builds credibility.
+
+---
+
+## Beat 7: One More Thing
+
+### Purpose
+
+A surprise. An unexpected feature, an unlikely partnership, an aggressive price point, an early-access announcement. The thing that elevates the launch from "solid" to "memorable."
+
+This beat is **optional.** Only use it if you genuinely have something surprising. A forced "one more thing" is worse than no surprise at all.
+
+### The "one more thing" test
+
+Ask yourself:
+1. Would this get a genuine reaction if the audience didn't know it was coming?
+2. Is it actually separate from the main product, a true addition rather than feature #6?
+3. Does it change the audience's mental model of what you're offering?
+
+If you can't answer yes to at least two of these, fold it into the demo or cut it.
+
+### Pacing
+
+Slow. Dramatic pause before. The preceding slide should feel like a natural ending. The audience should think you're wrapping up. Then: "One more thing." Beat. Click.
+
+### Example headlines
+
+> **Oh, and one more thing.** <span class="dim"></span>
+> **We weren't going to show this yet.** <span class="dim">But here we are.</span>
+> **Free.** <span class="dim">For everyone. Starting today.</span>
+> **And it works with** <span class="dim">everything you already use.</span>
+
+### Best components
+
+- **Dark slide:** "One more thing." Nothing else. Then the next slide reveals it.
+- **Product slide:** If the surprise is a second product or major feature.
+- **Collage slide:** Full-bleed visual of the surprise in action.
+- **Quote slide:** If the surprise is a partnership, let the partner's words carry it.
+
+### Common mistakes
+
+- Using this for something that isn't surprising. "And one more thing: we also have an API" is a feature, and belongs in the demo.
+- Multiple "one more things." You get one. That's why it works.
+- Telegraphing the surprise. Keep it out of earlier slides. The whole point is that it's unexpected.
+
+---
+
+## Beat 8: Availability & CTA
+
+### Purpose
+
+When can they get it? How? What do they do right now? This is the operational close. Clear, specific, actionable.
+
+The audience is excited. Tell them exactly what happens next.
+
+### Pacing
+
+Direct. No buildup needed. You've earned the ask. State the facts: date, URL, pricing, next step. Then move to the close.
+
+### Example headlines
+
+> **Available today.** <span class="dim">Start free at arc.dev.</span>
+> **Open beta** <span class="dim">starts next Tuesday.</span>
+> **Sign up now.** <span class="dim">First 1,000 teams get early access.</span>
+> **Ship it this week.** <span class="dim">No credit card. No setup call.</span>
+
+### Best components
+
+- **Eyebrow + headline + subtitle:** The primary CTA. Eyebrow: "AVAILABILITY". Headline: the date or action. Subtitle: the URL or next step.
+- **Three-column:** If there are multiple paths (try free / talk to sales / join waitlist).
+- **Capability list:** What's available now, what's coming in Q2, what's on the roadmap.
+- **Timeline:** A visual rollout schedule showing launch phases. Use for staged rollouts: "Today: early access. July: public beta. September: GA." Gives urgency and clarity in one slide.
+- **Dark slide:** For maximum urgency. White text, single CTA.
+
+### Common mistakes
+
+- No clear CTA. "Learn more at our website" is vague. "Start your free trial at relay.app" is actionable.
+- Burying availability in a paragraph. It should be the headline.
+- Too many options. One primary CTA. Maybe one secondary.
+- Forgetting the URL. They need to know where to go. Put it on screen.
+
+---
+
+## Beat 9: Close
+
+### Purpose
+
+One memorable line. The tagline. The thing they'll repeat to a colleague. The thing they'll tweet.
+
+This is a punctuation mark, a final beat of energy.
+
+### Pacing
+
+Slow down. Say it once. Stop. Let the line do its work.
+
+### Example headlines
+
+> **The future of work** <span class="dim">ships today.</span>
+> **Build faster.** <span class="dim">Ship with confidence.</span>
+> **One tool.** <span class="dim">Every team. No compromises.</span>
+> **This is day one.** <span class="dim">Imagine day 1,000.</span>
+
+### Best components
+
+- **Dark slide:** The closing line, nothing else. Maximum weight.
+- **Quote slide:** Large type, centered. The final word.
+
+### Common mistakes
+
+- A summary slide. "In conclusion, we showed you…" kills the energy. End on a high.
+- Thanking the audience before the line lands. Say the line first. Then thank them if you must.
+- A weak tagline. Spend more time on this line than any other in the deck. Test it out loud.
+- Adding slides after the close. The close is the last slide. Nothing follows it except applause or a Q&A card.
+
+---
+
+## Demo pacing: the setup-show-impact pattern
+
+The demo section is where most product launches fail. They either show too much (death by feature tour) or too little (all talk, no proof). The fix is the **setup-show-impact** loop.
+
+For every feature you show:
+
+### Setup (10 seconds)
+
+One sentence. What was the old way? What was frustrating? This primes the audience to appreciate what they're about to see.
+
+> "Right now, deploying a change means opening a ticket, waiting for DevOps, and hoping nothing breaks."
+
+### Show (20–30 seconds)
+
+The product doing the thing. A screenshot, a video clip, a live demo. No narration during the visual. Let the audience absorb it. If it's a video, keep it under 15 seconds.
+
+### Impact (5 seconds)
+
+One line. The result. The number. The "so what."
+
+> "Deploy time went from three days to twelve seconds."
+
+Then move to the next feature. The rhythm is: tension → proof → relief → tension → proof → relief.
+
+---
+
+## Visual rhythm
+
+A product launch deck should alternate between text and visuals like breathing in and out.
+
+```
+Text → Visual → Text → Visual → Text → Visual
+```
+
+Specifically:
+- **Setup slides** (eyebrow + headline + subtitle) give context
+- **Collage slides** (full-bleed images/video) give proof
+- **Product slides** introduce features
+- **Dark slides** mark transitions
+- **Quote slides** provide breathing room
+
+Never put three text slides in a row. Never put three visuals in a row. The alternation is what creates momentum.
+
+If you don't have visuals, you don't have a product launch. Get screenshots. Record a screen capture. Render mockups. A launch without visuals is just a memo.
+
+---
+
+## Adapting for audience
+
+### Press event / keynote
+
+Full theatrical treatment. Long pauses. One more thing. Big collage slides. The audience is there to be impressed. Give them a show.
+
+- Lean into dark slides for drama
+- Use video over screenshots where possible
+- Keep specs minimal. Journalists care about the story and the human impact.
+- End with a quotable line they can use as a headline
+
+### Internal launch (all-hands, team demo)
+
+Drop the theater. Keep the structure. The audience already trusts you, so they want clarity and directness.
+
+- Save the "one more thing" for external audiences
+- Expand the specs section. Internal teams need detail.
+- Add a "what this means for us" slide (staffing, timeline, dependencies)
+- Be honest about what's ready and what's still in progress
+
+### Customer webinar
+
+The audience is evaluating. They need to see themselves in the product.
+
+- Expand social proof. They want to know who else is using it.
+- Tailor the problem section to *their* specific pain
+- Demo the workflow they'd actually use, the one closest to their day-to-day
+- CTA should be "talk to us" or "start a trial," a low-commitment next step
+
+### Recorded / async (product video, launch page)
+
+No live energy to lean on. The deck must carry itself.
+
+- Tighter pacing, about 20% less time per beat than live
+- More collage slides. Visuals hold attention without a speaker.
+- Subtitles on every slide. The body copy does the speaker's job.
+- Keep it under 5 minutes total if it's a video
+
+---
+
+## Adapting for format
+
+### Live keynote (you're presenting)
+
+You are the setup. The slide is the punchline. Talk to the audience, then click to reveal. The audience can read faster than you can talk, so let the slides land visually while you provide the narrative frame.
+
+### Pre-recorded video
+
+Every second counts. Cut 30% of what you'd say live. Let visuals linger longer. Add music or ambient sound during collage slides.
+
+### Read-only deck (shared via link, no presenter)
+
+The headlines carry the narrative arc. The subtitles carry the detail. Every slide should make sense without hearing someone talk over it. Add more body copy. Use the capability list component for information density.
+
+---
+
+## Common mistakes
+
+### 1. Too many features
+
+You have twelve things to show. Pick five. The audience can absorb that many in one sitting. The rest go in a follow-up blog post, a documentation page, or version 2 of the launch.
+
+### 2. No demo
+
+If you announce a product without showing it working, the audience fills the gap with skepticism. Even a single screenshot is better than nothing. A 10-second video is better than a screenshot. A live demo is best of all.
+
+### 3. Burying the price
+
+If you have pricing, say it clearly and say it once. Give the audience the number directly. If the price is good, it's a feature: put it in a headline.
+
+### 4. Anticlimactic reveals
+
+The reveal should feel like a curtain drop. If it feels like "oh, here's another slide," you haven't earned it. The problem section must create enough tension that the reveal feels like relief.
+
+### 5. Feature parity as a selling point
+
+"We do everything they do, plus one more thing" is a comparison chart, and audiences don't rally behind comparison charts. Lead with what's *new* and uniquely yours.
+
+### 6. No visual proof
+
+Words describe. Images prove. If your demo section is all text slides, you're telling the audience to trust you. Show them instead.
+
+### 7. The fake "one more thing"
+
+If your surprise is just the last feature on your roadmap, it doesn't qualify. Skip the "one more thing" beat entirely. A clean CTA is more powerful than a forced reveal.
+
+### 8. Ending with a whimper
+
+"Thanks, that's all we have today" is a flat ending. Your last slide should be the most polished, most rehearsed, most memorable moment in the deck. Spend time on it.
+
+---
+
+## A formula that works
+
+If you don't know where to start:
+
+```
+1. Set the scene. Why does this matter now?
+2. Name the pain. What's broken?
+3. Reveal the product. One name, one line.
+4. Show it working. Three to five features, setup-show-impact for each.
+5. Give the specs. Numbers, pricing, compatibility.
+6. Show who's in. Logos, quotes, results.
+7. Surprise them (only if you can).
+8. Tell them how to get it.
+9. Close with one line you've rehearsed.
+```
+
+Nine beats. Use them. Skip the optional one. Reorder if your product demands it. They're a scaffold, a flexible framework you adapt to the story.
+
+---
+
+## On the reveal line
+
+Spend more time on your reveal line than any other line in the deck except the close.
+
+It should be:
+- **Named.** Give the product a proper name. A real, memorable name.
+- **Positioned.** One line that says what it is and who it's for.
+- **Clean.** Zero jargon, zero feature lists, zero qualifiers. Just the essence.
+
+Test it by imagining someone texting it to a friend: "They just announced [X]. It's [one-line description]." If that text doesn't make sense or doesn't sound exciting, rewrite the line.
+
+---
+
+## The visual hierarchy of a launch
+
+Each slide carries different weight. Here's the energy curve:
+
+```
+Energy
+  ▲
+  │         ★ Reveal
+  │        / \          ★ One More Thing
+  │       /   \        / \
+  │      /  Demo\     /   \
+  │     / section \  /     \
+  │    /           \/       \  ★ Close
+  │   / Problem   Specs/     \
+  │  /  section   Proof       \
+  │ /                          \
+  │/ Setup                      \
+  └──────────────────────────────→ Time
+```
+
+Design your slides to match this curve:
+- **Low energy** = text-heavy slides, subtle backgrounds, smaller type
+- **High energy** = dark slides, full-bleed collages, large type, product showcases
+
+The reveal and the close should be the loudest slides in the deck. If your spec section is louder than your reveal, something's wrong.