Explainers, logo animation, 3D product renders and the motion inside the site itself, made by the same team that builds it. Below is our own logo, keyframed: drag the playhead, or switch the curves off and watch it turn mechanical.
Script, storyboard, animation and sound, for the product that takes a paragraph to explain and ten seconds to show.
A mark that moves the way the brand behaves, cut for video intros, social posts and the site itself.
Products modelled and lit in Cinema 4D, rendered with Octane or Redshift, for the shot a camera cannot get or a prototype cannot yet show.
Scroll work in GSAP where a sequence needs timeline control, native Webflow interactions where the client will edit them later.
The person animating sits in the same team as the people building the site, so nothing is lost between the animation and the browser.
The After Effects and Cinema 4D files come with the finished video, render settings noted, so a change next year is an edit, not a remake.
Motion rarely fails in the review. It fails later: in a browser the animator never opened, on a phone that drops frames, for a visitor who asked their system for less movement, or in a file nobody can edit once the person who made it has moved on.
Motion for a site gets prototyped in the browser early, because a video file knows nothing about scroll, slow phones or the setting that asks for less motion.
One authored moment per page, and the rest stays calm, so the moment is actually seen instead of lost in the noise.
The tool is picked for whoever maintains it next: code where the sequence needs control, native interactions where the client edits later.
On the Qumra build that split is written down as a decision: GSAP for the scroll, native for the rest.
Some visitors ask their system for less motion, often because movement on screen makes them unwell. Honouring that is not a slower animation. It is the finished frame, straight away.
A loop that only runs faster is worse than no loop. Our own site learned that the hard way: a rule that shortened every animation left an endless one spinning in a hundredth of a second. Now anything that loops stops completely.
Nothing important waits for an animation. Text is readable before it moves; motion only decides how it arrives. Content hidden until a script reveals it is the one mistake we do not ship.
From $2,000
Above that, the number comes from three things.
Andrii
Explainers, logo animation, 3D and the motion on our sites
The same person storyboards the explainer, lights the 3D product and checks how the site’s motion behaves in a real browser, sitting next to the people who build it. Finished film includes the edit, the colour and the sound.
Usually shorter than the first draft of its script. When a product needs more than a couple of minutes to explain, the script is carrying too many ideas, and cutting them improves the video more than any animation can.
No. Writing it is part of the job, because the script decides the length and the length decides the price. If you already have one, we read it for what can be shown instead of said.
Yes, from the vector file. A logo that was never designed to move sometimes needs small changes before it animates well, and we say which ones before touching it.
Not the way we build it. Motion on the site moves transforms and opacity, honours the setting for reduced motion, and no text waits for an animation before it can be read.
Yes. The After Effects and Cinema 4D projects come with every job, render settings noted, so the work stays editable by whoever opens it next, us or not.