Motion Design for Business: Where It Genuinely Lifts Conversion and What It Costs

Three different products people call by one name

When a client says "we need motion", three things sit behind that phrase, incompatible in budget and in the specialists required. The first is interface micro-animation: state transitions, loading skeletons, a button responding to a press, a block expanding, an error highlighting in a form. It is work at the seam between design and front end, measured in components, requiring an understanding of browser performance, and ending not in a video file but in code or a Lottie file inside the project.

The second is motion graphics in video: explainers, ad creatives, presentation films, animated infographics. A different specialist works here, with different tools and a different process: script, storyboard, style frames, animatic, animation, sound. The unit is a second of runtime rather than a component, and cost grows non-linearly with duration, because every additional scene needs illustration, animation and revisions.

The third is brand identity animation: bringing a logo to life, an intro sting, an audio logo, motion rules for the identity. The job here is categorically different: not to attract attention or explain, but to fix recognition. Precision requirements are higher than in any other kind of motion, because you cannot deform the mark to make it move more attractively, since that breaks the identity. The cost is usually lower than a film and the timeline shorter.

The practical conclusion is simple: do not commission "motion" as a single line item. Work out which of the three products you need, because the vendor, the budget and the deliverable format all follow from it. A studio that makes excellent explainers can quite easily produce interface animation that wrecks site speed. That is not incompetence, it is a different specialisation.

• Interface micro-animation: measured in components, delivered as code or Lottie, performance matters.
• Motion graphics in video: measured in seconds, delivered as a video file, the script carries it.
• Identity animation: measured in precision, delivered as stings plus rules.

Where motion genuinely earns money

The first mechanism is directing attention. Peripheral vision reacts to movement before conscious reading catches up, so a single moving element on screen almost certainly gets the first look. That gives both the rule and its main limitation: it works while exactly one thing moves. If five elements move on a page they compete and nobody wins the attention, which is precisely why busy landing pages often convert worse than calm ones.

The second is explaining a complex product. Anything that happens over time or has a sequence of steps is cheaper to show than to describe: how a service works, what happens to a request after it is submitted, what goes on inside a device. A thirty-second explainer replaces two screens of copy that nobody reads on mobile anyway. The test is simple: if the explanation needs a process, a diagram or a before and after comparison, animation is justified; if one sentence covers it, it is not.

The third is reducing perceived wait time and giving feedback on actions. A skeleton instead of a spinner makes loading feel shorter, because the user sees the structure of the content to come and understands what is happening. An immediate button response to a press eliminates repeat clicks and therefore duplicate leads in the CRM. It is the most undervalued item on the list, because here animation works on error reduction rather than on impression.

The fourth is holding the first three seconds of an ad creative. In a feed the decision to watch is nearly instantaneous, and movement in the opening frame, cutting rhythm and getting the key message in before the third second directly affect completion, and through it the cost per action. Here motion is a function rather than decoration: a static banner and an animated creative produce different click costs on an identical offer, and this is the one mechanism of the four that is easy to verify with a split test in the ad platform.

Where animation actively does damage

The most common damage is animation for its own sake. Blocks fading in on scroll, parallax on every section, counters that spin when they enter the viewport, text revealing letter by letter. Individually each trick is harmless; together they turn reading into waiting. A user who came to find a price scrolls faster than your delays resolve and sees empty screens. This is not hypothetical: scroll-triggered content reveal is one of the few techniques that consistently worsens mobile behaviour metrics.

Second, interface latency. The working range for micro-animations is 150 to 300 milliseconds, and 200 to 500 for screen transitions. Anything longer reads as sluggishness, especially on an action somebody performs ten times in a row. A modal that opens over 600 milliseconds looks impressive in a demo and irritates on the fifth open. The rule: the more frequent the action, the shorter the animation, down to none at all on the most frequent operations.

Third and most expensive is the effect on Core Web Vitals. Animating layout properties such as height, width or position triggers reflow and directly damages CLS, and content shifting under a thumb also means lost taps. Autoplaying video in the first screen competes for bandwidth with the main content and hurts LCP. A two-megabyte Lottie file plus an animation library in the bundle push out time to interactive. One rule covers most of it: animate transform and opacity, and treat anything else as a deliberate decision that gets measured.

