A vector search service
Your docs go in. Here is what happens to them before a query hits.
Mechanism-first for an audience that will not accept a black box.
All selling angles
Selling angleRendered with: How It Works
The 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.
A surprising amount of hesitation in software buying is not about value but about plausibility. The viewer believes the outcome would be good and does not believe it can happen the way you describe. No amount of benefit language fixes that; only mechanism does.
The hard constraint is depth. Too shallow and it is a benefits video with arrows; too deep and you have made onboarding documentation that nobody watches. The workable target is three or four steps where each one is something the viewer can picture themselves doing, and where the interesting part — the bit that makes it work — is visible in at least one of them.
For developer tools this angle usually outperforms everything else, because the audience evaluates by mechanism as a matter of professional habit. A dev-facing video that hides the mechanism reads as though there is something to hide.
When this angle works
- The outcome sounds implausible until it is explained
- Your audience evaluates on mechanism — developers, technical buyers, operators
- The product does something structurally different from the obvious approach
- You are converting warm traffic that already understands the value
When to use something else
- The mechanism is boring or identical to every competitor, where showing it removes your differentiation for free
- Explaining honestly requires more prerequisites than the format allows
- The audience is cold and has not yet accepted there is a problem — mechanism before motivation lands on nobody
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 promise, compressed
One line naming the outcome so the mechanism has something to explain.
“A product page becomes eight different launch videos.”
- Beat 02
Step one, concretely
Start where the user starts, with the input they actually have.
“It reads the page you already wrote.”
- Beat 03
The interesting step
Show the part that makes it work. This is the beat the viewer came for.
“Then it argues the same product eight different ways — pain, proof, comparison, and so on.”
- Beat 04
Where you take over
End at the handoff. Naming what stays under the user's control resolves the trust question.
“Every scene is editable before anything is exported.”
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 feature flag platform
One flag, three environments — here is the evaluation path.
Shows the interesting step rather than the setup steps.
An invoice reconciliation tool
How it matches a payment to an invoice when the amounts do not agree.
Picks the hard case, which is where plausibility is actually won.
Questions about this angle
How much detail belongs in a how-it-works video?
Enough that a sceptic stops objecting, and no more. Three or four steps is the usual ceiling. If you find yourself defining terms, the video has turned into documentation and should link to the real docs instead.
Is this the same as a demo?
No. A demo shows the interface; how-it-works explains the mechanism behind it. A demo answers "what is it like to use", this answers "why does that work" — and technical buyers usually need the second before the first matters.
Should the mechanism video come before or after the value video?
After, in a sequence. Mechanism explains a promise the viewer has already accepted as desirable. Shown to a cold audience it explains something they have not yet decided they want.
Angles that pair with this one
The feature spotlight angle
A feature spotlight gives one capability the whole runtime. Its entire discipline is subtraction: the moment a second feature appears, it stops being a spotlight and becomes the feature list that nobody remembers.
Read the angleThe 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 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.