Persuasive Writing Frameworks: AIDA, PAS, and BAB Explained (With Examples)

You email a client asking them to approve a bigger budget. You post an announcement asking your team to adopt a new tool. You draft a proposal hoping a stakeholder finally says yes. Most of these messages fail for the same boring reason: they read like a diary entry, background first, point buried in paragraph four, and the reader never gets there.

Advertisers solved this problem more than a century ago. They built short, repeatable structures for moving a reader from “I don’t care” to “I’ll act” - and once you see them, you can’t unsee them in every good email, pitch, or post you read.

Why this matters

You don’t need to be a copywriter to need this. Anyone who writes to ask for something - a decision, a signature, a habit change, a click - is doing persuasive writing whether they call it that or not.

The frameworks below aren’t tricks. They’re shortcuts that match how a brain actually processes a request: notice it, understand it, feel something about it, then act. Skip a step and the reader stalls. Follow the sequence and you make your ask easy to say yes to, instead of easy to ignore.

Learn five of them - AIDA, PAS, BAB, the 4 Ps, and FAB - and you’ll have a structure ready for almost any message you need to write this week.

AIDA: Attention, Interest, Desire, Action

AIDA is the oldest framework in this list, sketched out by an advertising pioneer in 1898 and turned into a catchy acronym in 1921. Over a hundred years later it’s still the default taught in marketing and communication courses, because the psychology behind it - notice, care, want, act - hasn’t changed.

It has four moves:

• Attention - a hook specific or surprising enough that the reader stops skimming.
• Interest - a bridge connecting that hook to something the reader personally cares about.
• Desire - the case for why the solution matters to them, not in the abstract.
• Action - one clear, specific next step.

Here’s what it looks like inside a real internal email announcing a new tool:

Attention: “Subject: We just cut our reporting time from 3 hours to 12 minutes.” Interest: “If you’re one of the six people who builds the weekly ops report by hand, you know that pain. Most of it is copy-pasting between five spreadsheets.” Desire: “Starting Monday, the new dashboard pulls all five sources automatically and flags anomalies for you - meaning your Friday afternoons go back to being yours.” Action: “Watch this 4-minute walkthrough and log in with your existing credentials before Monday’s standup.”

AIDA earns its keep when the reader has zero prior awareness of the problem or offer you’re writing about - a cold email, a company-wide announcement, a pitch to someone who’s never heard of you. That’s why it spends real effort on Attention and Interest before it ever asks for anything.

The most common mistake is skipping straight from Attention to Action. The reader notices your headline, feels nothing, and closes the email. A surprising fact with no emotional or practical follow-up rarely turns into action - make your Attention line concrete and numeric (“cut reporting time from 3 hours to 12 minutes”), not vague (“we improved our process”).

PAS: Problem, Agitate, Solve

PAS is shorter and sharper than AIDA, built for a reader who already half-senses something is wrong but hasn’t been pushed to act on it. Instead of building interest from zero, PAS assumes the reader will recognize the problem the second you name it - so it goes straight to making that problem feel urgent, then relieves the tension with your fix.

• Problem - name the specific pain in the reader’s own language.
• Agitate - make the cost of leaving it unsolved vivid and real.
• Solve - present your solution as the direct relief.

Think of PAS like a doctor pressing gently on a sore spot before offering treatment. The press isn’t cruelty - it’s what makes the patient actually want the medicine instead of shrugging it off.

Here’s a manager pitching a process change to leadership:

Problem: “Our onboarding takes new hires 34 days to become fully productive - nearly double the industry benchmark of 18.” Agitate: “At our current hiring pace, that gap costs us roughly 640 lost productive days a year - the equivalent of leaving two full-time roles unfilled. New hires also cite the slow ramp-up as their top reason for early attrition, so we’re paying to recruit people twice.” Solve: “A structured 2-week onboarding sprint, already piloted successfully in the Denver office, cut ramp-up time to 19 days. I’m asking for approval to roll it out company-wide next quarter.”

PAS is the workhorse of proposals, internal memos, and outreach between professionals, because it respects a reader’s time - no warm-up, just here’s the pain, here’s why it matters, here’s the fix. It tends to work best when a reader already suspects a problem exists and just needs the stakes made concrete before deciding to act.

Two things to watch: agitate with facts, not exaggeration (“640 lost productive days” reads as credible; “this is a total disaster” reads as manipulative), and don’t overstay your welcome in the Agitate step. One or two sentences of consequence is usually enough - a full paragraph of dwelling on the pain makes the reader feel nagged rather than understood.

BAB: Before, After, Bridge

BAB takes a gentler, more hopeful route than PAS. Instead of pressing on the pain, it paints two pictures - life now, and life after your idea is adopted - then shows the reader the bridge between them. It shines when your audience is tired of hearing about problems and needs to be re-energized with a vision instead.

• Before - a short, relatable description of the reader’s current situation.
• After - a vivid picture of how much better things look once the problem is solved.
• Bridge - the specific action or plan that gets them from Before to After.

Here’s BAB re-engaging lapsed users of an internal platform:

Before: “Six months ago, your team stopped using the shared knowledge base - we get it, the old version was clunky and search barely worked.” After: “Picture finding any past decision, spec, or client note in under 5 seconds, with AI-generated summaries so you don’t even have to open the full document.” Bridge: “We rebuilt search from the ground up this quarter. Log back in this week - your old content is already indexed and ready to search.”