And fourth, accessibility. The prefers-reduced-motion media query is not a formality: for some users movement causes vestibular discomfort up to nausea, and parallax with auto-scrolling is not impressive to them, it is physically unpleasant. Supporting the query is a few lines of CSS and a matter of respect for the audience. Same category: autoplay with sound, animation that cannot be stopped, and flashing more than three times a second, which is directly dangerous for photosensitive users.

• Animate transform and opacity. Height, width and position are a direct route to bad CLS.
• 150-300 ms for micro-animations, 200-500 ms for transitions. Longer reads as lag.
• Support prefers-reduced-motion always, not when there is time left over.
• Scroll-triggered content reveal hurts more often than it helps on mobile.

What it costs and what drives the price

Below are 2026 market ranges for Russian studios and freelancers. Inside each row the spread comes from three factors worth understanding before you compare proposals. The first is runtime, and it is not linear: a 60-second film costs not twice but roughly two to three times a 30-second one, because the scene count grows and with it the illustration and revision volume.

The second factor is 2D versus 3D. The difference is structural: 3D adds modelling, materials, lighting and rendering, and rendering is measured in machine hours somebody pays for. Even a simple 3D piece is rarely cheaper than complex 2D. The third factor is revision count, and it is the one that most often blows up a budget. A change at style frame stage costs hours; the same change after finished animation costs days, because the whole scene has to be rebuilt.

Veltos.Tech entry pricing: motion and AI video from 15,000 RUB, design and creative from 5,000 RUB per layout. The first figure covers a short social creative or a simple logo animation, the second a static banner or cover. Cost then scales with scope, which is a deliberate choice: a small business needs the option to buy one unit of work for a specific test rather than a package sized for a national campaign.

Production: which stages the client must review

Production follows a fixed sequence: brief, script, storyboard, style frames, animatic, animation, sound and mix, master and export to formats. Each stage costs several times the previous one, and that is the single fact a client needs to understand before the start. A script change costs an hour. A style frame change costs half a day. The same change after finished animation means rebuilding the scene, and if it touches timing, the neighbouring scenes and the voiceover along with it.

From that follow the points where feedback is mandatory. The script, where you decide what the film is about. The storyboard, where sequence and logic become visible. The style frames, where the visual language is approved: two or three key frames at final quality that show how everything else will look. The animatic, where timing and cutting rhythm are approved, and which is the last cheap point for change. After the animatic, revisions become expensive structurally, not because the vendor decided so.

What a client must not do is give the first substantive feedback on the final render. That is the most common way budgets and schedules collapse: material was approved formally, with "looks fine, carry on", and on the finished film it turns out the character is wrong, the colour is off brand and the argument order needs changing. Formally the client is right, practically both sides lose money. The cure is a written sign-off at every gate and an agreed number of revision rounds, usually two per stage.

For interface animation the process is shorter but the principle holds: prototype the behaviour first, implement second. Changing timing in a prototype takes minutes; changing it in an implemented component, with all states and testing, takes hours and sometimes raises a performance question. The practical rule for both kinds of work: the earlier you say no, the cheaper it is, which makes a detailed no at storyboard stage worth far more than a polite yes throughout and a devastating review at the end.

Tools and formats: Lottie, Rive, MP4, WebM

For films the standard has not moved: After Effects as the main tool, Cinema 4D or Blender for 3D, Figma or Illustrator for style frames. For web and apps the picture differs, and one practical conclusion matters: for most interface work Lottie beats video. It is a vector format based on JSON, so the file weighs tens of times less than comparable video, scales losslessly at any screen density, supports transparency without alpha channel gymnastics, and is controllable from code, so you can pause it, scrub it, or bind progress to scroll or component state.

Lottie has limits worth knowing in advance: raster layers and some After Effects effects are unsupported or behave incorrectly, and a complex composition with hundreds of layers can load the CPU harder than equivalent video. A practical guideline is to keep the file within a few hundred kilobytes and test it on a real budget phone rather than only on a work laptop. Rive covers the adjacent job: interactive animation with states and transitions, where an element has to respond to user actions rather than simply play.

