How we built the five-phase pipeline
Most AI video tools hand you a clip and call it finished. StudioCut hands you a publish-ready video — and lets you approve it in five stages instead of betting on one. We built the pipeline that way because a video that looks done can still be wrong in a way nobody catches until it's live, and the generate-it-all-at-once alternative kept shipping confidently broken videos. Here is what we tried first, why it failed, and how the review gates earn their keep.
The version that generated everything at once
The first prototype was a single long-running job. You typed a topic, the job called every model it needed — script, images, voiceover, layout, render — and 12 minutes later a finished MP4 dropped into a folder. It demoed beautifully. It was also unusable in practice, and the reason is worth stating plainly.
When a 12-minute job produces a bad result, you have no idea which decision was bad. The script misread the topic? An image is off-brand? The voice picked the wrong emphasis? You re-run the whole thing and pay for the whole thing again, hoping the dice land differently. Cost and latency both scale with the part of the pipeline you trust least.
What to capture: The production detail page with the five-circle phase timeline at the top, mid-run — Phase 1 marked complete (green check), Phase 2 active (spinner/highlighted), Phases 3–5 pending (grey). Show the page header and the tab strip below the timeline.
Why five phases, not three and not ten
The phase boundaries are not arbitrary. Each one is drawn where a human can look at the output and make a cheap, confident yes/no decision — and where the work before the boundary is expensive enough that re-running it blind would hurt.
| Phase | Produces | Why the gate is here |
|---|---|---|
| 1 — Planning | Scene-by-scene storyboard | Cheapest possible point to catch a misread brief. No media generated yet. |
| 2 — Assets | Images, voiceover, music, clips | The expensive phase. You approve the plan before spending here. |
| 3 — Direction | Scene layouts and animation | Catches layout/timing problems before the render locks them in. |
| 4 — Render | The final MP4 | Last chance to see the actual video, not a description of it. |
| 5 — Publishing | Title, description, tags, thumbnails | Metadata is fast to fix and easy to get subtly wrong. |
Three phases would merge Planning and Assets — and that is precisely the merge that the monolith proved costly. Ten phases would gate decisions a human can't meaningfully evaluate ("approve this image's seed value?"). Five is the count where every gate is both cheap to judge and expensive to skip.
Phase 1 is the gate that matters most
If you only ever review one thing, review the storyboard. Phase 1 produces a complete scene-by-scene plan — narration text, visual intent, and pacing — and no pixels or audio have been generated yet. Editing a scene's script here costs a text re-prompt. Editing it after Phase 2 means regenerating that scene's image and voiceover. After Phase 4 it means a re-render.
So the gate after Phase 1 is doing the heaviest lifting in the whole system: it moves the most consequential corrections to the cheapest possible moment.
What to capture: The Plan tab after Phase 1 completes — the horizontal scene filmstrip with several scene cards visible, one scene selected showing its Script sub-tab. Include the "Approve & Start (Voiceover)" action button in the page header.
Your work is never lost between gates
A gated pipeline is only reassuring if the gates are unbreakable. Close the tab during Phase 3, lose your connection, step away for an hour, come back tomorrow — your production is exactly where you left it, waiting for your approval. Nothing has to be restarted, and nothing you already paid to generate is thrown away. What this means for you in practice:
- Walk away anytime. Closing the browser changes nothing. Your progress is held safely; pick up right where you stopped.
- A failure is recoverable, not lost. If a phase hits a snag, the production pauses there with a clear Retry — you never lose the run or the work before it.
- Hands-off when you want it. Trust a repeatable series? Auto-Approve clears the gates for you automatically, so a validated workflow runs end to end without you babysitting it.
Auto-Approve didn't weaken the gates — it proved them
A reasonable objection: if you let users turn the gates off with Auto-Approve, were the gates ever load-bearing? They were. Auto-Approve is for the run you've already validated — a weekly series on a brand preset you've watched succeed ten times. The gate still exists; you've simply pre-decided the answer.
What the gates buy you on a new kind of production — a new topic, a new brand, a new format — is still there the moment you want it. Auto-Approve is a trust setting, not a pipeline shortcut.
Three things we tried that didn't work
One review screen at the end. Reviewers approved videos that were 90% right because re-running was the only alternative. The gates have to be where the cheap fix is, not where the finished artifact is.
Letting phases overlap to save time. Starting asset generation before the plan was approved meant approving the plan sometimes invalidated work already in flight. The phases are sequential on purpose; the parallelism lives inside a phase (all of Phase 2's assets generate concurrently), never across a gate.
Auto-retrying failed phases silently. A silent retry that also fails just burns tokens and time. A failed phase now surfaces immediately with the error and a manual Retry, so a misconfigured run gets fixed instead of looped.
The one-sentence version: five phases exist because a review gate is only worth having where the judgement is cheap and the mistake is expensive — and there happen to be exactly five such places between a topic and a published video.
Further reading
- How It Works — the five phases walked through end to end.
- Phase 2–5 Reviews — what to check at each gate.
- Auto-Approve Mode — when to pre-decide the gates.
- Multi-language fan-out, explained — how one approved plan becomes 24 videos.
See the five gates for yourself
Start a free account and run a topic through the pipeline — approve the storyboard, the assets, and the render, then walk away with a finished, publish-ready video. No clip-roulette, no credit card.
Get Started Free