How do you demo a process that takes days?

Compress it and say so. The step where time passes needs a caption -- "Two days later, the manager approves" -- otherwise viewers read the sequence as continuous and conclude the product is faster than it is.

What matters most in a workflow demo?

The handoffs: the notification telling the next person it is their turn, that person's own view, a reminder firing when nobody acted, and the audit trail. The handoffs are the product; the individual screens are not.

Should a workflow demo show more than one person's screen?

Yes -- requester, approver, finance -- and it should say whose screen each step is on. Without that it reads as one confused person clicking through unrelated pages rather than a process moving between people.

← Back to blog

How to Demo a Process That Takes Days or Weeks

August 21, 2026

Approval workflows, hiring pipelines, insurance claims, employee onboarding, loan applications, shipping — plenty of software exists to manage a process measured in days, and a demo is measured in seconds.

A stepped demo is unusually well suited to this, because it can jump time in a way a video cannot.

Say when time passes

The step where "two days later" happens has to say so. Without it, a viewer reads a sequence of screens as a sequence of moments and concludes the product is faster than it is.

A caption is enough: "Two days later, the manager approves." That single line is what makes a compressed demo honest rather than misleading.

Show the handoffs, because that is the product

The notification that told the next person it was their turn.
The other person's view, which is a different screen and often a different app.
A reminder firing when someone did not act, since that is where these processes fail.
The audit trail, which is frequently the actual reason for purchase.

Compare against what it replaces

These products almost always replace a chain of emails and a spreadsheet. The buyer is not comparing you to a competitor, they are comparing you to chaos.

A demo that shows the current mess in one step — an inbox, a version-numbered file — and the same process in the tool afterwards makes an argument no feature list can.

Multiple people, one demo

Record it as the process, not as one person's screen: requester submits, manager approves, finance pays. Switching between roles is exactly what makes the value legible.

Say whose screen each step is on. Without it, the demo reads as one confused person clicking through unrelated pages.

End with the report

The person buying a workflow tool is usually the person accountable for the process, and what they want is visibility: how many are in flight, where they are stuck, how long they take.

That dashboard is the closing step, and it is a different argument from the workflow itself.

Frequently asked questions

How do you demo a process that takes days?: Compress it and say so. The step where time passes needs a caption -- "Two days later, the manager approves" -- otherwise viewers read the sequence as continuous and conclude the product is faster than it is.
What matters most in a workflow demo?: The handoffs: the notification telling the next person it is their turn, that person's own view, a reminder firing when nobody acted, and the audit trail. The handoffs are the product; the individual screens are not.
Should a workflow demo show more than one person's screen?: Yes -- requester, approver, finance -- and it should say whose screen each step is on. Without that it reads as one confused person clicking through unrelated pages rather than a process moving between people.

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 →