How to Demo a Product That Does Not Look Good Yet
August 22, 2026
Plenty of genuinely good software looks unfinished — a founder-built interface, a tool that grew feature by feature, an internal product being sold externally for the first time.
The usual response is to postpone the demo until after a redesign. That postpones revenue by a quarter or more, and the assumption underneath it is mostly wrong.
What buyers actually react to
Not beauty. Clutter, inconsistency and confusion — which are related to visual design but not the same thing. A plain interface that clearly shows one number is fine; a busy one with three competing panels is not, however well-styled it is.
The reaction you are afraid of usually comes from a screenshot that is too dense to parse in two seconds, and cropping fixes that today.
What to do before recording
- Crop hard. Show the panel that matters, not the whole application. Most "ugly" is peripheral.
- Zoom into the one thing the step is about, which removes everything around it.
- Clean the data. Realistic, tidy records make a plain UI look deliberate; test rows named "asdf" make it look abandoned.
- Collapse what you can. Sidebars, debug panels, unused nav — anything hideable is worth hiding.
- Fix the two-minute problems. Truncated labels, overlapping text and a broken avatar cost more than the whole colour scheme.
Lead with the outcome
A demo that opens on a settings screen invites judgement of the interface. One that opens on a finished report someone needed invites judgement of the result, which is the ground you want to compete on.
This is why the ordering advice matters more here than anywhere: with a polished product you can afford a slow start, and with an unpolished one you cannot.
Say it, if it is obvious
For an early product with an early-adopter audience, naming it directly works better than hoping nobody notices: "the interface is plain and we are rebuilding it in the autumn — the engine underneath is what this demo is about."
It disarms the objection instead of leaving it to form silently, and it is credible in exactly the audience most likely to buy an early product. It is the wrong move with a conservative enterprise buyer, who will take it as an admission rather than as candour.
Frequently asked questions
- Should I wait until my product is redesigned to make a demo?
- Usually not -- that postpones revenue by a quarter over an assumption that is mostly wrong. Buyers react to clutter and confusion rather than to plainness, and cropping, zooming and clean data fix most of that today.
- How do I make an unpolished product look better in a demo?
- Crop to the panel that matters rather than the whole application, zoom into the one thing each step is about, use realistic tidy data instead of test rows, collapse unused panels, and fix truncated labels and overlapping text.
- Should I acknowledge that the UI is rough?
- With an early-adopter audience, yes -- naming it disarms the objection instead of letting it form silently, and it reads as candour. With a conservative enterprise buyer it reads as an admission, so leave it out.
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 →