Copy Structures

The order a piece of persuasion moves through

Universal tool

Message Architecture decides what you're saying. This decides the order you say it in. A structure is a proven path from first line to action — reach for one instead of guessing at sequence. Six of them, the choice of motivator underneath, and the four shapes to recognise and refuse.

Problem-Promise-Proof-Price adapts Vitale's simplification of Aristotle's rhetoric (public domain). AIDA is public-domain advertising. The six-beat is yours. The Map & the Pin adapts Dunford's sales-pitch storyboard; The Turn adapts a testimonial script from Hormozi's marketing-machine playbook; the failure modes adapt Dunford's critique of the common pitch narratives. Every step is renamed and every example rewritten. The "hypnotic/manipulation" framing of the older source is dropped — it runs against the honest brand.

Problem → Promise → Proof → Price

The workhorse for anything that asks for action. Open on the reader's problem, make the promise, prove it, then ask. It's Aristotle's rhetoric in modern dress, and it maps cleanly onto your message architecture — promise and proof are already jobs there. Reach for it on pages, emails, and ads.

Problemcall out the painYour agent forgets everything the moment the session ends.

Promisethe outcomeGive it a memory that actually holds.

Proofwhy it's believableThe four-rung ladder, from files to graph — and when each one earns its place.

Pricethe askRead the ladder. Start at the bottom rung today.

P-P-P-P

The conversion workhorse

Problem, promise, proof, price. Aristotle, modernized.

Proof pulls from the proof ladder — specifics, not adjectives.

Yours: the "price" is honest — the real ask and its real cost, no fake urgency around it.

AIDA — Attention, Interest, Desire, Action

The tightest classic structure, best for short-form — an ad, a short post, a subject line into a body. Grab attention, earn interest, build desire, ask for action. It's the same arc as Problem-Promise-Proof-Price with different labels, compressed for speed.

AttentionMost agent failures aren't the model's fault.

Interest22 of them trace back to just five root causes.

DesireLearn the five and you can guard against all 22.

ActionThe catalog is one click away.

AIDA

The short-form classic

Attention, interest, desire, action. Compressed for ads and posts.

Attention = the hook (see Hooks & Openings). The rest carries it to the ask.

Same arc as P-P-P-P, tighter. Use it when space is short.

The six-beat — your reframe structure

Your own structure, sitting alongside the borrowed ones so you can see the full set. Where the others convert, this one builds authority — the Mode-1 reframe post. It ends on a verdict and leaves objections open, the exact opposite of a conversion close. (Full detail lives in the Content Engine.)

ClaimMore context is making your agent worse, not better.

TensionEveryone's answer is to stuff more into the window.

TurnContext isn't memory. Piling it up is the problem.

EvidenceThe failure modes that trace straight to context dilution.

ReframeComplexity is earned, not adopted.

VerdictStructure beats volume. Every time.

Six-beat

The authority structure

Claim, tension, turn, evidence, reframe, verdict.

Ends on a verdict, leaves objections open — the opposite of a conversion close.

Yours: this is the one that's already yours. The borrowed structures fill in around it.

The Map & the Pin — the considered decision

Most lost decisions aren't lost to a rival. They're lost to a reader who couldn't tell how to choose and so chose nothing. That reader doesn't need more pressure, they need orientation — so you spend the whole first half not talking about yourself. Draw the map. Then drop the pin.

Phase one — draw the mapyou are not in this half

The Readwhat you've learnedMost agent projects don't stall on the model. They stall the first time the thing has to remember something.

The Landscapeevery real option, fairlyFlat files, a database, retrieval, a graph — and carrying on without memory at all. Here's when each one is the right call.

The Barwhat any right answer must clearSurvives a restart. Doesn't need rewriting when the data doubles. Understandable by whoever's on call at 3am.

Phase two — drop the pinnow you appear

The Pinwhere you sit on that mapWhat we do is the third one, done properly. Here's where it sits.

The Onlyfrom the captured positioningThe thing none of the other four can do — and why it clears the bar you just set.

The Receiptsproof it deliversNineteen teams, the numbers, and the two cases where it didn't work.

The Snagthe objection, named firstIt costs a day to set up. That's real. Here's why it's a day and not a week.

The Next Stepone clear actionStart with the ten-minute version. If it doesn't hold, you've lost ten minutes.

Map & Pin

Orientation, then position

Read → Landscape → Bar ‖ Pin → Only → Receipts → Snag → Next Step.

The whole first phase is about the market, not you. That's what earns the second phase.

Name a competitor's genuine advantage out loud. A reader who's done the research already knows it, and pretending otherwise costs you the rest of the page.

The Bar is the pivot: build the criteria with them, then meet criteria they now own.

Yours: teach-first, as a sequence. Step 05 is lifted straight from the Positioning page — same name, same line.

The Turn — the customer story

The story shape for a person rather than a product. Six beats, and the bracketing is the design: numbers on the outside so the change is measurable, feelings outside those so it stays a person. The pair most story frameworks leave out is the doubt and what tipped it — which is objection handling done inside a story, in the customer's voice instead of yours.

