Persuasion Frameworks

A persuasion framework is a structure for sequencing ideas so the reader moves from "I don't care" to "I want this." Without a framework, copy meanders. With the wrong one, it misses the reader's emotional state entirely. The right framework depends on one thing: how much the reader already knows and feels about their problem.

Four frameworks cover nearly every scenario. Each one front-loads a different emotional beat.

PAS: Problem, Agitate, Solution

PAS meets the reader inside their existing pain. Name the problem in their words, amplify the consequences of leaving it unsolved, then present the product as the resolution.

1. Problem. Your API keys are scattered across .env files, CI configs, and Slack messages.
2. Agitate. One leaked key can take down production. You won't know until a customer calls.
3. Solution. Vault centralises every secret with per-environment rotation and zero-config CI integration.

Use when: The audience is problem-aware but hasn't acted yet. Cold email openers, long-form landing pages, display ads with enough word budget for all three beats.

Skip when: The audience is solution-aware and already shopping. Re-selling the problem wastes their time. And if the pain is hypothetical rather than real, PAS reads as manipulative.

The most common PAS failure is over-agitation. Push too hard and the reader feels manipulated; push too soft and the urgency doesn't land. Read the Agitate sentence aloud. If you cringe, soften. If a friend in the target audience shrugs, sharpen.

AIDA: Attention, Interest, Desire, Action

AIDA is a four-stage funnel for cold traffic. Each stage earns the next. It's the oldest framework on this list, first articulated in 1898, and still the workhorse for ads, cold email, and splash pages where the reader has zero context.

1. Attention. Interrupt the scroll. 73% of SaaS churn happens before users hit their first "aha" moment.
2. Interest. Show relevance. If your onboarding takes more than one session, you're already losing.
3. Desire. Show the outcome with proof. Teams using Onramp reduce time-to-value by 40%.
4. Action. One clear CTA. See your onboarding score free.

Use when: Cold traffic with no prior context. Display ads, cold email, paid splash pages, first-time visitors with a single conversion goal.

Skip when: Warm traffic. They already gave you Attention by clicking through; lead with Desire or Action. Also skip for editorial content: AIDA is sales-shaped and shouldn't be forced onto a thoughtful longform piece.

The most common AIDA failure: vague stages. "Get more done with our app" tries to be Attention, Interest, and Desire simultaneously and earns none of them. Each beat needs concrete content with space to land.

StoryBrand: Customer as hero

Donald Miller's StoryBrand framework inverts the typical brand narrative. The customer is the hero. The product is the guide: the mentor who hands the hero a plan and points them toward success.

Most product copy gets this backwards. "We built this. We're obsessed with X. Our mission is Y." The brand makes itself the hero of its own story; the customer disappears.

The seven beats:

| Beat | Question | Example | |---|---|---| | Hero | Who is the customer? | A founder who can't sleep because deploys keep failing | | Problem | External + internal + philosophical | Broken deploys; feeling incompetent; code should ship, not haunt | | Guide | Who helps them? | The product, positioned as the expert | | Plan | What are the steps? | Connect repo, set alerts, deploy with confidence | | CTA | What action do you invite? | Start your first deploy free | | Success | What does winning look like? | Ship on Friday without anxiety | | Failure | What's at stake? | More 3 a.m. incidents, more team burnout |

The simplest test: count how often the copy says we/our/us versus you/your. If we-language outweighs you-language, the brand is the hero.

Use when: Homepage heroes that need warmth, about pages that risk sounding self-important, sales pages with room for narrative.

Skip when: Pricing pages (the reader is shopping, not following a story), reference docs, and pure reassurance copy like security and compliance pages.

BAB: Before, After, Bridge

BAB paints the reader's current frustration, shows the desirable future, and explains how the product creates the transition. It's the warm, aspirational alternative to PAS. Where PAS leans into pain, BAB leans into the dream.

1. Before. You spend two hours every Monday pulling reports from four different tools before you can answer one question.
2. After. Every metric you care about, live, in one dashboard. Monday starts with decisions, not data wrangling.
3. Bridge. Metric pairs your existing stack in 15 minutes and surfaces the numbers that move revenue.

Use when: The audience is motivated but stuck. They want change; they need a path. Most B2C apps work better with BAB.

Skip when: The audience hasn't felt the pain yet. BAB assumes motivation exists; PAS creates it.

The Bridge is the hardest beat. "Our product makes it easy" is a dead bridge. "Connect Stripe and Postgres; the dashboard is live before your coffee cools" is a bridge the reader can picture walking across.

Choosing by audience temperature

| Temperature | Definition | Framework | |---|---|---| | Cold | No context, no awareness | AIDA | | Problem-aware | Knows the pain, hasn't acted | PAS | | Solution-aware | Comparing alternatives | StoryBrand | | Motivated | Wants change, needs a path | BAB |

The same product page written with the wrong framework will under-perform regardless of how good the prose is. The framework is the structural decision that precedes every word choice.