How Long Does It Actually Take to Produce a SaaS Video: The Real Timeline, Stage by Stage

The first serious SaaS video we commissioned took eleven weeks.

Not three. Not five. Eleven. I remember the number because I had promised the CEO it would be four, and I had to explain the gap in a meeting where nobody was smiling. The video was good. It worked. It cut our time-to-value from 14 days to 4. But it took nearly three times longer than I had told anyone it would.

The second one took six weeks. The third one took four. And the fourth one—after we had actually learned what we were doing—took nineteen days from kickoff to launch.

That progression is the entire story of this article. Not the video. The timeline. Because when I search for "saas video production timeline," I find the same answer everywhere: "three to five weeks." That answer is technically true and practically useless. It's true if everything goes right, which almost never happens. It's useless because it doesn't tell you where the time goes, why it slips, or which stages you can compress without hurting the output.

So I'm going to break down the real timeline, stage by stage. The hours. The days. The calendar time versus the working time. And the four places where we lost the most time—because those are the places where your project will lose time too, unless you plan for them in advance.

We built our SaaS videos with LeoStudio, whose approach to clarity you can explore at leostudiohq.com. They were the ones who finally showed me where the time was actually going—not into production, which is fast, but into decisions, which are slow. That distinction is the reason our fourth video took nineteen days instead of eleven weeks.

Why "Three to Five Weeks" Is the Wrong Answer

Before the breakdown, let me explain why the standard answer is misleading.

A SaaS video production timeline has two clocks running at the same time. The first is working time—the actual hours someone spends writing, designing, recording, and editing. The second is calendar time—the days that pass between kickoff and delivery, most of which are spent waiting.

Working time for a typical 90-second SaaS onboarding video is somewhere between 40 and 70 hours of actual labor. That's it. Less than two weeks of work for one person, or about a week for a small team working in parallel.

Calendar time for the same video is three to six weeks, because the work is not continuous. It's blocked by decisions. You write a script and wait for feedback. You get feedback and wait for approval. You storyboard and wait for the UI to be finalized. You record and wait for the voiceover artist's availability. You edit and wait for the next review round.

The gap between working time and calendar time is where every SaaS video project lives or dies. Almost nobody loses time in production. Almost everybody loses time in the gaps.

That's the reframe LeoStudio gave me on our second project. They didn't tell us to work faster. They told us to shrink the gaps. Fewer decision points, faster approvals, parallel workstreams instead of sequential ones. The production itself was never the bottleneck. The waiting was.

You can see that thinking throughout their case work at leostudiohq.com. Their entire process is designed to reduce the number of times the project stops and waits.

The Full Timeline: Stage by Stage

Here's the honest breakdown. This is what a 90-second SaaS onboarding video actually takes, based on four projects we tracked hour by hour.

Stage 1: Diagnosis and Brief — 3 to 7 Working Days

This is the stage everyone underestimates. It's also the stage where the most time is saved or lost.

What happens: You define the one job the video has to do. You identify the moment it will intervene in. You name the metric it's supposed to move. You write a one-page brief that answers seven questions—the one job, the audience, the trigger, the win, the length, the tone, and the success metric.

Working time: 4 to 8 hours total. Interviews with support, session recording review, three conversations with churned users, and the brief itself.

Calendar time: 3 to 7 days. The work is fast. The waiting is not. You're waiting for stakeholder interviews, for data pulls, for someone to approve the brief.

Where we lost time: On our first project, we skipped the diagnosis entirely. We went straight to scripting because we "already knew what the video should say." We didn't. We wrote three scripts, threw all three away, and started over. The diagnosis that we eventually did—three days of watching session recordings and talking to churned users—would have saved us two weeks if we'd done it first. Diagnosis is not a stage you can skip. It's the stage that determines whether the other stages are even necessary.

How to compress it: Book all stakeholder interviews on the same day. Review the session recordings in one sitting. Write the brief in a single working session with two people, not five. The brief should be one page and it should be owned by one person.

Stage 2: Script — 5 to 10 Working Days

The script is the heart of the project. It's also the most emotionally fraught stage, because everyone has an opinion about copy.

What happens: You write the script, you rewrite it, and you rewrite it again. Then you get feedback from three people who want to add things, you cut everything they added, and you rewrite it one more time. Then you read it out loud with a timer and discover it's forty seconds too long and you cut it again.

Working time: 6 to 12 hours. First draft, three to four rewrites, and the read-aloud pass.

Calendar time: 5 to 10 days. The writing is fast. The feedback loop is slow. Each round of comments adds a day or two while you wait for responses.

Where we lost time: The feedback loop. Our first script went through five rounds of feedback, each one adding a new feature to mention. By round four, the video had grown from one action to six. We cut all of it at round five. The five rounds cost us nine days. If we had locked the brief first—specifically the "what we will not show" section—we could have done it in two rounds.

