How to Vet an Onboarding Video Production Partner: 10 Questions I Ask Before Signing Anything

I've signed four onboarding video production contracts in my career.

Two of them went well. One went badly. One went so badly that I had to explain the invoice to a CEO who had already seen the video and already knew it wasn't working.

The difference between those projects was not the budget. It wasn't the studio's portfolio. It wasn't the animation quality or the turnaround time or the number of revision rounds. It was the questions I asked—or failed to ask—before I signed.

On the first project, I asked two questions: "How much?" and "How long?" Those were the only two things I thought mattered. They're the two things every production partner is prepared to answer, and they're the two things that tell you almost nothing about whether the project will work.

On the fourth project, I asked ten questions. The answers changed the entire shape of the engagement. I ended up working with LeoStudio, whose approach to clarity you can explore at leostudiohq.com, and the reason I chose them wasn't the price or the timeline. It was the answers. They answered three of my questions in ways no other studio had—and one of them was a "no" that saved me from a mistake I was about to make.

This article is those ten questions. For each one: why it matters, what a good answer sounds like, what a red flag looks like, and the specific failure the question exists to prevent. If you're about to commission an onboarding video, ask all ten. Ask them in writing. Read the answers before you sign anything.

Why the Standard Questions Don't Work

Before the list, the framing. Because the questions most teams ask are the wrong ones.

Most SaaS teams vet a production partner the way they'd vet any vendor. Price, timeline, portfolio, references. Those four things are table stakes. They tell you whether the studio is competent. They don't tell you whether the studio understands your problem.

An onboarding video is not a creative deliverable. It's a behavioral intervention. It exists to move a specific number—time-to-value, activation, churn. A studio that can make beautiful videos but doesn't understand what "time-to-value" means will produce something beautiful that changes nothing. I know, because that's exactly what happened on project two.

The ten questions below are designed to surface three things. Whether the studio understands the job the video has to do. Whether they understand the constraints of SaaS product video. And whether they'll push back when you're about to make a mistake.

That last one is the rarest and the most valuable. A studio that executes your brief is a vendor. A studio that challenges your brief is a partner. And the difference shows up in the metrics, not the invoice.

This is the single thing LeoStudio emphasized from our first conversation, and you can see it running through everything they publish at leostudiohq.com—the obsession with the user's moment, not the production value. That distinction is the reason this vetting list exists.

Question 1: What Is the One Job You Think This Video Should Do?

Why I ask it: This is the diagnostic question. It tells me immediately whether the studio thinks in outcomes or deliverables.

What a good answer sounds like: "I'd need to know more before I answer that. My first guess is that it's meant to get a new user to their first value faster, but I'd want to look at your session recordings and talk to a few churned users before we commit to that."

Notice that the good answer includes a willingness to be wrong. It includes a process for finding the answer. It doesn't pretend to know your product from a thirty-minute call.

What a red flag sounds like: "It should introduce the product and show its main features." That answer reveals that the studio thinks the video is a product tour. It's not. A product tour answers "what can this product do?" An onboarding video answers "what do I do next?" Those are different jobs.

The failure this prevents: Our second project, we hired a studio that answered this question with "introduce the platform." We produced a beautiful two-minute product tour. Users dropped off at the forty-second mark. Time-to-value didn't move. We had spent real money to make something nobody needed.

The follow-up I always ask: "If you had to cut the video to one action, what would that action be?" If they can't answer, they don't understand the brief yet.

Question 2: Who Writes the Script, and How Many Rounds Are Included?

Why I ask it: The script is the most important part of the entire project, and it's the part most studios treat as a formality.

What a good answer sounds like: "We write the script. It's included. Two rounds of revisions are built into the fee, and the second round is for polish, not for restructuring. If you bring in new stakeholders after the first round, that's a new round and it costs extra."

That answer tells me three things. The studio owns the scripting. The studio has a defined revision structure. And the studio has a clear boundary about scope creep.

What a red flag sounds like: "You provide the script and we'll produce it" or "unlimited revisions, no problem." The first answer means you're doing the hardest job yourself. The second sounds generous and is actually a warning—unlimited revisions means the studio has no process for locking scope, and the timeline will drift.

