How to Make a SaaS Product Video with Claude Motion: Brief, Scenes, Export
A step-by-step workflow for SaaS and AI software teams: pick one viewer and one message, outline the scenes before you animate, prepare clean screenshots and real numbers, fix the Claude Motion draft scene by scene, and export an MP4 for a launch post, onboarding email or sales deck.
- #claude-motion
- #saas-marketing
- #product-video
- #explainer-video
- #feature-launch
- #ai-software
- #ai-video
Which SaaS video should you make first?
| Video | Suggested length | Where it plays | What to attach |
|---|---|---|---|
| Feature launch | 20 to 30 seconds | Changelog, LinkedIn, launch email | Before and after screenshots, the benefit in one line |
| Product explainer | 45 to 60 seconds | Landing page, sales deck | 3 to 5 screenshots, the problem in one sentence |
| Onboarding walkthrough | 30 to 45 seconds | Welcome email, help center | The setup steps in order, one screenshot per step |
| Metrics or customer proof | 15 to 20 seconds | Board deck, case study page | The CSV or chart, and the source of each number |
| Pricing comparison | 20 to 30 seconds | Sales kickoff, pricing page | The plan table, and what changes between plans |
How do you make a SaaS product video with Claude Motion, step by step?
- 1
Pick one viewer and one message
Write one sentence that names who is watching and what they should believe or do afterwards. For example: a trial user who hasn't connected a data source should see that it takes three clicks. If you can't write that sentence, the video will try to cover the whole product and the viewer will remember none of it.
- 2
Ask for a scene outline before any animation
Ask Claude for the outline as plain text first, in the chat where you will build the video. This is the step people skip. Text is quick to fix, and Anthropic notes that longer or more complex animations use more of your usage limit than a typical message, so settle the story while it is still cheap to change. Approve the outline, including every on-screen line, before you ask for motion.
Prompt: outline first Before you animate anything, write a scene outline for a 30-second product video. Viewer: [who is watching and what they already know] Message: [the one sentence they should remember] Use this structure: 1) the problem in the viewer's own words, 2) the product doing the job in 2 or 3 steps, 3) one proof point from the attached numbers, 4) the next step. For each scene give the on-screen text (12 words or fewer) and what moves. Do not invent numbers or features that are not in the attached files.
- 3
Prepare clean screenshots, numbers and brand details
Capture screenshots from a demo workspace, never a real customer account, and crop each one to the part of the screen the scene is about. List the numbers you plan to show with the file or dashboard each came from. Type your brand colours as hex codes and attach the logo as an image. Anthropic's pages say Motion animates the images you give it; they do not mention brand kits or custom fonts for Motion, so state the colours in the prompt and check the result.
- 4
Build the animation from the approved outline
Select Output in the message box, choose Motion, and tell Claude to build the outline you approved. Repeat the three details Anthropic asks for (who will watch, where it will play, roughly how long) and add your colours and the closing line. Keeping the request in the same chat means Claude already has the outline and the files.
Prompt: build it Build the outline above as a Motion animation. 30 seconds, for the top of our changelog page, so it must make sense without sound. Viewers are existing customers who know the product. Use the attached screenshots as they are. Colours: background #0B1020, accent #5B8CFF, text white. End on a scene with our logo and the line: [your call to action].
- 5
Review the draft scene by scene
Pause on every scene and check four things. One idea per scene. Text that can be read in the time it stays on screen. Every number equal to its source. And every screen equal to the real product: if a screen looks redrawn instead of shown, confirm each label and button exists, or ask Claude to use the attached screenshot unchanged. A video that shows a button your product doesn't have creates support tickets.
- 6
Fix one scene per message
Send each correction as its own message and name the scene. Because the animation is code, Claude changes that detail and the rest stays as it was, which is the main practical difference from tools that generate the whole clip again. Use the editor for small adjustments you would rather make by hand.
Edit requests, one per message Scene 2: hold the screenshot for one more second before the highlight appears. Scene 3: change the number to 42%, as in cell B7 of the attached sheet. Scene 4: shorten the text to: Connect in three clicks.
- 7
Make a version for each channel
Ask for a shorter cut or a different shape in the same chat once the main version is right. Anthropic's pages do not list the aspect ratios Motion supports, so treat a portrait or square version as something to test: export it and look at it on a phone before you promise it to anyone.
Prompt: a second cut Make a second version of this animation for a phone held upright: 15 seconds, keeping only scenes 1, 3 and 5, with larger text.
- 8
Export the MP4 and add sound only if you need it
Click Export and choose MP4. Anthropic's help pages did not mention voiceover or music for Motion as of 22 November 2026, so the on-screen text has to carry the message. If the channel needs narration, add it in a video editor and keep the text anyway, so the video still works wherever it plays muted.
- 9
Publish it with the words beside it
Put the video on a page that also says the same thing in writing: a heading that names the feature, the steps as a short list, the numbers with their source. Search engines and AI assistants work from the text on a page far more reliably than from what is inside a video file, so the written version is what gets your launch found and quoted.
A brief you can fill in
Viewer: [role, and what they already know about the product] Where it plays: [page, email, deck or feed] Length: [seconds] Message: [the one sentence the viewer should remember] Scenes: the problem, the product in 2 or 3 steps, one proof point, the next step Material attached: [screenshots, CSV, steps] Brand: [hex colours, logo file, tone in three words] Rules: 12 words or fewer on screen per scene. Use only numbers from the attached files. Must make sense without sound.
Paste this into the chat with your files, then ask for the outline (step 2) before the animation.
Viewer: support leads who already use our AI assistant for drafting replies Where it plays: release notes and LinkedIn Length: 25 seconds Message: agent mode resolves a ticket in one run, with a human approving the final reply Scenes: the old way (five separate prompts), agent mode reading the ticket, the tools it calls, the approval step, how to turn it on Material attached: 4 screenshots from the demo workspace, the run log for one ticket Brand: #111827 background, #22C55E accent, calm and precise Rules: 10 words or fewer per scene. Show only steps that appear in the run log. Must make sense without sound.
An invented product, to show the level of detail. For AI software, the run log is the source of truth: the video should not show a step the agent doesn't take.
List every number and product claim that appears on screen, scene by scene, and the attached file each one comes from. Flag anything that is not in the files.
This gives you a list to verify by eye. It does not replace your own check against the source.
Frequently asked questions about SaaS videos in Claude Motion
Can Claude Motion make a SaaS product demo video?
Yes, as an animation. Claude Motion builds a short animated walkthrough from your screenshots, steps and numbers and exports it as an MP4, and Anthropic names a product walkthrough for customer onboarding as one of its uses. It is not a recording of the live product and it cannot show a presenter, because it doesn't generate realistic footage or people.
How long should a SaaS product video made with Claude Motion be?
We suggest 20 to 30 seconds for a feature launch, 30 to 45 for an onboarding walkthrough and 45 to 60 for a product explainer. Those are our starting points; Anthropic states no maximum, and its own example is a 30-second explainer. Longer animations also use more of your plan's usage limit.
Can I use my own screenshots and brand colours in Claude Motion?
You can attach images, and Anthropic's advice is to attach them so the animation is built from your own content. For colours, write the hex codes in the prompt. As of 22 November 2026, Anthropic documents design systems for designs and decks, not for Motion, so check that the result matches your brand.
Can I make a vertical version for LinkedIn, TikTok or Reels?
You can ask for one, since Claude builds the animation from your description. Anthropic's help pages do not list supported aspect ratios or export sizes, so export the vertical version and check it on a phone before you plan a campaign around it.
Is it safe to upload product screenshots to Claude Motion?
Use screenshots from a demo workspace, with no customer names, emails or keys, because whatever is in the image can appear in the video. The animation itself starts private to you, and on Team and Enterprise plans artifacts stay inside your organization unless an owner allows external sharing.
Do I need a designer or video editor to use Claude Motion?
Not to produce the animation: you describe it, Claude builds it, and you edit by chat or in the editor. You still need someone to check numbers, product accuracy and brand, and a video editor if you want narration or music, which Anthropic's pages don't document for Motion.
Key Takeaways
Decide on one viewer and one message, and get the scene outline right as text before you animate. Give Claude Motion real material: demo-workspace screenshots, numbers with sources, colours as hex codes. Review every scene for one idea, readable text, correct numbers and a true picture of the product, then fix one scene per message. Export the MP4, test other shapes before relying on them, plan for no documented audio, and publish the video next to its written version so search engines and AI assistants can read it.