Naming and Organising Your Demos Before It Gets Messy
August 19, 2026
Nobody sets up a naming convention for their first demo, and they are right not to. The problem is that the transition from "a few demos" to "which of these seven is on the homepage" happens quietly and quickly.
The cost is not tidiness. It is that nobody can tell which demo is live, so nobody dares delete anything, so the library fills with copies.
The three things a name has to carry
- Where it is used. Homepage, cold email, help centre, a specific campaign. This is the thing you will most often need and the thing most names omit.
- What it shows, in buyer language rather than feature names.
- Whether it is live. A draft that looks identical to the published version is how the wrong link gets sent.
A convention that survives contact with reality
Something like "Homepage -- Fleet overview in 60s" or "Sales follow-up -- Contract signing". Placement first, because that is how you will search; content second, in words a buyer would use.
Prefix retired demos with a marker such as "OLD --" rather than deleting them immediately. Old demos are frequently still linked from somewhere you have forgotten, and a renamed one is recoverable in a way a deleted one is not.
Version numbers are usually a mistake
"Demo v3 final v2" is a familiar failure. The problem it is trying to solve -- which of these is current -- is better solved by having exactly one current demo per placement and archiving the rest.
If you genuinely need history, keep the date rather than a version: "Homepage -- Fleet overview (Aug 2026)" tells you what you actually want to know, which is how stale it is.
Keep an inventory of where links live
The demo library tells you what exists. It does not tell you where each demo is embedded, and that is the information you need when a demo goes out of date or you change tools.
One document listing demo, placement and URL is enough. Update it when you publish, not later. This is the single highest-value habit in this article and takes about a minute each time.
Review on a cadence, not on a feeling
Put a recurring reminder somewhere it cannot be ignored. Open each live demo, click through it, and check nothing has drifted from the product.
Quarterly is enough for a stable product; monthly if you ship often. What matters is that it is a fixed date rather than something you will get to.
Frequently asked questions
- How should I name my product demos?
- Placement first, then content in buyer language -- "Homepage -- Fleet overview in 60s". Placement is how you will actually search for them, and it is the part most naming schemes leave out.
- Should I delete old demos?
- Rename rather than delete at first, with a prefix like "OLD --". Old demos are often still linked from a help article or an email sequence you have forgotten, and a renamed demo is recoverable where a deleted one is not.
- How do I keep track of where my demos are embedded?
- Keep one document listing demo, placement and URL, updated when you publish rather than afterwards. The demo library tells you what exists but not where it is used, and that is what you need when a demo goes stale or you switch tools.
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 →