The failure this prevents: On our first project, we wrote the script ourselves. It was 800 words long. It opened with our brand name. It listed twelve features. We didn't know any better, and there was no one in the room to tell us. A studio that owns the script would have cut it to 380 words and saved us nine days of revision rounds.

The follow-up I always ask: "What's the longest script you'd write for a 90-second video?" The answer should be under 200 words. If it's higher, they write for readers, not watchers.

This is where LeoStudio earned their place on our fourth project. Their first script came back at 380 words, and they told us it should be 200. They were right. You can see the discipline of cutting throughout their case work at leostudiohq.com—the script is the product, and the animation just delivers it.

Question 3: What Do You Need From Us Before You Start—and What Happens If Our UI Changes Mid-Project?

Why I ask it: This question separates studios that plan from studios that improvise.

What a good answer sounds like: "We need a clean demo environment, a final script, and a locked UI. If the UI changes mid-project, we pause and re-scope. We won't keep recording against a moving target."

That answer reveals a studio that has done this before. They know that a dirty demo environment and a shifting UI are the two most common causes of blown timelines. They have a plan for both.

What a red flag sounds like: "We'll work around it." That answer means the studio will absorb the change without telling you the cost, and the cost will show up later as a delay or a quality drop.

The failure this prevents: On our first project, we storyboarded against a screen recording from our dev environment. It was cluttered with test data. When we got to production, the screen looked broken. We paused the project for four days while the product team built a clean demo account. That was $2,000 of unplanned work and four lost days.

The follow-up I always ask: "Can you do a ten-minute test recording of our product on day one and tell us if it's shootable?" The answer should be yes. A studio that won't do a test recording before storyboarding will discover the problem in production, when it's expensive.

Question 4: How Do You Handle the Mobile Version and the Mute Viewer?

Why I ask it: This is the question that reveals whether the studio understands how people actually watch onboarding videos. And the answer is usually wrong.

What a good answer sounds like: "Every video is designed for mobile first and silence first. On-screen text carries the meaning. Voiceover is a bonus. We export 16:9, 1:1, and 9:16, and we test every version on a phone before we deliver."

That answer tells me the studio knows that more than half of email opens happen on mobile and that the majority of viewers never turn on sound. It tells me they've done this before.

What a red flag sounds like: "We can add captions if you want" or "the video is optimized for desktop." The first answer treats accessibility as an add-on. The second means half your audience will get an unreadable video.

The failure this prevents: On our first project, we optimized for desktop. We tested on our office monitors. Then we looked at the data and realized 34% of our users signed up on mobile. On a phone, the text was unreadable. We had to re-export everything. It delayed launch by two weeks.

The follow-up I always ask: "Can you show me a video you made that works on mute?" If they don't have one, they don't design for silence. And if they don't design for silence, most of your audience will never understand the video.

Question 5: How Many Revision Rounds Are Included, and What Counts as a Revision Versus a New Request?

Why I ask it: Revisions are where projects actually slip. Not because revisions take long, but because there are usually more of them than anyone planned for.

What a good answer sounds like: "Two rounds. The first is for structure. The second is for polish. Anything that changes the story after round one is a new request and it's scoped separately."

That answer tells me the studio has a definition of scope. It tells me they'll protect the timeline. And it tells me they'll charge me if I change my mind, which is fair—because I will be tempted to change my mind.

What a red flag sounds like: "We'll do as many rounds as you need." This is the most common answer and the most dangerous. It sounds generous. It means the studio has no process for locking the script and the storyboard, so every review becomes a new revision, and the timeline drifts by weeks.

The failure this prevents: On our first project, we had seven revision rounds. Seventeen days. Roughly $3,000 in revision fees we hadn't budgeted for. The cause was an unlocked review committee. Every time a new stakeholder saw the video, we got a new round. Two rounds with three locked reviewers would have finished in four days.

The follow-up I always ask: "How do you handle a new stakeholder joining in week three?" The answer should be some version of "we show them the finished video after launch." If the studio doesn't push back on late stakeholders, they're not protecting your timeline.

