Claude Motion · Build and Sell a SaaS Launch Video in One Day

Quick Summary

• The case study follows one $1,000 fixed-price SaaS launch video. Sanji says five targeted proposals produced three replies, one client accepted a one-day delivery, and the finished Claude-built video was approved the same day.
• The $880 figure is the creator's calculation: $1,000 revenue minus a reported $100 Upwork fee and a $20 Claude subscription. Upwork currently states that freelancer fees can range from 0% to 15% per contract, so this is not a universal net-income formula.
• The production system is storyboard first. The client brief, brand tokens, fonts, backgrounds and Figma UI exported as SVG are prepared before Claude writes the animation. The video is rendered at 1920 by 1080 and 60 fps.
• A reusable motion skill carries narrative structure, timing, easing, stagger, grouping, cursor behavior, safe zones and rendering rules. It reduces repeated instruction, but it does not replace art direction or quality control.
• The first render failed in predictable ways: overlapping text, incorrect scale, missing fonts, instant counters, stacked cards and an overly fast camera. Short, specific correction prompts fixed one variable at a time.
• The human comparison is useful as a demonstration, not a controlled benchmark. One freelancer, one brief, one delivery and one buyer cannot establish that code-based motion is always faster, cheaper or better than professional motion design.

What the $880 case study actually shows

Sanji's experiment is specific. He searched Upwork for SaaS and technology launch-video work, selected five jobs, sent tailored proposals and reports that three clients replied within hours. He chose one startup project, quoted $1,000 for a 30-second launch video with a one-day turnaround, and says the client approved the delivered files that day.

The creator then compares his code-rendered result with a Fiverr motion designer who received the same brief and a $1,000 budget. The human designer originally quoted five days and delivered after seven, while the Claude version was produced in under a day. Both videos are shown, but the final quality judgment is left to the viewer.

This is evidence that a prepared creator can use a strong storyboard, reusable instructions and programmatic rendering to deliver one type of product video quickly. It is not evidence that every beginner can close a $1,000 client, that every project takes one day, or that a single AI subscription is the complete cost of doing business.

The $880 calculation, with the missing context

The video's arithmetic is simple: $1,000 paid by the client, minus a reported $100 Upwork fee and $20 for Claude, leaves $880. That number is better described as the creator's reported project contribution after two named costs, not audited profit or a repeatable daily wage.

Upwork's current help documentation says the freelancer service fee ranges from 0% to 15% per contract and is shown before a proposal or offer is accepted. A 10% fee reproduces the $100 deduction in this example, but another contract may use a different percentage.

A real quote also needs to cover Connects, discovery calls, proposal time, ten hours of prior workflow research mentioned in the video, storyboard creation, revisions, failed renders, hardware, storage, taxes, insurance and any licensed fonts, music or footage. A monthly subscription is also not necessarily a project-specific cost if it supports several jobs.

Use the case study as a pricing exercise: start with the client outcome and scope, estimate all labor and risk, add platform fees and operating costs, then calculate the price required to reach your target margin. Do not advertise $880 per day as guaranteed income.

Step 1: find the right Upwork jobs

The creator searches several phrases instead of relying on one feed: SaaS launch video, product launch video, UI animation, app promo video and SaaS explainer. The goal is not maximum application volume. It is a small set of jobs where the product, assets, budget and launch pressure make a fast motion-design delivery valuable.

His four checks are client history, freshness, competition and money. He prefers payment-verified clients with meaningful spend and a hire rate above 50%, recently posted work with fewer than 15 proposals and no active interviews, plus companies that appear to have a real product and launch budget.

Upwork defines hire rate as the share of a client's job posts that ended in a hire. Its current Connects guidance also recommends reviewing client history, feedback, job activity and whether the client has already hired someone before spending Connects. These signals reduce uncertainty, but none guarantees that a client will respond or pay a premium.

Research the company only with public information. Do not infer funding from a polished website alone. Confirm the product, launch date, decision maker, required deliverables, rights to supplied assets and whether the deadline is realistic before offering one-day delivery.

