The BAB Framework for AI Prompts (Before – After – Bridge)

TL;DR: BAB (Before – After – Bridge) is a classic copywriting framework: the reader's problem, their life once it's solved, and your product as the bridge between them. As an AI prompt it works two ways: ask a model to write BAB-structured copy, or structure your own prompt as current state, desired state, and the transformation you want. Both uses, plus where BAB oversells, are below.

Two different readers land on this page. If you want AI to produce copy shaped like Before-After-Bridge for a landing page, an email, or an ad, that's the more common use, and it's covered first with a worked example and 12 ready prompts. If you came here because you want to use the before/after/bridge shape to brief the model itself (describing a current draft, the end state you want, and the change to make), that's a genuinely different technique, covered further down. Both are legitimate uses of the same three-beat idea; they just point in opposite directions.

What Is the BAB Framework?

BAB stands for Before, After, Bridge: a copywriting structure that's been standard in direct-response marketing for decades, well before anyone was prompting a language model. It has no single credited inventor; it belongs to the same family of persuasion formulas as PAS and AIDA, all of which predate AI writing tools by a long way.

Before names the reader's current problem, in language close to how they'd describe it themselves, not the vaguer, more generic version a marketer might default to. After paints their life once the problem is gone: the outcome that matters to them, not a list of features. Bridge is your product or offer, framed specifically as what closes the gap between those two states, not as a general pitch.

The reason it still works on an AI writing task is structural, not magical: it forces the model to write concretely about a specific pain and a specific outcome before it's allowed to mention the product at all. Left to a vague brief, models default to describing features first and benefits vaguely. BAB's ordering prevents that.

How Do You Write Each Part of a BAB Prompt?

Take a project-management tool as a working example, deliberately generic so the pattern is visible without borrowing a real product's specifics.

Before, written concretely: "A ten-person team loses track of who owns what. Status updates happen in four different Slack channels and nobody trusts the roadmap doc because it's three weeks out of date." Specific tools, specific number, specific symptom. Not "teams struggle with organization."

After, written as an outcome, not a feature: "Every person on the team can answer 'what am I blocked on' in ten seconds, without asking anyone. The roadmap reflects reality because updating it is the same action as marking a task done." Notice this describes a changed experience, not a changed interface.

Bridge, naming the product plainly: "[Product] does this by making the task board and the roadmap the same object — no separate status update, no separate planning doc." One sentence, no adjectives doing the persuading.

Here's the same structure as a single prompt you can paste into any model:

Write BAB-structured copy (Before / After / Bridge) for [CONTEXT — e.g. landing page hero, cold email, ad].