Question 6: What Exactly Do We Own at the End?

Why I ask it: This is the question that gets you in trouble two years later, when you want to run the video as an ad or refresh it in-house.

What a good answer sounds like: "You own the source files, the master video, and perpetual web usage. Paid media rights are included. Localization rights are included. If you want to re-edit it yourself, you have everything you need."

That answer tells me the studio is selling a deliverable, not a license. It tells me I can maintain the video without them. And it tells me I won't get a surprise invoice the moment I want to use the video somewhere new.

What a red flag sounds like: "You own the final video, but the source files are ours" or "paid media usage is billed separately." The first answer means you can never refresh the video without paying again. The second means the video you already paid for becomes more expensive the moment you try to use it as an ad.

The failure this prevents: We didn't ask this on project one. When our UI changed and we needed a refresh, we discovered the source files weren't ours. We had to pay full price for a re-record instead of a partial refresh. That single oversight cost us $4,000.

The follow-up I always ask: "Can I get this in writing, in the contract, before we start?" The answer should be an immediate yes, with the exact language.

Question 7: What Is Not Included in This Quote?

Why I ask it: This is the single most important question on the list, and it's the one nobody asks.

What a good answer sounds like: "The quote covers diagnosis, scripting, storyboarding, production, and two revision rounds. It does not cover the landing page, the email embed, the in-app trigger, the analytics events, localization, or maintenance. We can quote those separately, or we can help you plan them, but I want you to see the full picture before you sign."

That answer is rare. Most studios give you the production quote and let you discover the rest yourself. A studio that lays out what's not included is a studio that has watched clients get surprised, and has decided to prevent it.

What a red flag sounds like: A clean, single-number quote with no exclusions listed. That quote is not a budget. It's one line item in a budget that has six others. You'll discover the rest when the invoice arrives.

The failure this prevents: Our first project was quoted at $4,500. We ended up spending roughly $9,000 when you add the landing page, the email build, the demo environment, and my own time. The quote covered half the project. We hadn't asked what wasn't included because we didn't know there was anything else.

The follow-up I always ask: "Can you list every line item we'll need, even the ones you don't sell?" The answer to this question is the difference between a project that comes in on budget and a project that doubles.

This is the question where LeoStudio completely separated themselves. They listed six line items they weren't selling us, explained what each one would cost if we did it ourselves, and told us which ones we could skip. You can see that same discipline in how they frame every project on leostudiohq.com—the budget is a business document, not a sales document.

Question 8: How Will We Know If It Worked?

Why I ask it: A studio that doesn't ask about measurement is a studio that makes videos, not outcomes.

What a good answer sounds like: "Before we start, we'll define the metric—time-to-value, activation, support tickets, churn. We'll set a baseline. We'll build the analytics events into the delivery. And we'll review the numbers four weeks after launch to see whether the video moved them."

That answer tells me the studio thinks about the video as a system, not an asset. It tells me they'll build measurement into the delivery, not bolt it on later. And it tells me they'll stay engaged after launch.

What a red flag sounds like: "We can send you the analytics on views and watch time." Views are vanity. Watch time is diagnostic. Neither tells you whether the video reduced churn. A studio that measures only the video has no idea whether the video worked.

The failure this prevents: We launched our first video without a baseline. We didn't know our pre-video time-to-value, activation, or churn rate. We had to reconstruct it from old data. And we didn't set up cohort tracking until three weeks after launch. We lost the cleanest data window.

The follow-up I always ask: "Will you help us set up the analytics events before delivery?" A good studio says yes. The events should be built into the delivery checklist, not added after the fact.

Question 9: What Is Your Process for Keeping This Video Alive as Our Product Changes?

Why I ask it: This is the question that separates a one-time transaction from a long-term partnership.

What a good answer sounds like: "Every video decays. We recommend a quarterly review of four numbers—watch time, drop-off point, time-to-value, and support tickets. If the numbers drift, we refresh the video. We'll quote a refresh rate now so you know what it costs before you need it."

