@rubytech/create-realagent-code 0.1.255 → 0.1.256

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

@@ -0,0 +1,464 @@
+# Storytelling: Sales
+
+How to build a sales deck that actually closes.
+
+A sales deck is a conversation tool. Every slide should open a door for the prospect to walk through. The goal is to get them to say "tell me more."
+
+The difference between a sales deck and a keynote: a keynote is a performance. A sales deck is a collaboration. They are the protagonist. Your job is to hold up a mirror and show them what their life looks like: before you, and after you.
+
+---
+
+## The nine-beat structure
+
+Every sales conversation has a shape. This is ours:
+
+```
+Start ─────────────────────────────────────────────────────── End
+│ Hook │ Pain │ Cost │ Solution │ Proof │ How │ Pricing │ Ask │ Close │
+```
+
+Nine beats. The timing flexes for your deal. A 10-minute discovery call won't cover all of them. But when you have the full meeting, these are the proportions:
+
+| Beat | ~Share | Purpose |
+|------|--------|---------|
+| The Hook | 5% | Start in their world |
+| The Pain | 15% | Deepen the problem |
+| Cost of Inaction | 10% | Make doing nothing expensive |
+| The Solution | 15% | What you built |
+| Proof | 20% | Customers like them |
+| How It Works | 10% | Remove friction |
+| Pricing / Packaging | 10% | Anchor value |
+| The Ask | 5% | One clear next step |
+| Close | 5% | The line they'll repeat |
+
+---
+
+### The Hook: *start in their world*
+
+Start with a problem they recognize. A stat that makes them uncomfortable. A question they've been avoiding. Lead with their world, their numbers, their friction.
+
+The first slide belongs to them. If it's about you, you've already lost momentum.
+
+Examples:
+
+> **"Your team ships 3 features a quarter.** <span class="dim">Your competitor ships 12."</span>
+> **"63% of deals stall** <span class="dim">after the second call."</span>
+> **"You're spending $400K/year** <span class="dim">on a process that doesn't scale."</span>
+> **"Your best rep just quit.** <span class="dim">Again."</span>
+
+**Purpose:** Earn the next 60 seconds. Create a gap between where they are and where they want to be.
+
+**What belongs:** One stat, one provocative observation, one question they've asked themselves in the shower. Something specific to their industry or role.
+
+**What doesn't:** Your logo. Your tagline. "About us." Anything that makes them feel like they're being pitched.
+
+**Components:** Quote slide or cover slide with bold-then-dim headline. Dark slide works if the stat is stark enough.
+
+**Common mistakes:**
+- Opening with "We're [Company], we help [category] do [thing]." Give them a reason to care first.
+- Using a generic industry stat instead of something specific to their situation.
+- Making the hook about you instead of them.
+
+---
+
+### The Pain: *deepen the problem*
+
+Now expand. What does this problem actually cost them? In their daily life. The rep who quits. The deal that slips. The report that takes four hours. The meeting where nobody has the number.
+
+Make the status quo feel expensive through recognition. They should see themselves in this slide and think "yeah, that's us."
+
+Examples:
+
+> **"Manual reporting** <span class="dim">costs your team 12 hours every week."</span>
+> **"Today vs. what it costs you"**: two-column, left is what they do, right is the price they pay.
+> **"Three things that slow you down"**: capability list of friction points.
+
+**Purpose:** Build enough tension that the prospect is ready for a solution. Let this section breathe. If the pain isn't vivid, the solution won't feel urgent.
+
+**What belongs:** Specifics. Numbers. Day-in-the-life descriptions. Quotes from people in their role. The friction they've normalized.
+
+**What doesn't:** Your product. You haven't earned the right to talk about yourself yet. Stick to problems they actually have. If you're wrong about the pain, the whole deck collapses.
+
+**Components:** Two-column (what they do today vs. what it costs). Capability list (friction points as rows). Eyebrow + headline + subtitle for the framing slide.
+
+**Common mistakes:**
+- Listing pain points they haven't actually felt. Do your discovery first.
+- Being too generic. "Companies like yours struggle with…" is weaker than "Your team told us onboarding takes 6 weeks."
+- Rushing through this to get to your product. Sit in the pain. Let them feel it.
+
+---
+
+### Cost of Inaction: *make doing nothing expensive*
+
+This is the urgency slide. What happens if they stay the course? The gap widens. Competitors move. The problem compounds.
+
+Most deals die to "no decision." This beat exists to make "do nothing" feel like a choice, an expensive one.
+
+Examples:
+
+> **"Every quarter you wait** <span class="dim">costs $180K in lost pipeline."</span>
+> **"Your competitors aren't waiting."** <span class="dim">They shipped this last quarter.</span>
+> **"The gap compounds.** <span class="dim">6 months from now, it's twice as hard to close."</span>
+
+**Purpose:** Eliminate "let's revisit next quarter" as an option. Create a ticking clock while staying honest about it.
+
+**What belongs:** Compounding cost projections. Competitor moves. Market shifts. The trajectory if nothing changes.
+
+**What doesn't:** Fear-mongering. Made-up urgency. Artificial deadlines. If the urgency feels thin, find a different angle.
+
+**Components:** Dark callout or dark slide. The black background signals weight. One stat, one line, maximum impact. Timeline showing cost compounding over quarters: visualize how the gap widens the longer they wait. Or a simple two-column: "If you act now" vs "If you wait 6 months."
+
+**Common mistakes:**
+- Skipping this beat entirely. Without it, "we'll think about it" is too comfortable.
+- Being dishonest about urgency. Prospects can smell artificial scarcity.
+- Making it too long. One slide. One punch. Move on.
+
+---
+
+### The Solution: *what you built*
+
+Only now have you earned the right to talk about yourself. Keep it tight. Three capabilities with clear outcomes. The prospect needs to understand what changes for them.
+
+Frame it as: "Here's what becomes possible." Lead with outcomes, always.
+
+Examples:
+
+> **"Three things that change"**: three-column, each column is one capability with a 1-sentence payoff.
+> **"One platform.** <span class="dim">Pipeline, forecasting, coaching. Connected."</span>
+> **"What you get"**: capability list, left column is the capability, right column is the outcome.
+
+**Purpose:** Show the prospect a world where the pain they just felt doesn't exist. Paint the after.
+
+**What belongs:** Three core capabilities. Outcome-first language. The "what changes for you" framing. Simple visual structure.
+
+**What doesn't:** Feature lists. Technical architecture. Roadmap items you haven't built. Comparisons to competitors (that comes later, if at all). Anything that requires a glossary.
+
+**Components:** Three-column (one capability per column). Feature card row (capability + icon + payoff per card). Capability list (feature → outcome rows). Art overlay when the solution has a strong visual or product screenshot worth anchoring. Eyebrow + headline + subtitle for the positioning line.
+
+**Common mistakes:**
+- Feature dumping. If you show 15 features, they remember zero.
+- Leading with how it works instead of what it does for them.
+- Using your internal language instead of their language.
+
+---
+
+### Proof: *customers like them*
+
+The most important section of the deck. Everything before this was a promise. This is where you deliver evidence. Specific customers. Specific metrics. Specific timelines.
+
+The best proof is a customer who looks like them, had the same problem, and solved it with you. If you can get that specific, you win.
+
+Examples:
+
+> **"Acme reduced onboarding from 6 weeks to 4 days."**
+> **"3 customers.** <span class="dim">Same problem. Same result."</span>: testimonial grid.
+> **"40% fewer stalled deals.** <span class="dim">In the first quarter."</span>: stat grid.
+> A logo bar of recognizable names in their industry.
+
+**Purpose:** Shift from "trust us" to "look at the data." Let other customers make your argument for you.
+
+**What belongs:** Named customers (with permission). Specific metrics with timeframes. Before/after comparisons. Quotes from people in the same role as the buyer. Logos they recognize.
+
+**What doesn't:** Anonymous case studies ("a Fortune 500 company"). Vanity metrics ("10,000 users!"). Results that aren't relevant to their problem. Logos from a different industry unless they're famous enough to impress anyway.
+
+**Components:** Stat grid (three to four big numbers with labels). Two-column (before/after a customer implemented). Capability list (customer quotes as rows). Testimonial grid (multiple customer voices side by side). Logo bar. Product slide for a customer case showcase: screenshot, metric, and quote in one frame. Collage slide if you have a compelling visual of the customer's success.
+
+**Common mistakes:**
+- Using proof that doesn't match the prospect's situation. A fintech case study doesn't help a healthcare buyer.
+- Too many logos, too little depth. One deep story beats ten logos.
+- Metrics without context. "Saved 12 hours/week" is good. "Saved 12 hours/week for a team of 8, paying for itself in 3 weeks" is better.
+
+---
+
+### How It Works: *remove friction*
+
+The prospect is interested. Now their brain shifts to: "Okay, but what does this actually look like? How hard is it to switch? How long until we see value?"
+
+Answer that. Show the path from "yes" to "first value." Make it feel easy, or at least manageable.
+
+Examples:
+
+> **"Live in 2 weeks.** <span class="dim">From handshake to first value."</span>
+> A dot flow: Discovery → Setup → Import → Training → First Win.
+> **"What happens after you say yes"**: five steps, each with a timeline and outcome.
+
+**Purpose:** Remove the implementation objection before they raise it. Show them the bridge between today and the world you just promised.
+
+**What belongs:** A clear process (3–5 steps). Timelines. Who does what. When they see first value. What support looks like.
+
+**What doesn't:** Technical implementation details. Migration specs. API documentation. Anything that makes it feel harder than it is.
+
+**Components:** Dot flow (the horizontal step-by-step). Step stack (vertical sequence when the process is more than five steps). Spec block (input → process → output for technical buyers who want clarity). Capability list (step → description rows). Three-column if there are three clear phases.
+
+**Common mistakes:**
+- Skipping this entirely. The prospect's brain is asking "but how?" Answer it.
+- Making it sound too easy. If implementation takes 8 weeks, say 8 weeks. Lying here kills trust later.
+- Too much detail. This is an overview. Save the gantt chart for after they sign.
+
+---
+
+### Pricing / Packaging: *anchor value*
+
+Clear. Simple. Honest.
+
+Show what they get. Show what it costs. If you have tiers, make the difference between them obvious. Anchor the price against the cost of the problem.
+
+"You're spending $400K/year on this problem. We solve it for $80K" is stronger than any competitor comparison.
+
+Examples:
+
+> **"$80K/year.** <span class="dim">You told us the problem costs $400K."</span>
+> Two-column: Growth tier vs. Enterprise tier.
+> Capability list: what's included in each tier.
+
+**Purpose:** Make the price feel small relative to the value. Remove ambiguity. Let them do the math.
+
+**What belongs:** Clear pricing (or pricing framework if it's usage-based). What's included. The anchor: cost of the problem vs. cost of the solution. Contract terms if they're simple.
+
+**What doesn't:** Complex pricing matrices. Per-seat calculations for 47 different team sizes. Discounts you haven't discussed yet. "Contact us for pricing." If you're in a live meeting, show the number.
+
+**Components:** Two-column (tier comparison). JEDUF for presenting tiers as a spectrum: let the buyer see themselves on a continuum from starter to full platform. Capability list (what's included). Stat grid if the value/cost ratio is compelling enough to deserve big numbers.
+
+**Common mistakes:**
+- Apologizing for the price. State it with confidence. You just spent five slides proving the value.
+- Making it too complex. If the prospect can't explain the pricing to their CFO in one sentence, simplify it.
+- Showing pricing before value. The sequence matters. Cost of Inaction → Solution → Proof → Pricing. In that order.
+
+---
+
+### The Ask: *one clear next step*
+
+One specific action with a specific timeline. Own it. Propose the next step yourself.
+
+You're the one proposing next steps. Own the momentum. Tell them what happens next and ask if that works.
+
+Examples:
+
+> **"Let's run a pilot in Q3.** <span class="dim">Four reps. Four weeks. We'll prove it."</span>
+> **"I'll send the contract Tuesday.** <span class="dim">You'll have it by noon."</span>
+> **"Next step: a 30-minute deep dive with your team** <span class="dim">next Thursday."</span>
+
+**Purpose:** Convert interest into action. A deal without a next step is a dead deal.
+
+**What belongs:** One clear CTA. A specific timeline. Who does what. What the prospect needs to do (and how little it is).
+
+**What doesn't:** Multiple options. "We could do X or Y or Z." Pick one. If they push back, adapt. But lead with one clear path.
+
+**Components:** Quote slide with the ask as a bold statement. Or eyebrow + headline + subtitle with the details.
+
+**Common mistakes:**
+- Being vague. "Let's find time next week" is a non-ask.
+- Giving them homework. "Take a look at our docs and let us know." That's a dead deal, every time.
+- Skipping the ask entirely and hoping they'll propose something. They won't.
+
+---
+
+### Close: *the line they'll repeat*
+
+One line. The thing they'll say to their boss when they're selling this internally. Make it stick.
+
+This is the sentence that crystallizes everything you just said into something memorable. One line that sticks.
+
+Examples:
+
+> **"You're 4 weeks away** <span class="dim">from never having this problem again."</span>
+> **"This is what your pipeline looks like** <span class="dim">when nothing slips through."</span>
+> **"Your best quarter is ahead of you.** <span class="dim">Let's go get it."</span>
+> **"Stop managing the chaos.** <span class="dim">Fix it."</span>
+
+**Purpose:** Give them language. The champion in the room needs a sentence to carry upstairs. This is that sentence.
+
+**What belongs:** One bold line. Maybe a subtitle. Nothing else. White space. Confidence.
+
+**What doesn't:** Logos. Contact information (save that for a follow-up email). Lengthy summaries. "Any questions?"
+
+**Components:** Closing slide (dark or light). Quote slide. The bold-then-dim headline pattern at its most powerful.
+
+**Common mistakes:**
+- Ending with "thank you" or "any questions?" Close with conviction instead.
+- Summarizing everything you said. They were there. They heard it.
+- Adding your email and phone number on the closing slide. That's a business card.
+
+---
+
+## The champion test
+
+After you finish your deck, ask this question: could your prospect use this deck to sell internally without you in the room?
+
+If the answer is no, the deck isn't done.
+
+Your prospect is your champion. After the meeting, they'll go to their VP, their CFO, their procurement team. They'll pull up your deck, or worse, try to summarize it from memory. Your deck needs to work both ways: as a conversation tool with you present, and as a standalone argument when you're gone.
+
+**What this means practically:**
+- Headlines should carry the full argument. If someone only reads the headlines, they should understand your pitch.
+- Proof slides should be self-explanatory. Names, metrics, timelines, all legible without narration.
+- The ask slide should make sense to someone who walked in cold.
+- Body copy should do more work than you'd normally include in a live deck.
+
+If you're sending the deck afterward, add subtitles to slides that rely on your narration. Let the bold-then-dim headlines carry the arc.
+
+---
+
+## Personalizing for the prospect
+
+A generic deck is a dead deck. The minimum viable personalization:
+
+1. **Their logo** on the cover or hook slide. Lead with their brand.
+2. **Their metrics** in the pain section. "Your team of 45" instead of "teams like yours."
+3. **A customer in their industry** in the proof section. If you don't have one, find the closest analog and acknowledge it.
+4. **Their language.** Use the words they used in discovery. If they said "pipeline velocity," use "pipeline velocity." Mirror their exact words.
+5. **Their timeline.** "Ready for your Q3 planning cycle" instead of "whenever you're ready."
+
+The deeper you personalize, the harder it is to say no. It stops being "a sales pitch" and starts being "a plan for us."
+
+---
+
+## Discovery-first selling
+
+The deck is a conversation guide. The best sales meetings use maybe 40% of the slides.
+
+**How to use the deck as a conversation tool:**
+
+- **Open with the hook.** Then pause. Ask: "Does this resonate? Is this what you're seeing?"
+- **Show the pain slide.** Then ask: "What does this cost you? Am I close?"
+- **Skip slides freely.** If they're already convinced of the problem, jump to the solution. If they want proof first, go there.
+- **Let them drive.** If they ask about pricing on slide 3, show them pricing. The structure exists to orient you. Follow the energy in the room.
+- **Use the deck as a whiteboard.** "Let me show you what this looks like for a team like yours." Then walk through the relevant slides.
+
+The worst sales call: you present 35 slides in order while the prospect checks email. The best sales call: you show 8 slides and spend 40 minutes in conversation.
+
+---
+
+## Adapting for deal size
+
+### SMB (< $50K ACV)
+
+- Shorter deck. 10–15 slides max.
+- Skip the "Cost of Inaction" beat or compress it to one stat.
+- Pricing should be on-screen and unambiguous.
+- The ask is immediate: "Start a trial" or "Let's go live next week."
+- Speed matters more than depth.
+
+### Mid-market ($50K–$200K ACV)
+
+- Full nine-beat structure.
+- Two to three proof stories, at least one in their industry.
+- The ask is a defined next step: pilot, technical review, contract.
+- You'll present this 2–3 times to different stakeholders. Make it champion-ready.
+
+### Enterprise / Strategic (> $200K ACV)
+
+- The deck is one artifact in a longer sales process.
+- Add depth to proof: named customers, detailed case studies, ROI models.
+- The "How It Works" section needs more detail: implementation timeline, team requirements, integration points.
+- The ask is a process: "Here's what the next 30 days look like."
+- Consider a separate executive summary (3–5 slides) for the C-suite meeting.
+
+---
+
+## Adapting for format
+
+### Live meeting (you're presenting)
+
+- Lean headlines, minimal body copy. You are the body copy.
+- Use dark slides and quote slides for emphasis. You control the pacing.
+- Skip slides freely based on the conversation.
+- The deck is your back-up singer. You are the lead.
+
+### Async / emailed deck (they're reading alone)
+
+- Add subtitles to every slide. The headline + subtitle should tell the full story.
+- Body copy does more work. Two to three sentences per slide instead of one.
+- The bold-then-dim headlines are even more important. They carry the argument.
+- Include a "How to read this deck" note on slide 2 if the structure is non-obvious.
+- The ask slide needs to be complete: what you're proposing, timeline, how to respond.
+- Consider adding a short Loom or video walkthrough link on the cover slide.
+
+### Follow-up deck (after a discovery call)
+
+- Personalize heavily. Reference things they said.
+- Open with: "Based on our conversation, here's what we heard."
+- Skip the generic pain slides. Replace them with their specific pain.
+- Proof section should be tailored to their objections.
+- The ask should reference the next step you already agreed on.
+
+---
+
+## Handling objections
+
+Keep slides ready for common objections. Know which slide to skip to.
+
+| Objection | Go to |
+|-----------|-------|
+| "We're not sure this is a priority" | Cost of Inaction |
+| "We've tried tools like this before" | Proof (find a customer who switched from their old tool) |
+| "How long does this take to implement?" | How It Works |
+| "It's too expensive" | Go back to Pain + Cost of Inaction, then show pricing in context |
+| "I need to get buy-in from my team" | The champion test: make sure the deck works standalone |
+| "Can you show me how it works?" | Skip ahead to a demo or the How It Works flow |
+| "What about [Competitor]?" | Stay gracious. Go to Proof. Let results speak. |
+
+**The meta-move:** When an objection comes up, stay curious. Ask a question back. "What would you need to see to feel confident about this?" Then show that slide.
+
+---
+
+## Common mistakes
+
+### 1. Leading with your company
+Nobody opens a sales meeting wanting to hear your founding story, your headcount, or your investor list. Start with their problem. They can read your About page later.
+
+### 2. Feature dumping
+Fifteen features on one slide is overwhelming. Three capabilities with clear outcomes beats a feature matrix every time. If they want the full list, send it after.
+
+### 3. No social proof
+Claims without evidence are just opinions. If you don't have named customers, use aggregated metrics. If you don't have metrics, get them before you build the deck.
+
+### 4. Vague CTA
+"Let us know if you'd like to continue the conversation" is a shrug, and prospects treat it like one. Propose something specific. Own the next step.
+
+### 5. Talking about yourself instead of them
+Count the slides. If more than 30% are about your company, your team, your vision, your roadmap, you've lost the thread. Flip it. Make it about their outcomes.
+
+### 6. One deck for everyone
+The deck you show a VP of Sales differs from the one you show a CFO. Personalize. Swap the proof stories. Change the metrics. Adjust the language. Same structure, different flavor.
+
+### 7. No pause for conversation
+If you present for 25 minutes straight without asking a question, you're lecturing. Build pauses into the structure. After the hook. After the pain. After the proof. Ask: "Does this match what you're seeing?"
+
+### 8. Burying the price
+If pricing is complex or hidden, the prospect spends the whole meeting wondering about it instead of listening. Show it clearly. Show it with confidence. Show it in context of the value.
+
+---
+
+## The headline pattern (for sales)
+
+The bold-then-dim pattern is especially powerful in sales because it does two things at once: states the claim and softens the extension.
+
+```html
+<h1>Pipeline grew 40%. <span class="dim">In one quarter.</span></h1>
+<h1>One platform. <span class="dim">Every rep. Every deal.</span></h1>
+<h1>6 weeks to value. <span class="dim">From handshake to results.</span></h1>
+<h1>The bottleneck is visibility. <span class="dim">And it's solvable.</span></h1>
+```
+
+The bold part is the claim. The dim part is the context, the surprise, or the payoff. Together they create a headline with built-in tension.
+
+For sales specifically:
+- **Hook headlines:** Bold = their problem. Dim = the scale of it.
+- **Solution headlines:** Bold = the capability. Dim = what it means for them.
+- **Proof headlines:** Bold = the metric. Dim = the timeframe or context.
+- **Ask headlines:** Bold = the action. Dim = how easy it is.
+
+---
+
+## One more thing
+
+The conversation closes the deal. Every time.
+
+The deck is the scaffolding. It keeps the conversation on track, surfaces the right proof at the right moment, and gives your champion something to carry upstairs. The words you say, the questions you ask, the way you listen, the specificity of your follow-up: that's what actually moves the deal.
+
+Spend 50% of your prep on the deck. 50% on understanding the prospect.
+
+If you know their world better than they expect you to, you won't need a perfect deck. You'll need three slides and a good question.
+
+That's enough.