For advertising the formats sort out like this. MP4 with H.264 is the universal option every platform accepts, and it should be your default. WebM is for cases needing transparency on the web. GIF in 2026 has exactly one justification, which is a platform that refuses video: it weighs several times more at worse quality and is limited to a 256-colour palette, so gradients band. Delivering GIF where MP4 is accepted is a deliberate downgrade in both quality and load time.

And on preparing creatives for platforms, which people forget regularly. You need a 9:16 vertical and a 1:1 square, because horizontal video occupies a quarter of the screen in a feed. Subtitles are mandatory: a large share of the audience watches with sound off, and a spot that makes no sense without audio simply does not work. The key message has to land inside the safe area, because platform interface overlays the frame edges and text neatly placed along the bottom ends up under the buttons.

• Lottie for interface work: vector, small, code-controllable. Test it on a budget phone.
• Rive when the animation must respond to actions rather than simply play.
• MP4/H.264 by default, WebM for transparency, GIF only when the platform refuses video.
• 9:16 and 1:1 formats, subtitles and safe areas are conditions of the creative working, not options.

Where AI fits into a 2026 motion pipeline

AI has confidently taken over the preparatory and supporting stages. Storyboards and style frames generate in minutes, which lets you show a client three visual directions instead of one and lock the style before the animator starts. Backgrounds, textures, abstract environments and b-roll for cutaways are all cheaper to generate than to draw or license from stock. Technical tasks work particularly well: upscaling, frame interpolation, background removal, and scratch voiceover for the animatic.

What AI does not cover, and this is worth stating up front. Logo animation to a brand guide needs pixel accuracy: the mark cannot be deformed, proportions cannot shift, and a generative model is structurally the wrong tool. Interface micro-animations live in code with exact timings and states, which video generation does not touch at all. Shots where the product must look exactly as it looks rather than similar. And any Cyrillic text in frame, which still has to be composited manually.

A realistic estimate of the effect: AI cuts preparatory and supporting work by roughly 20 to 40 percent and noticeably speeds up approving a visual direction. It does not shorten editing, sound, colour or final assembly, and on precision work it tends to add effort, because generation is followed by manual correction. So the accurate framing for 2026 is not "AI instead of a motion designer" but "a motion designer whose pre-production takes a day instead of a week".

Frequently asked questions

Related services

• Motion design and AI video for adsWe produce short video ads: shots generated with AI models, motion graphics on top, then edit, grade and sound design. You get a 16:9 master plus reframed 9:16 and 1:1 cuts, ready to upload to social feeds, Reels, Shorts, marketplace listings and ad accounts. We are straightforward about where AI delivers in a day and where filming or hand-built animation is still the right answer.
• UX/UI design for websites and appsWe design interfaces that survive contact with production: research, structure, UI kit and a clean handoff to the developers. Everything lives in Figma as components with real states and real breakpoints, not as a folder of flat mockups. The same process covers landing pages, corporate sites, e-commerce, web apps and mobile.
• Targeted and search advertisingPaid advertising brings traffic the day after launch, and burns budget just as fast when audiences are guessed at and nobody counts the leads. We build campaigns in the channels that genuinely work in Russia in 2026: VK Ads, Telegram Ads and Yandex Direct, plus Meta and Google Ads for projects selling abroad. Tracking goes in before launch, not after.

Read next

• AI Video Models in 2026: Sora, Veo, Kling, Runway and Higgsfield by TaskA model selection matrix by task, an honest cost per finished second including the three to five iterations everyone actually needs, notes on access from Russia, and a blunt list of what AI video still gets wrong.
• A Slow Site Loses Money: Core Web Vitals and ConversionSite speed is not a technical metric, it is a line in the revenue report. Core Web Vitals explained in plain language, how to find the real cause of a slow page, and a fix list sorted by return per hour of work.
• Branding for a Startup: The Minimum Set at Launch and What It CostsStudios sell 200-page brandbooks while a startup needs a set that fits in one PDF and lets you launch ads next week. The minimum scope, staged payment, market prices and the legal step almost everybody skips.