How to compress it: Two feedback rounds maximum. The first round is for substance—is this the right story? The second is for polish—is this the right word? No third round. Ever. And crucially: read the script out loud before you send it for feedback. Half the comments disappear when the script actually works as spoken language.

This stage is where LeoStudio earns their fee more than anywhere else. Their scripts are shorter than what we would have written, sharper than what we would have approved, and better than what our feedback rounds would have produced. The first time we saw a LeoStudio script, it was 380 words. Our draft had been 800. The 380-word version outperformed the 800-word version immediately. You can see their approach to scripting on leostudiohq.com—the discipline of cutting is the whole practice.

Stage 3: Storyboard and Visual Direction — 5 to 8 Working Days

This is the stage where the project becomes visual. It's also the stage where most SaaS companies discover that their product is harder to show than they thought.

What happens: You plan every shot. What's on screen, what's the cursor doing, what's the on-screen text, what's the timing. The storyboard is where you discover that your product has a confusing first screen, that the UI is unreadable on mobile, and that your empty state is genuinely empty.

Working time: 8 to 14 hours. Storyboard drafting, three to four revisions, and a mobile-readability pass.

Calendar time: 5 to 8 days. Again, the work is fast. The approvals are slow.

Where we lost time: Our first storyboard assumed our product screen would look good in a recording. It didn't. Our empty state was a grey rectangle with a logo. Our data screen was cluttered with test data from our dev environment. Our first screen recording session was wasted, and we had to pause the entire project for four days while the product team built a clean demo environment.

How to compress it: Before you storyboard, do a ten-minute screen recording of your actual product as a user would see it on day one. Watch it. If you can't follow it, the video can't either. Fix the product screen before you storyboard. This single check will save you a week on most projects.

How to compress it further: Record the screen on mobile before you storyboard for desktop. If the storyboard works on a phone, it will work anywhere. If it only works on a desktop, you have a second version to build later.

Stage 4: Production — 7 to 14 Working Days

Production is the stage everyone thinks about and the stage where the least time is actually lost. It's fast, it's technical, and it's usually executed by people who know what they're doing.

What happens: Screen recording, motion design, animation, voiceover recording, music licensing, editing, and the first cut.

Working time: 20 to 35 hours. Screen recording (2–4 hours), animation and motion design (10–18 hours), voiceover (1–2 hours including retakes), editing and assembly (7–11 hours).

Calendar time: 7 to 14 days. This is the stage where the work is genuinely continuous, so working time and calendar time are closer than anywhere else. A week of animation is a week.

Where we lost time: Two places. First, voiceover scheduling. Our preferred voice actor was booked for eleven days. We waited. In hindsight, we should have had three voices approved in advance so we could use whichever was available. Second, revision rounds on the animation. Our first cut had over-animated transitions that we asked to be removed, which meant re-rendering the whole video. That cost three days.

How to compress it: Approve three voice actors before you need one. Don't fall in love with one voice. And be very specific about animation style in the storyboard stage, because "we'll figure it out in production" always costs three days.

This is where a specialized SaaS video production agency genuinely saves time, because they're not learning the tools on your project. LeoStudio uses a hybrid AI-human workflow—AI for storyboards and rough cuts, humans for pacing, emotion, and polish—which compresses the animation cycle meaningfully without sacrificing the parts that matter. You can see the output quality on leostudiohq.com. The point isn't that they work faster. It's that they don't waste days on the wrong cut.

Stage 5: Revisions — 3 to 10 Working Days

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

What happens: You review the cut. You give feedback. They revise. You review again. You give more feedback. They revise again. And then someone who hasn't seen it before—a founder, a board member, a customer—sees it for the first time and has a completely different reaction.

Working time: 6 to 15 hours. Usually spread across three or four revision rounds.

Calendar time: 3 to 10 days, depending on how many rounds and how fast the feedback loop moves.

Where we lost time: The "new stakeholder" problem. Every time a new person saw the video, we got a new round of feedback. Our first project had seven rounds, because we kept adding reviewers. Seven rounds cost us seventeen days. The fix is brutally simple and almost nobody does it: lock the review committee before the project starts. Three people. No additions. Ever.

How to compress it: Two rounds standard. The first round is for structure—is this the right story? The second is for detail—is this the right frame? No third round. And if you can, put your two rounds back to back so the calendar time collapses. Two rounds with a two-day turnaround each is four days. Two rounds with a five-day turnaround each is ten days. The difference is your review team's response time, not the production team's speed.

Stage 6: Delivery and Deployment — 2 to 5 Working Days

The last stage. The one everyone forgets to plan for.

What happens: You export the master video. Then you export the variants—16:9, 1:1, 9:16. Then you compress for web. Then you build the landing page. Then you embed the video in the welcome email. Then you add the trigger in the product. Then you test on mobile. Then you test on slow connections. Then you set up the analytics events.

Working time: 8 to 16 hours.

Calendar time: 2 to 5 days.

