Business
Business

Copywriting Frameworks Pp Paso Pastor

Business

Copywriting Frameworks Pp Paso Pastor

The counterintuitive core: you don't pick a framework by how clever you want to sound.
developing·concept·1 source··Jun 16, 2026

Three Wrenches of Increasing Size

A mechanic doesn't own one wrench. He owns a set, sized to the job, and reaching for the right one is most of the skill. Dan Koe's three copywriting frameworks work the same way. There's a small one for a tweet, a medium one for a post that sells, and a big one for a full sales page — and they're the same tool getting longer and heavier as the job grows.1 All three start from one move Koe makes in nearly everything he writes: open on a pain point or problem.2 Name the ache first, and the writing flows; the reader's mind locks onto a goal and starts filling in the story.3

The counterintuitive core: you don't pick a framework by how clever you want to sound. You pick it by length of the job — a tweet, a newsletter, a landing page — and the frameworks are deliberately ranked by difficulty so you climb them as your reach grows. And every one of them rides on top of the answer-first Pyramid Principle Koe teaches first.4

What This Actually Is: PP, PAS(O), and PASTOR

Three frameworks, increasing in difficulty and length:5

PP — Pain & Process. The simplest. State the pain point, then show the step-by-step process to overcome it.6 Good for a tweet, a short, or even the spine of a whole long-form piece. Koe adds a wrinkle: cap it with a conclusion line — the last sentence that locks in engagement and earns the like, share, or comment.7

PAS(O) — Problem, Amplify, Solution, (Offer). State the problem, then amplify it by showing how it bleeds into the person's life, then give the solution, then — optionally — the offer.8 The offer only appears if you're actually selling something. The amplify step is the new muscle here: you make the problem vivid and personal before you relieve it.9

PASTOR — Problem, Amplify, Story, Testimony, Offer, Response. The heaviest, built for sales copy.10 Problem and amplify as before, then a Story (personal, client, or borrowed), then Testimony (proof they can get the same result), then the Offer (features and their benefits), then the Response (the ask). This is newsletter-launch and landing-page territory.11

The mechanism under all three is identical: agitate a felt problem, then resolve it, with more proof and more story stacked in as the piece gets longer and the ask gets bigger.

The Internal Logic: Why Pain Comes First Every Time

Koe starts with a problem in everything he writes, and his reasoning is precise.12 A pain point does three jobs at once. It reframes the situation so the reader sees themselves in it. It qualifies the reader — the ones for whom the pain is real stay, the rest leave, which is exactly what you want.13 And it opens a story loop: humans make sense of the world in stories, and stories start with a problem that foreshadows a goal, so naming the pain makes the reader's mind start filling in the blanks and wanting to read on to see if it was right.14

The frameworks then climb in difficulty for a reason tied to trust and length. A tweet can get away with just pain and a process. A newsletter promoting something needs amplification so the reader feels the cost of inaction. A landing page asking for money needs the full PASTOR — story to build identification, testimony to kill doubt, a broken-down offer, and an explicit response — because the bigger the ask, the more resistance you have to clear first.15

There's a craft note Koe is emphatic about: don't get dogmatic. The frameworks are training wheels, not laws.16 "You kind of have to paint between the lines." Add the conclusion line to a tweet even though "pure" PP doesn't have one. One experimental post won't ruin your life.17 The frameworks structure the climb; they don't cage it.

The amplify step has its own internal trick: it gets dramatically easier and more relatable when you draw the pain from your own past experience rather than inventing it.18 Dig into a real situation where you lived the problem and the amplification writes itself — and it rings true because you weren't making it up.19

What This Gives the Rest of the Vault: The Working Templates

This page is where the Koe writing cluster turns from theory into something you can fill in tonight. It sits on top of the Pyramid Principle — the pyramid sets the answer-first shape, these frameworks organize the supports into an emotional sequence. It's aimed by the five levels of awareness — the Problem and Amplify moves serve the unaware and problem-aware rungs, Solution serves the solution-aware, Offer serves the most-aware. And the opening move of all three is just identify and agitate the big problem, done at three scales.

For the sales side of the vault, this page is the broadcast-medium cousin of the NEPQ conversation spine — the same agitate-then-resolve arc, written for an audience that can't talk back.

Analytical Case Study: The "Tired" Tweet, Three Ways

