Sales Narrative Deck

Sales Narrative Deck

When to use

Use this skill when you need to turn positioning, customer research, sales feedback, or product context into a customer-facing sales narrative deck.

Best fit for:

• First-call or discovery-call decks
• Value decks for account executives
• Founder-led sales decks that need to become repeatable
• New product or new buyer GTM stories
• Category, problem, or point-of-view narratives
• Demo-adjacent sales decks where the product should appear early
• Competitive or pricing-ready sales materials

Do not use this skill to make a brand manifesto, investor pitch, internal strategy deck, or generic product tour. The output should help a rep win a real customer conversation.

Inputs

Ask for or infer as much of the following as possible:

• Target audience: buyer, practitioner, influencer, economic buyer, industry, company size
• Audience pains: what is broken, risky, slow, expensive, frustrating, or newly urgent
• Audience needs: what they need to achieve, avoid, prove, or change
• Current solutions: status quo, spreadsheets, internal workarounds, legacy tools, services, competitors
• Product: what you sell, core capabilities, integrations, packaging, pricing motion
• Category or market point of view: the problem you want to own
• Differentiation: why this approach wins versus alternatives
• Proof: customer stories, metrics, logos, quotes, case studies, analyst proof, screenshots
• Sales motion: first call, follow-up, demo, enterprise cycle, transactional motion, land-and-expand
• Objections: budget, priority, change management, incumbent tools, security, IT, ROI
• Demo assets: product areas to show, realistic data, screenshots, flows, or demo environment
• Constraints: deck length, required slides, brand tone, vertical, competitor names, pricing inclusion

If the inputs are thin, produce a useful draft but mark assumptions and proof gaps clearly.

Workflow

1. Identify the real audience.

• Separate practitioners from leaders.
• Serve practitioners with specificity, but help reps win deals with leaders.
• If a new product targets a different buyer, do not reuse the old GTM story. Name the different problems, pains, needs, current solutions, and sales motion.

1. Start with customer truth.

• Lead with the problem, not the product.
• Describe the audience's pains, needs, and current solutions before saying what you sell.
• Use the buyer's language where available.
• Own the problem or category the company wants to be associated with.

1. Teach before pitching.

• Explain the shift in the market, the hidden cost of the status quo, or the new standard buyers should expect.
• Make the buyer feel smarter and seen before asking them to believe the solution.

1. Introduce the product as the logical answer.

• Connect every product claim to a previously established pain or need.
• Focus on what reps can sell now.
• Put fast-follow assets, roadmap, and future vision in notes or appendix unless they are essential to the deal.

1. Build a simple sales story.

• Follow a clear beginning, middle, and end.
• Make the first impression strong: the opening slides should immediately signal relevance.
• Make the ending strong: recap the value and ask for a concrete next step.
• Ensure each slide relates to the one before it.
• Avoid more than three bullets per slide.

1. Design for live selling.

• Write slide titles as the story, not labels.
• Include talk track notes that a rep can actually say.
• Add proof placeholders where evidence is needed.
• Include customer stories, quotes, icons, product shots, pricing, competitive context, and solution slides when they help the rep advance the conversation.

1. Plan the demo moment.

• Get to product early enough that the buyer is not waiting through a long lecture.
• Use realistic data and scenarios.
• Pause and confirm the audience follows.
• Ask discovery questions during the demo.
• Address confusion directly.
• End with a recap slide that ties the demo back to the pain, value, and next step.

Output format

Return a practical deck outline, not polished copy pretending to be final design.

Include:

• Deck purpose and audience
• Core narrative in one paragraph
• Assumptions and missing proof
• Slide-by-slide outline with:
• Slide number
• Slide title written as a message
• Slide goal
• Suggested content, with no more than three bullets where possible
• Talk track notes
• Visual direction, such as icon, diagram, product shot, customer quote, proof, or pricing table
• Discovery question where useful
• Proof placeholder where needed
• Demo moment:
• Where it happens
• What to show
• What realistic data to use
• Questions to ask
• How to transition back to the deck
• Recap and CTA
• Optional appendix slides for pricing, competition, security, implementation, roadmap, or deeper customer proof

