A backup service
Nothing has gone wrong yet. That is the entire argument for waiting.
Names the deferral logic explicitly instead of pretending urgency.
All selling angles
Selling angleRendered with: Cost of Inaction
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.
The default outcome for any software purchase is deferral. Nothing bad happens today if the decision waits until next quarter, and that asymmetry is what quietly kills pipelines. The cost-of-inaction angle exists to make the invisible running cost of "later" visible enough to compete with the very visible cost of acting.
It has to be arithmetic the viewer can check, not pressure. Four hours a week at a rate they know is a number they can verify against their own timesheet, and verification is what makes it persuasive. A countdown timer or a fake deadline achieves the opposite: it tells a careful buyer that you are willing to manufacture pressure, which raises the perceived risk of dealing with you at all.
The most common execution error is inflating the number. A defensible small figure outperforms an impressive large one, because the viewer is going to sanity-check it against their own experience within about two seconds. Lose that check and you have lost the whole video.
When this angle works
- The cost of waiting is real, ongoing, and calculable from numbers the viewer already has
- Your audience is stuck in deferral rather than choosing a competitor
- The problem compounds — technical debt, data loss, accumulating manual work
- You are talking to someone who has to justify the spend internally and needs the arithmetic
When to use something else
- The cost of waiting is genuinely low, where the honest answer is that they can wait and pretending otherwise is a lie with a spreadsheet attached
- You would need invented or unverifiable figures to make the case
- The audience has not yet accepted the problem exists — you cannot price the delay of solving something they do not think is happening
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 unremarkable weekly cost
Start with something so small it is not worth acting on. Credibility begins here.
“Forty minutes a week, reconciling two lists.”
- Beat 02
Extend the horizon
Same number, longer window. Let the arithmetic do the escalating rather than the language.
“By the end of the quarter that is a full working week.”
- Beat 03
The compounding part
Name what gets worse rather than merely accumulating — the part that is not linear.
“And the mismatches you did not catch are now in three reports.”
- Beat 04
The proportional step
Ask for an action sized to the problem. An honest small ask beats manufactured urgency.
“Connect one source this week. Not a migration — one source.”
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 dependency updater
Eleven versions behind. Next quarter it is nineteen.
Compounding stated as arithmetic the team can verify in their own repo.
A data quality tool
Every week of bad rows is a week of dashboards someone will trust.
The compounding cost is downstream belief, not just accumulated work.
Questions about this angle
How is this different from creating urgency with a deadline?
A deadline is a cost you impose; cost of inaction is a cost the viewer is already paying and had not counted. The first is discounted by anyone who has seen a sales tactic before. The second is arithmetic they can check, which is why it survives scrutiny.
What if we do not know the customer's numbers?
Use a stated assumption and show your working — "if this takes your team an hour a week" — so the viewer can substitute their own figure. Never present an assumed number as a measured one; the moment that is noticed, every other figure in the video is discounted too.
Does this angle work for cheap products?
It works best when the cost of inaction obviously exceeds the price, which is usually easier to demonstrate at low price points. At twenty dollars a month, one saved hour a quarter already closes the argument.
Angles that pair with this one
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.
Read the angleThe statistic angle
One number, given the whole frame. The statistic angle works when the figure is surprising, verifiable, and about the viewer's situation rather than your company's success — and it fails completely the moment the number cannot be sourced.
Read the angleThe 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 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.