# Playbook: PAS — Problem · Agitate · Solve

> Name the pain, twist it until it's vivid, then present the mechanism of relief.

## Origin

Popularized by **Dan Kennedy** (*The Ultimate Sales Letter*) as the load-bearing skeleton of direct-response info-product and coaching copy. Kennedy didn't invent naming a problem before solving it — that's as old as Kennedy's own forebear John E. Kennedy's "salesmanship in print" — but he's the one who named the three-beat sequence and made **agitation** a deliberate, disciplined step rather than something a writer stumbled into. The agitate beat is the applied form of Kahneman & Tversky's loss aversion (§2.3 of MANUAL.md): a felt loss looms roughly 2x larger than an equivalent gain, so dwelling on the cost of the unsolved problem does more persuasive work than describing the reward of solving it.

## When to use it

- Prospect is **Problem-Aware** on the Schwartz grid (§3.1) — they feel the pain but don't know a solution exists or don't know yours.
- Info-products, coaching offers, local-business direct response, anything selling relief from a named, felt discomfort.
- Short-to-mid length surfaces: ads, emails, landing hero copy, the opening of a longer page.

## When NOT to use it

- **Sophisticated, luxury, or Bernbach-register audiences** (the 19Keys restraint register, per §4's "creative/brand school" caveat) — overt agitation reads as cheap and try-hard against a market that expects understatement.
- **Most-Aware buyers** who are already sold and just want the offer — agitating a problem they've already solved-for in their head wastes their readiness (§3.1's core rule: directness must scale to awareness).
- **Sophistication Stage 5** markets, where the audience is cynical and has seen agitation as a manipulation tactic a thousand times — lean on Bernbach voice + Bencivenga proof + identity instead (§5.2).

## Step-by-step build

1. **Name the problem in one sentence** — plain, concrete, in the prospect's own vocabulary if VoC material exists (Wiebe, §4). No adjectives, no hedging.
2. **Agitate** — expand the problem to roughly **2-3x the length** of the problem statement. This is not padding; each sentence adds a new cost of inaction: a consequence, a compounding effect, a future scene where the problem has gotten worse, a status/identity cost. Loss-salience is the engine — dwell on what's being lost, not yet on what could be gained.
3. **Turn** — a single sentence that pivots from pain to possibility. This is the hinge; it should feel like relief is imminent, not yet delivered.
4. **Solve** — present the mechanism of relief. Per RMBC discipline (§6.4) and the mechanism-section requirement (§3.2.3), this needs a **named mechanism**, not just "our product." Close with the smallest next step, not the full offer stack.

## Worked mini-example

**Problem:** "Your calendar is full and your bank account still isn't."

**Agitate:** "Every hour you bill goes to a client who forgets you exist the second the invoice clears. You're not building anything — you're renting out your one asset that never comes back: this year. Meanwhile the operators who used to be one deal behind you are now buying the buildings you meet clients in. The gap isn't talent. It's that you're still selling hours, and hours have a ceiling built into them the day you're born."

**Turn:** "There's a reason some builders stopped selling time and started selling systems."

**Solve:** "The Builder Passport is the mechanism: it converts your one-off client work into a licensable asset — once, indexed, sellable to the next buyer without you re-doing the hour. Start with the 12-minute audit."

## How the verify gate applies

Per §8.1 (`sales-page`) and the universal bar (§8.6): the agitate block must not smuggle in unsourced numbers ("70% of freelancers fail" needs a tagged citation or it fails proof-coverage). The **Solve** step must name a mechanism string, matching the mechanism-section requirement — "our product" alone fails. Watch the **paragraph-length gate** (≤90 words) — agitation is the beat most likely to run long; break it before the linter does. Flesch Reading Ease ≥50 applies to the agitate copy specifically, since dense, escalating sentences are where writers most often let readability slip. Exactly one CTA at the end of Solve — do not let agitation carry a premature CTA.