An interactive demo on a product page: let people try it before asking for access
Plan a short product demo using sample data: one task, a clear result, an exit and a useful next step.
Article language: English

In this article
The most interesting moment on a product page often comes just after the words "see how it works". A visitor expects to try one thing. Instead, they get a form, a choice of meeting times and a question about the size of their organisation. A conversation may be necessary, but the promised sample has just become a meeting booking.
A short interactive demo can fill that gap. It lets someone complete a limited task using sample data before requesting a conversation or access to the product. It does not have to reproduce the entire application. It should, however, clearly distinguish a working demonstration from an example result and from anything that still requires implementation or configuration.
Imagine a page for a tool that schedules deliveries of promotional materials. Instead of showing every tab, the demo lets a visitor assign a fictional shipment to a date and see the schedule change. They learn how to move a delivery and read a conflict. They do not need to create yet another account for "Test Ltd", a company that probably has more accounts than many corporations by now.
One task is more interesting than a tour of every tab
Start with the question the demo needs to answer. Does moving a date reveal a conflict? Does configuring a product expose dependencies? Can someone review the result before confirming? That question defines the start, the choice and the end. "We will show the wealth of features" mainly defines the future length of the presentation.
In our example, the task is to move a sample delivery to Friday and check whether it conflicts with another collection. You need two dates, one shipment and a clear result. You do not need user administration, carrier prices or a notification inbox. They may look convincing, but they distract from the decision you want to explain.
Make the limited scope visible. A "Sample data" label and a short introduction establish the rules. If a "Send" button only displays a sample confirmation, call it "View sample confirmation". Nobody should finish wondering whether they have accidentally ordered transport to a fictional warehouse.
Choose data that makes the decision understandable. "Shipment A" and "Shipment B" may suffice in a mock-up, but "Trade fair materials" and "Warehouse replenishment" are easier to recognise in a finished demo. Both are fictional, yet they describe different needs, making the date conflict meaningful. Do not copy a real order just because it looks more convincing.
A useful exercise for the team is to write down three things: what the visitor starts with, what they can change and what they see after the change. Note inactive elements and why they are present. Every dead button needs a reason. If it is only decoration, removing it is often better than adding another explanation.
In a product configurator (in Polish), the available choices follow actual dependencies in the offer. A demo can show a selected part of those dependencies, but must not suggest a freedom of choice the product does not offer. An example should make a rule easier to understand, not improve the rule for the presentation.
Not every offer needs interaction. When movement or the order of actions matters most, a short video on a service page (in Polish) may explain it faster. A demo has an advantage when the visitor's own choice helps them understand the consequence. Merely pressing five arrows is not that advantage.
Before production, make a paper version or a simple prototype. Before a session, you can also walk through the interface as a first-time user (in Polish), explicitly stating what you assume the visitor already knows. Ask someone to perform the task and describe what changed. If you have to keep saying "click here now, skip that", fix the scenario first. A more impressive animation will not supply its logic.
Show the result before explaining the interface
The first screen should present a situation. "A shipment needs a date" says more than "Welcome to our modern dashboard". Show the goal and a way to start. Someone who already knows the product should also be able to skip the introduction easily. Not everyone comes for the same amount of explanation.
After an action, show the difference where the visitor expects it. A moved date can change position on the schedule, with a short explanation of the conflict. Avoid making a coloured bubble in the corner the only evidence. The team sees it because they know the design. A new visitor is probably looking at the thing they just touched.
Showing before and after can help. You do not need an elaborate comparison panel. A label for the previous date and a new value are enough if they explain the consequence. Keep the result visible long enough to read and discuss. A message that disappears just as someone looks at it tests reflexes more than the product.
Now a short hint beside a specific control can help. The Atlassian Spotlight component documentation describes directing attention to an element and mechanisms for closing and moving between steps. It is a useful reference for explaining one step. The demo scenario still determines which step to explain and what the hint should say.
Do not cover the thing the visitor needs to compare. A bubble saying "The conflict appears here" placed directly over the conflict is a small act of informational sabotage. Check its position on a narrow screen and with enlarged text. If the hint is always competing with the task for space, shorten it or move it somewhere quieter.
Allow a wrong but safe choice when it helps explain a rule. In our example, someone can select an occupied slot and receive an explanation. There is no need to let them enter arbitrary contact details. The demo should communicate how a problem is solved, not collect information the scenario does not need.