Koe builds a worked PP example live, and it's the clearest window into the mechanism.20

The pain: "If you're tired all the time…" The process: "stop scrolling at midnight, fix your shitty nutrition, go on walks, move your body, become obsessed with a new interest." Then the conclusion line — the part most people skip — "You're tired because you're trapped in a routine that has the outcome of being tired."21 Koe catches himself mid-example noticing how good that last line is, and points out it's the engagement lock he keeps insisting on.22

Now watch it grow into PAS(O). The same tired problem gets amplified: how being tired makes your spouse think something's wrong, how little problems spring up, how you can't perform on your side hustle, how you get home and just want to lie down and eat junk.23 The pain is no longer a single line — it's a spreading stain across someone's whole life. Then the solution (the same step-by-step), then optionally a linked offer framed as a further solution.24

Push it to PASTOR and you'd add a story (Koe's own years of being tired and grinding), testimony (a client who fixed it, or data), the offer broken into modules and benefits, and the response (the link, the ask).25 Same tiredness, three lengths, three levels of resistance cleared. The case shows the frameworks aren't different ideas — they're the same idea zoomed out one notch at a time.

Implementation Workflow: 10:10 Saturday, Turning a Real Bad Week Into Copy

It's 10:10 on a Saturday and you're trying to write the newsletter that sells your course. The blank page is winning. So you stop trying to write copy and start remembering a week — the specific stretch eighteen months ago when you were so fried you snapped at your partner over nothing and she gave you that look. You write that down first. That's your amplify, and it's true, so it costs you nothing to make vivid.

From there the PASTOR shape almost fills itself. The problem is right there in the memory — burnout you couldn't see. You amplify with the look on her face and the side project that stalled. The story is the week itself. Testimony is the line from the student who emailed you last month saying the same thing lifted. The offer is the three modules, each named by the benefit it delivers. The response is one clear link with one clear reason to click now. You read it back and it doesn't feel like copy — it feels like you finally telling someone what that week was actually like. That's the framework disappearing into the writing, which is the point.

The Framework Failure (Diagnostic Signs)

  • Your tweet states the pain and the process and then just… stops — no conclusion line, so it informs but nobody shares it.
  • You amplify a problem you've never lived, so it reads generic and a little fake; the reader can smell the invention.
  • You reach for PASTOR's full machinery on a tweet, or try to sell a course in PP's four words — wrong wrench for the job's size.
  • You treat the framework as scripture, refusing to add a line or bend the order, and the writing goes stiff. Koe's whole warning was: paint between the lines.
  • Your "solution" arrives before the problem is felt, so there's nothing to relieve and the reader never had a reason to want it.

Evidence / Tensions / Open Questions

🚩 SINGLE SOURCE: this page rests on one transcript, and the frameworks are presented as practitioner craft, not tested copy. The PAS and AIDA lineage Koe gestures at elsewhere is standard copywriting folklore; PASTOR is commonly attributed to Ray Edwards, though Koe doesn't cite an originator and this page won't invent one. [UNVERIFIED — framework provenance not established in source]

The honest tension is between the frameworks and authenticity, and Koe meets it head-on: people ask "what if I want to write whatever I want?" and his answer is to use the framework as training wheels until you internalize what makes writing work, then drop it.26 But there's an unresolved edge — the amplify step rewards making a problem feel worse than the reader currently experiences it, which sits uncomfortably close to manufacturing distress to sell relief. Koe's defense (use real personal pain) blunts but doesn't dissolve it. The page preserves that tension rather than smoothing it.

Author Tensions & Convergences

These frameworks are the one-to-many mirror of the NEPQ sales corpus, and the comparison is sharp. The NEPQ eight-stage engagement spine walks a single prospect through problem awareness and amplification in a live conversation — exactly Koe's Problem and Amplify moves — but NEPQ does it by asking questions until the prospect amplifies their own pain. Koe, writing to an audience that can't answer back, has to amplify for them, narrating the spreading damage himself. The convergence is total at the level of structure: both agitate before they resolve, both delay the offer until the pain is felt. The divergence is the medium — a conversation can extract the pain, a tweet must assert it. That difference explains why Koe's copy reads more declarative and occasionally more manipulative than a skilled NEPQ call: the broadcast medium denies him the prospect's own voice, so he supplies it, and supplying someone's pain for them is a riskier ethical position than letting them name it.