Slide and narrative structure

Default first-call deck sequence:

1. Relevance opener

• Show that you understand the buyer's world.
• Name the audience and problem clearly.

1. Problem today

• Explain the practical pain and business impact.
• Include current solutions and why they fall short.

1. What changed

• Teach the market shift or new expectation.
• Make the problem feel urgent without fearmongering.

1. Cost of the status quo

• Connect pain to measurable risk, wasted time, lost revenue, compliance exposure, poor customer experience, or missed execution.

1. New standard or category point of view

• Define what good now looks like.
• Own the problem/category in plain language.

1. Solution introduction

• Say what you sell only after the buyer understands the problem.
• Connect the product directly to the new standard.

1. How it works

• Show the core workflow or architecture.
• Keep it simple enough for a first call.

1. Demo moment

• Move into product early enough to create belief.
• Use realistic data and a buyer-relevant scenario.

1. Proof

• Use customer story, quote, metric, logo, benchmark, or before/after.
• Be explicit about what the proof demonstrates.

1. Why us / why now

• Clarify differentiation against the status quo and competitors.
• Address the buyer's likely objection.

1. Commercial path

• Include packaging, pricing shape, implementation, pilot path, or buying process when appropriate.

1. Recap and CTA

• Summarize the pain, value, proof, and next step.
• Ask for a specific action: technical validation, stakeholder meeting, pilot scoping, business case, or proposal.

Adjust this structure based on the sales motion. A short transactional deck may need 6-8 slides. An enterprise deck may need appendix support for security, architecture, implementation, pricing, and competition.

Demo guidance

A strong sales narrative deck should not hide the product until the end.

Demo rules:

• Get to product early, usually after the problem and point-of-view slides.
• Use realistic data that matches the buyer's world.
• Show one coherent workflow, not a feature inventory.
• Pause after important moments and confirm the audience follows.
• Ask discovery questions while showing product, for example:
• "How does your team handle this today?"
• "Where does this usually break down?"
• "Who needs to trust this output before it moves forward?"
• If the audience looks confused, stop and clarify before continuing.
• Recap what the demo proved before moving to proof, pricing, or next steps.

Quality bar

The deck is good when:

• A rep could use it in a real first call without rewriting the whole story.
• The opening feels immediately relevant to the target audience.
• The story starts with pains, needs, and current solutions before the product.
• The deck educates the buyer before it pitches.
• The company clearly owns a problem or category.
• Each slide naturally follows the previous slide.
• Slide titles tell the story when read by themselves.
• No slide relies on more than three bullets to make its point.
• Product, proof, and pricing appear at the right level of depth for the sales motion.
• The demo moment is specific, realistic, and tied to discovery.
• Practitioners see their daily pain; leaders see business value and risk reduction.
• The CTA is concrete and appropriate for the stage.

Anti-patterns

Avoid:

• Opening with company history, logos, or product architecture before the buyer cares.
• Saying what you sell before naming the audience's problem and current alternatives.
• Creating a generic deck that could fit any SaaS company.
• Treating different buyers as if they share the same pains, needs, and GTM motion.
• Overbuilding a first-call deck with every feature, proof point, and roadmap idea.
• Saving the product demo until the last five minutes.
• Using fake precision or unsupported ROI claims.
• Writing slide titles like "Problem," "Solution," or "Demo" instead of message-led headlines.
• Stuffing slides with more than three bullets.
• Building a beautiful narrative that sales cannot actually sell now.
• Ignoring confusion during the demo.
• Ending without a recap and clear next step.

Source & license

This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.

• Author: adam-lagerhausen
• Source: adam-lagerhausen/b2b-marketing-skills
• License: MIT

Install and usage instructions live in the source repository linked above.