A release notes tool
Before: a doc nobody updated. After: notes that write themselves from the merge.
One axis — who does the writing — held constant across both halves.
All selling angles
Selling angleRendered with: Before / After
The before / after angle
The before-after angle puts two states side by side and lets the gap between them make the argument. It is the most legible angle there is, which is exactly why it is easy to do badly: the contrast only persuades when both halves are honest.
This angle asks very little of the viewer. There is no claim to evaluate, no feature list to parse — just two pictures and the distance between them. That legibility is why it survives being watched on mute in a feed, and why it works for products whose value is hard to describe but easy to see.
The trap is a strawman before. If the "before" state is a mess nobody actually has — six browser tabs artfully arranged, a spreadsheet with deliberately terrible formatting — the whole thing collapses, because the viewer knows their real workflow is not that stupid. A believable before is unglamorous and slightly boring. That is the point. The gap should come from the after being genuinely better, not from the before being rigged.
The second thing teams get wrong is contrasting the wrong axis. Before-after works on one dimension at a time — time taken, steps required, people involved, mess produced. Trying to show that everything is better simultaneously produces two vague states and no readable gap.
When this angle works
- The improvement is visible rather than conceptual — fewer steps, less time, cleaner output
- Your product replaces a workflow people can picture, not an abstraction
- You want an angle that reads with the sound off
- You have a real before state to point at, ideally one your own team lived through
When to use something else
- The change is qualitative and slow — better decisions, stronger culture, less risk — where any before-after you build is a claim dressed as a demonstration
- Your honest before is "nothing", because the user was not doing this at all; that is a new-behaviour story, not a transformation
- You would have to exaggerate the before to make the gap readable, which is the single fastest way to lose a technical audience
Script structure
How to build the script
Each beat has a job. Keep the order, replace the examples with your own product and your own numbers.
- Beat 01
The before, played straight
Show the current workflow without mockery. Credibility is the whole budget here.
“Today: export the CSV, clean it, paste it, chase whoever owns the last column.”
- Beat 02
One named axis
State the single dimension the comparison runs on, so the viewer knows what to watch.
“Forty minutes, every Monday.”
- Beat 03
The after
Same task, same axis, new state. Keep the framing identical so the eye does the comparison.
“Now: it is already there when you open it.”
- Beat 04
The honest boundary
Say what did not change. A limit stated on purpose buys more trust than the claim costs.
“You still decide what ships. It just stops being a copy-paste job.”
What it looks like for a SaaS product
Product categories rather than real companies — we do not invent customers, and neither should your script.
An onboarding SDK
Two weeks of glue code, or an afternoon.
Time is the only dimension, so the gap is instantly readable.
A customer feedback aggregator
Before: feedback in five inboxes. After: one list, ranked.
The before is unglamorous and true rather than a strawman.
Questions about this angle
How long should each half of a before-after video be?
Roughly a third on the before and two thirds on the after. The before only needs to be long enough to be recognised — its job is orientation, not persuasion.
Does the before have to be a competitor?
No, and it is usually stronger when it is not. Naming a competitor turns a demonstration into a fight and invites the viewer to defend a tool they already chose. The manual workflow is a safer and more common before.
What if our after is not dramatic?
Then pick a narrower axis until it is. An undramatic gap across everything is often a dramatic gap on one specific step, and one honest step beats a vague overall improvement.
Angles that pair with this one
The comparison angle
The comparison angle places your product next to the alternative the viewer is actually considering — which is often a spreadsheet, not a competitor — and argues on one axis that matters. Done fairly it is the highest-intent angle you can run. Done unfairly it is the fastest way to look small.
Read the angleThe pain point angle
The pain angle opens on the problem your user already has, in language they would use themselves, and only then shows the product as the way out. It works because recognition comes before interest: nobody evaluates a solution to a problem they have not admitted having.
Read the angleThe how-it-works angle
This angle answers the question a sceptical viewer is already asking: fine, but how? It converts interest into belief by showing the mechanism — enough of it to be credible, not so much that it becomes documentation.
Read the angleBrowse the full angle library for the rest of the directions available in the product.
Get this angle for your own product
Paste your product page and get this angle back as an editable video—alongside the other directions worth testing.