Audience: [who specifically — role, company size, situation]
Before: [the specific problem, in the audience's own language — not a generic complaint]
After: [the specific outcome — what changes for them, not what feature they get]
Bridge: [product name] + [the one specific mechanism that gets them from Before to After]

Write one tight paragraph per beat. No adjectives standing in for evidence.
Do not invent a statistic, a customer quote, or a result I haven't given you.

That last line matters more than it looks; see the section on where this goes wrong, below.

What Are the Best BAB Prompts for Marketing Copy?

Twelve ready-to-copy prompts, organized by the format you're writing. Fill in the bracketed specifics. The framework does the ordering; you still supply the actual Before and After.

Landing page hero

Write a BAB-structured hero section for a landing page.
Before: [specific frustration the visitor has right now]
After: [specific state once solved — one sentence, concrete]
Bridge: [product] does this by [one mechanism]
Format: headline (under 10 words) + 2-sentence subhead. No invented stats.

Write a BAB landing page intro (100-150 words) for [product] targeting [audience].
Lead with Before as a scene, not a statement. End Bridge with a single next action, not a list of features.

Cold email

Write a BAB cold email to [role] at [company type].
Before: one sentence naming a problem they'd recognize, not a generic pain point.
After: one sentence on the specific outcome.
Bridge: one sentence connecting [product] to that outcome, plus a low-commitment ask.
Under 90 words total. No fabricated social proof.

Write a BAB follow-up email for someone who opened but didn't reply.
Keep Before to a single reminder line. Spend most of the email on After.
Bridge should be a question, not a pitch.

Ad copy

Write 3 BAB variants of a [Meta/Google] ad for [product], each under 40 words.
Before must differ across all 3 — three different entry points into the same problem.
After and Bridge can stay consistent. Flag which variant leads hardest with emotion vs. specificity.

Write a BAB script for a 15-second video ad.
Before: 3 seconds, visual + one line of copy.
After: 5 seconds, the payoff.
Bridge: 7 seconds, product name + the mechanism, plus a CTA.

Sales page

Write a BAB section for a sales page, positioned after the headline and before pricing.
Before: 2 short paragraphs building a scene of the current problem.
After: 2 short paragraphs on life afterward — specific, not aspirational fluff.
Bridge: 1 paragraph introducing [product] and its core mechanism, ending with a link to pricing.

Rewrite this sales page section [PASTE] using BAB structure.
Identify what's currently Before, After, and Bridge in the existing draft, then reorder and tighten so each beat is one clear paragraph.

Case study framing

Write a BAB summary (80-100 words) for a case study about [customer/situation].
Before: their situation prior to using [product], stated as fact, not drama.
After: the specific change, using only the details I give you below — do not estimate a number I haven't provided.
Bridge: one sentence on what they did differently.
Details: [paste the real facts here]

Write a BAB pull-quote style summary for a case study, under 50 words, suitable for a homepage testimonial block. Use only facts provided below; if a number isn't given, describe the change qualitatively instead of guessing.

LinkedIn post

Write a BAB LinkedIn post (150-200 words) about [topic/product], first-person, from a founder's voice.
Before: an honest, specific frustration — not a humblebrag disguised as a problem.
After: the change, described plainly.
Bridge: one line connecting it to [product], no hard sell. End with a question, not a link.

Write a BAB LinkedIn post recounting a real mistake and its fix.
Before: what went wrong, without excuse-making.
After: what's true now.
Bridge: the one decision or tool that made the difference. Keep it under 180 words.

Can BAB Structure the Prompt Itself, Not Just the Output?

This is the less obvious use, and it's a genuinely good prompting pattern independent of copywriting entirely: instead of asking for BAB-shaped output, you shape the instruction as Before (current state), After (desired end state), and Bridge (the specific transformation).

This works because it front-loads exactly what a rewriting, editing, or refactoring task needs and a vague instruction usually omits: what exists now, what "done" looks like, and what has to change to get there. Compare an underspecified ask ("make this better") with the same task briefed in BAB shape:

Before (current state): [paste the current draft, code, or document as-is]
After (desired end state): [describe specifically what "done" looks like —
  tone, length, what a reader/user should be able to do or understand]
Bridge (the transformation): [name the specific changes — e.g. "cut by 40%,
  remove jargon, add one worked example" — not just "improve it"]

Apply the transformation described in Bridge to move the input from Before to After.
Don't change anything the Before/After description doesn't call for.

The template generalizes past writing tasks. It works for a code refactor ("Before: this function; After: it should handle null input without throwing; Bridge: add a guard clause and a test") as cleanly as it works for a paragraph rewrite. The common failure with rewriting prompts is a model that "improves" things you didn't ask it to touch; naming Before and After explicitly constrains what counts as done.

Where Does BAB Cross Into Manipulation?

BAB is a persuasion structure, and its failure mode sits specifically in the After beat. The framework rewards a vivid, specific After, and the shortest path to vivid is to describe an outcome more certain, faster, or more dramatic than what the product reliably delivers.

The fix is procedural, not stylistic: never let a model generate the "result" half of a case study or testimonial from nothing. Give it the real facts and ask it to write around them, and explicitly instruct it not to estimate or invent a number you haven't supplied; both prompts in the case-study section above do this. If you don't have a real result yet, write the After beat as a described experience ("you'll know what's blocked without asking") rather than a claimed outcome ("teams see productivity double"). The first is honest framing, the second is a number nobody measured.

BAB vs PAS vs AIDA: Which Framework Should You Use?

All three are persuasion shapes, not competitors in the sense that you pick one and never use the others. They suit different emotional entry points and different lengths of copy.

In practice, BAB and PAS are often interchangeable at the sentence level (same three slots, different emotional lever in the middle beat), while AIDA is closer to a container that a BAB or PAS beat can sit inside, usually in the "Desire" stage. If you're deciding between BAB and PAS for a specific piece, ask whether the audience needs to feel the cost of waiting (PAS) or needs to picture the better state clearly (BAB). For the wider set of structures, including reasoning-oriented frameworks that have nothing to do with copywriting, see The 7 ChatGPT Prompt Frameworks Every Power User Knows, or for a similarly compact single-purpose framework, the RTF prompt framework.

If you write a lot of BAB copy — landing pages this week, cold emails next — the repetitive part isn't the structure, it's re-typing the same Before/After/Bridge skeleton with new specifics every time. A saved template in a prompt library removes that step; the prompt engineering cheat sheet covers BAB alongside the other structures worth keeping on hand, and the AI prompts for email, ads, and landing pages post has more ready-made copy prompts organized by channel if you write these regularly. For a different single-purpose structure worth comparing against BAB and PAS, see the AUTOMAT framework.