Magnetic Story Selling
A tactical guide for turning St. Pierre’s operator experience into stories that earn attention, build belief, and lead to a clear next step.
Objective
Publish sales stories without sounding like an ad.
Why it matters
More trust, response, booked calls, and repeat attention.
Akash needs to
Choose one true story and draft it — 30 min.
Status
Ready to use · July 14, 2026
Start here: use the 20% that creates 80% of the result needs you
- Pick a strong story premise: a real moment, composite situation, fictional client drama, mistake, surprise, hard choice, or strongly held belief.
- Write it with the eight-beat story spine below. Keep only details that change the reader’s understanding.
- Connect the lesson to one St. Pierre belief: demand generation, AI speed, one brain, real-time thresholds, or owned infrastructure.
- End with one action: watch the tactical video, reply, or book the 20-minute stack look.
- Reuse the same story across a reel, email, YouTube opening, and sales call.
Quality controls: enter the story at the moment of change, make the tension specific, connect every detail to the lesson, and use one clear call to action.
The operating idea: influence compounds when the audience knows who you are reference only
The useful premise behind Magnetic Story Selling is bigger than “tell better stories.” A business becomes magnetic when its stories repeatedly create four effects:
1 · Character
A recognizable operator with opinions, standards, flaws, and earned authority—not a faceless agency voice.
2 · Cause
A fight bigger than the offer. For St. Pierre: contractors should own the infrastructure that creates their growth.
3 · Connection
Specific moments that make the buyer feel understood before they are taught or sold.
4 · Consistency
The same worldview, language, and core beliefs repeated across channels until the market can retell them.
The goal is not universal appeal. Clear stories should attract right-fit operators and repel people who want rented leads, vague reporting, or hands-off magic.
The eight-beat magnetic story spine no action
| Beat | Write this | Prompt |
|---|---|---|
| 1. Moment | Open inside a scene, not with context. | Where were you? What had just happened? |
| 2. Want | Name the practical outcome. | What were you or the client trying to get? |
| 3. Friction | Show the costly obstacle. | What made the obvious solution fail? |
| 4. Wrong move | Admit the default approach or mistake. | What did you try that looked right but was not? |
| 5. Turn | Reveal the observation that changed the diagnosis. | What did you finally notice? |
| 6. New rule | State the reusable belief in one line. | What should the reader now believe? |
| 7. Proof | Give a real result, demonstration, or mechanism. | What can you show without exaggeration? |
| 8. Action | Offer one low-friction next step. | What is the natural continuation of the story? |
Use this fast spine for daily emails, short videos, sales-call stories, and campaign openings. Use the long-form architecture below when the story must carry an entire presentation.
The long-form campaign story architecture no action
Use this 17-beat structure for a VSL, webinar, keynote, founder film, case-study video, or long sales letter. Each beat should earn the next one; combine adjacent beats when the format needs speed.
| Act | Beat | Job | St. Pierre application |
|---|---|---|---|
| Act I · The old world | 1. Pattern break | Open on a surprising image, result, or contradiction. | A contractor with fourteen dashboards cannot answer which ad created a closed job. |
| 2. Character | Establish the operator, situation, and credibility. | Introduce the owner and the real operating environment. | |
| 3. Desired result | Name what the character is trying to achieve. | Keep estimators booked with profitable, right-fit work. | |
| 4. Visible obstacle | Show the problem the character initially blames. | Lead volume appears too low or inconsistent. | |
| 5. Stakes | Make the cost of staying stuck concrete. | Idle crews, wasted spend, missed follow-up, and owner dependence. | |
| Act II · The break | 6. Default solution | Show the accepted approach. | Buy more shared leads, add another tool, or request another report. |
| 7. Early hope | Explain why the default solution looked reasonable. | More activity creates a temporary feeling of progress. | |
| 8. Failure | Reveal the point where the old approach breaks. | The tools disagree and follow-up still depends on a person noticing. | |
| 9. Costly truth | Name the deeper diagnosis. | The owner has become the integration layer. | |
| 10. Guide or insight | Introduce the observation that changes the frame. | Growth needs owned infrastructure, not more disconnected activity. | |
| 11. New rule | Turn the insight into memorable intellectual property. | “A dashboard is not a brain.” | |
| 12. Choice | Show the commitment to act differently. | Stop patching tools and map one lead-to-job data path. | |
| Act III · The new world | 13. Mechanism | Show how the new approach works. | Demand generation, ten-second triage, one brain, and closed-job feedback. |
| 14. Resistance | Answer the strongest reasonable objection. | Installation can happen in stages without replacing everything at once. | |
| 15. Proof | Demonstrate the mechanism with verified evidence. | Show the real path from source to contact, quote, and closed job. | |
| 16. Transformation | Contrast identity and operating reality before and after. | The owner moves from human glue to asset architect. | |
| 17. Invitation | Offer the next step that continues the transformation. | Book a 20-minute stack look to map the first owned path. |
Long-form pacing
- First 10%: beats 1–5. Create recognition and stakes quickly.
- Middle 55%: beats 6–12. Let the old belief fail, then introduce the new rule.
- Final 35%: beats 13–17. Demonstrate the mechanism, answer resistance, show proof, and invite action.
Six story types to keep in the bank no action
| Story type | What it changes | St. Pierre prompt |
|---|---|---|
| Origin | Why this cause matters to you. | When did you stop believing contractors needed “another agency”? |
| Oops / mistake | Humanizes the guide and creates a lesson. | What did you build, buy, or report that looked useful but added more duct tape? |
| Belief break | Replaces an old assumption. | When did “more leads” prove less valuable than faster, smarter follow-up? |
| Customer turning point | Lets the buyer see themselves in the result. | What changed between a lead arriving and a booked quote? Use a real case, composite, or recurring fictional archetype. |
| Behind the build | Shows competence without a claim dump. | What broke during an install, and what guardrail did it create? |
| Point-of-view | Creates healthy polarization. | What accepted contractor-marketing practice should be retired—and why? |
Minimum story-bank record
Date · story lane · character · scene · tension · wrong move · lesson · proof available · belief · best CTA
Fictional client drama: the Big Mike story engine no action
The character contract
- Mike is lovable-wrong, not stupid. The buyer is Mike. Recognition disappears if the character feels like an attack.
- The drama is invented; the psychology is observed. Dialogue, timing, callbacks, and situations can be written for the bit. The objections come from the market.
- Recognition is the job. The viewer should think, “That is literally my business,” before receiving the lesson.
- Deadpan restraint creates the comedy. Mike supplies certainty; Akash supplies the smallest possible correction.
- The “is this real?” loop stays intact. Recurring details and callbacks make Mike feel like a person whose story continues between episodes.
- Every episode moves one belief. The joke is the delivery system; the belief shift is the product.
The serialized Big Mike arc
| Stage | Mike’s role | Story move | Example |
|---|---|---|---|
| 1. Certainty | Mike confidently names the wrong cause. | Introduce his recurring worldview. | “Your leads suck.” |
| 2. Evidence resistance | He explains away the first contradiction. | Let the belief survive one correction. | “So send better leads.” |
| 3. Escalation | The same belief creates a new operational consequence. | Move from lead quality to no-shows, late calls, empty calendars, and wasted estimates. | “He ghosted me”—after Mike waited three days. |
| 4. Callback | An earlier line returns with a different meaning. | Reward repeat viewers and deepen the serial. | The calendar, tire-kicker, or nephew line reappears. |
| 5. Crack | Mike briefly sees that he may be the constraint. | Create catharsis without fully resolving the character. | “...how do you know my response times?” |
| 6. Partial adoption | Mike tries the new mechanism imperfectly. | Open the redemption arc and introduce deeper systems. | He installs fast intake but still refuses to qualify. |
| 7. New-level problem | Progress reveals the next constraint. | Keep the franchise alive while climbing the belief ladder. | A full calendar exposes hiring confidence or sales-process gaps. |
Episode template
Mike’s voice begins mid-complaint. On-screen text identifies the consequence, not the lesson.
Mike gives the industry-default explanation in language an owner would actually use.
Akash asks two or three short questions that let Mike reveal the contradiction himself.
One concrete reframe connects Mike’s behavior to the business result.
A recurring phrase, number, person, or past episode makes the world feel continuous.
The final line names the new belief and hands off to one comment trigger.
Canonical Big Mike references: series scope · angle bank · Wave 1 scripts.
Worked example: from “dashboard” story to sales message reference only
This example can be executed as documentary, composite, or fictionalized drama. Keep the mechanism and any factual claims internally consistent with the chosen lane.
At 6:47 p.m., a contractor had fourteen logins open and still could not answer which leads had become jobs.
He did not need another report. He needed one trustworthy answer before making tomorrow’s budget call.
Our first instinct was to make the dashboard prettier. That would have displayed the confusion more clearly, not fixed it.
The issue was not reporting. The tools disagreed because no system owned the full path from ad to closed job. A dashboard is not a brain.
Show the real data path: lead source → contact → booked quote → closed job. Add a verified result only if the underlying record supports it.
If your numbers live in five places, watch the five-minute One Brain setup. Then book a 20-minute stack look if you want us to map yours.
Channel templates: one story, four assets no action
20–30 second reel
Hook: “[Unexpected scene or mistake].”
Tension: “We thought [default fix]. The real problem was [root cause].”
Rule: “[Named belief].”
Proof visual: show the system or record.
CTA: “Watch the full setup on YouTube.”
250-word email
Subject: the scene or surprising mistake.
Body: Moment (2 lines) → friction (3–4) → wrong move (2) → turn (3) → rule (1) → proof (2–3) → one link.
Five-minute YouTube opening
0:00–0:30: story scene and end result. 0:30–1:15: why the old approach failed. 1:15–4:30: show the mechanism. 4:30–5:00: rule, verdict, and Infrastructure Audit CTA.
Sales-call bridge
“We saw the same pattern with [approved comparable situation]. The surface issue was [symptom], but the constraint was [root cause]. Can I show you how that maps to what you just described?”
The magnetic story scorecard no action
Score each item 0, 1, or 2. Publish at 8/10 or better.
| Check | 0 | 1 | 2 |
|---|---|---|---|
| Character | Faceless | Named voice | Clear operator, opinion, and stake |
| Cause | No belief | Lesson implied | Memorable rule tied to the category |
| Connection | Abstract | Some detail | Concrete moment with felt tension |
| Story integrity | Lane is confused | Story is coherent | Fiction is internally consistent; factual claims are supportable |
| Action | None or many | Generic CTA | One natural next step |
- Could the intended contractor see themselves in the first five seconds?
- Does the story change one belief rather than teach five ideas?
- Would the story still be useful if the offer were removed?
- Does the story stay coherent in its chosen lane: documentary, composite, or fictional serial?
- Does the CTA continue the story instead of interrupting it?
A seven-day implementation sprint no action
| Day | Output | Definition of done |
|---|---|---|
| 1 | Mine 10 moments | Ten one-line scenes from calls, builds, mistakes, and convictions. |
| 2 | Choose three | Each maps to one belief and has a clear story lane, mechanism, and button. |
| 3 | Draft the first | Eight beats, under 350 words, one CTA. |
| 4 | Record reel | One take, 20–30 seconds, result visual included. |
| 5 | Record tactical video | Five-minute setup showing the mechanism behind the story. |
| 6 | Send email | Same story, deeper lesson, one link. |
| 7 | Review response | Log watch time, replies, clicks, booked calls, and exact audience language. |
Scale: stories that create replies, retention, or qualified next steps. Rewrite: stories that get attention but no belief shift. Recast: premises whose characters, conflict, or mechanism do not land.
Story-lane rules reference only
- Documentary: preserve the real event, result, and meaning; shape the telling for pace.
- Composite: combine repeated market patterns into one representative character and scene.
- Fictional serial: invent character, dialogue, events, running jokes, escalation, and redemption to dramatize true buyer beliefs.
- Big Mike canon: keep the character sympathetic, the objections recognizable, the deadpan restrained, and the world continuous.
- Proof: demonstrations, mechanisms, and factual statistics should withstand scrutiny even when the surrounding drama is fictional.
- Measurement: track sends, repeat viewing, qualified replies, video completion, booked calls, and sales-cycle movement.
Sources and scope reference only
- Google Books record — lists Magnetic Story Selling as a 2025 book by Dan Kennedy and Russell Brunson.
- Magnetic Marketing product page — official product listing.
- Dan Kennedy on visibility and brand narrative — audience understanding, a clear call to action, brand story, consistency, and healthy repulsion.
- Dan Kennedy on customer experience — frames the book’s premise around keeping customers for the long term.
This original implementation guide turns the publicly described principles into a working system for St. Pierre’s content, sales, and customer communication.