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."
3–4	Pitch acknowledges a problem but jumps immediately to the solution. Alternatives exist in the conversation only as targets to attack. Value claims are generic ("saves time," "increases productivity"). No proof matched to customer context.
5–6	Setup exists but is thin — a slide or two on market trends before the demo. Alternatives are mentioned but not fairly characterized. Differentiated value is articulated but not linked to specific capabilities. Proof is present but not customized.
7–8	Clear Setup and Follow-Through separation. Market insight is specific and credible. Alternatives are described honestly with genuine trade-offs. Differentiated value is tied to unique capabilities. Proof matches customer context. Call to action is clear.
9–10	Pitch reads as collaborative market education. Buyer confirms understanding at each Setup stage. Differentiation is narrow, specific, and impossible for competitors to claim. Proof is contextually matched. Champion is enabled to advocate internally. Next steps are concrete.

The Two-Phase Pitch Structure

The core architecture of every sales conversation is a Setup followed by a Follow-Through. These phases serve fundamentally different purposes and must not be collapsed into each other.

The Setup (three components):

1. Market Insight — What your experience in this market has taught you about the problem space
2. Alternatives — An honest tour of approaches buyers can take, including doing nothing
3. Perfect World — What an ideal solution looks like for a buyer in this situation

The Follow-Through (five components): 4. Introduction — Where your product fits in the landscape you just described 5. Differentiated Value — Outcomes only you deliver, compared to alternatives 6. Proof — Evidence matched to the buyer's specific context 7. Objection Handling — Anticipated concerns addressed proactively 8. The Ask — A specific, frictionless next step

Why it works: The Setup creates the mental scaffolding that makes your Follow-Through land. Without context, your differentiation sounds like marketing copy. With it, it sounds like a logical conclusion the buyer reached themselves.

Key insights:

• The Setup can run as short as 90 seconds for educated buyers or extend into deep discovery for complex environments — time is not the measure, alignment is
• You know the Setup is complete when the buyer acknowledges market dynamics, understands trade-offs, and has articulated what they need
• Rushing into Follow-Through before Setup alignment destroys the entire effect — buyers who haven't formed an evaluation framework can't appreciate your differentiation
• Each phase requires different conversational skills: Setup demands listening and market knowledge; Follow-Through demands precision and proof
• The structure applies across formats: sales calls, demos, conference talks, explainer videos, and buyer's guides

Pitch structure applications:

Context	Setup Depth	Follow-Through Focus
Cold outbound call	60–90 seconds, 1–2 key insights	Lead with sharpest differentiation point
First discovery meeting	Full Setup with discovery questions woven in	Tailored to pain uncovered during Setup
Demo to technical evaluators	Setup emphasizes architecture trade-offs	Follow-Through centers on proof and integration depth
Executive sponsor meeting	Setup focuses on business outcomes and risk	Follow-Through emphasizes ROI and strategic fit
Proposal or written follow-up	Setup summarized in context section	Follow-Through as the main body with evidence

Copy patterns:

• "Before I show you what we do, I want to share what we've learned working with companies like yours in this space…"
• "Let me walk you through the approaches your peers are taking — there are really three, and each has a different profile of strengths and trade-offs…"
• "Based on what you've told me, it sounds like the ideal solution for your situation would need to [X, Y, Z]. Does that feel right?"

Ethical boundary: The Setup is not a manipulation technique to pre-condition buyers toward a foregone conclusion. Present alternatives honestly, including their genuine strengths. Buyers who feel set up rather than educated will disengage — and they'll be right to.

See: references/two-phase-pitch-structure.md

Market Insight: Opening With Credibility

The first move in every pitch is a market insight — a specific, experience-grounded observation about the problem space that demonstrates you understand the buyer's world better than they might expect from a vendor.

Why it works: Buyers default to treating sellers as biased sources. Opening with a genuine insight about market dynamics — not a product claim — immediately shifts how they perceive you. You become someone who has seen this problem across many contexts, not someone trying to make a quota. This credibility compounds: everything you say afterward lands with greater weight.

