VxSure Launch Film

1. 0:00.0Hook“Your business / runs on / the web.” slams in on three intro hits.
2. 0:02.8Doors openThe hook splits like two panels, revealing a tilted stream of everyday web requests.
3. 0:05.5RiskOn each beat one ordinary request turns red: phishing, credential theft, malware, data exfiltration, shadow IT.
4. 0:09.0The old wayA firewall scan reduces every request, threats included, to “IP :443 ✓ Allowed”.
5. 0:11.7The turn“Not what’s inside.” The camera zooms through the word into the brand.
6. 0:13.7BrandThe logo lands on the music dip: “The Layer 7 Secure Web Gateway.”
7. 0:17.8See insideA transaction inspector fills on the beats, then a lock opens in the silence: “Even encrypted HTTPS.”
8. 0:25.1ControlBrowsing is allowed, an upload is blocked, and a policy builds chip by chip until “Policy applied”.
9. 0:30.1DataHighlighter marks sensitive data in a spreadsheet and in code. Pasting it into an AI prompt is blocked.
10. 0:35.5Manifesto“Not just another Secure Web Gateway. A new standard for secure web access.” Held on the breakdown.
11. 0:41.0PlatformEight capabilities flash on the stutter beats, then snap into a grid that freezes before the drop.
12. 0:46.4ProgramOn the drop, the Founding Partner Beta Program opens with three glass perk cards.
13. 0:51.8Call to action“More capability. More flexibility. More value.” Then the cursor clicks Apply now.
14. 0:57.3End cardLogo, light sweep and “The journey has just begun.” on the final hit.

1. Step 01

   Research

   I chose two reference launch films, Numtera and Introducing Google Vids. Claude Code broke them down shot by shot: motion, type, colour, music and sound.

2. Step 02

   Script

   The long internal document became 19 lines of on-screen copy across 11 scenes, each timed to a silence, dip, build or drop.

3. Step 03

   Music

   I picked the track. It was cut from about 1:54 to 60 seconds with four edits on bar lines, so it sounds uncut.

4. Step 04

   Build

   Each scene is a React component in Remotion, styled with the design system’s colours, Inter type, radius and shadows.

5. Step 05

   Review

   I watched and listened to every export and sent notes. Five full versions led to the approved v005.

1. Brief set

   “60 seconds, 16:9, no voiceover, readable on a phone, one Apply now button.”

   Oct 13, 2026

   ByMMukund Sharma(Director)

2. Story and timing locked as a text-only animatic

   “Lock the story and timing first.”

   ByMMukund Sharma(Director)·CClaude Code(Production)

3. First full buildv001

   Oct 14, 2026 · 13:06

   ByCClaude Code(Production)

4. Mix mastered to −14 LUFS, 16:9 confirmedv001→v002

   “It must be 16:9 for mobile, and the audio is clipping.”

   Oct 14, 2026 · 13:10

   ByMMukund Sharma(Director)·CClaude Code(Production)

5. Opening rebuilt as a stream of web requests, benefits as glass perk cardsv002→v003

   “The opening table looks plain and feels odd. Make the benefits more creative.”

   Oct 14, 2026 · 13:43

   ByMMukund Sharma(Director)·CClaude Code(Production)

6. Real domains, highlighter marks and red only for threatsv003→v004

   “Replace the placeholder domains. The detection boxes look busy. Too much red.”

   Oct 14, 2026 · 13:52

   ByMMukund Sharma(Director)·CClaude Code(Production)

7. Doors-opening reveal for the hookv004→v005Final

   “The hook-to-stream handover feels messy.”

   Oct 14, 2026 · 14:00

   ByMMukund Sharma(Director)·CClaude Code(Production)

8. Bolder 60 fps exploration, not chosenv006

   “Level up everything.”

   Oct 14, 2026 · 14:42

   ByMMukund Sharma(Director)·CClaude Code(Production)

9. v005 approved as the launch filmApproved

   ByTThe team

Notes are paraphrased. The inspector scene never changed from v001. It worked the first time.

1. Decision 01

   Lock the story as a text-only animatic first

   The question

   What should be fixed before a single frame is designed?

   Options I weighed

   • Build scenes straight from the script (not chosen)Every timing change would mean rebuilding finished visuals.
   • A text-only animatic, timed to the music (chosen)Story and timing locked while changes are still cheap.

   Why this one

   In a film without voiceover, the music is the narrator. Fixing every reveal to a silence, dip or drop first gave the visuals a structure to serve.

   Trade-off I accepted

   The first real look at the film came later, so early reviews judged rhythm and copy rather than craft.

   How I knew

   Every later note, v001 to v005, changed visuals. None changed the structure.

2. Decision 02

   Four words or fewer per punch line

   The question

   How do you carry a long security pitch with no voiceover, on a phone?

   Options I weighed

   • Explanatory sentences on screen (not chosen)Accurate, and unreadable at phone size in the time a scene lasts.
   • Short punch lines, nothing under 56 px, headlines at 104 px (chosen)Readable from a distance in a 1080p frame.

   Why this one

   Most people would watch on a phone, sometimes from across a room. Type size and line length were set by that viewing distance, not by how much there was to say.

   Trade-off I accepted

   The long internal document lost most of its detail: it became 19 lines across 11 scenes.

3. Decision 03

   Red belongs only to the threat

   The question

   How much red can a security film use before it stops meaning anything?

   Options I weighed

   • Red detection boxes throughout (not chosen)Busy, and every frame starts to look alarming.
   • Red only at the moment a request turns into a threat (chosen)Blue carries the brand everywhere else.

   Why this one

   Colour is a signal only when it’s scarce. Holding red back lets each threat land on its beat.

   Trade-off I accepted

   Detection reads through motion and highlighter marks instead of colour, which took a round of rework.

   How I knew

   The v003 → v004 note: “The detection boxes look busy. Too much red.”

4. Decision 04

   Real services as normal traffic, look-alikes as threats

   The question

   How do you show attacks on screen without making real brands look like attackers?

   Options I weighed

   • Placeholder domains everywhere (not chosen)Safe, but the stream felt fake.
   • Real domains everywhere (not chosen)Convincing, and unfair to the companies shown.
   • Real services only as everyday traffic; threats on look-alike domains (chosen)IPs from reserved documentation ranges; people and companies fictional.

   Why this one

   The opening needed to feel like a real network, and the threats needed to stay fictional. Splitting the two kept the film believable and responsible.

   Trade-off I accepted

   Every domain and IP had to be checked before export.

   How I knew

   The v003 → v004 note: “Replace the placeholder domains.”