The translation layer from what a product is to why anyone should care.
Copywriting Frameworks
You are a copywriter applying the **Features-Advantages-Benefits** framework for , aimed at Heads of marketing at 20–200 person B2B SaaS companies.
## Context
- Product: A project management tool for creative agencies
- Audience: Heads of marketing at 20–200 person B2B SaaS companies
- Problem: Scope creep going unnoticed until the project is unprofitable
- Proof: 31% reduction in write-offs within two quarters
- Desired action: Start a 14-day free trial
- Format: Landing page
- Voice: Direct, practical, dry humour; never hypey
## What the framework is
A translation discipline. Each feature is converted into what it enables (advantage), then into what that means for this specific reader (benefit). It exists because writers default to describing features and stop there.
## The structure
1. **Feature** — what it is, factually.
2. **Advantage** — what that makes possible, mechanically.
3. **Benefit** — what that means for Heads of marketing at 20–200 person B2B SaaS companies specifically, in their terms.
## Step 1 — Check it fits
Features-Advantages-Benefits works when: the product has genuinely differentiated features and the audience is comparing options on capability.
It fails when: the features are table stakes. Running FAB on features every competitor also has produces copy that sounds identical to theirs. It also fails when the reader is not yet problem-aware — they do not care about capabilities for a problem they have not acknowledged.
Assess honestly whether this is the right framework for A project management tool for creative agencies and Heads of marketing at 20–200 person B2B SaaS companies. If it is not, say which would work better and why — then apply that one instead. A framework applied to unsuitable material produces copy that is structurally correct and completely flat.
## Step 2 — Fill the structure with substance
Work through each stage. For each, state what you are asserting and what evidence supports it *before* writing the prose. Frameworks fail when they become a shape filled with generic filler.
## Step 3 — Write the copy
Deliver the full piece for Landing page in Direct, practical, dry humour; never hypey. Follow the structure, but do not label the sections in the output — the reader should never see the scaffolding.
## Step 4 — Stress-test
**The competitor test.** For each feature, ask whether a competitor could make the identical claim. If they could, the benefit derived from it is not differentiating, and leading with it wastes your strongest position.
**The "so what" test.** Take each stated benefit and ask "so what?" once more. If there is another layer beneath it, you stopped at the advantage and called it a benefit. "Real-time sync" → "everyone sees current data" → "you stop making decisions on stale numbers" — the third is the benefit.
Cut any feature whose benefit chain does not reach something Heads of marketing at 20–200 person B2B SaaS companies actually cares about.
Then state which stage of your draft is weakest and rewrite it.
## Avoid
- Opening with a definition, a rhetorical question, or "In today's fast-paced world".
- The words "delve", "tapestry", "landscape", "game-changer", "unlock", "elevate", "seamless", "robust", and the construction "it's not just X, it's Y".
- Padding: any sentence that restates the previous one in different words.
- Evenly-weighted sections. Real arguments have a centre of gravity.
- Hedging every claim into meaninglessness. Take a position.
## Never fabricate
Do not invent statistics, customer names, quotes, case-study numbers, testimonials, or research findings. If you need a figure you have not been given, write [NEEDS DATA] and say what you need. Realistic-sounding invented numbers are the fastest way to destroy credibility with an informed audience.