Key insights:

• Generic insights ("digital transformation is accelerating") signal that you haven't done the work; specific insights ("companies in your segment typically discover their current approach breaks down around 50 concurrent users, and by then they've already committed to contracts that are painful to exit") signal genuine expertise
• Insights should connect directly to the buyer's current situation — not all of your market knowledge is relevant to every conversation
• The best insights come from aggregated customer experience: what you've seen repeatedly across dozens of similar implementations
• Insights don't have to be surprising to be effective — often, naming something the buyer vaguely knew but hadn't articulated creates immediate resonance
• If your insight doesn't prompt the buyer to say something like "yes, that's exactly what we're dealing with," it needs refinement

Insight quality applications:

Context	Weak Insight	Strong Insight
SaaS analytics tool	"Companies are drowning in data."	"Most analytics teams we work with hit a wall when data requests from the business start outnumbering analyst capacity — usually around 3:1. At that point, self-serve tools get deployed but adoption stays under 20% because the underlying data model isn't business-user-ready."
DevSecOps platform	"Security is more important than ever."	"The pattern we see in engineering orgs that ship fast is that security debt accumulates in the same three places every time: dependency management, secrets handling, and access reviews. The first two are automatable; the third almost always requires a manual process that nobody owns."
Enterprise HR software	"Talent retention is a challenge."	"The companies coming to us after failed HRIS implementations share one thing: their previous vendor scoped the project around HR users, not managers. Manager adoption predicts whether the system actually changes behavior — and it's almost never in the implementation plan."

Copy patterns:

• "One thing we've learned working with [similar companies] is that…"
• "The pattern we see consistently in this space is…"
• "What surprises most of our customers when they first talk to us is…"

Ethical boundary: Insights must be accurate. Fabricating or exaggerating market observations to create artificial urgency destroys trust faster than any competitor can. If you're uncertain whether an observation is broadly true, present it as a question: "We see this pattern a lot — is that consistent with what you're experiencing?"

Competitive Alternatives: The Honest Market Tour

After establishing your market insight, walk the buyer through the realistic alternatives they face — including the option to do nothing. This is where most sellers panic and either skip the section entirely or use it as an excuse to attack competitors. Both responses damage your credibility.

Why it works: Buyers will evaluate alternatives with or without your help. If you refuse to discuss them, buyers do it alone — using information that may be outdated, biased by analyst reports, or shaped by a competitor's positioning. By guiding the alternatives discussion yourself, you control which criteria matter, ensure your strengths get surfaced fairly, and build trust that you're focused on the buyer's success rather than your close rate.

Key insights:

• Every buyer has at least three alternatives: your competitors, adjacent solutions (e.g., spreadsheets, manual processes), and doing nothing — all three deserve honest characterization
• "Do nothing" is your fiercest competitor and must be treated as an active choice with real costs and trade-offs, not a neutral default
• Acknowledge genuine competitor strengths; buyers know them anyway, and pretending otherwise signals that you're not trustworthy
• Frame alternatives around the trade-offs they impose, not a scoring rubric you've designed to make yourself win
• The goal of this section is for the buyer to leave with a sharper evaluation framework — one that naturally includes your differentiating capabilities as important criteria

Alternatives framework applications:

Alternative Type	How to Present	What to Watch For
Direct competitor	Genuine strengths + where their approach makes trade-offs	Buyer who already has a strong preference — use discovery to understand why
Adjacent/DIY solution	Acknowledge the appeal of control and cost; surface hidden costs	Buyer underestimating total cost of ownership or maintenance burden
Do nothing / status quo	Acknowledge stability; name the active cost of inaction	Buyer who hasn't fully internalized the cost of their current problem
Build in-house	Fair for technical buyers; address ongoing maintenance reality	Engineering-led companies who see "build" as the default answer

