Most sites explain the product. A scroll film shows it happening, one beat at a time, as the visitor moves down the page.

The catch is that agencies build the motion site and the launch video twice, as two separate projects, and bill you for both. Then the video drifts out of sync with the site by the second revision.

I build one composition. Scroll-drive its timeline & it is your site. Render the same timeline & it is your MP4. Same geometry, same type, same cadence, one source of truth.

What ships

A scroll-driven page section or full page, built in GSAP

The launch video, rendered from the same composition, not rebuilt

Real device chrome & real product frames, not stock mockups

60fps on a laptop, with a reduced-motion fallback that still tells the story

The source files, so your developer can change a beat without calling me

I learned the discipline the expensive way. I improvised a "close enough" version twice instead of building from the real assets, & both times I threw the work out & started over. Now the rule is written down: inventory the real assets first, build from them, never paraphrase them.

I ran a services company to $649,206 with 25 remote workers, so I price this as an operator. Two deliverables, one build, one invoice.

If a static page with three good screenshots converts the same, I will tell you. That answer is free.