Name: Rosteme spolu
Uploaded: 2026-10-08
Duration: 20 s
Channel: Igor Brezina
Description: A 20-second animated intro for Grow UP, a Prague marketing agency, built in 3D from code.

One rocket lifts off from a meadow, climbs through the clouds into space, loops above the Earth and hops over a meteor. When its engine sputters, it re-ignites and surges on. It lands on a magenta planet, and the Grow UP logo arrives with the agency's slogan, „Rosteme spolu.“

The 6-second cut takes the same journey at a sprint and goes straight to the logo. It's made to open Grow UP's videos and the RRP Talks podcast.

Roman Řehák, who runs Grow UP, sent a short brief one morning: the slogan, the rocket from the agency's brand visual, and one sentence about how the agency sees marketing, as a shared journey past planets that are opportunities and adventures that are obstacles. „Zkuste k tomu vymyslet nějakou animaci, jako upoutávku pro videa.“ (Try to come up with an animation for it, as a teaser for videos.)

The first version went out the same evening. It had two identical rockets, the agency and its client, helping each other through the trip. Roman asked for one rocket in Grow UP red. The revision was ready the next day, and he published it on his LinkedIn on 2 October 2026.

Story. I sketched the journey: a launch from Earth, the sky darkening into space, a meteor, an engine that fails, a landing on a new planet, and short lines of text along the way. Claude Opus 5.5 tightened it into a 20-second beat sheet, added the 6-second cut and the landing that turns into the logo, and took both text lines from Roman's own brief.
Look. Claude pulled the logo, colours and typeface from Grow UP's website and modelled the rocket on their brand visual. The first launch frame was pink. I sent it back because it looked like another planet, not Earth, and the meadow, trees and blue sky came from that note.
Animation. There is no generated video. Every shot is a Blender scene written in Python, so the rocket, the trails, the timing and the camera are values in code, not a prompt. Claude wrote the scenes and checked them frame by frame; I reviewed the rough cuts.
Rendering. The scenes render on my laptop's GPU through a small render queue Claude set up.
Music. I generated six soundtrack takes in Adobe Firefly against the rough cut and chose one for each length. Claude levelled them to −14 LUFS (LUFS measures how loud audio sounds to the ear; −14 is the usual target for YouTube and social media) and laid them under the picture.
Text and logo. These sit in a separate 2D layer built in code, in Grow UP magenta, the Poppins typeface and the agency's own logo file, so a line of text can change without re-rendering anything in 3D.
The revision. One rocket instead of two changed three scenes. The rockets circling each other became a loop-the-loop, the rescue from the meteor became a hop with a roll, and the engine trouble became the rocket's own. The timing stayed the same, so the music still fits.

Roman Řehák, Grow UP

The brief, the slogan, the brand visual, and the note to keep one rocket.

Igor Brezina direction

Found the client and agreed the brief
The story and its key scenes
Art direction and every approval: concept, look, text, rough cuts, final film
Music: generated the tracks in Adobe Firefly and chose them
All client communication, delivery and the revision round

Claude Opus 5.5 by Anthropic production, directed by me

The beat sheet, the 6-second cut, and the text lines taken from the brief
Brand research: logo, colours, typeface
The 3D rocket, every scene and all the animation, in Blender and Python
The render queue on my laptop, the 2D text and logo layer, and the final assembly
Audio levelling and frame-by-frame quality checks

A branded intro built this way stays editable. Text, length and colour change in the code, not by re-rolling a generator and hoping the rocket looks the same.