Copy patterns:

• "There are really three ways companies in your position approach this. Let me walk through each one honestly, because the right answer genuinely depends on your situation…"
• "Competitor X does this really well, especially if [their strength scenario]. Where that approach runs into friction is [honest trade-off]…"
• "The 'do nothing' path is also worth naming — it's not a neutral choice. What it costs you is [specific outcome], and that compounds over time in these specific ways…"

Ethical boundary: This section fails if it becomes a staged comparison designed to produce a predetermined winner. Buyers who sense a rigged evaluation framework disengage. If your solution genuinely isn't the right fit for this buyer, the honest alternatives discussion will surface that — and that outcome, while not a sale today, builds the kind of reputation that generates referrals.

See: references/competitive-alternatives-framing.md

Differentiated Value: The Only Claims That Win Deals

Differentiated value is the outcome only you can deliver, compared to what the buyer could achieve with the best available alternative. It is not a feature list, a benefits summary, or a generic value proposition.

Why it works: When buyers can't distinguish between options, they either choose on price, choose based on existing relationships, or make no decision at all. All three outcomes are losses for you. Precise differentiation gives buyers a concrete, defensible reason to choose you — one they can articulate to their own stakeholders during internal evaluation.

Key insights:

• The two-question test for every value claim: "So what?" (push until you reach a business outcome) and "Compared to what?" (ensure that outcome is genuinely unique to your approach)
• Differentiation can come from product capabilities, but also from company capabilities: deployment model, professional services quality, integration ecosystem, speed of implementation, or industry-specific expertise
• Narrow differentiation is stronger than broad differentiation — a specific claim about what you uniquely do for a specific type of buyer is more credible than a general claim about being better
• If your differentiation claims could appear verbatim in a competitor's pitch, they're not differentiated
• Differentiated value must connect directly to the unique capabilities you actually have — claims that aren't grounded in real product or company strengths will collapse under technical scrutiny

Differentiated value development:

Starting Point	After "So What?"	After "Compared to What?"
"We have real-time data sync"	"You make decisions on current data instead of yesterday's export"	"Competitors sync on 15-minute intervals, which matters when you're managing live inventory across 3+ warehouses"
"We offer dedicated onboarding"	"Your team reaches value faster and with less internal effort"	"Self-serve onboarding from alternatives takes an average of 6 weeks to first workflow; we average 8 days because our onboarding team handles the data migration"
"Our API is more flexible"	"Your engineering team can build integrations without workarounds"	"The two alternatives require you to use their SDK, which limits integration patterns; ours is REST-based with full documentation and no undocumented rate limits"

Copy patterns:

• "What we do differently — and this is specific to how we've built the product — is…"
• "The reason that matters compared to [alternative] is…"
• "Most [category] tools solve [X]; we're the only ones that also solve [Y], which for companies in your situation means…"

Ethical boundary: Differentiation claims must be accurate and defensible. Overstating uniqueness — especially in technical areas buyers will verify — is not just ethically problematic, it's strategically damaging. A claim you can't back up in a technical evaluation is worse than not making the claim at all.

See: references/differentiated-value-development.md

Proof: Evidence That Matches the Buyer's Context

Proof in a sales pitch isn't a logo wall or a list of customer names. It's contextually matched evidence — case studies, testimonials, data, and demonstrations — that answers the specific question "would this work for someone like me?"

Why it works: Buyers in complex B2B purchases are fundamentally risk-managing. Generic proof that your product works for large enterprises doesn't help a mid-market buyer; a logo from a different industry doesn't speak to a healthcare buyer. When proof is contextually matched, it directly reduces the perceived risk of the decision — which is the actual barrier to closing.

Key insights:

• Match proof to the buyer's profile: company size, industry, use case, and the specific outcome they care most about
• The most effective proof format depends on the buyer's stage: early-stage buyers need conceptual proof (market data, peer benchmarks); late-stage buyers need operational proof (implementation details, migration stories, support responsiveness)
• A single deeply matched case study is worth more than ten logo slides
• Quantified outcomes are stronger than qualitative testimonials — but only if the numbers are credible and context-specific
• Live demos, when structured as proof of specific differentiated value claims rather than feature tours, are among the most powerful proof formats

Proof type applications:

Proof Type	Best Used When	Caution
Customer case study	Buyer is evaluating fit for their specific situation	Must match industry, size, and use case — mismatched case studies raise doubts
Quantified outcome data	Buyer is building an internal business case	Ensure the methodology is defensible; aggregate numbers without context feel fabricated
Technical demo	Buyer's evaluators need to see capability, not hear about it	Demo must prove differentiation, not just feature breadth — a feature tour without context is not proof
Reference call	Buyer has specific concerns they need validated by a peer	Choose references who match the buyer's situation; prepare them for the likely questions
Third-party validation	Buyer distrusts vendor-produced evidence	Analyst coverage, review site ratings, and independent benchmarks carry credibility vendor content can't

Copy patterns:

• "Let me show you what this looked like for [company type similar to buyer] — the situation they were in and what they measured afterward…"
• "I want to show you exactly the thing I claimed we do differently, in the actual product, so you can see how it works rather than just take my word for it…"
• "The number I keep hearing from customers in your segment is [specific metric] — here's where that comes from and why it's typical for your type of deployment…"

Ethical boundary: Do not present proof you haven't verified. Citing case study numbers you can't source, using customer names without permission, or running demos in sanitized environments that don't reflect real product behavior are all forms of deception that surface during due diligence and destroy deals at their most critical moments.

Building the Pitch Storyboard

A pitch storyboard is the working document that assembles all eight components into a coherent narrative before a single slide is designed. It's a cross-functional artifact, not a sales artifact.