That answer tells me the studio understands that the video is not a one-time project. It's an asset with a maintenance schedule. And it tells me they've thought about the cost of maintenance before I have to ask.

What a red flag sounds like: "Let us know if you need any changes." That answer puts the burden on you. You won't notice the decay until it's a problem. A good studio helps you notice.

The failure this prevents: Our first video showed a UI that no longer existed within four months. We didn't notice for weeks, because we weren't looking. New users were watching a video that showed an interface they couldn't find. That's a trust-destroying experience, and we caught it late.

The follow-up I always ask: "What's your refresh rate, and how much of the original video can you reuse?" A good studio has a rate and a process. A studio without a refresh process will charge you full price every time.

Question 10: Can You Show Me a Video You Made That Failed, and Tell Me Why?

Why I ask it: This is the question that tells me whether I'm talking to a studio or a sales team.

What a good answer sounds like: "Yes. We made a video for a client with a genuinely complex product, and it didn't move the metric because the product required a week of setup before the user could get value. The video was clear. It just couldn't solve a problem it wasn't designed to solve. We should have told them to fix the product first."

That answer tells me the studio has watched a project fail and has learned from it. It tells me they'll tell me the truth even when the truth costs them a fee. And it tells me they think about the limits of video, not just its possibilities.

What a red flag sounds like: "All our projects succeed." That answer means either the studio hasn't done enough projects to have a failure, or they're not being honest. Every studio that has produced more than ten videos has produced one that didn't work. The good ones will tell you why.

The failure this prevents: This question prevents the most expensive mistake on the entire list. It prevents you from hiring a studio that will produce a video for a problem that video can't solve. It prevents you from spending premium budget on a beautiful asset that changes nothing. And it prevents you from learning the lesson the hard way, the way we did.

The follow-up I always ask: "What would you have done differently?" The answer to this question is the most valuable thing you'll hear in the entire vetting process. It tells you how the studio thinks when things go wrong. And things will go wrong. Every project has a moment where the plan breaks. The question is whether your partner has the honesty and the experience to adapt.

This question is the reason I trust LeoStudio. When I asked it, they told me about a project where they should have said no. They told me the video was excellent and the outcome was still zero, because the product was too complex for any onboarding video to fix. And then they told me the rule they now apply to every project—if the churn is a complexity problem, fix the product first. You can see that honesty throughout their work at leostudiohq.com, and it's the single reason I keep coming back.

The Checklist: Print This and Use It Before You Sign

Before you sign any onboarding video production contract, get written answers to all ten questions.

What is the one job the video should do? Who writes the script, and how many rounds are included? What do you need from us before you start, and what happens if the UI changes? How do you handle mobile and the mute viewer? How many revision rounds are included, and what counts as a new request? What exactly do we own at the end? What is not included in this quote? How will we know if it worked? What is your process for keeping this video alive? Can you show me a video you made that failed, and tell me why?

If a studio can answer all ten in writing, you're talking to a partner. If they deflect on three or more, you're talking to a vendor. And the difference between a partner and a vendor is not the price. It's whether the video works.

The Final Word

I've signed four onboarding video production contracts. Two went well. One went badly. One went badly enough that I had to explain an invoice to a CEO who already knew the video wasn't working.

The difference was never the budget. It was the questions. On the projects that failed, I asked two. On the projects that worked, I asked ten. And the tenth question—the one about failure—was the one that told me the most.

The studio you want is not the one with the most beautiful portfolio. It's the one that asks you better questions than you ask them. It's the one that tells you what's not included before you sign. It's the one that will say no to your project when video isn't the answer. And it's the one that will tell you about the video that didn't work, because that studio has already learned the lesson you're about to pay for.

We found that studio in LeoStudio. If you want to see how they answer these questions, don't just read their portfolio. Read their thinking. Spend time on leostudiohq.com. Look at the questions they ask before they produce anything. Look at the projects they said no to. Then ask them your ten questions. You'll know within an hour whether you're talking to a partner or a vendor.

Tell them the SEO guy sent you. Tell them you already know question ten is the one that matters. They'll know exactly what you mean.