ANALYTICS · LAUNCH FILM
PostHog launch video: from raw signals to a pull request in 15s
An unofficial 15-second concept film built from posthog.com. It starts in a wall of raw event names, then tells the site’s own demo story: PostHog AI is asked why paid conversions are falling, finds a required field at mobile checkout, edits the form and opens a pull request. Short highlighted captions carry the story at a fast pace.
- Length
- 15 seconds
- Creative direction
- Website identity
- Source
- posthog.com
- Generated
- 2026-09-27
The finished film. Sound on.
This video couldn’t load.
Open the videoMade with LaunchVideoAI
15 seconds, 1080p.
01 / SCENE BY SCENE
How the PostHog film is built.
- 0:00–0:03
Your product is full of signals
A light grey wall of event pills drifts across the frame: $pageview /pricing, stripe.charge.succeeded, zendesk.ticket, rage_click, 500 POST /api/checkout. “Your product is full of signals.” types in over it, with “signals.” in PostHog blue. The noise is the point, and the headline sits on top of it.
- 0:03–0:06
Hedgehog logo and product panels
The PostHog hedgehog logo appears in the middle of the noise, then small windows open: a Product analytics signups chart, an Error tracking card with a TypeError stack trace, and a Session replay of a checkout page. The chart numbers are sample UI recreated for the film.
- 0:06–0:07
Your product’s context layer
The site headline “Your product’s context layer” appears above a Data warehouse window running SELECT customer, amount, status FROM stripe.charges, with succeeded, incomplete and declined rows.
- 0:07–0:11
PostHog AI finds, fixes and ships
A PostHog AI window is asked “Why are signups growing, but paid conversions falling?” and checks Google Ads, PostHog, Stripe and GitHub. Panels then move through quickly: a signup to payment funnel (100%, 64%, 23%, sample data), a diff in checkout/MobileForm.tsx that makes the company field optional, and an open pull request “Shorter mobile checkout”. Highlighted captions read “finds problems”, “fixes bugs”, “opens pull requests”.
- 0:11–0:15
Self-driving mode end card
The windows fly out and the PostHog logo settles above “Shift your product into self-driving mode”. The command npx @posthog/wizard self-driving types into a field beside an orange “Get started – free” button, with posthog.com below.
02 / FROM THE WEBSITE
What the AI took from posthog.com.
The only input was the website link. Everything else came from researching the public site.
- The homepage’s illustrative demo story: “Why are signups growing, but paid conversions falling?”, the Google Ads, PostHog, Stripe and GitHub checks, and the extra required field at mobile checkout.
- Headline “Your product’s context layer” and the site’s self-driving framing, used in the end card line.
- The install command npx @posthog/wizard self-driving and the “Get started – free” button.
- Captions adapted from the meta description, which says PostHog diagnoses problems, fixes bugs and generates pull requests.
- Warm grey background, PostHog blue highlights, the hedgehog logo, and IBM Plex Sans with Source Code Pro for code.
03 / WORTH BORROWING
Ideas to steal for your own launch video.
- Open on the problem as texture. A wall of raw event names says “too much data” before any copy appears.
- If your site already has a demo scenario, reuse it. One question with one answer is easier to follow than a feature tour.
- In a 15-second film, let two- or three-word captions carry the story and let the UI move behind them.
- End on the exact install command so a developer knows the first step.
SAME PROCESS. YOUR PRODUCT.
Paste your website and get a film like this.
Original animation and music. One-time payment from $13, with revisions included.
This is an unofficial concept film generated by LaunchVideoAI from PostHog’s public website. It is not affiliated with or endorsed by PostHog; trademarks and product imagery belong to their owners. Brand owners can ask for removal at [email protected].