Step 2: write a proposal around the client's outcome

The proposal structure in the video is task, solution and deadline. The opening lines repeat the client's own language, such as product launch video and Figma, so the preview immediately demonstrates relevance. A short concept then helps the buyer picture the finished video before seeing a full portfolio.

Sanji reduces buyer risk by suggesting a small first milestone. A practical version is a paid storyboard and style-frame milestone before the full render. This gives both sides a clear checkpoint for story, visual direction, timing and scope while revisions are still inexpensive.

Upwork's official proposal guide recommends describing what you can do, asking useful questions, suggesting next steps and adding relevant work samples. An empty portfolio is not an advantage, so never pretend otherwise. A tailored concept can strengthen a proposal, but it should not include unpaid speculative production that gives away the whole project.

The template in this article is an original reconstruction from the demonstrated structure. The exact on-screen proposal, storyboard layout and downloadable skill are available through Sanji's credited Higgsfield resource.

Step 3: lock scope before opening Claude

For a 30-second SaaS launch video, define the aspect ratio, resolution, frame rate, duration, delivery format, number of scenes, audio responsibilities, revision rounds, source-file handoff and deadline. State whether the price includes alternate crops, captions, localization or product changes after approval.

Collect the brief, product positioning, audience, main problem, core feature, payoff, call to action, launch date and proof points. Obtain explicit permission to use the client's Figma file, fonts, logos, screenshots, illustrations and any third-party material inside it.

The video uses a fixed 1920 by 1080 canvas at 60 fps with safe zones for future vertical adaptation. That is a reasonable delivery spec, but choose frame rate and dimensions based on the destination. A 60 fps render doubles the number of frames compared with 30 fps and can increase render and review time.

Step 4: storyboard the narrative before animation

Sanji's four-beat story is attention, problem, solution and payoff. Every scene must serve one of those jobs. The storyboard records what is visible, how long it stays, what the camera does, how the scene enters and exits, and what the viewer should understand before the next beat.

The no-storyboard comparison is the clearest lesson in the video. With the same assets and motion instructions but no scene plan, Claude guesses the order, moves too many elements at once and produces a montage of attractive UI rather than a coherent product story.

Approve the storyboard with the client before building. A six-scene plan might allocate three seconds to the hook, five to the problem, twelve to the product demonstration, six to proof and payoff, and four to the logo and call to action. Adjust the timing to the voiceover and reading load rather than forcing every idea into equal blocks.

Step 5: prepare Figma assets, fonts and brand tokens

The creator exports product UI from Figma as SVG instead of using screenshots. Vector assets remain sharp during camera moves and zooms, while raster screenshots can become visibly soft. Figma's official documentation confirms that layers, frames, components and groups can be exported, including copy as SVG, when the file owner has not restricted copying or sharing.

Export only the states needed by the storyboard. Name files by scene and state, such as dashboard-empty, dashboard-processing and dashboard-complete. Remove hidden layers, confirm text is either outlined or packaged with the licensed font, and preserve a clean mapping between each asset and its intended shot.

Create a small brand manifest containing canvas size, safe zones, font files, color values, corner radii, shadows, logo rules and UI scale. The first render in the video fell back to Times New Roman because the chosen font was not loaded before frame capture. Asset readiness is part of animation quality.

Step 6: encode motion direction as a reusable skill

A Claude skill is a reusable instruction and reference package loaded when the task is relevant. Sanji's skill stores the rules he does not want to rewrite for every launch video: narrative structure, timing, easing, overshoot, staggering, grouping, cursor movement, safe zones and render specifications.

The motion rules are concrete. Important information remains readable for roughly one and a half seconds. Elements enter over about half a second with a slight overshoot, exit faster than they entered, and overlap in time so the composition never feels frozen. Related elements move under one parent group instead of drifting independently.