Why it works: Pitches built by sales alone tend to overclaim on differentiation (because sales doesn't know what product can and can't do), underclaim on proof (because sales doesn't have access to customer success data), and drift from the company's actual market positioning (because sales adapts messaging to individual deals without coordination). A cross-functional storyboard forces alignment on what's actually true and uniquely valuable — and surfaces disagreements before they reach prospects.

Key insights:

• Include sales, marketing, product, and customer success at minimum; founders or executives add credibility validation for companies where that matters
• Work through all eight components before touching slide design — structure first, format second
• Some components work best as scripted language (the market insight, the differentiated value statement); others work best as conversation prompts (the alternatives discussion, objection handling)
• Test the storyboard with salespeople you respect before testing with any prospect — internal critique is cheaper than prospect confusion
• Watch for components where salespeople struggle to deliver the language naturally — that signals the script is inauthentic, not that the rep is weak
• Expect three to five rounds of revision before the pitch feels solid; one round of feedback rarely surfaces everything

Storyboard building process:

Step	Component	Questions to Answer	Format
1	Market Insight	What have we learned that buyers don't already know? Is it specific? Does it connect to their current situation?	Script
2	Alternatives	What are the realistic options? What are honest trade-offs of each? Where does "do nothing" belong?	Conversation framework
3	Perfect World	What would an ideal solution look like for a buyer in this situation? What criteria should they care about?	Conversation prompts
4	Introduction	Where do we sit in the landscape we just described? What makes this the right moment to introduce our product?	Script
5	Differentiated Value	What do we uniquely deliver, for whom, compared to what? Has each claim passed the "so what / compared to what" test?	Script + visual
6	Proof	What evidence matches this buyer's context? Which format — case study, demo, data, reference — fits best?	Slide + demo
7	Objections	What concerns will this buyer raise? What are the honest, complete responses?	Conversation framework
8	The Ask	What is the specific next step? Is it clear, low-friction, and appropriately sized for where we are?	Script

Ethical boundary: Storyboards should reflect what your product and company actually deliver. The cross-functional process is an opportunity to pressure-test claims against reality — use it. A storyboard built on aspirational rather than current capabilities sets up sales reps to overpromise and customers to be disappointed.

See: references/pitch-storyboard-process.md

Positioning as the Foundation of Every Pitch

Dunford's framework connects directly to the five components of positioning from Obviously Awesome: competitive alternatives, unique capabilities, differentiated value, best-fit customers, and market category. A sales pitch without grounded positioning is a house without a foundation.

Why it works: Positioning determines what you say; the pitch determines how you say it. When these two are misaligned — when marketing positioning says one thing and salespeople pitch another — buyers encounter contradictory signals across touchpoints. That inconsistency reads as organizational dysfunction and erodes trust. When they're aligned, every interaction reinforces the same clear story.

Key insights:

• Your understanding of competitive alternatives in your positioning work directly feeds the alternatives section of your Setup
• Your unique capabilities (from positioning) are the raw material for differentiated value claims in the Follow-Through
• Your best-fit customer definition guides how you customize the pitch — which insights are relevant, which proof to lead with, which objections to anticipate
• Your market category choice shapes how buyers frame the decision — a category they understand requires less Setup; a new or repositioned category requires more
• If your sales pitch and your marketing positioning tell different stories about what you are and who you're for, fix positioning first

Positioning-to-pitch translation:

Positioning Component	Pitch Location	Translation
Competitive alternatives	Setup — Alternatives	The realistic options you walk buyers through honestly
Unique capabilities	Follow-Through — Differentiated Value (input)	The specific product or company capabilities that make your differentiation real
Differentiated value	Follow-Through — Differentiated Value (output)	The business outcomes those capabilities create, compared to alternatives
Best-fit customers	Pitch customization	Which insights, proof, and objections are relevant for this specific buyer
Market category	Setup — Market Insight + Introduction	How you frame the problem space and where you introduce yourself in it

Copy patterns:

• "We sit in the [category] space, which means you're probably also looking at [alternatives]. Let me share how we think about where they each fit…"
• "The companies that get the most value from us are specifically those who [best-fit criteria] — which is why I was interested to talk with you, because you match that profile…"

Ethical boundary: Do not use positioning to artificially inflate your market category to seem larger or more established than you are. Buyers who discover the category inflation — through analyst research or competitor conversations — lose confidence in everything else you've told them.

See: references/positioning-to-pitch-translation.md

Common Mistakes

Mistake	Why It Fails	Fix
Opening with a company overview or product demo	Gives buyers no framework for evaluation; positions you as a vendor, not an advisor	Start with market insight; earn the right to show your product
Generic market insights	"Data is growing" or "security matters" could come from any competitor; creates no differentiation or credibility	Ground insights in specific patterns observed across your actual customer base
Skipping the alternatives discussion	Buyers evaluate alternatives anyway — without your guidance, they use weaker information	Walk through alternatives honestly; your credibility depends on it
Treating "do nothing" as neutral	Inaction has real costs that compound; not naming them lets buyers underweight the cost of their status quo	Frame "do nothing" as an active choice with specific, quantified consequences
Weak or generic differentiation	"We're faster, easier, and more reliable" could describe any product in any category	Run every value claim through "so what?" and "compared to what?" until claims are narrow and specific
Proof that doesn't match the buyer	A logo from a Fortune 500 doesn't reassure a 50-person startup; an enterprise case study doesn't address a mid-market buyer's concerns	Build a proof library organized by buyer segment, use case, and concern — and select accordingly
Collapsing Setup and Follow-Through	Jumping to your product before buyers have formed an evaluation framework means differentiation lands as marketing copy	Treat Setup as complete only when buyers confirm alignment on market dynamics
Vague or multi-step calls to action	"I'll follow up soon" or "let us know if you want to continue" creates friction and delays momentum	Define a specific next step with a date, owner, and clear outcome — make it easy to say yes
Pitching the champion as if they're the final decision-maker	Champions need to advocate internally; if they can't explain your differentiation to others, they can't close	Equip champions with specific, repeatable language and supporting materials for internal conversations
Building the pitch without cross-functional input	Sales-only pitches overclaim on differentiation and miss proof assets that customer success and product know about	Run the storyboard process with marketing, product, and customer success before finalizing

Quick Diagnostic

Question	If No	Action
Does your pitch open with a market insight before mentioning your product?	You're leading with a vendor posture	Develop 2–3 specific, experience-grounded insights; open every conversation with one
Does your pitch include an honest tour of alternatives, including their genuine strengths?	Buyers learn about alternatives elsewhere, with less favorable framing for you	Map the realistic alternative landscape; practice articulating each option's honest trade-offs
Does your pitch explicitly address "do nothing" as an alternative with real costs?	Buyer inertia is your largest competitor and you're not competing against it	Quantify the cost of the status quo; make inaction feel like a choice with consequences
Can you state your differentiated value in one sentence that names a specific outcome and names the comparison point?	You're competing on features or price without knowing it	Apply the "so what / compared to what" test to every value claim until you reach specificity
Is your proof (case studies, demos, data) matched to this specific buyer's industry, size, and use case?	Generic proof reduces rather than increases buyer confidence	Build a segmented proof library; select evidence that answers "would this work for someone like me?"
Does your call to action name a specific next step with a date and a clear outcome?	Decision momentum stalls after the pitch	Define the ask before every meeting; make the next step as low-friction as possible
Was your pitch built with input from marketing, product, and customer success — not just sales?	You're likely overclaiming on differentiation or missing key proof assets	Run a storyboard session with cross-functional stakeholders before the next pitch revision
Has your pitch been tested with actual sales reps before going to prospects?	Scripts that feel right to the author often feel unnatural to the people who deliver them	Test delivery with reps you trust; revise anything they can't deliver authentically
Does your pitch align with your current marketing positioning on competitive alternatives, value, and best-fit customers?	Buyers encounter contradictory messages across touchpoints	Audit pitch against positioning; resolve conflicts before they reach prospects
Have you reviewed and updated your pitch in the last 90 days?	Market dynamics shift; an outdated pitch signals you're not current	Set a quarterly pitch review with cross-functional stakeholders; update immediately after significant market events

Reference Files

• Two-Phase Pitch Structure — Detailed breakdown of all eight pitch components with templates, timing guidance, and worked examples for common B2B software scenarios
• Competitive Alternatives Framing — Step-by-step process for mapping and presenting competitive alternatives honestly, including how to handle "do nothing" and prospects with existing vendor preferences
• Differentiated Value Development — Worksheets and worked examples for running the "so what / compared to what" process, identifying weak claims, and building a differentiation statement library
• Pitch Storyboard Process — Facilitation guide for cross-functional storyboard sessions, including agenda, decision templates, and testing protocols for new and revised pitches
• Positioning to Pitch Translation — Framework for connecting the five positioning components from Obviously Awesome directly to pitch elements, with audit checklist and alignment diagnostic

Further Reading

• Sales Pitch by April Dunford — Primary source for this skill
• Obviously Awesome by April Dunford — Prerequisite reading; establishes the five-component positioning framework that Sales Pitch applies to sales conversations
• The Challenger Sale by Matthew Dixon and Brent Adamson — Complementary approach to teaching customers something new; useful contrast to Dunford's confidence-building model
• SPIN Selling by Neil Rackham — Questioning framework for the discovery and Setup phases; adds tactical depth to uncovering buyer needs

About the Author

April Dunford is a positioning consultant and former VP of Marketing who has led go-to-market strategy for over two dozen B2B technology companies. She developed the positioning framework in Obviously Awesome from fifteen years of first-hand experience repositioning products at companies ranging from early-stage startups to IBM. Sales Pitch extends that positioning work into the sales conversation layer, drawing on her consulting work helping sales teams translate strong positioning into pitches that actually close.