Velocity — AI Video
Generation at Scale
HP needed 2,500 product videos. Agencies quoted $1.25M and 6 months.
We shipped it in 7 minutes per video, at $50 each, across 28 markets.
HP came to us needing 2,500 product videos across 28 markets. The agency quote was $1.25M and 6 months. We said 7 minutes and $50 per video. They said yes.
That's the story of Velocity.
E-commerce was drowning in static images. Customers wanted to see products in motion — but video production was gated behind agency timelines and $500–$2,000 per video price tags. For a brand like HP with thousands of SKUs, that math simply didn't work.
The brief: make video production as fast and cheap as image generation, without sacrificing quality. No studio. No actors. No 6-week turnaround.
Three things had to be true simultaneously: quality had to be indistinguishable from studio output, speed had to be under 10 minutes per video, and the pipeline had to support 28 languages without re-recording.
Existing tools handled one of these. None handled all three.
We also had to make it accessible to non-technical brand managers — not engineers — because the people generating videos at HP were marketers, not ML teams.
Velocity is an AI video generation pipeline built on top of Avataar's 3D rendering engine. Input: a product SKU, a script, and a language. Output: a broadcast-quality video in under 7 minutes.
The pipeline handles 3D asset rendering, AI voiceover via ElevenLabs, background scene generation, lip-sync where needed, subtitle baking, and multi-format export.
HP used it to generate their entire catalog — 2,500 videos across 28 markets — in weeks, not years. Cost per video dropped from $500–$2,000 to $50. Time dropped from 2–3 weeks to 7 minutes.
HP contract signed for 2,500 videos across 28 markets. 25,000 users signed up in 6 months after public launch. Video conversion rates 3–5x higher than static images across HP's catalog. $50 per video vs $500–$2,000 agency rate — a 10–40x cost reduction. Product featured in Avataar's enterprise pitch deck as the flagship AI capability.
We built Velocity for HP first and the market second. The pipeline was heavily optimized for their SKU structure and SAP data format. When we tried to onboard the next enterprise client, we had to rebuild 40% of the ingestion layer. I'd have designed for a configurable data schema from day one, even if it meant shipping HP two weeks later.
The other miss: we never built a self-serve tier. 25k signups sat in a waitlist because onboarding was fully manual. That was a missed growth unlock. We got the enterprise contract. We left the bottom of the funnel on the table.
The best product insight isn't always technical. The real unlock for Velocity wasn't a better model — it was realizing that brand managers needed a tool that felt like Canva, not like Blender.
Speed and quality were table stakes. Simplicity was the moat. If the person generating the video has to open a terminal, you've already lost.
Video at scale isn't a creative problem. It's a pipeline problem. Once you treat it like infrastructure — inputs, transforms, outputs, quality gates — the cost and time numbers become inevitable.
The creativity happens at the edges. The middle is just engineering.
Building AI products since 2020 — from spatial computing to finance automation.