Clicks receive a small press response. Cursors move along a human arc instead of a perfectly straight line. Cards enter a few frames apart, and the next action begins before the previous one has completely settled. These are creative defaults, not laws. Adjust them to brand personality, accessibility and the amount of information on screen.

Downloadable instructions are a starting point, not a warranty. Inspect any third-party skill before installing it, understand what tools it can access and test it on a non-sensitive sample project before using client assets.

Step 7: build scene by scene

The concise instruction shown in the video is: Using the motion skill, build this storyboard as a 30-second launch video. Scene by scene. That short request only works because the brief, storyboard, brand system, UI assets and skill already carry the other ninety percent of the context.

Ask for one component or module per scene, a master timeline, deterministic frame-based timing and a single source of truth for dimensions and brand tokens. Require the project to load every font and asset before capture begins, then render a few test frames from every scene before exporting the full sequence.

Keep the implementation editable. Text, counts, colors, timings and camera values should live in configuration rather than being scattered across generated files. The video's example of changing a counter from 200 to 999 is fast only when the number is isolated and the render pipeline remains stable.

Step 8: fix the first broken render methodically

The initial output is not presented as a miracle. Text overlaps, the camera moves too quickly, content leaves the frame, the font falls back, the counter jumps instantly and every agent card appears at once. Sanji spends roughly another hour debugging and refining the result.

His corrections are narrow: lock the canvas to 1920 by 1080 and position from the center; load the font before rendering; make the count-up last about one second; stagger cards and delay their check marks; slow the pan and use eased acceleration and deceleration.

This is the right revision pattern. Describe the visible failure, identify the likely system rule behind it, change one factor and compare the same representative frames. Once the technical defects are gone, switch to taste: emphasis, breathing room, camera motivation, cursor hesitation, glow intensity and transition rhythm.

Do not accept a correction merely because the code compiles. Review the rendered result at full size, on a phone, with and without sound, and against the approved storyboard. Motion is judged in time, not in source code.

Claude versus a human motion designer

The human version is described as clean and smooth, and the Claude version emphasizes camera movement, depth and weighted interaction. The creator prefers his code-driven result and highlights the faster delivery, while inviting viewers to judge both outputs themselves.

The comparison does not isolate the variables. Sanji had already invested more than ten hours refining the workflow, controlled the AI art direction and had a reusable skill. The hired designer's process, communication, revision history and other workload are not examined. Delivery time from one freelancer is not a benchmark for the profession.

A more useful conclusion is that code-based motion can be competitive for structured UI animation when the brief, assets and storyboard are strong. Experienced motion designers still contribute concept development, typography, pacing, accessibility, sound direction, original transitions, stakeholder management and the judgment to remove motion that distracts from the product.

Step 9: deliver professionally and protect the relationship

Send a review link or watermarked preview first, then provide the final export and agreed source package after approval and payment. Include a short change log, output specifications and any limitations the client should know before publishing.

Disclose your AI-assisted production method when the contract, client policy, platform rules or asset licenses require it. Never upload private Figma files, customer information, unreleased product data or credentials to a model without written authorization and an approved data-handling setup.

Do not promise one-day delivery until your own test project proves the workflow. A safer commercial offer includes a paid storyboard milestone, one style frame, a first-cut deadline, a defined revision window and an explicit rush fee when the buyer needs priority scheduling.

Turn the experiment into a repeatable service

Package one narrow offer: a 20 to 30-second SaaS feature or launch video built from approved Figma assets. Define the included number of scenes, one aspect ratio, one soundtrack treatment, two revision rounds and a clear delivery calendar.

Use the first projects to measure proposal response rate, time to storyboard approval, implementation hours, render time, revision count, actual platform fees and client outcomes. Replace the headline metric with your own median delivery time and margin after at least several completed jobs.

The strongest long-term advantage is not unlimited output. It is a reusable system that preserves brand consistency, makes revisions traceable and leaves enough time for better creative decisions. Fast code is valuable when it supports reliable delivery, not when it creates more work for the client to review.