How do you choose a video partner for a SaaS launch?

Choose the partner who can explain your hardest product detail

Choose a SaaS video partner by watching complete relevant films, testing how they handle one difficult product detail and comparing a written scope. Check who owns the script, who verifies product behaviour, how revisions work and what you receive when the project ends. A polished showreel is a useful introduction, but it cannot answer those questions.

The important distinction is between a launch film that earns interest and a walkthrough that teaches someone to do a task. A studio can be excellent at one and a poor fit for the other. Before collecting quotes, decide which job you actually need. This is FDM’s selection framework, not an independent ranking of agencies. Use it to assess us too.

Is this a launch film, an explainer or product education?

For a launch, the viewer may need to understand why a new product matters before they care how it works. A product explainer can make an unfamiliar workflow understandable. Product education needs enough accurate detail for a user to follow a task. These can share visual assets without being the same edit.

Write down the placement and next action. “A homepage visitor should recognise the problem and request a demo” is different from “an existing user should configure the approval rule.” Ask each supplier what they would leave out. Someone who agrees to fit every feature into one short film has not yet helped you make the editorial decision.

Sources: FDM: Product explainer versus product demo

Ask for two complete films, not twenty client logos

Request a finished film that solves a similar communication problem and one example showing how the team handled real interface detail. Ask what the supplier actually did: script, animation, editing, recording or some combination. A familiar client name does not establish responsibility for the whole production.

In FDM’s Krista.ai email explainer, a shared inbox leads into business-system cards, policy and approval steps. You can inspect how the connections are made visible. TikaMobile’s walkthroughs do a different job: narration, screen framing and paced movement guide attention through particular modules. These are observable production choices, not claims of higher conversions or faster adoption.

Watch once without pausing. Can you describe the task, what the software does and where a person still makes a decision? Then watch again for labels, readable screens and transitions. Separate a film you personally like from a film that answers your buyer’s question.

Sources: FDM: Watch the Krista.ai email workflow explainerFDM: TikaMobile walkthrough examples and FDM scope

Use a simple scorecard, with evidence beside each score

Score each supplier from 0 to 2 on the six checks in the scorecard below: 0 means not demonstrated, 1 means partly demonstrated or only promised, and 2 means supported by relevant work or a clear written commitment. Record the film, proposal clause or conversation that supports each score. The maximum is 12; this is an FDM comparison tool, not a validated industry benchmark.

Do not let the total hide a deal-breaker. If the proposed approach misrepresents your product or cannot meet a genuinely fixed launch date, resolve that before choosing the prettiest film. You can weight the checks differently, but decide the weights before reviewing proposals. Otherwise the scorecard becomes a way to justify a favourite.

For a complex assignment, consider a paid, limited pilot: one approved storyboard sequence or a short section using representative material, plus one agreed revision. Confirm cost, usage rights and acceptance criteria first. Do not ask several studios for unpaid production disguised as a selection test.

A sample brief you can send to shortlisted studios

Illustrative brief, not a description of an FDM client project: “We need a launch explainer for operations managers evaluating an invoice-routing product. It will appear on our website and in sales follow-ups. After watching, the buyer should understand how a document reaches the right reviewer and why they would request a demo.”

“Show the incoming document, the information extracted, the routing rule and the human approval step. Do not imply that approval means payment has been completed. We will provide an approved product walkthrough, a demo account using fictional data, brand files and a product owner to check accuracy.”

“Please propose a suitable length and visual approach. Quote the main film, caption file, thumbnail and two separately scoped short versions. State script responsibility, review rounds, source-file access, third-party licences, review dates and the cost basis for later screen updates. Our publication date is [date], and our approver is available on [dates].”

Replace the example with your real requirements. It gives every supplier the same problem to solve without prescribing every scene. If you have a budget range, share it so the producer can explain which approach fits rather than design a film you cannot commission.

Agree how product accuracy and revisions will be checked

Nominate a product owner before scripting. Their job is to check claims, permissions, integrations, UI labels and the difference between current and planned features. Marketing can approve positioning; it should not have to guess what the product actually does. Use safe demonstration data and agree access before sharing a private recording.

Approve the story, then important screens or storyboard frames, then the complete edit. Ask how the quote distinguishes correcting an error from changing an approved decision. “Two rounds” is not enough detail if nobody has defined which stage they apply to, how notes are consolidated or what happens when the interface changes midway.

A useful revision request names the scene, the problem and the approved replacement. For example: “At the routing step, this role cannot approve invoices. Replace the reviewer label and show the correct permission.” That gives the producer an implementable correction instead of asking them to interpret “make it more accurate.”

Sources: FDM: How staged approvals prevent rework

Compare the handover and update plan, not just the price

Put deliverables side by side: script, storyboard, narration, animation, screen capture, music, captions, versions, source files and licences. Identify what is included, optional or supplied by you. Ask whether a vertical version requires a new layout, not merely a crop. Confirm who keeps editable project files and for how long.

For software that changes often, ask which scenes can be replaced independently. A stable explanation of the customer problem may last longer than a specific click path. Agree how later changes are estimated; “editable” does not mean unlimited free updates.

Require a schedule that includes your reviews. A supplier’s production days and your publication deadline are not the same thing. If time is tight, commission the smallest useful first film and defer nonessential versions. Do not treat a promise to work faster as proof that the scope fits.

Sources: FDM: Keeping SaaS demos current

What should you know before saying yes?

You should know who leads the work, what they will make, why that format fits, who approves product facts, what a revision includes and what you can use after delivery. If a proposal leaves those unanswered, ask for clarification before paying a deposit.

FDM is worth considering when the brief needs workflow explanation, interface-led editing or repeatable product education. Start with the Krista.ai and TikaMobile work linked here, then bring the hardest part of your own product story. If a simple internal screen recording already answers the question, a custom animated launch film may not be the right purchase.

Sources: FDM: Watch the Krista.ai email workflow explainerFDM: TikaMobile walkthrough examples and FDM scope