A typical agency explainer takes 4–9 weeks from kickoff to final file — agencies quote 4–6, and real projects drift toward the high end. Almost none of that time is animation: the weeks are made of rounds, handoffs, and days a draft spends waiting for someone to say yes.
That gap between "quoted" and "actual" isn't dishonesty. It's structure. Once you see where the time lives, you can compress it — with any vendor.
Where the weeks actually go
The standard agency pipeline, stage by stage:
- Week 1: discovery. A kickoff call, maybe two. Then a creative brief you review. Elapsed time is mostly scheduling — finding an hour that fits both calendars.
- Weeks 2–3: script. A draft, your notes, a revision, your sign-off. Two rounds is normal. Each round is a day of writing wrapped in several days of waiting.
- Weeks 3–4: storyboard and voiceover. Frames for each scene, another approval, then VO recording — which adds a booking dependency: the actor's calendar joins yours and the agency's.
- Weeks 4–7: animation. The only stage that's genuinely slow to produce. Two to three weeks of actual work.
- Weeks 7–9: revision rounds. One or two contracted rounds. Your notes, their fixes, your re-review. If VO was recorded before animation and a wording change surfaces now, add a re-record and a re-edit.
Count the approvals: brief, script (twice), storyboard, VO, cut one, cut two. Seven or more round trips, each crossing at least two calendars. A project where every review takes you three days is a project that runs three weeks longer than the same project with same-day feedback — identical work, different calendar.
The math nobody puts in the quote: revision is half the work
Here are our own production numbers, and they're worth staring at before you believe any timeline. Across sixty-odd produced videos: simple videos took 4–6 revision passes each. The flagship pieces took 13 to 24, staged as three full versions — the best videos we've made were re-made, not touched up. Roughly a quarter of all production commits are revision-shaped, and counting rejected parallel attempts, about half of all production work happens after first review.
That's a shop that does this daily, with a standing system. So when a timeline budgets one polite revision round at the end, one of two things is true: the vendor plans to talk you out of your notes, or the schedule is fiction. Either the quality flexes or the calendar does.
The takeaway isn't "demand unlimited revisions" — unlimited-revision offers price the chaos in. It's that speed comes from making each revision cheap, not from pretending there won't be any.
What actually determines speed
Four things, biggest lever first:
1. Your feedback turnaround. The biggest lever, and you hold it. Elapsed time on most projects is dominated by drafts sitting in inboxes. One reviewer with authority, answering same-day, can take weeks off any vendor's schedule. Approval by committee adds them back: three stakeholders who each need a pass turn every round trip into three.
2. Reviewing cheap artifacts early. The expensive failure is the one caught late. Our process reviews rendered still frames before any motion, narration, or final render exists — one look at one frame catches wrong layouts, invented UI, and broken framing at about 5% of a finished video's cost. Before we installed that gate, one batch went to full render and nine of ten videos were rejected; the next batch, reviewed as stills first, passed five of five. The same principle works with any vendor: insist on approving the script and the storyboard properly, because a structural note delivered against a finished cut costs weeks, and the same note against a storyboard costs a day.
3. Whether words are welded to pictures. In the traditional pipeline, VO is recorded early and animation is timed to it — so a late wording change means re-record, re-book the actor, re-time the scenes. In our system narration is text: edit the sentence, the changed scene re-synthesizes and re-times itself, re-render. A narration fix is about a sixty-second loop. That one architectural choice moves the most common revision class (wording) from "a week" to "same day."
4. Decisions made once. Slow shops re-decide everything per project — voice, pacing, easing, layout style. Fast ones decide once and pin it: we A/B-tested voice settings one time, froze them, and committed approved audio takes for reuse. Every decision that's already made is a meeting that never happens. This is most of why a standing system beats a fresh crew, whoever you hire.
A realistic fast path
What a compressed schedule looks like when the process is built for it, using our own numbers: candidate directions within 24 hours of getting your product's URL — roughly twenty short rendered directions, which replace the discovery call, script round, and storyboard round, because you spec the video by picking instead of by meeting. First full cut in 5 business days (72 hours on the top tier). Then your revision rounds, which run at the speed of your feedback.
The honest caveats: this works because the scope is constrained — 60–180 second software explainers built from your real UI. Custom character animation, 3D, and filmed footage genuinely take agency weeks; nothing compresses a shoot or a rigging pipeline. And no process removes your review time — it just makes each review small and early.
Compressing any timeline, with anyone
If you've already picked a vendor, five moves shorten the calendar:
- Name one reviewer with final authority. Route all notes through them.
- Answer every review the same day. Put the review slots on your calendar at kickoff, like meetings.
- Front-load product truth: real screens, real values, a real demo run, delivered before scripting. Every value the vendor has to chase later is a stall — and every value they invent instead is a revision.
- Treat the approved script as locked. Mid-animation scope additions restart the clock; keep a list for video two instead.
- Ask to review the cheapest artifact at each stage — outline before script, frames before motion. Never accept "it's coming together" as a substitute for something you can look at.
FAQ
Why does it take 4–9 weeks when animation is only 2–3? Because the other weeks are coordination: approvals crossing calendars, booking dependencies, and revision rounds. The work is days; the waiting is weeks.
Can an agency deliver in two weeks? Some offer rush delivery for a premium. Look at what the rush removes — usually a script round or a revision round. Given that revision is about half the real work, a schedule that deletes it is deleting quality, not waiting.
What slows projects down the most? Client-side feedback latency, by a wide margin. Second place: wording changes after voiceover is recorded, which is a pipeline problem — agency vs. DIY covers how the paths differ here.
How fast can I see something for my product? Twenty rendered candidate directions in 24 hours, free. The first paid cut lands within 5 business days.
If you'd rather test the fast path than read about it, paste your product's URL and check the clock.