Rock bottominternal — what it felt likeI'd rebuilt the same context loader four times and I was starting to think the whole approach was wrong.

The number thenexternal — measurableNine hours a week of manual re-priming. Two of three sessions failed on recall.

The doubtwhy they nearly didn'tHonestly, it looked like more infrastructure to maintain, and I had enough of that.

What tipped itthe thing that overcame itThe ten-minute version. I could see whether it held before committing anything.

The number nowexternal — measurableUnder an hour a week. Recall failures are rare enough that I notice them.

What changedinternal — the real payoffI stopped dreading the first prompt of the day. That's the bit I didn't expect.

The Turn

Six beats, bracketed

Feelings outside, numbers inside, doubt in the middle.

The doubt beat is the load-bearing one. A story with no doubt in it reads as an advert, because real decisions have doubt in them.

Doubles as a capture script: ask these six as questions and edit the answers. Don't write it.

Yours: you never author this arc — you collect it. Inventing the beats is a refusal on The Honest Line.

Which structure for which job

The job picks the structure. Don't force one shape onto everything — a reframe post and a pricing page want different sequences. Here's the quick map, including PAS (Problem-Agitate-Solve) for the times the pain itself is the lever.

When you're writing…	Reach for	Room needed
A landing page, email, or ad	Problem → Promise → Proof → Price	Medium
A short ad or post	AIDA	Short
A LinkedIn reframe (authority)	The six-beat	Short
A considered decision — long page, sequence, talk	The Map & the Pin	Long
A customer story, case study, or testimonial	The Turn	Medium
When the pain is the lever	Problem → Agitate → Solve	Short

Structure picker

Job first, shape second

The task decides the structure. Match, don't force.

Conversion → P-P-P-P or AIDA. Authority → six-beat. Considered → Map & Pin. Person → The Turn.

All of them share a spine: hook, build, ask (or verdict).

Room matters. Map & Pin needs the space to draw a map — crushed into 200 words it becomes a worse AIDA.

Ask first: is the blocker desire or confidence? Desire wants a conversion shape. Confidence wants the map.

Pain or pleasure — chosen honestly

Under every structure sits one choice: move the reader toward a better future, or away from a real pain. Pain drives faster action but, overused, becomes the knife-twisting manipulation you're against. The honest landing: lead with the better future, and name the real pain only when the reader's genuinely in it — a gentle reminder, never a nose-rub.

Toward pleasure (lead here)

Give your agent a memory that holds, and every session builds on the last.

Away from pain (when real)

Every session that starts from zero is work your agent already did, thrown away.

The motivator

Honest either way

Toward a better future, or away from a real pain. Usually lead with the future.

Name real pain when the reader's in it — a reminder, not a nose-rub.

Yours: never manufacture or exaggerate the pain. Real stakes only — the honest-marketing line holds here too.

Structures that misrepresent the choice

Not bad writing — bad architecture. These shapes survive a line-edit because nothing in any individual sentence is wrong; the distortion is in what the sequence lets the reader conclude. Worth being able to name them, because they're the default shapes in this industry and you'll be handed them constantly.

The old way / new way binary

Collapses every real alternative into "old", treats new as self-evidently better, and leaves the reader in a two-option world that doesn't exist. It also invites delay: sell someone a future and they'll wait for it. And to a technical reader, new frequently reads as untested rather than better.

InsteadThe Landscape step of Map & the Pin. Lay out the four real options, say where each one wins, and win inside the truth. Also refused outright on The Honest Line, card 14.

The feature walkthrough

Shows everything the thing does, most of which is table stakes, and never answers the only question the reader has: why you rather than the others. Spends its best minutes on how the login works.

InsteadShow only The Only, and show it against a named alternative. The Positioning page already sorted differentiators from table stakes — use that sort.

Problem → solution, with nothing in between

Works when you're the only option. Falls over when there are several, because every competitor defines the problem exactly the way you did — so a reader who agrees with your problem statement still has no reason to pick you.

InsteadKeep the problem, then add The Bar. A shared problem plus criteria you can meet and they can't is a reason. A shared problem alone is a category description.

The hero's journey, used as a pitch

Not refused — misapplied. As a story it's excellent, and the guide-not-hero framing is right. As a pitch it fails at one point: the plan it hands the reader explains how to start, not how to choose. A reader deciding between five options needs the second one.

InsteadUse it where it belongs — a customer story, which now has its own shape here: The Turn. For the choosing part, Map & the Pin.

Failure modes

Bad architecture, not bad prose

These survive a line-edit, which is why they need naming at the structure layer.

One test catches most of them: does the shape let the reader see options you'd rather they didn't?

Three of these are weak. The first one is dishonest — it's a refusal, not a preference.

Yours: these are the default shapes in AI marketing. Recognizing them on sight is most of the advantage.

Created for you, with ❤️ by Robert Evans · The AI Design Architect