How to Demo an Action You Cannot Safely Perform
August 22, 2026
Some of the most persuasive moments in software are actions with consequences — an invoice actually sending, a payment actually charging, a record actually deleting, a page actually going live.
These are exactly the actions you cannot casually trigger while recording, and the ones most often skipped as a result. Skipping them removes the proof the buyer came for.
Use a real test account, not a mock
The correct answer for most products is a sandbox or test environment where the action genuinely runs: test-mode payments, a test recipient you control, a throwaway record you are happy to destroy.
This is worth the setup because the demo then shows real states — the real confirmation, the real receipt, the real empty row afterwards. Reconstructed screens are almost always subtly wrong in ways that are noticeable.
Show the whole sequence, including the guardrail
- The confirmation dialog is a feature, not friction, when the action is destructive. Show it.
- The undo window, if you have one, is worth a step of its own.
- The resulting state — sent, charged, deleted — because the outcome is the proof.
- The audit trail afterwards, for anything a buyer will be asked about internally.
What to redact and what to keep
Real recipient addresses, card numbers and customer names come out. The structure stays: a masked card ending in four digits still demonstrates that a card was charged.
Blurring the whole panel is over-correction and it destroys the thing you were proving. Redact the identifying values, keep the surrounding evidence.
Never fake the outcome
An edited screenshot of a payment that did not happen, or a "sent" state assembled in a design tool, is the one line worth treating as absolute. If it comes out — and in a sales cycle it often does, because someone asks to see it live — the demo becomes evidence against you.
If you genuinely cannot run the action, say what the demo stops short of. "The demo ends before the charge; we can run a live test on a call" is a weaker demo and a stronger position.
Frequently asked questions
- How do I demo an action like sending an invoice or charging a card?
- Use a real test environment where the action genuinely runs -- test-mode payments, a recipient you control, a record you are happy to destroy. Real states are subtly right in ways reconstructed screens are not.
- Should a demo include the confirmation dialog?
- Yes. For a destructive action the guardrail is a feature rather than friction, and the undo window deserves its own step. So does the resulting state and, for anything a buyer must justify internally, the audit trail.
- Can I edit a screenshot to show a successful result?
- No -- this is the one absolute. A fabricated result often surfaces, because someone asks to see it live, and then the demo becomes evidence against you. If you cannot run the action, say where the demo stops and offer a live test.
Keep reading
This is what Demorta does
Click through it — the same kind of demo you can record of your own product.
Try it on your own product
Record your first interactive demo free.
Five demos on the free plan, forever. No credit card, no trial countdown, no sales call. Install the Chrome extension, click through your product once, and you have a shareable link in about ten minutes.
Start free →