FREEFirst project with us? Your landing page design is on the house.See the offer

Process

SaaS website copy frameworks, and when to use each

Six copy frameworks for SaaS websites: PAS, AIDA, Before After Bridge, FAB, Jobs to Be Done and 4U. When each one fits, with short worked examples.

By Abdul QuadirUpdated 2026-10-246 min read
TL;DR
  • A framework gives copy a shape. It does not give you something to say. That comes from talking to customers.
  • Use Jobs to Be Done to find the message, then PAS, Before After Bridge or AIDA to shape it.
  • FAB is good for feature sections, and 4U is a handy check for headlines.
  • Do not fit a whole page into one framework. Different sections have different jobs.
  • Clear beats clever. If a stranger cannot tell what you do, no formula will save the page.

The short answer

The most useful copy frameworks for SaaS websites are Jobs to Be Done for working out what to say, PAS and Before After Bridge for explaining a problem and its solution, AIDA for the flow of a page, FAB for features, and 4U for headlines. Each is a simple tool, and none works without knowing your customer.

The examples below use an imaginary invoicing tool, to show the shape. Write yours from what your real customers say.

First: do the research

Frameworks arrange what you know. So find out first. A few hours can make a big difference:

  • Listen to recorded sales calls, and note the exact words buyers use.
  • Read support tickets, cancel reasons and reviews, including reviews of competitors.
  • Ask recent customers what they used before, and what made them switch.
  • Write down the doubts that come up before people buy.

Keep a sheet of direct phrases. Good copy often comes straight from it, with permission if you quote someone by name.

1. Jobs to Be Done: find the message

The idea. People "hire" a product to make progress in a situation. Instead of describing features, you describe the situation and the progress.

A simple form. When [situation], I want to [motivation], so I can [outcome].

Example. When a client is late to pay, I want to chase them without an awkward email, so I can get paid and keep the relationship.

Use it for positioning, deciding what the page is about, and choosing which use cases to show. It is more of a research tool than a writing formula, so do this first.

2. PAS: Problem, Agitate, Solution

The idea. Name the problem, show what it costs, then offer the way out.

Example. Late invoices eat your week. You chase, you wait, and you still cannot say when the money will arrive. Our tool sends the reminders for you, and shows you who pays when.

Use it for problem sections, landing pages and ads. It suits products that solve a pain people already feel.

Be careful. Agitating too hard feels pushy, and B2B buyers notice. Describe the real cost and do not invent a crisis.

3. Before After Bridge

The idea. Show life now, show life after, then explain what takes you from one to the other.

Example. Before: three spreadsheets and a Friday spent chasing payments. After: one screen that shows what is due, with reminders already sent. The bridge: connect your accounting tool and set your rules once.

Use it for hero sections, how it works sections and customer stories. It is softer than PAS, so it suits buyers who are not in pain yet but want better.

4. AIDA: Attention, Interest, Desire, Action

The idea. An old and simple model for the flow of a whole page. Get attention, hold interest with something relevant, build desire with benefits and proof, then ask for the action.

On a page, roughly.

  • Attention. A headline that names the outcome.
  • Interest. The problem and a view of how you solve it.
  • Desire. Benefits, customer stories, and answers to doubts.
  • Action. A clear next step, with what happens after it.

Use it for checking the order of a long page. See how we design landing pages that convert for how this looks in practice.

5. FAB: Features, Advantages, Benefits

The idea. Connect what the product has, to what it does, to why that matters to the reader.

Example. Feature: automatic payment reminders. Advantage: they go out on a schedule you set, with no manual work. Benefit: you get paid sooner, without writing another awkward email.

Use it for feature sections and product pages. It is the fastest cure for a page full of feature names. Do not claim a benefit that you cannot back up, though. "Get paid sooner" needs to be true for your customers.

6. The 4 Us: a check for headlines

The idea. A headline should be useful, urgent, unique and ultra specific. You will rarely hit all four, so use it as a way to compare options.

Example. Weak: "The future of invoicing." Better: "Send invoices that chase themselves." The second says what the product does. The first could describe any invoicing tool.

Use it for reviewing headlines. For SaaS, useful and specific matter most. Fake urgency hurts trust in B2B.

Which framework goes where

  • Positioning and messaging: Jobs to Be Done.
  • Hero: Before After Bridge, checked with the 4 Us.
  • Problem section: PAS, kept gentle.
  • Feature section: FAB.
  • Whole-page flow: AIDA.
  • Customer story: Before After Bridge.
  • Ads and short landing pages: PAS.

For what the page should include, see the pages every SaaS website needs. If you sell to specific sectors, our SaaS page shows how we think about them.

Mistakes to avoid

  • Clever over clear. A pun may work in an ad. On a homepage, people need to know what you do.
  • Writing about yourself. Count "we" and "our", then rewrite sentences around the reader.
  • Empty words. "Seamless", "powerful" and "all in one" cannot be checked. Say what actually happens.
  • Claims you cannot prove. Do not state results without evidence, and check claims with whoever needs to approve them.
  • Copy written after the design. Decide what needs to be said first, then design around it.
  • Copy that AI wrote with no research. AI can help you draft, but it cannot know your customers' words unless you give them to it.

A simple way to test your copy

  1. Read it aloud. Fix anything you would not say to a customer.
  2. Replace your product name with a competitor's. If the sentence still works, it is too general.
  3. Ask someone in your market to explain your page back to you.
  4. Check that your page answers real questions in plain language. This helps search and AI tools too. See What is AEO?
  5. Test big differences, such as a new angle, not small word swaps. See A/B test.

What to do next

Start with one page, ideally your homepage. Gather real customer words, and rewrite the hero and the problem section first. If you want help, see strategy and copywriting or talk to us.

More reading: how to write a website brief.

Abdul Quadir
Abdul QuadirFounder of Kookies. Builds Webflow and Astro sites for startups and growing teams.

Terms used: Core Web Vitals, AEO

FAQs

Questions
people ask.

Abdul Quadir
Still have a question?Ask us directly. We reply within a day.
Book a callPick a timehello@kookies.io

There is no single one. Use Jobs to Be Done to work out the message, then PAS, Before After Bridge, AIDA or FAB for each section.

Problem, Agitate, Solution. You name the problem, show what it costs, and then offer the way out.

PAS leans on a pain the reader feels now. Before After Bridge paints the better state and how to reach it, so it feels softer.

Not strictly. AIDA can guide the flow of the page, but each section may use a different structure.

It can help you draft and edit. It cannot replace real customer research, and a person should check every claim.

Ask people in your market to explain the page back to you, watch what they do next, and test big differences if you have enough traffic.

Your turn

Let's kook
what you krave.

Hi Kookies, I need a built on . I'd love to launch . Reach me at
or book a callSent. We reply within one working day.