An API monitoring tool
You found out from a customer. Again.
The pain is a specific humiliating event, not "downtime is costly".
All selling angles
Selling angleRendered with: Glitch Title
The 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.
Most SaaS launch videos open with the product. The pain angle deliberately spends its first three seconds elsewhere — on the annoying, specific, Tuesday-afternoon version of the problem. The bet is that a viewer who thinks "that is my week" will stay for the part where you explain yourself, and a viewer who does not think that was never going to convert anyway.
The failure mode is vagueness. "Managing projects is hard" describes nothing and moves nobody. "You have three tools open and none of them agree on the deadline" describes a specific afternoon. Specificity is doing all the work here, and it is the part most teams skip because specific pains feel too narrow to put in an ad. They are not too narrow — they are the reason the ad lands.
The second failure mode is dwelling. Pain is an opener, not a subject. Once the viewer has recognised themselves, every extra second spent on how bad things are is a second spent making your product feel like part of the misery. Get in, get recognised, get out.
When this angle works
- Your product solves a problem people actively complain about, in words you can quote back to them
- You are reaching cold audiences who do not know your category exists
- The pain is frequent and concrete rather than occasional and abstract
- Your competitors are all leading with features, so the problem framing is unoccupied
When to use something else
- Your product creates upside rather than removing pain — a tool that makes good work better has no wound to press on, and inventing one reads as manipulation
- The pain is embarrassing or identity-threatening, where naming it makes viewers defensive instead of interested
- You are talking to an audience already shopping in your category, who have moved past problem recognition and want comparison and proof
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 specific moment
Name one concrete situation, not a category of problem. The viewer should be able to date the last time it happened to them.
“It is 6pm and you are still copying numbers between two dashboards.”
- Beat 02
The cost you do not count
Escalate once, to the consequence the viewer has stopped noticing because it is normal.
“That is four hours a week you never put on a timesheet.”
- Beat 03
The turn
Introduce the product as the exit, in one line. This is the only beat that mentions you.
“Both dashboards, one view, updated on their own.”
- Beat 04
The proof and the next step
Show the product doing the thing, then ask for one small action. Keep the ask proportional to a first meeting.
“Connect a source and see it merged. Free while you look.”
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 team scheduling app
Six people, four time zones, and one meeting that keeps moving.
Concrete enough that the target user pictures a named colleague.
An expense tool for small teams
Your receipts are in a shoebox, a Slack DM, and someone else's inbox.
Names where the mess actually lives instead of saying "disorganised".
Questions about this angle
Is the pain point angle too negative for a product launch?
It is negative for about three seconds. The structure spends most of its runtime on the exit rather than the wound. What makes pain angles feel bleak is dwelling — staying in the problem past the point of recognition — not the opening itself.
How do I find the right pain to lead with?
Use language your users already produced: support tickets, sales call notes, churn surveys, and the review sites for the tool they are leaving. The goal is a sentence you could have quoted rather than one you wrote.
Can one product use several pain angles?
Yes, and it usually should. Different segments feel different versions of the same underlying problem, and a pain angle written for an engineer rarely lands with a finance lead. Producing one video per pain is cheaper than trying to write a pain that covers everyone.
Angles that pair with this one
The cost-of-inaction angle
Most deals are lost to nothing at all — not a competitor, but a decision that keeps getting postponed. This angle makes the price of postponing visible, using the viewer's own numbers rather than manufactured urgency.
Read the angleThe 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.
Read the angleThe 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.
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.