How to Demo a Product That Takes Time to Respond
August 22, 2026
Some products do real work — importing a file, rendering an export, syncing an account, running a model. That work takes seconds or minutes, and in a demo it is dead air.
The temptation is to hide it entirely. That is a mistake for a specific reason: buyers who discover the wait after signing up feel misled, and the wait was rarely the dealbreaker anyway.
Compress the wait, do not conceal it
Keep one step showing the operation in progress, then cut to the finished state. The viewer sees that a wait exists, sees it is a normal part of the flow, and does not have to live through it.
The caption does the honest work: "Imports run in the background — a 10,000-row file takes about two minutes." That sentence prevents a support ticket and costs you nothing, because nobody rejects a product over two minutes they were told about.
Show the waiting state as a feature, if it is one
- A progress bar with a real estimate is reassuring; a bare spinner is not.
- "You can close this tab" is worth a whole step if it is true.
- An email when it finishes turns waiting into something handled rather than endured.
- A partial result while it works is the strongest version, and worth showing if you have it.
Capture the finished state separately
Do not record yourself waiting. Trigger the operation, capture the in-progress step, then let it complete and capture the result as its own step. The demo shows a continuous story assembled from two moments, which is what every demo is anyway.
This also avoids the worst version of the problem: a recording that captured a timeout, an error, or a spinner that never resolved because the tool moved on before the page did.
Do not demo the slowest path
If a 200-row import takes four seconds and a 50,000-row import takes twenty minutes, demo the first one. That is not dishonesty — it is choosing a representative case, the same as choosing which feature to show.
It becomes dishonest when the fast case is the unrepresentative one. If most customers arrive with the large file, showing the small one sets up a disappointment that surfaces in week one.
Frequently asked questions
- Should a demo hide loading times?
- Compress them, do not conceal them. Keep one step showing the operation in progress, then cut to the finished result, with a caption stating the real duration. Buyers who discover a wait after signing up feel misled, and the wait is rarely the dealbreaker.
- How do I record a step for a slow operation?
- Do not record yourself waiting. Trigger the operation and capture the in-progress step, then let it finish and capture the result as a separate step. This also avoids recording a timeout or an unresolved spinner.
- Is it dishonest to demo the fastest case?
- Not if it is representative. Choosing a 200-row import over a 50,000-row one is the same kind of choice as picking which feature to show. It becomes dishonest when most customers actually arrive with the large file.
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 →