Use case
Launch with a demo people can drive, not a GIF.
One micro-demo per headline feature, embedded in the announcement, the changelog, the docs, and the launch post — and the analytics that show which feature landed.
Launch posts describe features; buyers want to try them. A four-stop lane per feature lets a reader click through the new thing in thirty seconds, and the same lane drops into the changelog entry, the help article, the Product Hunt listing, and the customer email.
How it works
Step by step
- One micro-demo per headline featureThree to six stops: the trigger, the feature doing its job, the result. Capture from a demo account the day before launch.
- Embed everywhere the announcement goesBlog post, changelog, docs, in-app notice, and the email — the same public link or iframe in each.
- Use a prospect link for press and partnersMint a personalized link per publication or partner so you can see who actually drove it.
- Re-capture when the feature changesA micro-demo is four screens; keeping it current is minutes, not a project.
See the format
Drive a lane
What you learn
What the analytics show
- Plays per embed location via referrer — which channel drove the launch
- Completion per micro-demo — which feature people finished exploring
- CTA clicks to the feature's sign-up or docs page
- Prospect-link drives from press and partners
Plan
Free for one lane; Growth for a lane per feature and prospect links.
FAQ
Questions
How is this better than a GIF in the launch post?
A GIF plays once at one speed; a lane is driven and measured. You learn which feature people explored and where they stopped.
Can I put a lane in the Product Hunt listing?
Product Hunt galleries take images and video; link the lane from the listing text and the first comment, and use a prospect link so the drives are attributed.
Related
Keep reading
Comparing tools?