sales-pitch
Sales Pitch (Dunford)
This skill captures the structured sales conversation framework from April Dunford's Sales Pitch. It translates her two-phase pitch model — Setup and Follow-Through — into actionable guidance for building buyer confidence, articulating differentiated value, and closing deals that too often stall due to decision paralysis rather than product weakness.
Core Principle
Buyers don't stall because they dislike your product — they stall because they lack the confidence to choose among alternatives, and your job is to be their market guide, not their salesperson.
Forty to sixty percent of B2B purchase processes end without any decision. Most sales teams attribute this to competitor wins or budget constraints, but the actual culprit is buyer uncertainty about the decision itself. Buyers who can't clearly articulate what makes one option better than another for their situation default to inaction. Traditional pitch formats — product demos, problem-solution decks, feature walkthroughs — do nothing to address this root cause. They assume market literacy the buyer doesn't have.
Dunford's framework flips the script by making market education the opening act of every sales conversation. Before you show your product, you help buyers understand the landscape: what approaches exist, what trade-offs each carries, and what an ideal solution looks like for someone in their position. By the time you introduce your product, buyers already have a mental model for evaluating it — one you helped construct. That's not manipulation; it's the difference between a vendor and a trusted advisor.
Scoring
Goal: 10/10. When reviewing a sales pitch or evaluating sales conversation quality, rate it 0–10:
| Score | Description |
|---|---|
| 0–2 | Pitch is entirely product-centric. Opens with features or a company overview. No market context. No competitive landscape discussion. Buyer has no framework for evaluating what they're seeing. Deals frequently stall or go to "no decision." |
More from tomaszstaniak/pm-ai-skills
continuous-discovery-habits
Product discovery framework based on Teresa Torres'' "Continuous Discovery Habits". Use when you need to: (1) build an opportunity solution tree from desired outcomes, (2) identify and prioritize customer opportunities, (3) design assumption tests for product ideas, (4) structure customer interview snapshots, (5) map assumptions to experiments, (6) move from output-driven to outcome-driven product development, (7) map current-state customer experiences, (8) build a weekly discovery habit.
13good-strategy
Strategy evaluation and design framework based on Richard Rumelt''s "Good Strategy Bad Strategy" and Michael Porter''s "What Is Strategy?". Use when you need to: (1) evaluate whether a strategy is good or bad, (2) diagnose the core challenge before proposing solutions, (3) build a coherent strategy kernel (diagnosis + guiding policy + coherent actions), (4) stress-test strategic plans with pre-mortem analysis, (5) distinguish strategy from goals, ambitions, or wish lists.
10working-backwards
Amazon''s Working Backwards product development method based on Colin Bryar and Bill Carr''s "Working Backwards". Use when you need to: (1) write a PR/FAQ document for a new product or feature, (2) validate an idea by defining the customer experience first, (3) stress-test a proposal with pre-mortem analysis, (4) align stakeholders around a product vision, (5) decide whether an idea is worth building before writing code.
9positioning-and-pitch
Framework based on April Dunford''s "Obviously Awesome" and "Sales Pitch". Use when you need to: (1) define or evaluate product positioning using the five-component framework, (2) translate positioning into a compelling pitch for stakeholders or buyers, (3) choose a market category strategy that shapes what you build and how you compete, (4) develop differentiated value claims that connect product decisions to market reality, (5) structure a pitch for exec reviews, board updates, or partner conversations, (6) diagnose why your product story isn''t landing with customers or internal stakeholders, (7) align cross-functional teams around a shared positioning narrative, (8) connect positioning decisions to roadmap priorities and feature trade-offs
6first-90-days
Leadership transition framework based on Michael D. Watkins'' "The First 90 Days". Use when you need to: (1) plan onboarding for a new leadership or management role, (2) build a 30-60-90 day plan, (3) diagnose the business situation you''re entering (STARS model), (4) plan critical early conversations with your new boss, peers, and team, (5) identify and avoid common transition traps, (6) accelerate time to value in a new role.
5escaping-build-trap
Product management framework based on Melissa Perri''s "Escaping the Build Trap". Use when you need to: (1) diagnose whether a team is stuck in the build trap (shipping features without outcomes), (2) shift from output-driven to outcome-driven product development, (3) evaluate product manager archetypes and team maturity, (4) design a product strategy that connects company vision to team-level decisions, (5) run a pre-mortem on a product roadmap to detect build-trap patterns.
5