Reviews and Expert Analysis · book-summary

Sell with a Story by Paul Smith — Cliff Notes Summary

👁 0 views📖 2,316 words⏱ 11 min read5/31/2026

Direct Answer

Sell with a Story: How to Capture Attention, Build Trust, and Close the Sale by Paul Smith (AMACOM, 2016) is the most operational sales-storytelling playbook ever written. Smith — a former Procter & Gamble communications executive turned corporate storytelling consultant — argues that every seller needs a Story Bank of 25 specific stories, organized into six categories (Introduction, Trust-Building, Discovery, Demo, Objection-Handling, Closing), each constructed from a nine-component Story Structure (Hook, Backstory, Challenge, Conflict, Solution, Resolution, Lesson, Action, Connection-to-Product).

The thesis is unromantic: persuasion is not an art, it is a parts list. The book matters because it is the only sales-storytelling text that names exactly which story to deploy at which moment of a deal — turning the abstract advice from Chip and Dan Heath's Made to Stick and Simon Sinek's Start with Why into a slot-fillable kit any rep can use on Monday morning.

1. Foundations — Why Stories Outsell Facts

1.1 Chapter 1 — The Case for Storytelling in Sales

Smith opens with neuroscience and Stanford research from Jennifer Aaker showing stories are remembered up to 22 times more than facts alone. He frames the modern buyer's problem: a typical B2B prospect sits through six vendor pitches in a week and forgets the slide deck within 48 hours.

Stories survive because they encode emotion and sequence, which is how human memory actually files information. The chapter sets the operational claim: "Sellers without a Story Bank are like surgeons without instruments."

