The Frankenstein Shot: What's Left When AI Makes the Whole Take

A two-minute brand film shot with an AI-agent pipeline recently ran three days from script to finished cut, against roughly two months for the traditional equivalent shoot, according to invideo's own documented production case. A ninety-second horror short pulled around four hundred separate video generations before it was done. Numbers like that used to be the whole story: AI got fast enough to make an entire scene, so why would you need a person in the room. The more interesting number is the other one buried in that same case study: more than 40 percent of the finished shots in one documented project weren't a single generation at all. They were stitched together from the strongest few seconds of several different attempts, a practice invideo's own team describes bluntly: "Prompt, eight tries, Frankenstein the keepers."

That detail says more about what's actually happening than the speed claims do. A model that can render a whole scene on command doesn't remove the need for a person making decisions, it just moves all those decisions earlier and makes them faster to act on. The workflow behind these AI-made shorts isn't one person typing a single magic sentence and getting a finished film back. It's a full crew of separate roles, a producer role holding the script and characters, a storyboard role visualizing shots before anything gets generated, a cinematography role taking direction like "hold the shot longer" or "track the actor through the doorway," a costume role, a production design role, each one scoped to its own job the way a real set is. The AI executes inside each of those roles. The structure of the roles themselves is still the same structure a film crew has always had, because someone still has to decide what the shot should look like before anything generates it.

The clearest evidence that judgment, not generation, is the bottleneck is what happens after the footage exists. Documented productions build in a step where the assembled rough cut gets sent back for a critique pass specifically looking for pacing problems, sound issues, and moments where the emotional register is off, the kind of thing invideo's own workflow notes call the step most commonly skipped and the one that catches errors human editors miss. That's a genuinely strange sentence to sit with: an automated pass flagging what a trained editor overlooked. It doesn't mean the AI has better taste. It means taste is being applied at a different point in the process now, on the assembled whole rather than shot by shot, and someone still has to be the one who decides whether the note is right and acts on it.

So what is the creator actually making, if not the pixels. They're making the same thing a director has always made: the specific sequence of choices that turns raw coverage into a scene that lands the way it's supposed to. Which take gets used, which two generations get spliced together because neither one alone had the whole shot, which note from the critique pass actually matters and which one gets ignored, all of it decided by someone rather than generated by anything. None of that shows up if you only look at "who generated the footage," and all of it is the actual difference between a finished piece of work and four hundred generations sitting in a folder. The model can make the scene. It still can't decide, on its own, which version of the scene was worth keeping.