Topic
Every product category has one moment a demo has to show: the reconciliation that balances, the route that optimises, the report that used to take an afternoon. These guides find that moment for each industry and product type, and say what to record around it.
Written for the vendor. If you sell software into one of these industries and want the demo that its buyers recognise, start with your category.
134 guides
If signing up is free, a demo that says "look what it does" is answering a question nobody had.
Nobody buys a TMS for the happy path. They buy it for the load that goes wrong.
A demo cannot make a price rise welcome. It can make it look like something was bought.
Nobody is buying it, which removes the pitch and leaves the harder half.
This audience can read your code. A demo that oversells is checkable in about a minute.
Every e-commerce demo has two products in it: the shopper sees one, the merchant runs the other.
In EdTech the person who loves your product, the person who buys it and the person who uses it are three different people.
The hard part is not the software. It is producing a demo that looks clinically real without a single line of PHI.
HR software shows salaries, performance ratings and terminations. Almost every screen is a confidentiality problem.
Lawyers evaluate software the way they read contracts: looking for what is missing.
Logistics software is dense tables and multi-day workflows. Both are hostile to a fifteen-minute demo.
Property software is either a tool for agents or a system for owners. They want opposite demos.
Security buyers assume your demo is staged. They are right, and the demo has to account for it.
A demo sent in month one is forgotten by month four, which is when the decision actually happens.
A screen with forty numbers on it communicates none of them.
A canvas is pixels to the browser. That single fact decides your whole approach.
The value is the second person. A recording only has one.
The building is slow and the result is invisible. Both need solving.
Nobody will watch a two-week process in real time. Compress it honestly.
Nobody watching a usage-priced demo is asking what it does. They are asking what the bill will be.
A demo of something people cannot buy yet is a promise. Be careful what it promises.
Buyers forgive a plain interface. They do not forgive not understanding what it does.
The software is capturable. The device is not. Split the demo accordingly.
A spinner in a demo does not read as "processing". It reads as "this is slow".
If every install looks different, a demo of one install is a demo of somebody else.
The whole value is that you never touch the mouse, and a demo records the mouse.
Your buyer sees the admin. Their customer sees something with your name nowhere on it.
The moment a second person appears, the viewer stops knowing who they are.
Show a reconciliation. Everything else in an accounting integration demo is preamble.
The scariest button is usually the one the buyer most wants to see working.
The product works while nothing is happening on screen.
A recorded AI demo is a claim about typical output. Choose the run you show accordingly.
Your dashboard is unreadable at the size people watch demos. Plan for that first.
Your product is the pipe. The demo has to be about the water.
Your competition is not another app. It is the export they already do every Monday.
The question is never whether it syncs. It is what happens to the records they already have.
The person who likes your integration is not the person who can approve it.
No two Notion workspaces look alike. Your demo has to work for someone whose setup you cannot predict.
The admin who will maintain this is the person you have to convince, and they are rarely in the room.
A merchant is deciding whether this will slow their store down. Answer that first.
Nobody buys your Slack integration for the settings page. They buy it for the message.
Payments demos are judged on trust before features. Show the boring parts.
The value is something happening while nobody is watching. Show it happening.
This audience reads the numbers in your screenshots. Make sure they add up.
Ninety percent of invoices are easy. The other ten take the whole week.
Your buyer is in a field, on a phone, in the one month they have time to look.
Two staff, four thousand members, and a renewal season every year.
You are not replacing their system. You are proving you can live next to it.
The person you demo to is not the person who decides.
The backups ran every night for two years. The restore had never been tried.
Nobody buys core banking software because the dashboard looked nice.
Two weeks a year decide whether this software was worth it.
A screenshot of a dashboard is not a demo. It is a wall of small numbers.
A recall means naming every pallet that batch went to. In an afternoon.
The client just added forty people and moved the start time.
The person deciding is also the person doing pickup at six.
The person evaluating your CMMS is standing up, on a phone, between two work orders.
Marketing wants to change a headline. It takes two weeks and a sprint.
Your buyer is standing in mud holding a phone. Design the demo for that.
Legal wants control. Sales wants it to take less than a week.
To the rep, this is not analytics. It is a manager listening.
Nobody buys CPQ because two-line quotes are hard.
You are not demoing a CRM. You are demoing the difference from their last CRM.
Your visitors have been taught that clicking the wrong thing costs them everything.
The same customer exists four times, spelled three ways.
Every pipeline works until the source changes a column name.
The agent has ninety seconds and a script they are not allowed to leave.
Your buyer has ten minutes between patients, and a compliance officer behind them.
The library has forty thousand files and three of them are the right one.
The near miss that never gets reported is the one that repeats.
A laptop was left on a train. That is the demo.
Nobody in a control room is trying your software because a demo looked nice.
Every rental business has the same question: what is out, what is back, what is broken.
Anyone can show a green dashboard. The question is where the number came from.
They are signing on a phone, in a car park, slightly annoyed.
Everything works until three thousand people arrive at once.
The expense report is done at eleven at night, resentfully, three weeks late.
Somebody reported a broken door. Everything after that is the product.
The release is bad and the rollback takes twenty minutes. That is the pitch.
The office loves the dispatch board. The van decides whether you get the deal.
The owner is on the gym floor, not at a desk. And their members are the other half of your demo.
One side wants control. The other wants to be left alone.
This audience builds interfaces for a living. They will notice everything.
In this sector the demo has to survive being read by a committee months later.
They are not imagining the dashboard. They are imagining the finding.
The schedule is the product. Everything else sits around it.
Someone left four months ago and can still open the admin console.
Show the quote. Everything else in an insurance demo is context.
Nobody replaces a service desk because password resets are hard.
The answer exists. Nobody can find it, so they email support anyway.
Your audience spends its working life finding holes in things.
The admin console sells the deal. The learner experience decides whether it renews.
Nobody buys an ERP from a demo. They shortlist from one.
Shore has fibre. The ship has a satellite link and a tired chief engineer.
The journey diagram in the demo has three steps. Theirs has forty.
You have two products and two audiences. Most marketplace demos show neither properly.
Finance says one thing, the CRM says another, and both are certain.
A newsroom will not learn your tool during a news cycle. Show them it needs no learning.
The shift that finds the problem is never the shift that fixes it.
The loan is not waiting on the system. It is waiting on one document.
An MSP needs demos pointing in two directions at once.
The person evaluating may not be the person deciding, and neither may be technical.
Nobody evaluates monitoring on a calm afternoon.
There is a queue behind them and the app is loading.
Nobody changes payroll because it is exciting. They change it because something went wrong.
In this category, the boring compliance screen is the one they came to see.
There is a queue at the counter. Every extra click is a person waiting.
The clinic does not have an admin problem. It has an evenings-and-weekends problem.
A clean catalogue in a demo proves nothing. They already have a clean spreadsheet.
Somebody built two hundred units to the previous revision.
Every printer has lost money on a job they quoted in four minutes.
Somebody bought it on a personal card because the process took nine days.
The work was done in March. The invoice went out in June, for less.
The real audience for your QMS demo is an auditor who is not in the room.
Nobody is evaluating software at 7pm. Build the demo for the gap between shifts.
The buyer is imagining a queue of six people while they watch.
The rep has ninety tasks queued and forty minutes before their first call.
They have eleven minutes between a colour and a cut. That is your demo slot.
Occupancy and delinquency. Everything else is a preference.
The treasurer is a parent who volunteered in a moment of weakness.
The buyer is a recruiter, and a recruiter will not sit through a scheduled demo.
A customer upgraded on the eleventh. What does the invoice say?
The product succeeds when nothing goes wrong, which is hard to film.
Collecting the feedback was never the hard part.
They are not replacing their billing system. Show them you can live beside it.
One misdirected wire ends a company. Everyone in this industry knows one.
The word was "Book". Nobody told them whether it was a verb.
Availability, price and confirmation. Everything else in a booking demo is scenery.
A vet nurse will judge your software in the ninety seconds between appointments.
The office signs it off. The floor decides whether it survives.
Nobody calls to say the bin was emptied.
The schedule is finished. Then two people drop out.
You have the footage. The question is whether converting it beats spending ten minutes recording again.
Training is the one place where making the viewer click the right thing is the point, not friction.