Topic
The same demo performs very differently on a homepage, next to a pricing table, in a cold email and in a help article. These guides cover each placement -- what the visitor is deciding there, how long the demo should be, and the mechanics of embedding on each platform.
49 guides
They have seen your numbers. Most of them never see the product.
The embed is one tag. The work is loading it without hurting your Core Web Vitals.
GitBook is more restrictive than most. Plan for a link, not an iframe.
Stars come from people who understood the project in ten seconds.
The help article is not the only place, and often not the best one.
A demo that gets watched and a demo that converts are not the same demo.
A marketplace visitor has one question, and it is not what your product does.
Someone else is describing your product to their customers.
They carry twelve products. Yours gets four minutes of their memory.
"Improved filtering" tells a customer nothing at all.
Bubble can do something most site builders cannot: show a different demo per user.
Framer embeds are straightforward once you know the canvas lies to you about whether it worked.
Two very different jobs: a demo on your store, and a demo of your Shopify app for merchants evaluating it.
Webflow makes this easy and has two traps: fixed heights, and the code element you did not know had a limit.
Astro ships no JavaScript by default, and an iframe does not change that.
Carrd is one page. Spend it carefully.
MDX means you can build this properly once and use it everywhere.
Ghost makes this genuinely easy. The interesting choice is post-level or site-wide.
Squarespace can host an embed happily. The catch is which plan you are on.
Svelte makes the click-to-load version about fifteen lines.
One small component, and every demo on the site behaves the same way.
Wix positions everything absolutely, which is the source of every embed problem on it.
WordPress will silently strip your iframe if you use the wrong block or the wrong user role.
Zendesk strips iframes by default. There is a setting, and it is worth understanding before you flip it.
Notion embeds a demo in one paste. The interesting part is what you use it for internally.
HubSpot landing pages take an embed happily. HubSpot emails will not, and that surprises people every time.
Ten minutes of preparation is the difference between one take and six.
The demo is finished. Where it goes decides whether it is watched.
The link survives if the article would be worse without it.
Your response is being scored by somebody who will never meet you.
You are paying by the send. The demo is how you find out if anyone cared.
A QR code pointing at a homepage wastes the only scan you get.
You already send the emails. This is the free part.
Your headline says what you do. Nobody can picture it.
Half of them will register and not attend. Give them something anyway.
They watched four minutes. Do not send them to a signup form.
Your proposal is read by people who never attended the call.
Nobody on your pricing page is asking what it does. They are asking if it is worth it.
Every message in their inbox asks for time. Send one that gives something.
The call you did not need to take is the cheapest one you will ever run.
Post a link to your product and you have spent your welcome.
On social, the link preview does the selling. The demo only has to keep the promise.
Five screenshots and a paragraph is not much to decide on.
You just described software to people who are driving.
Nobody browses a review site casually.
Candidates are evaluating you too, and most job posts give them nothing to evaluate.
Launch day traffic gives you about ten seconds and will not book a call. A demo is the only thing that fits.
People do not join waitlists for descriptions. They join for things they have seen.
They believed you. They just did not want to sign up to find out.