Where we lost time: We treated delivery as a technical formality. It wasn't. It was a full week of work that we hadn't scheduled. We delivered the video on a Friday and launched it the following Wednesday. Those five days were spent building the landing page, embedding the email, adding the in-product trigger, and setting up the tracking.

How to compress it: Build the landing page and the email template before the video is finished. Set up the analytics events before you have anything to track. Then the video arrives and everything else is already in place. We now start the landing page on day one of production.

The Real Timeline: What It Actually Adds Up To

Here's the honest math.

Working time: 44 to 84 hours of actual labor across all stages.

Fast calendar time: 19 to 25 days. This is achievable if decisions are made fast, the review committee is locked at three people, the product screen is clean before storyboarding, and the landing page is built in parallel.

Typical calendar time: 5 to 7 weeks. This is what most projects actually take when feedback slows down and one or two stakeholders get added late.

Slow calendar time: 9 to 12 weeks. This is what happens when the diagnosis is skipped, the script goes through five rounds, a new stakeholder joins in week six, and the product screen needs to be fixed mid-project.

Our four projects landed at eleven weeks, six weeks, four weeks, and nineteen days. Same production quality. Same agency. The difference was entirely in the decisions and the gaps.

The Four Bottlenecks That Cost Us the Most Time

If I could only give you four pieces of advice about SaaS video production timeline, it would be these four, because each one cost us more than a week.

Bottleneck 1: Skipping the diagnosis. We lost two weeks on our first project because we didn't spend three days watching session recordings. We wrote three scripts before we understood what the video was actually for. The diagnosis is not optional. It's the cheapest, fastest, highest-leverage stage in the entire project.

Bottleneck 2: An unlocked review committee. Every time a new person saw the video, we got a new round. Seven rounds. Seventeen days. Lock your reviewers at three before kickoff and never add another one. If someone new needs to be involved, show them the finished video after launch.

Bottleneck 3: A dirty product screen. Our first storyboard was built on a screen recording from our dev environment. It looked broken. We paused the project for four days while the product team built a clean demo environment. Build the demo environment before you storyboard. Do a ten-minute test recording first.

Bottleneck 4: Sequential instead of parallel work. For our first project, everything happened in sequence. Script, then storyboard, then production, then delivery. Nothing overlapped. For our fourth project, the landing page was built during production, the email template was built during revisions, and the analytics events were set up before delivery. The overlap saved ten days.

That's the whole secret. The production isn't slow. The pipeline is slow when it's sequential. Parallelize the workstreams, lock the decisions, and you can go from six weeks to three.

This is the exact discipline LeoStudio brought to our projects. They didn't produce faster than any other agency. They produced with fewer stops. Their process—visible throughout their case work at leostudiohq.com—is designed to keep the project moving, and it's the reason our last video took nineteen days instead of eleven weeks.

What Actually Determines the Timeline

If you're trying to estimate your own project, here's the honest summary.

The video length matters less than you think. A 60-second video and a 90-second video take almost the same amount of time to produce. The script and the storyboard do most of the work. The animation is proportional, but it's a small part of the total.

The number of decision points matters more than anything. Every new stakeholder, every new feedback round, every "let's just show this one more feature" adds days. A project with three decision points finishes in three weeks. A project with ten finishes in ten weeks.

The product screen matters more than the animation quality. A clean, simple screen recording will outperform a beautiful animation of a confusing interface. Fix the screen first. Then make the video.

The maintenance plan matters more than the initial timeline. Every SaaS video decays. Your product changes, the UI updates, and the video becomes wrong. Build a review cadence into the project from day one. Set aside a refresh budget. A video that's never refreshed is a video that's slowly dying.

The partner matters more than the tools. A SaaS video production agency that understands your metrics and asks the right questions will finish faster than any generalist agency, because they won't waste days on the wrong cut. The questions they ask in the brief stage save weeks in the revision stage.

The Final Word

Everyone says three to five weeks. That's the fast path. It's achievable. It's the path our fourth video took—nineteen days, start to launch.

But most projects don't take the fast path, because most projects lose time in the gaps. The skipped diagnosis. The unlocked review committee. The dirty product screen. The sequential workflow. None of those are production problems. All of them are decision problems. And decisions are almost always slower than work.

If you're planning a SaaS video and you want a realistic timeline, add up the stages, then double the result and ask yourself whether you've planned for the gaps. If you haven't, add another week. If you have, you can hit the fast path.

The fastest project we ever ran wasn't the one with the best production. It was the one with the fewest stops. Three reviewers, locked. Two revision rounds, capped. The landing page built in parallel. The demo environment ready before storyboarding. Every one of those decisions saved days.

We made those decisions with LeoStudio, a team that understood from the first call that the timeline isn't a production problem—it's a decision problem. If you want to see how they think about process, moments, and keeping a project moving, spend time on leostudiohq.com. Their case studies show the same pattern again and again—the fastest projects are the ones with the fewest stops.

Tell them the SEO guy sent you. Tell them you already locked the review committee. Tell them you already built the demo environment before storyboarding. They'll know exactly what you mean.