Label the result as sample data too. If you present an AI-supported tool, identify a prepared response as a prepared example. Do not call it the result of live processing if no model performed the task. The distinction between a claim of action and a checked result also appears in responsible AI agent workflows (in Polish); it is easy to blur on a product page too.
Leaving is part of the demo
A visitor must be able to end the trial, go back one step and start over. These actions should not look identical. "Start again" restores the sample data, "Close demo" returns to the page, and "Back" lets someone correct the last choice. In a short scenario, the labels can prevent the need for another guide to the guide.
When the demo closes, return the visitor to where they started. If they launched it from the delivery-planning section, they should still recognise that part of the offer afterwards. Sending them to the top makes them search again. Leaving the demo need not mean the end of their interest.
For interfaces using the native popover mechanism, MDN describes connecting a control to the element it opens, keyboard navigation order and focus returning after Escape closes it. A different implementation needs its own check. Do not assume the same behaviour merely because a window looks similar.
Test the whole task with a keyboard: open it, reach the choice, change it, read the result and close it. Have someone who did not design the element order test it too. If they must remember an invisible shortcut or click the background with a mouse, the route is incomplete. A working first button is only the beginning.
A way to skip the interaction helps even when the demo works technically. Someone may only want implementation terms or to return to the price. Keep a plain description and a concrete next step nearby. The principle resembles a route without the 3D scene (in Polish): an extra presentation format should help, and its absence must not remove the basic meaning of the offer.
Before publication, test launching the demo from different places on the page. A header button and one beside a feature description may need different introductions, but should lead to a recognisable task. If the second link opens the demo midway, show the selected date and name the starting step. Someone entering halfway has not seen the earlier steps.
On a phone, pay particular attention to an embedded demo with its own scrolling inside the page. Check whether someone can move on to the next part of the offer or keeps scrolling the same panel. A full separate section with a clear exit can be more comfortable than a small window showing mostly the device frame.
These decisions belong to product presentation design. Aeneia Design's offer is a starting point for discussing the page and how it shows the product at work; the scope of a larger application needs a separate agreement.
Aeneia Design
Let us plan a short demonstration of one task: sample data, a visible result and a return to the offer. This makes it clear during design which screens and materials need preparing.
Plan a demo that explains how your product works
The end of the trial should naturally lead to a question the visitor can now ask. "Discuss delivery planning for your company" follows from our scenario. A generic "Learn more" does not use what the person has just learned. You could also offer implementation terms or another distinct use case.
The demo's place on the page depends on its role in the whole offer. On a short landing page (in Polish), it may be the main way to explain the product. On a larger site, it may fit one use-case page better. There is no need to move the same sample into every section just because it took considerable work.
Prepare for an answer the team will not like. A participant may believe they changed a real delivery date or that the tool chose a carrier itself. That interpretation points to a specific boundary that needs stating or fixing in the interface. Asking only "Is everything clear?" rarely reveals it. Ask the participant to describe the next step they would take in their own company instead.
Judge the demo by understanding of the task. Afterwards, ask the participant to explain in their own words what they chose and what changed as a result. Ask what they still need to know before a purchase conversation. The number of demo starts may help identify where to observe, but alone it does not show whether anyone understood the product.
Keep a version of the scenario and the sample-data list. When the product changes its scheduling rule, you will know which step to review. An outdated demo can convincingly teach something the offer no longer does. The problem then is not a low number of clicks, but how effectively those clicks make the wrong point.
The best short trial ends with the feeling, "I know what to ask next". The visitor has seen the consequence of their choice, recognised the limits of the example and can return to the offer. That is plenty for a few screens. There is no need to tour every tab, the basement and the product's utility room as well.








