How to Get Money for Creating Motion Design with Opus 5.5 & Fable 5.5 (From Scratch)

Why is everyone hyping Opus 5.5/Fable 5.5 for motion design, but nobody talking about the SERIOUS money you can make with it?

Probably, I'll be the first to tell you about it... So listen:

• Companies/clients that need design work for their products are actually willing to pay for videos like these and even state in their requirements: "The person must be highly skilled at using Opus 5.5."

In this article, I'll explain step by step how to go from zero to your first order using only Opus 5.5 + Viktor and I'll also provide these offers!

before the alpha - subscribe to my substack for more fresh alpha - https://substack.com/@0xcodila

Part One - Make something a buyer can use

01. Choose the job before the effects

I'm starting with a short SaaS product demo because the deliverable is specific: show one useful interaction clearly enough that a viewer understands the product.

There's a real example behind this choice. AlKhwarizmi Metrics advertised for 15–30 second product videos made with Remotion

• The brief offers product access, brand assets and real workflows to demonstrate. Its displayed project budget is $300 (damn $300 from 15 sec video

We'll return to that request when we reach the sales section, cause To get your first offer, you need to show the client a few examples of your work

So for now, make an independent concept: three marketing-report cards becoming one overview. Use original interface graphics and label the sample "Concept demo."

• That gives you something relevant to show without pretending you've worked for the company.

If you already have permission to use a real product, use its approved materials instead.

Your starting scope is one fifteen-second film, a widescreen master, a vertical adaptation and editable source files.

02. Get the studio running

• Install Node.js and Claude Code. Sign in with access to Opus 5.5

Opus 5.5 requires Claude Code 2.1.280 or later. Update an existing installation:

1claude update
2claude --version

Then follow Remotion's official project setup:

1npx create-video --yes --blank --no-tailwind motion-studio
2cd motion-studio
3npm install
4npx remotion skills add
5npm run dev

Select Claude Code if the skill installer asks - leave the preview running and open another terminal in the same project folder:

Check /model before proceeding. Start at medium effort, use /effort high when a difficult implementation needs deeper investigation

1claude --model claude-opus-5-5

You should now have a browser preview and a Claude session that can read the project. Keep the package lockfile once this setup works...

03. Give the video a story and a visual reference

Before asking for motion, decide what changes on screen. Our example has four beats:

• 0–3 seconds: three disconnected report cards. Headline: “Too many tabs.”
• 3–7 seconds: a cursor selects the cards; they move into one shared view.
• 7–12 seconds: the overview settles. Headline: “One clear view.”
• 12–15 seconds: a readable closing card: “Explore the demo.”

Keep the interface fictional. Use labels such as Ads, Social and Website, without fabricated performance results.

Next, attach one or two visual references. Process below is useful for understanding how references guide production

https://x.com/rexan_wong/status/2103707054108299437

I want Claude to extract typography, spacing and motion decisions. For a real client, supply its logo, fonts, screenshots and approved copy too.

Paste into Claude Code:

1Read the installed Remotion skills and inspect this project. We are making an original, self-initiated SaaS concept demo, not a real client's advertisement.
2Prepare brief.md, style-guide.md and storyboard.md for a 15-second, 1920x1080, 30 fps video. Use original interface graphics. Keep a small readable ‘Concept demo’ label throughout. Do not use third-party logos, testimonials or performance claims.
3Storyboard: frames 0–89 show three report cards labelled Ads, Social and Website with ‘Too many tabs.’ Frames 90–209 show a cursor selecting and gathering them into one overview. Frames 210–359 reveal that overview with ‘One clear view.’ Frames 360–449 hold ‘Explore the demo.’
4Analyze any references I supplied for visual principles, not assets to copy. If no reference is available, propose a restrained typographic direction using an available licensed font and two accent colors. List exact copy, assets, frame ranges, transitions and sound cues. Cover every frame. Preserve existing CLAUDE.md instructions and add these project rules. Show the storyboard for review before building.

• Read the storyboard. You should be able to explain what the viewer learns before any animation exists

For an actual brand, replace the concept material with its approved product behavior. Product below shows why recognizable product details matter:

https://x.com/tdinh_me/status/2103703135902740699

04. Build the film so revisions stay manageable

Opus produces the code, Remotion renders it into video.

Every visual change should follow the frame number, so seeking and exporting reproduce the intended scene:

https://x.com/__morse/status/2103485566570369333

• This example uses the same idea through a seek function. We'll keep the renderer in Remotion for this project.

Approve the storyboard, then build a rough preview first. Check the interaction and reading time before spending effort polishing shadows.

Continue in Claude Code:

1Implement the approved storyboard as a registered Remotion composition named SaaSDemo: 1920x1080, 30 fps, 450 frames. Preserve existing project work. Use the installed versions and their official APIs.
2Separate editable copy, colors and asset paths from animation logic. Drive motion from useCurrentFrame and useVideoConfig; avoid wall-clock timers and unseeded randomness. Load the chosen font explicitly with the supported loading mechanism.
3First render a low-resolution preview that covers all four scenes. Run the project's available type and lint checks. Fix errors before polishing.
4Use Remotion spring() for the cards gathering into the overview. Start with mass 1, stiffness 180 and damping 22 as a tuning baseline, then inspect the result. Preserve element position when transitioning between states. Keep the headline still while it needs to be read. Do not animate every element simultaneously.
5Export preview.mp4 and a contact sheet. Open the frames if supported, identify visible defects and fix the three most important ones. Save successful render commands and asset requirements in README.md. Report any checks you could not perform

Remotion's spring controls let you tune the weight of that transition. Increase damping if the cards keep bouncing after the viewer should be reading.

• Look specifically at the moment separate cards become the overview. A jump in position or a sudden font change will break the illusion.

Pause near three and seven seconds. The cursor should touch the intended control, and the cards should land where the next scene expects them.

*For longer films, expand the same brief into scenes with checkpoints.

*

here's a useful reference:

https://x.com/donaldjewkes/status/2102801469976248500

also let a budget for paid tools and cap revision passes. Local work needs your computer available, save progress so another session can continue from it

btw in many job offers, companies cover all expenses; this is also something to keep in mind

05. Add sound and inspect the actual export

A few well-placed sounds are enough for this sample: a click at selection, a soft movement cue and a restrained sound when the overview settles.

Use original synthesized effects or assets you're licensed to publish.

• If you supply music, listen to the detected beats before aligning the whole film to them.

The Remotion audio documentation covers placing and controlling sound within the composition.

Paste into Claude Code:

1Finish the sound and review SaaSDemo against storyboard.md. Use approved audio if supplied. Otherwise synthesize a short click, a soft movement cue and a restrained completion tone as local WAV files; use no paid service.
2Place cues at the actual interaction frames, with short fades and headroom. Integrate them into the Remotion composition so the MP4 contains the intended audio. Preserve a silent version if needed for comparison.
3Render a contact sheet at one-second intervals and around every scene boundary. Inspect the images if supported. Check readable text at phone size, spacing, cursor continuity, scene coverage and the final three-second hold. Inspect the exported file's duration, dimensions, frame rate and audio stream. Check audio peaks for clipping; if you cannot listen, ask me to review the mix.
4Fix the three most important defects and repeat for at most three passes. Save timestamped findings in review.md. Never mark an unavailable check as passed. Return the actual files and remaining issues for my review

Watch the export once muted and once with sound. Does the story still make sense? Can you read the closing line without pausing?

If you want a loop, check the end-to-start transition separately. Matching positions, movement and audio requires more than restarting the timeline.

06. Turn the render into a portfolio deliverable

Now make the vertical adaptation. Reposition the cards and resize the typography for the narrower screen.

Keep the same message and timing. The adaptation should look designed for its frame.

Final production prompt:

1Create SaaSDemoVertical at 1080x1920, 30 fps, 450 frames by relaying out the approved film, not cropping it. Keep readable text, the concept label, the story and the audio timing.
2Render both compositions as H.264 MP4s using the installed Remotion CLI. Verify each output opens and has the expected dimensions, duration and audio. Package the source project without secrets or node_modules, including the lockfile, permitted assets, license notes and exact install/render commands.
3Create .claude/skills/motion-reel/SKILL.md with valid name and description frontmatter. Save the verified workflow and actual commands for future work, preserving unrelated instructions. Explain how to invoke /motion-reel and what must be supplied for a real client brief

You can also use Remotion Studio's Render button or the CLI picker:

1npx remotion render

open both MP4s yourself. Keep the source archive and check Remotion's license for your commercial setup.

Upload the sample somewhere a prospect can view it. Label it as self-initiated work and check the link opens without your login.

• Write a short portfolio caption naming the problem, your contribution and the delivered formats.

A buyer should understand your role without asking which parts you actually made.

You now have something specific to show: a short SaaS interface film, two formats and an editable project.

That's what we take into the sales work.

So of course, I didn't include absolutely every little detail of the video-making process, but that's a matter of taste and experience -as well as your own styl..

Part Two - Find a buyer and prepare the proposal

07. Give Viktor the finished sample and a clear assignment

Set up Viktor , then give him the video, portfolio link and a short account of what you can deliver

Include your actual availability and supported source formats also if this is your first sample, say so!

Viktor's research tools can investigate current sources. I want him to match the work to requirements, then explain the fit.

Useful searches include SaaS product video, UI animation, Remotion developer and product launch video.

Searching only for Opus misses buyers who describe the outcome they need.

Paste into viktor.com:

1Help me find buyers for the SaaS motion sample I attached. Review the video if supported; otherwise use my description and identify what you could not inspect. Ask for missing essentials about my availability, turnaround and editable source formats.
2Find up to ten relevant public hiring requests, starting with the last 14 days and expanding to 30 and 90 only when needed. Open original pages. Record the URL, posting date, public buyer name, requested deliverables, stated budget/currency, source-file requirements and visible status.
3Score fit using specific evidence: similarity to my sample, required tools, source compatibility, workload and stated deadline. Distinguish Opus 5.5, Claude, Remotion and general motion requests. Keep inaccessible or closed sources separate. Do not invent budgets, open status or completed sales.
4Return a short ranked report and a lead spreadsheet. Select one strong candidate, explain the match and list questions that must be resolved before quoting. Do not contact anyone or submit applications

*you can also try doing the same thing with your existing videos

*

I would open the selected source myself. "They need video" is too broad - I want matching deliverables and a realistic path to meeting the brief.

If there is no good fit, keep searching or adjust the offer - the market is indeed full of offers. The shortlist should save you from unsuitable work too

Some of offers + places from Viktor:

-Upwork - SaaS Promo Video - $500

1. Upwork - Two UI Animations - $400 total
2. Upwork - Website Demo Video - $200
3. Upwork - Podcast Logo Animation - $100
4. Upwork - Fintech Promo Videos - $60–80 per video
5. Upwork - B2B SaaS Demo - approximately $2,000
6. Upwork - Website Explainer Video - $100
7. Upwork - Website Animations - $100 total
8. Freelancer - SaaS Video Ad - $30–250
9. Freelancer - Looping LED Visuals - approximately $42–62 total, converted from INR. Wise

• Upwork

• Freelancer
• PeoplePerHour
• Contra
• TwineAnd of course, you can also ask Viktor to look for startups and businesses on Instagram, Facebook, and so on - that’s a good starting point; there’s always someone who needs videos like that**

1. Read the brief as someone who has to deliver it**

Return to the AlKhwarizmi Metrics request. It asks for real product flows, with access and materials supplied by the client.

Our concept demonstrates relevant animation skills - the paid film would need their actual interface and approved story.

Have

Viktor

separate three things: requirements you can meet, missing information and work your sample doesn't demonstrate.

For this brief, clarify how many videos the project includes, required formats, revision rounds and source-file expectations before treating $300 as an acceptable quote

also published requests can close, these examples were checked October 2. Reopen the source before applying, or use Viktor to find a current equivalent.

For another angle, this DTC brief explicitly prefers Opus 5.5 for motion graphics.

It also requests AI product films and multiple examples. A single SaaS demo would cover only part of its needs.

09. Calculate the offer before promising the price

For the SaaS example, I'd propose a bounded first assignment: one approved interaction, a fifteen-second film and the agreed aspect ratios.

Include a storyboard review, one revision round and the source project if the buyer wants it. Define what counts as a new request.

Give Viktor your real time estimate: briefing, asset preparation, animation, review, adaptation and delivery.

• Include direct costs and the applicable marketplace fee.

A repeatable template may reduce animation time. It won't remove client communication or revisions.

Here's an illustrative calculation: five hours at $40, including revision time, plus $20 in direct costs. That gives you a $220 base.

If the platform fee were 10%, dividing $220 by 0.90 gives a quote of $244.44 before tax. Replace every assumption with your own numbers.

Now check the quantity - If a $300 project includes several films, this single-film calculation cannot justify accepting the entire job.

Continue in Viktor:

1Use the selected buyer's original brief and my confirmed capabilities to prepare a scoped offer. Ask me for missing production-time estimates, desired hourly earnings, direct costs, revision allowance and available delivery dates.
2Calculate the quote transparently. Separate labor, direct costs and percentage fees; verify the current applicable fee from its official source. If the buyer's budget cannot cover the proposed scope, suggest a smaller paid pilot or recommend passing.
3Produce offer.md and a client intake checklist. Specify exact deliverables, durations, aspect ratios, required assets, revision boundaries, source format, acceptance checks and when the delivery clock starts. Label proposed terms as proposed. Do not invent a price or deadline when inputs are missing

On Upwork, fees can vary by contract. Use the fee shown for your opportunity.

Your result here is an offer whose price and limits you can defend - send it only when you can deliver those terms.

10. Write a proposal the buyer can evaluate

I want the opening to show that you read the brief. Then give the buyer an example, a proposed first step and a useful question.

For our SaaS request, the core message could read:

1Your brief calls for short videos built around real product workflows. I'd start with one interaction and turn it into a fifteen-second demo using your supplied access and brand assets.
2My self-initiated sample shows the interface animation and pacing I can bring to that format. Before production, I'd share a storyboard with the exact screens and copy for approval.
3Could you confirm how many videos the project covers and whether you need editable Remotion source files? That will let me confirm the scope and quote

Attach your actual sample, then add the price and timeline from the reviewed offer.

That passage is a proposed approach, not a claim of client results..

Have Viktor prepare the complete version:

1Draft one concise proposal for the selected buyer using offer.md and my actual portfolio link. Refer to a specific requirement and explain how the sample demonstrates relevant work. Include the confirmed deliverables, proposed price and timeline, with any unresolved condition stated clearly.
2Use only experience and results I supplied. If the sample is self-initiated, describe it that way. Ask for any missing detail needed for a send-ready proposal instead of inserting placeholders.
3Return the proposal, source URL and proposed production brief for Claude Code. Do not submit it. After I provide a reply, help me resolve the buyer's questions and update the offer without silently expanding the scope

Review and submit through the appropriate channel yourself. Viktor's email rules exclude cold outreach and bulk mail.

After agreement, confirm the Upwork milestone is funded before starting paid production.

11. Let the first offer open other routes (+ a few more offers)

The same sample can support more than one sales approach. I would have Viktor adapt the offer to evidence from each channel.

For Upwork Project Catalog or Fiverr, have him turn the offer into a package with clear requirements and extras.

Fiverr permits AI-assisted work under its rules. Respect buyers who require a different production process.

For founder prospecting, Viktor can research a public launch and draft a relevant pitch.

For inbound work, he can turn your sample into a breakdown with a commissioning link.

For agencies, have him investigate production needs and accepted source formats. Prismea's white-label request provides a concrete example.

• Viktorcan also research referral partners and Remotion's expert directory. I'd consider paid acquisition after an offer starts converting.

Once there is demand, expand the deliverable: launch bundles, ad-hook variations, localizations and product updates.

• Viktorcan price the additions from your actual production history.

For recurring work, have him scope monthly production, part-time support or agency capacity around what you can reliably deliver.

Reusable work opens another branch: branded motion kits, templates and components sold through Gumroad or Contra.

• Viktor can research comparable products, prepare documentation and draft a listing.

For stock animations, have him check rules such as Adobe Stock's AI-content requirements.

At larger volumes, ask him to research demand for data-driven batches, client-owned generators or a subscription service.

Those require engineering and ongoing support.

Consulting and training are options too: this $1,000 workflow brief already shows a hire.

Viktor can help turn your demonstrated process into a workshop and handover plan

12. Keep the work moving after the first proposal

Give Viktor the outcome of each conversation - with a connected HubSpot workspace, he can help maintain the deal and prepare follow-ups.

Keep the approved scope beside the next action.

Send the agreed production brief into Claude Code, then return delivery notes so future estimates improve.

Log estimated versus actual hours and the reason for each revision.

viktor.com can use that history to flag underpriced packages and requests that repeatedly expand beyond the agreement.

Once the process is useful, save it as a Viktor skill and prepare a scheduled search.

Final Viktor prompt:

1Save our reviewed qualification, offer and proposal process as a reusable skill named motion-sales-research. Include my confirmed capabilities, actual source files, pricing inputs and evidence requirements.
2Prepare a weekday 09:00 search for up to five new suitable buyer requests. Confirm my time zone, available capacity and delivery destination. Deduplicate against the saved lead file and include source links and checked dates.
3Show a test result and the proposed schedule before activation. Keep outreach and submissions as drafts. Track replies and agreed work only through connections I authorize, or from updates I supply. Report where the skill and results are saved, what was activated and how to pause it. Flag blocked steps rather than claiming success

You now have a concrete starting point: a finished sample, a researched buyer and a proposal based on what you can deliver.

Open Viktor, give him your sample and run the buyer-research prompt

Pick one request worth answering properly!

The real example + the shift:

https://x.com/achxvi/status/2103918792845963545

chainpocket - https://x.com/achxvi

This guy has literally created his own animation style and has already made several sales for $129, spending less than an hour (as he writes)

All of this was made possible by Opus 5.5, and this guy knows that there are actually a lot of people willing to pay for it...

-So, as always, it all comes down to desire!

**I’ve given you a complete guide on how to start your own one-person marketing agency from scratch.

**

• Just try selling your first graphic - you’ll be inspired by how easy it is to find opportunities right now (speaking from personal experience)

Everything described in this article can also be done with Fable 5.5 - for those who already have early access (as of this post) or when it becomes available

*

Try free at [@viktor_com](https://x.com/@viktor_com) $100 in credits, no card: https://ref.viktor.com/codila-x*](https://ref.viktor.com/codila-x)

Paid Partnership