A pricing experimentation tool
You picked your price in a meeting and never touched it again.
Names an inherited default rather than a deliberate choice.
All selling angles
Selling angleRendered with: Bold Poster
The mistake angle
The mistake angle names an error the viewer is probably making right now, explains why it is costing them, and positions the product as the correction. It borrows the authority of a teacher — which only works if you have actually earned it.
This angle is a close relative of the pain angle with one important difference: pain says "this is happening to you", mistake says "you are doing this". That shift is what gives it stopping power, and also what makes it easy to get wrong. The line between useful correction and condescension is thinner than most scripts assume.
What keeps it on the right side of that line is implicating yourself. "We shipped three launches this way before we noticed" turns an accusation into a shared discovery, and costs you nothing but a sentence. Scripts that skip this read as a stranger telling a professional they are bad at their job.
The mistake also has to be non-obvious. If the error is one your audience already knows about, you have spent the whole video agreeing with them and taught nothing. The best version names something the viewer is genuinely doing without having decided to — a default they inherited rather than a choice they made.
When this angle works
- There is a widespread default in your category that quietly produces bad outcomes
- You can explain the correction in one sentence, not a course
- Your audience thinks of themselves as competent and will respond to a sharper method
- You have the standing to make the correction — usage data, your own scar tissue, or a visible track record
When to use something else
- The mistake is obvious, which makes the video an expensive way to state the known
- Your audience is new to the category and has not made the mistake yet — you are describing a wound they do not have
- The correction requires your product to be true; a mistake angle that resolves only by buying something reads as manufactured
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
Name the default
State the common practice plainly, without judgment yet. The viewer should recognise it as what they do.
“Most launch videos open with the product.”
- Beat 02
Show the cost
Explain what it quietly costs. This is the beat that converts recognition into attention.
“Which means the first three seconds argue with nobody in particular.”
- Beat 03
Implicate yourself
Share the error. One sentence turns a lecture into a comparison of notes.
“We did it for our own launch, twice.”
- Beat 04
The correction
Give the sharper method, and only then connect it to the product.
“Open on the reason someone should care — and make a different one for each audience.”
What it looks like for a SaaS product
Product categories rather than real companies — we do not invent customers, and neither should your script.
A documentation platform
Writing docs last is why nobody reads them.
Non-obvious causal claim the audience can check against their own experience.
An error tracking service
Alerting on everything is the same as alerting on nothing.
Corrects a practice engineers recognise in themselves without feeling insulted.
Questions about this angle
How is the mistake angle different from the pain angle?
Pain describes something happening to the viewer; mistake describes something the viewer is doing. Mistake has more stopping power and more risk, because it assigns agency — which is why the self-implicating beat matters so much.
Will calling out a mistake offend our audience?
It offends when the correction is obvious, when the tone is superior, or when the only fix is your product. Naming a non-obvious default, admitting you made it too, and giving a correction that works even without buying anything avoids all three.
Can this angle work for a technical audience?
It is one of the strongest angles for developers, provided the mistake is real and specifically stated. Technical audiences reward precise corrections and punish vague ones faster than any other segment.
Angles that pair with this one
The myth-busting angle
Myth-busting takes one widely held belief that is keeping people from acting, shows why it is wrong, and installs a better belief in its place. It is an angle about removing a blocker, not about winning an argument.
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.