Context
Replay Vision is one of the strongest signals feeding the self-driving story and the Inbox, so I feel like a video is worth making. And it closes the loop: it doesn't just spot what matters, it opens a PR to fix it, so all you have to do is hit merge. The video needs to land that whole arc: PostHog watches your sessions, saves you tons of hours, spots the issue, surfaces it to you, and hands you the fix. You just hit merge.
Video ideas
Three directions I think could be interesting (but also these are just suggestions and you can pursue your own ideas):
1. Attenborough-style – "Field Guide to Wild Users"
We're doing a campaign where we'll have a Field Guide page on the website and a physical booklet. This is the text and Lottie is working on the designs here. I think these designs could be reusable for a video too once they're done.
We could do a nature-documentary treatment that extends this concept. A narrator that sounds like Attenborough observes "species" of users in their natural habitat, while Replay Vision quietly does the observing on our behalf.
The product demo could live inside the bit: as the narrator spots a behavior, we cut to the scanner catching it, surfacing it to the Inbox, and opening a PR that's ready to merge.
2. Detective-style – "Noir Hog"
A film-noir mystery that plays off our GA graphics – the noir hog, the pink accents, a case to crack. Something's wrong in the product and nobody knows why; Replay Vision is the detective piecing the session evidence together until the culprit is caught, the case is closed, and the fix is waiting for you as a PR to merge.
3. Plain demo
A straight product walkthrough in the style of the Slack app video and the general PostHog demo. Clear, fast, shows exactly how Replay Vision works, from setting up the scanner to spotting the issue to opening the PR you just need to merge, and where it fits in the self-driving flow. I think this is the lowest effort.
I don't have a preference, and I would be happy with any of these directions. If you have a better idea, go for it!
Goal & audience
Goal: Awareness and narrative first. The video's job is to land "self-driving product, surfaces issues to you" and make Replay Vision the proof point people remember it by. There are some YC startups that do this as a separate tool we're competing against. We need to show we have this as part of the whole self-driving motion.
New signups are a secondary outcome with a soft CTA, but not a hard sell.
Audience: Technical builders and product managers who watch session replays. Users of other session replay tools. Broader dev crowd who will share it because it's entertaining.
Placement
YouTube, product page, email campaigns, socials
Timeline
Replay Vision is launching in paid beta on Aug 3. We already have activities planned for the first couple of weeks, and I would like us to publish a video a bit later to keep the momentum going.
IMO, end of August/early September would be ideal, but if it's too short notice, I'm okay with later too.
--
Also, what do you need from me to take these forward: screenshots, a breakdown of how it works, anything else?
Context
Replay Vision is one of the strongest signals feeding the self-driving story and the Inbox, so I feel like a video is worth making. And it closes the loop: it doesn't just spot what matters, it opens a PR to fix it, so all you have to do is hit merge. The video needs to land that whole arc: PostHog watches your sessions, saves you tons of hours, spots the issue, surfaces it to you, and hands you the fix. You just hit merge.
Video ideas
Three directions I think could be interesting (but also these are just suggestions and you can pursue your own ideas):
1. Attenborough-style – "Field Guide to Wild Users"
We're doing a campaign where we'll have a Field Guide page on the website and a physical booklet. This is the text and Lottie is working on the designs here. I think these designs could be reusable for a video too once they're done.
We could do a nature-documentary treatment that extends this concept. A narrator that sounds like Attenborough observes "species" of users in their natural habitat, while Replay Vision quietly does the observing on our behalf.
The product demo could live inside the bit: as the narrator spots a behavior, we cut to the scanner catching it, surfacing it to the Inbox, and opening a PR that's ready to merge.
2. Detective-style – "Noir Hog"
A film-noir mystery that plays off our GA graphics – the noir hog, the pink accents, a case to crack. Something's wrong in the product and nobody knows why; Replay Vision is the detective piecing the session evidence together until the culprit is caught, the case is closed, and the fix is waiting for you as a PR to merge.
3. Plain demo
A straight product walkthrough in the style of the Slack app video and the general PostHog demo. Clear, fast, shows exactly how Replay Vision works, from setting up the scanner to spotting the issue to opening the PR you just need to merge, and where it fits in the self-driving flow. I think this is the lowest effort.
I don't have a preference, and I would be happy with any of these directions. If you have a better idea, go for it!
Goal & audience
Goal: Awareness and narrative first. The video's job is to land "self-driving product, surfaces issues to you" and make Replay Vision the proof point people remember it by. There are some YC startups that do this as a separate tool we're competing against. We need to show we have this as part of the whole self-driving motion.
New signups are a secondary outcome with a soft CTA, but not a hard sell.
Audience: Technical builders and product managers who watch session replays. Users of other session replay tools. Broader dev crowd who will share it because it's entertaining.
Placement
YouTube, product page, email campaigns, socials
Timeline
Replay Vision is launching in paid beta on Aug 3. We already have activities planned for the first couple of weeks, and I would like us to publish a video a bit later to keep the momentum going.
IMO, end of August/early September would be ideal, but if it's too short notice, I'm okay with later too.
--
Also, what do you need from me to take these forward: screenshots, a breakdown of how it works, anything else?