BAB is the warmest of the three core frameworks. It works well for re-engagement, culture change, and community posts, because it never dwells on blame or pain - it simply contrasts “now” with “better,” which keeps the tone friendly even when the underlying message is “please come back” or “please change a habit.”

Keep the Before brief and non-judgmental - the goal is recognition (“yes, that’s me”), not guilt, and save the emotional payoff for After. Just don’t stretch the After picture past believable (“you’ll never have another bad day at work again”). Keep the future vivid but credible, or the reader will discount the whole message.

The 4 Ps: Promise, Picture, Proof, Push

The 4 Ps is built for situations where a short email isn’t enough convincing - a full proposal, a sales page, a detailed pitch document. It adds a step the other frameworks skip: Proof, meaning hard evidence that backs your claim before you ask for the decision.

• Promise - a bold, specific claim about the single biggest benefit you’re offering.
• Picture - a vivid mental image of life once that promise is delivered.
• Proof - numbers, case studies, or third-party data confirming the promise is real.
• Push - a direct, unambiguous call to act now.

Here’s an opening pitch to a finance committee for a new vendor contract:

Promise: “Switching our logistics partner will cut shipping costs by 22% without changing delivery speed.” Picture: “Imagine closing out Q3 having returned $340,000 to the budget that can instead fund the two headcount requests currently on hold.” Proof: “Three companies of our size in this industry made the same switch last year and reported average savings of 19-26%, confirmed in their published earnings notes. Our own pilot shipment last month came in 21% under current cost.” Push: “I’m requesting sign-off by Friday so we can lock in Q4 pricing before the vendor’s rate increase takes effect October 1st.”

Notice how much heavier this is on evidence than the AIDA or PAS examples - that’s the point. The 4 Ps is the right tool for high-stakes, considered decisions where a reader needs proof before committing, not quick reactive ones.

FAB: Features, Advantages, Benefits

FAB is different from the other four - it isn’t a message structure so much as a translation habit. It traces back to a phrase from 1930s sales training: “sell the sizzle, not the steak.” Every FAB statement has three layers.

• Feature - a factual characteristic of what you’re offering. What it is or has.
• Advantage - what that feature does. How it functions or beats the alternative.
• Benefit - what the reader personally gains. Time saved, risk reduced, status improved.

A mattress ad says “12-inch memory foam” (feature), “which contours to your body and stays cool” (advantage), “so you fall asleep faster and wake up without back pain” (benefit). Nobody buys a mattress for its foam density - they buy better sleep. FAB forces you to finish every sentence at “benefit.”

You’ll use this constantly outside of sales too. In a job interview: “I built automated test coverage for our checkout flow” (feature) - “which catches bugs before they reach customers” (advantage) - “so the team shipped three releases last quarter with zero customer-facing payment bugs, down from an average of four incidents per quarter before” (benefit).

Most people stop at the feature: “I have five years of experience,” “our platform has an API,” “this report includes twelve charts.” A reader doesn’t act on features - they act on what those features mean for them. Use FAB as a self-editing check: after writing any sentence about a feature, ask “so what?” twice - once to reach the advantage, once more to reach the benefit. Don’t assume the benefit is obvious. What’s obvious to you as the expert is rarely obvious to the reader.

Common misconceptions

• “These frameworks are just sales manipulation.” They’re structures, not tricks. A doctor still tells you the truth whether they lead with the diagnosis or the treatment plan - the order just determines whether you actually hear it.
• “More persuasive writing means more words.” PAS and BAB both work in three tight beats. Length isn’t what persuades; sequence is.
• “I should pick one framework and always use it.” Different readers need different approaches - a cold audience needs AIDA’s slow build, while a reader who already senses a problem just needs PAS’s speed.
• “If the offer is good enough, structure doesn’t matter.” A great offer buried in paragraph four still gets ignored. Structure is what gets your good offer read in the first place.

How to use this

1. Diagnose your reader’s starting point first. Ask: do they know the problem exists yet? If no, reach for AIDA. If they half-know it, reach for PAS or BAB depending on whether they need pressure or hope.
2. Match framework to stakes. Quick asks and cold outreach: PAS. Big, considered decisions needing evidence: the 4 Ps. Re-engagement or culture messages: BAB.
3. Write your Action or Push line first, then work backward. Knowing exactly what you want the reader to do prevents a message that persuades beautifully and asks for nothing.
4. Agitate or Picture with real numbers, never adjectives. “640 lost productive days” beats “this is a real problem” every time.
5. Run every claim through the FAB filter before you send anything, regardless of which framework you used. Ask “so what?” twice until you land on what the reader actually gains.
6. Cut your Before or Problem section in half. Most first drafts spend too long on the setup and not enough on the point - your reader needs recognition, not a re-telling of their own situation.

Conclusion

Every framework here is really answering the same two questions: how aware is my reader of the problem already, and how much convincing does this decision need? Pick AIDA for a cold start, PAS when they half-know it, BAB when they need hope instead of pressure, the 4 Ps when the stakes call for proof - and run FAB underneath all of them so every claim ends on a benefit, not a feature.

The next time you open a blank email you’re dreading, don’t start with background. Pick the framework that matches your reader, write the last line first, and work backward. That single habit will save you more rewrites than any amount of “better word choices” ever could - and it’s the same instinct that separates writing people skim from writing people act on.

Knowing the right skeleton is half the job. The other half is filling it in - what you actually say in the subject line, the opening sentence, and the ask itself, especially when the stakes are a real budget or a real signature. That’s exactly the ground writing a persuasive email or proposal covers next.