1.2 Chapter 2 — What a Sales Story Is (and Isn't)

A sales story is not a war story, a brag, or a case study read aloud. It is a short, structured narrative — usually 60-120 seconds — that puts a named hero into a concrete conflict and resolves it with a lesson the buyer can apply. Smith dismisses three common imposters: the feature dump disguised as a story, the vague success story with no named protagonist, and the monologue with no buyer-facing lesson.

A real sales story passes the "so what?" test in the first ten seconds.

1.3 Chapter 3 — The 25-Story Inventory

Smith introduces the headline claim: every sales meeting has 25 distinct moments where a story would land — and most reps tell zero. The remainder of the book is a slot-by-slot playbook for filling those 25 moments with rehearsed, on-brand narratives.

2. The Six Categories of Sales Stories

2.1 Introduction Stories (Stories 1-4)

These are the four stories every rep needs in the first five minutes of any new buyer conversation: Who You Are, What You Do, Why You're Here, and Why You Care. Smith calls these the "airport elevator set" because each must fit a 90-second window. Who You Are is your origin story compressed to a hook; What You Do translates your job title into a customer-relevant verb; Why You're Here explains the specific reason this meeting exists; Why You Care is the emotional anchor that separates you from the next vendor.

2.2 Trust-Building Stories (Stories 5-7)

Personal Vulnerability, Why You Were Hired, and Lesson You Learned. The Vulnerability story is counterintuitive — Smith argues that admitting a small, relevant failure within the first 20 minutes raises buyer trust scores more than any credential. Why You Were Hired establishes that someone with skin in the game already bet on you.

Lesson You Learned demonstrates you metabolize experience — you are not selling them version 1.0 of your judgment.

2.3 Discovery Stories (Stories 8-10)

Why Should I Care, Industry Trend, and Future-State Vision. These are the stories that earn the right to ask diagnostic questions. The Industry Trend story positions you as a peer, not a vendor. The Future-State Vision lets the buyer try on a world in which the problem is solved before you have priced anything.

2.4 Demo Stories (Stories 11-13)

Product Origin, Use-Case Hero, and Side-by-Side Comparison. The Product Origin story explains the founder's frustration that birthed the product — Smith cites James Dyson's 5,127 failed prototypes as the canonical example. The Use-Case Hero story names a real customer, a real metric, and a real before/after.

Side-by-Side Comparison is the only story type where naming a competitor is permitted, and even then only through a third-party protagonist's voice.

2.5 Objection-Handling Stories (Stories 14-16)

Past Objection-Handled, Risk-Mitigation, and Better Alternative. These are pre-loaded responses to the five or six objections every rep hears weekly. The discipline: when you hear the objection, you do not argue — you say "that reminds me of a customer who said exactly that" and tell the rehearsed story.

2.6 Closing Stories (Stories 17-25)

The final nine slots — Decision-Maker Resolution, Implementation Success, Long-Term ROI, plus six situational closers covering procurement, legal, security review, executive sponsorship, the unexpected stakeholder, and the renewal-year retrospective. Long-Term ROI is the most underused: a story about a customer who is still benefiting three years later beats any spreadsheet projection.

3. The Nine-Component Story Structure

3.1 Hook, Backstory, Challenge

Every story opens with a Hook — a single sentence designed to interrupt the buyer's attention pattern. Smith insists "hook in the first 7 seconds or you've lost the buyer." The Backstory is the minimum context the buyer needs — usually two sentences naming the protagonist, their role, and the year.

The Challenge is the stakes: what would have gone wrong if nothing changed.

3.2 Conflict, Solution, Resolution

The Conflict is the specific obstacle — a competitor, a regulatory deadline, a hostile CFO, a failed previous attempt. The Solution is what the hero tried (often, but not always, your product). The Resolution is the measurable outcome — revenue saved, weeks recovered, audit passed. Without a quantified Resolution, the story is anecdote.

3.3 Lesson, Action, Connection-to-Product

The Lesson is the universal principle the story dramatizes — buyers remember lessons even when they forget protagonists. The Action tells the buyer exactly what to do next ("what I'd suggest you do is..."). The Connection-to-Product is the final beat — the one sentence that links the lesson back to your offering without sounding like an ad.

Smith warns that 90% of sales stories die at the Connection-to-Product step because the rep panics and lurches into a feature pitch.

4. Building and Maintaining the Story Bank

Smith devotes three chapters to the operational discipline of the Story Bank itself — the physical or digital library where the 25 stories live. He recommends a single document (or a tool like Notion, Highspot, or Seismic) with one page per story, each containing: the title, the trigger (when to tell it), the 9-component breakdown, the estimated duration, and a last-rehearsed date.

He insists on monthly rehearsal — stories degrade the same way muscles do. A rep who has not told a story in 90 days will fumble the Hook every time.

5. The Story Spine — Smith's Drafting Shortcut

For reps who freeze when asked to write a story from scratch, Smith borrows improv teacher Kenn Adams's Story Spine: "Once upon a time… Every day… But one day… Because of that… Because of that… Until finally… And ever since then…" The Spine is not the finished story — it is a drafting scaffold that forces a beginning, escalation, climax, and resolution.

Smith demonstrates the Spine on a W.W. Grainger procurement story and a General Electric services-renewal story, showing how the same scaffold produces wildly different finished narratives.

6. Delivery — Voice, Pace, and the Verbatim Trap

The final operational chapter covers delivery mechanics: pause before the Hook, slow down on the Conflict, drop your voice on the Resolution, make eye contact on the Lesson. Smith warns against the "verbatim trap" — reps who memorize stories word-for-word sound robotic.

The Story Bank stores the structure and the key phrases, not a script. Rehearse the beats; improvise the words.

7. Story Types Organized by Sales-Process Stage

flowchart TD A[New Buyer Conversation] --> B[Intro Stories 1-4] B --> B1[Who You Are] B --> B2[What You Do] B --> B3[Why You're Here] B --> B4[Why You Care] A --> C[Trust-Building 5-7] C --> C1[Personal Vulnerability] C --> C2[Why You Were Hired] C --> C3[Lesson You Learned] A --> D[Discovery 8-10] D --> D1[Why Should I Care] D --> D2[Industry Trend] D --> D3[Future-State Vision] A --> E[Demo 11-13] E --> E1[Product Origin] E --> E2[Use-Case Hero] E --> E3[Side-by-Side] A --> F[Objection 14-16] F --> F1[Past Objection-Handled] F --> F2[Risk-Mitigation] F --> F3[Better Alternative] A --> G[Closing 17-25] G --> G1[Decision-Maker Resolution] G --> G2[Implementation Success] G --> G3[Long-Term ROI] G --> G4[Procurement / Legal / Security / Sponsor / Renewal]

Frameworks at a Glance

The 25 Sales Stories — the master inventory every rep maintains in a personal Story Bank.
The Six Categories — Introduction, Trust-Building, Discovery, Demo, Objection-Handling, Closing.
The 9-Component Story Structure — Hook, Backstory, Challenge, Conflict, Solution, Resolution, Lesson, Action, Connection-to-Product.
The Story Spine (borrowed from Kenn Adams) — Once upon a time / Every day / But one day / Because of that / Until finally / And ever since then.
Story Bank discipline — one page per story, monthly rehearsal, last-rehearsed date tracked.
The 7-Second Hook rule — if the opening sentence does not interrupt attention, the story is dead on arrival.
The "so what?" test — every story must pass it within the first ten seconds.

The Per-Call Storytelling Operating Loop

flowchart LR A[Pre-Call: Pick 3-5 Stories from Bank] --> B[Opening: Intro Story + Trust Story] B --> C[Discovery: Industry Trend Story] C --> D[Demo: Use-Case Hero Story] D --> E[Objection Surfaces] E --> F[Deploy Pre-Loaded Objection Story] F --> G[Close: Long-Term ROI Story] G --> H[Post-Call: Log Which Stories Landed] H --> I[Monthly: Rehearse + Refresh Bank] I --> A

What Holds Up, What Has Aged

What holds up: the 25-story inventory, the 9-component structure, and the Story Bank discipline are timeless. The Hook-Conflict-Resolution-Lesson backbone maps cleanly onto any communication medium — Zoom, Loom, LinkedIn DM, voice note. Smith's insistence that stories beat statistics has only strengthened as buyer attention has fragmented.

What has aged: Smith's 2016 examples assume in-person meetings and 30-60 minute discovery calls. Modern B2B selling has compressed story budgets to 60-90 seconds for Zoom-call attention spans, and async video has displaced many of the live-storytelling moments the book describes.

The Story Bank itself is now a Notion, Highspot, or Seismic library with tagged metadata, not a Word document. ChatGPT and Claude can scaffold first-draft stories from a few inputs, but they cannot source the authentic Backstory or Resolution — those still require real customer interviews.

Finally, Smith's chapter on cold-call openers reads as quaint; the modern equivalent is a personalized LinkedIn voice note, but the 9-component structure inside it is identical.

FAQ

How long should a sales story be? Smith's target is 60-120 seconds in a live call, compressed to 45-60 seconds on a modern Zoom call. Anything longer and you have lost the buyer; anything shorter and you have skipped a structural component.

Do I really need all 25 stories? Yes, eventually — but Smith recommends building the Introduction four and the Trust-Building three first, because those seven cover the opening five minutes of every new conversation. The remaining 18 can be built over a quarter.

What if I do not have a great customer story yet? Borrow one from a colleague, a published case study, or a marketing-approved reference. Smith insists you credit the source ("a colleague of mine had a customer who...") rather than fabricate.

How is Sell with a Story different from Lead with a Story? Smith's earlier Lead with a Story (2012) targets leaders and executives — stories for vision, change, and culture. Sell with a Story (2016) is the sales-rep-specific application — narrower audience, more operational, more slot-by-slot.

Where does this book sit relative to StoryBrand and Stories That Stick? Donald Miller's StoryBrand (2017) is marketing-positioning storytelling. Kindra Hall's Stories That Stick (2019) is the executive-keynote version. Smith's book is the only one that maps stories to specific deal stages with a rehearsed inventory.

Can AI write my sales stories? AI can scaffold the 9-component skeleton from inputs, but the Backstory (real protagonist) and Resolution (real metric) must come from human customer research. Smith would call AI-generated stories without sourced inputs "fiction wearing a tie."

Bottom Line

Read Sell with a Story if you are a B2B seller who has ever frozen when a prospect asked "can you give me an example?" Monday morning, list the 25 story slots in a Notion doc, fill in the first seven from your existing wins, and rehearse them once a week for a quarter. By month three, you will have a Story Bank that compounds across every deal you run.

In the modern sales canon, Smith sits between Daniel Pink's To Sell is Human (the philosophy) and Kindra Hall's Stories That Stick (the keynote version) — but for an individual seller looking for parts and instructions, this is the only book that ships with the full kit.

Sources

Paul Smith — *Sell with a Story: How to Capture Attention, Build Trust, and Close the Sale* (AMACOM, 2016)
Paul Smith — *Lead with a Story: A Guide to Crafting Business Narratives* (AMACOM, 2012) — author's prior volume
Chip Heath & Dan Heath — *Made to Stick: Why Some Ideas Survive and Others Die* (Random House, 2007) — academic foundation for SUCCESs framework
Daniel Pink — *To Sell Is Human: The Surprising Truth About Moving Others* (Riverhead, 2012) — modern sales-philosophy companion
Simon Sinek — *Start with Why: How Great Leaders Inspire Everyone to Take Action* (Portfolio, 2009) — the Why-You-Care story foundation
Kindra Hall — *Stories That Stick: How Storytelling Can Captivate Customers, Influence Audiences, and Transform Your Business* (HarperCollins Leadership, 2019) — executive-keynote descendant
Donald Miller — *Building a StoryBrand: Clarify Your Message So Customers Will Listen* (HarperCollins Leadership, 2017) — marketing-positioning application
Andy Raskin — *The Greatest Sales Deck I've Ever Seen* (Medium, 2016) — Strategic Narrative framework, the enterprise-positioning cousin
Jennifer Aaker — Stanford Graduate School of Business research on narrative memory retention
Kenn Adams — originator of the Story Spine improv framework Smith borrows

Keep reading

Download:

### Direct Answer

**Sell with a Story: How to Capture Attention, Build Trust, and Close the Sale** by **Paul Smith** (**AMACOM, 2016**) is the most operational sales-storytelling playbook ever written. Smith — a former **Procter & Gamble** communications executive turned corporate storytelling consultant — argues that **every seller needs a Story Bank of 25 specific stories**, organized into **six categories** (**Introduction, Trust-Building, Discovery, Demo, Objection-Handling, Closing**), each constructed from a **nine-component Story Structure** (**Hook, Backstory, Challenge, Conflict, Solution, Resolution, Lesson, Action, Connection-to-Product**). The thesis is unromantic: persuasion is not an art, it is a parts list. The book matters because it is the only sales-storytelling text that names exactly which story to deploy at which moment of a deal — turning the abstract advice from **Chip and Dan Heath's Made to Stick** and **Simon Sinek's Start with Why** into a slot-fillable kit any rep can use on Monday morning.

## 1. Foundations — Why Stories Outsell Facts

### 1.1 Chapter 1 — The Case for Storytelling in Sales

Smith opens with neuroscience and **Stanford research from Jennifer Aaker** showing stories are remembered up to **22 times more than facts alone**. He frames the modern buyer's problem: a typical B2B prospect sits through six vendor pitches in a week and forgets the slide deck within 48 hours. Stories survive because they encode emotion and sequence, which is how human memory actually files information. The chapter sets the operational claim: **"Sellers without a Story Bank are like surgeons without instruments."**

### 1.2 Chapter 2 — What a Sales Story Is (and Isn't)

A sales story is **not** a war story, a brag, or a case study read aloud. It is a **short, structured narrative** — usually 60-120 seconds — that puts a named hero into a concrete conflict and resolves it with a lesson the buyer can apply. Smith dismisses three common imposters: the **feature dump disguised as a story**, the **vague success story with no named protagonist**, and the **monologue with no buyer-facing lesson**. A real sales story passes the **"so what?" test** in the first ten seconds.

### 1.3 Chapter 3 — The 25-Story Inventory

Smith introduces the headline claim: **every sales meeting has 25 distinct moments where a story would land** — and **most reps tell zero**. The remainder of the book is a slot-by-slot playbook for filling those 25 moments with rehearsed, on-brand narratives.

## 2. The Six Categories of Sales Stories

### 2.1 Introduction Stories (Stories 1-4)

These are the four stories every rep needs in the first five minutes of any new buyer conversation: **Who You Are**, **What You Do**, **Why You're Here**, and **Why You Care**. Smith calls these the **"airport elevator set"** because each must fit a 90-second window. **Who You Are** is your origin story compressed to a hook; **What You Do** translates your job title into a customer-relevant verb; **Why You're Here** explains the specific reason this meeting exists; **Why You Care** is the emotional anchor that separates you from the next vendor.

### 2.2 Trust-Building Stories (Stories 5-7)

**Personal Vulnerability**, **Why You Were Hired**, and **Lesson You Learned**. The Vulnerability story is counterintuitive — Smith argues that admitting a small, relevant failure within the first 20 minutes raises buyer trust scores more than any credential. **Why You Were Hired** establishes that someone with skin in the game already bet on you. **Lesson You Learned** demonstrates you metabolize experience — you are not selling them version 1.0 of your judgment.

### 2.3 Discovery Stories (Stories 8-10)

**Why Should I Care**, **Industry Trend**, and **Future-State Vision**. These are the stories that earn the right to ask diagnostic questions. The **Industry Trend** story positions you as a peer, not a vendor. The **Future-State Vision** lets the buyer try on a world in which the problem is solved before you have priced anything.

### 2.4 Demo Stories (Stories 11-13)

**Product Origin**, **Use-Case Hero**, and **Side-by-Side Comparison**. The **Product Origin** story explains the founder's frustration that birthed the product — Smith cites **James Dyson's 5,127 failed prototypes** as the canonical example. The **Use-Case Hero** story names a real customer, a real metric, and a real before/after. **Side-by-Side Comparison** is the only story type where naming a competitor is permitted, and even then only through a third-party protagonist's voice.

### 2.5 Objection-Handling Stories (Stories 14-16)

**Past Objection-Handled**, **Risk-Mitigation**, and **Better Alternative**. These are pre-loaded responses to the five or six objections every rep hears weekly. The discipline: when you hear the objection, you do not argue — you say "**that reminds me of a customer who said exactly that**" and tell the rehearsed story.

### 2.6 Closing Stories (Stories 17-25)

The final nine slots — **Decision-Maker Resolution**, **Implementation Success**, **Long-Term ROI**, plus six situational closers covering procurement, legal, security review, executive sponsorship, the unexpected stakeholder, and the renewal-year retrospective. **Long-Term ROI** is the most underused: a story about a customer who is still benefiting three years later beats any spreadsheet projection.

## 3. The Nine-Component Story Structure

### 3.1 Hook, Backstory, Challenge

Every story opens with a **Hook** — a single sentence designed to interrupt the buyer's attention pattern. Smith insists **"hook in the first 7 seconds or you've lost the buyer."** The **Backstory** is the minimum context the buyer needs — usually two sentences naming the protagonist, their role, and the year. The **Challenge** is the stakes: what would have gone wrong if nothing changed.

### 3.2 Conflict, Solution, Resolution

The **Conflict** is the specific obstacle — a competitor, a regulatory deadline, a hostile CFO, a failed previous attempt. The **Solution** is what the hero tried (often, but not always, your product). The **Resolution** is the measurable outcome — revenue saved, weeks recovered, audit passed. Without a quantified Resolution, the story is anecdote.

### 3.3 Lesson, Action, Connection-to-Product

The **Lesson** is the universal principle the story dramatizes — buyers remember lessons even when they forget protagonists. The **Action** tells the buyer exactly what to do next ("**what I'd suggest you do is...**"). The **Connection-to-Product** is the final beat — the one sentence that links the lesson back to your offering without sounding like an ad. Smith warns that 90% of sales stories die at the Connection-to-Product step because the rep panics and lurches into a feature pitch.

## 4. Building and Maintaining the Story Bank

Smith devotes three chapters to the operational discipline of the **Story Bank** itself — the physical or digital library where the 25 stories live. He recommends a single document (or a tool like **Notion**, **Highspot**, or **Seismic**) with one page per story, each containing: the **title**, the **trigger** (when to tell it), the **9-component breakdown**, the **estimated duration**, and a **last-rehearsed date**. He insists on monthly rehearsal — stories degrade the same way muscles do. A rep who has not told a story in 90 days will fumble the Hook every time.

## 5. The Story Spine — Smith's Drafting Shortcut

For reps who freeze when asked to write a story from scratch, Smith borrows improv teacher **Kenn Adams's Story Spine**: **"Once upon a time… Every day… But one day… Because of that… Because of that… Until finally… And ever since then…"** The Spine is not the finished story — it is a drafting scaffold that forces a beginning, escalation, climax, and resolution. Smith demonstrates the Spine on a **W.W. Grainger** procurement story and a **General Electric** services-renewal story, showing how the same scaffold produces wildly different finished narratives.

## 6. Delivery — Voice, Pace, and the Verbatim Trap

The final operational chapter covers delivery mechanics: **pause before the Hook**, **slow down on the Conflict**, **drop your voice on the Resolution**, **make eye contact on the Lesson**. Smith warns against the **"verbatim trap"** — reps who memorize stories word-for-word sound robotic. The Story Bank stores the structure and the key phrases, not a script. Rehearse the beats; improvise the words.

## 7. Story Types Organized by Sales-Process Stage

```mermaid
flowchart TD
    A[New Buyer Conversation] --> B[Intro Stories 1-4]
    B --> B1[Who You Are]
    B --> B2[What You Do]
    B --> B3[Why You're Here]
    B --> B4[Why You Care]
    A --> C[Trust-Building 5-7]
    C --> C1[Personal Vulnerability]
    C --> C2[Why You Were Hired]
    C --> C3[Lesson You Learned]
    A --> D[Discovery 8-10]
    D --> D1[Why Should I Care]
    D --> D2[Industry Trend]
    D --> D3[Future-State Vision]
    A --> E[Demo 11-13]
    E --> E1[Product Origin]
    E --> E2[Use-Case Hero]
    E --> E3[Side-by-Side]
    A --> F[Objection 14-16]
    F --> F1[Past Objection-Handled]
    F --> F2[Risk-Mitigation]
    F --> F3[Better Alternative]
    A --> G[Closing 17-25]
    G --> G1[Decision-Maker Resolution]
    G --> G2[Implementation Success]
    G --> G3[Long-Term ROI]
    G --> G4[Procurement / Legal / Security / Sponsor / Renewal]
```

## Frameworks at a Glance

- **The 25 Sales Stories** — the master inventory every rep maintains in a personal Story Bank.
- **The Six Categories** — **Introduction**, **Trust-Building**, **Discovery**, **Demo**, **Objection-Handling**, **Closing**.
- **The 9-Component Story Structure** — **Hook, Backstory, Challenge, Conflict, Solution, Resolution, Lesson, Action, Connection-to-Product**.
- **The Story Spine** (borrowed from **Kenn Adams**) — **Once upon a time / Every day / But one day / Because of that / Until finally / And ever since then**.
- **Story Bank discipline** — one page per story, monthly rehearsal, last-rehearsed date tracked.
- **The 7-Second Hook rule** — if the opening sentence does not interrupt attention, the story is dead on arrival.
- **The "so what?" test** — every story must pass it within the first ten seconds.

## The Per-Call Storytelling Operating Loop

```mermaid
flowchart LR
    A[Pre-Call: Pick 3-5 Stories from Bank] --> B[Opening: Intro Story + Trust Story]
    B --> C[Discovery: Industry Trend Story]
    C --> D[Demo: Use-Case Hero Story]
    D --> E[Objection Surfaces]
    E --> F[Deploy Pre-Loaded Objection Story]
    F --> G[Close: Long-Term ROI Story]
    G --> H[Post-Call: Log Which Stories Landed]
    H --> I[Monthly: Rehearse + Refresh Bank]
    I --> A
```

## What Holds Up, What Has Aged

**What holds up:** the 25-story inventory, the 9-component structure, and the Story Bank discipline are timeless. The Hook-Conflict-Resolution-Lesson backbone maps cleanly onto any communication medium — Zoom, Loom, LinkedIn DM, voice note. Smith's insistence that stories beat statistics has only strengthened as buyer attention has fragmented.

**What has aged:** Smith's 2016 examples assume in-person meetings and 30-60 minute discovery calls. Modern B2B selling has compressed story budgets to **60-90 seconds for Zoom-call attention spans**, and async video has displaced many of the live-storytelling moments the book describes. The Story Bank itself is now a **Notion**, **Highspot**, or **Seismic** library with tagged metadata, not a Word document. **ChatGPT** and **Claude** can scaffold first-draft stories from a few inputs, but they cannot source the authentic **Backstory** or **Resolution** — those still require real customer interviews. Finally, Smith's chapter on cold-call openers reads as quaint; the modern equivalent is a personalized LinkedIn voice note, but the 9-component structure inside it is identical.

## FAQ

**How long should a sales story be?** Smith's target is **60-120 seconds** in a live call, compressed to **45-60 seconds** on a modern Zoom call. Anything longer and you have lost the buyer; anything shorter and you have skipped a structural component.

**Do I really need all 25 stories?** Yes, eventually — but Smith recommends building the **Introduction four and the Trust-Building three first**, because those seven cover the opening five minutes of every new conversation. The remaining 18 can be built over a quarter.

**What if I do not have a great customer story yet?** Borrow one from a colleague, a published case study, or a marketing-approved reference. Smith insists you credit the source ("**a colleague of mine had a customer who...**") rather than fabricate.

**How is Sell with a Story different from Lead with a Story?** Smith's earlier **Lead with a Story (2012)** targets leaders and executives — stories for vision, change, and culture. **Sell with a Story (2016)** is the sales-rep-specific application — narrower audience, more operational, more slot-by-slot.

**Where does this book sit relative to StoryBrand and Stories That Stick?** **Donald Miller's StoryBrand (2017)** is marketing-positioning storytelling. **Kindra Hall's Stories That Stick (2019)** is the executive-keynote version. Smith's book is the only one that maps stories to specific deal stages with a rehearsed inventory.

**Can AI write my sales stories?** AI can scaffold the 9-component skeleton from inputs, but the **Backstory** (real protagonist) and **Resolution** (real metric) must come from human customer research. Smith would call AI-generated stories without sourced inputs "**fiction wearing a tie.**"

## Bottom Line

Read **Sell with a Story** if you are a B2B seller who has ever frozen when a prospect asked "**can you give me an example?**" Monday morning, list the 25 story slots in a Notion doc, fill in the first seven from your existing wins, and rehearse them once a week for a quarter. By month three, you will have a Story Bank that compounds across every deal you run. In the modern sales canon, Smith sits between **Daniel Pink's To Sell is Human** (the philosophy) and **Kindra Hall's Stories That Stick** (the keynote version) — but for an individual seller looking for parts and instructions, this is the only book that ships with the full kit.

## Sources

- **Paul Smith** — *Sell with a Story: How to Capture Attention, Build Trust, and Close the Sale* (AMACOM, 2016)
- **Paul Smith** — *Lead with a Story: A Guide to Crafting Business Narratives* (AMACOM, 2012) — author's prior volume
- **Chip Heath & Dan Heath** — *Made to Stick: Why Some Ideas Survive and Others Die* (Random House, 2007) — academic foundation for SUCCESs framework
- **Daniel Pink** — *To Sell Is Human: The Surprising Truth About Moving Others* (Riverhead, 2012) — modern sales-philosophy companion
- **Simon Sinek** — *Start with Why: How Great Leaders Inspire Everyone to Take Action* (Portfolio, 2009) — the Why-You-Care story foundation
- **Kindra Hall** — *Stories That Stick: How Storytelling Can Captivate Customers, Influence Audiences, and Transform Your Business* (HarperCollins Leadership, 2019) — executive-keynote descendant
- **Donald Miller** — *Building a StoryBrand: Clarify Your Message So Customers Will Listen* (HarperCollins Leadership, 2017) — marketing-positioning application
- **Andy Raskin** — *The Greatest Sales Deck I've Ever Seen* (Medium, 2016) — Strategic Narrative framework, the enterprise-positioning cousin
- **Jennifer Aaker** — Stanford Graduate School of Business research on narrative memory retention
- **Kenn Adams** — originator of the **Story Spine** improv framework Smith borrows

Was this helpful?

⌬ Apply this in PULSE

Gross Profit CalculatorModel margin per deal, per rep, per territory

Related in the library