A quieter convergence runs to identify and agitate the big problem — that page is essentially the first two beats of PAS(O) and PASTOR isolated and studied on their own. These frameworks show what comes after the agitation, where the big-problem page stops.

Cross-Domain Handshakes

Plain version: these three frameworks all agitate a problem before offering relief, which makes them the written, one-to-many version of what a skilled salesperson does live — and lining the two up shows that "content marketing" and "sales" are one skill wearing two outfits.

The first handshake is with the NEPQ eight-stage engagement spine. The spine is a problem-then-solution arc run as one private conversation; PASTOR is a problem-then-solution arc run as one public sales page. Put them side by side and a structural identity surfaces that neither corpus claims about itself: the eight stages and the six PASTOR beats are the same persuasion arc fanned out to different audience sizes. NEPQ's discovery questions = Koe's Problem and Amplify. NEPQ's solution-presentation = Koe's Solution and Offer. NEPQ's commitment stage = Koe's Response. The one component NEPQ has that Koe can't fully replicate is the prospect's own spoken words doing the amplifying — which is exactly why broadcast copy leans harder on Story and Testimony (PASTOR's S and T) to manufacture the identification a conversation would get for free. The insight is that the difference between a sales call and a sales page is not the persuasion structure — it's identical — but who voices the pain: in conversation the buyer does, in copy the writer must, and that single substitution is the source of most of copy's ethical hazard.

The second handshake is with the big problem: identify and agitate. That page isolates the opening move all three frameworks share; this page shows the full arc that move sets up. Reading them together exposes a dependency the frameworks hide: PASTOR's later beats — Story, Testimony, Offer — only land if the Problem and Amplify did their job, because Testimony answers a doubt the reader only has if they now feel the problem, and an Offer only relieves a pain that's been made real. The amplification isn't one step among six; it's the load-bearing wall the rest leans on. The connection produces a diagnostic neither page states alone: when a PASTOR sales page underperforms, the failure is almost never in the offer or the testimony — it's that the amplification was thin, so everything downstream had nothing to push against. Fix the agitation and the rest starts working, because the whole arc was only ever as strong as the pain it made you feel.

The same pairing also clarifies why the frameworks climb in exactly the order Koe gives them. The big-problem page treats identification-and-agitation as a single skill; the three frameworks reveal that this one skill gets re-used at increasing depth as the ask grows. A tweet (PP) agitates a problem just enough to justify a three-step fix — shallow agitation, small ask. A newsletter (PAS(O)) agitates until the reader feels the cost spreading into their relationships and work — deeper agitation, bigger ask. A sales page (PASTOR) agitates, then re-agitates through story and testimony, layering the same pain in narrative and proof until the reader is fully inside it — deepest agitation, biggest ask. Lined up, the frameworks aren't three different tools so much as one tool (agitate-the-problem) applied with escalating force in proportion to how much resistance the ask must clear. This gives a calibration rule the big-problem page can't supply alone, because it only studies the single move: match the depth of your agitation to the size of your ask, and a mismatch in either direction fails — over-agitate for a small ask and you sound hysterical, under-agitate for a large ask and the price feels unjustified. The frameworks, read against the identify-and-agitate page, turn out to be a graduated dosage chart for a single active ingredient.

The Live Edge

The Sharpest Implication — The frameworks rank by difficulty, but the real difficulty isn't the structure — it's the amplify step, and the amplify step is hardest precisely because it's where craft shades into manipulation. The writer who amplifies from lived pain is honest; the one who amplifies from imagined pain to manufacture a sale is not. Same six letters, opposite ethics. The framework can't tell you which one you're doing — only you can.

Generative Questions

  • If amplification works best when drawn from real personal pain, does the framework quietly require a writer to keep mining their own wounds — and what happens when they run out?
  • Where exactly is the line between amplifying a problem the reader already has and installing a problem they didn't, and does any framework beat encode that line?
  • If a sales call and a sales page share one persuasion arc, why does the page so often feel sleazier — is it the missing buyer's voice, or something about being unable to answer back?

Connected Concepts

Footnotes

Related — Expert Secrets (Russell Brunson)

Brunson's opportunity-switch headline — "How to [result they desire most] without [thing they fear most]" — is a sibling formula in the same family. See The Opportunity-Switch Headline.

domainBusiness
developing
sources1
complexity
createdJun 16, 2026
inbound links7