How many free versions are you really delivering with one video?
The client approved one hero cut. Then the follow-up requests arrive: a 9:16 version, a 4:5 version, a 15-second cut, a 6-second cut, a version with burned-in captions, a clean version without text, a variant with a different end card, and one more export for internal use. None of those requests sounds dramatic on its own.
But together they stop being “a few quick exports.” They become a deliverables system with its own edit decisions, approvals, file management, and deadline pressure. If a studio treats that work like a small add-on, it usually gives away editor time, producer time, and margin without noticing until the project is already closed.
This problem matters more now because multi-format delivery is no longer an exception. Clients expect vertical and square versions as part of normal campaign production. Marketing teams want more versions for testing. Reframing tools make extra outputs sound easy. And once platforms reward more short-form placement, “can we get 3 more cuts?” becomes a standard ask instead of a special case.
So the real issue is not technical. It is operational. More versions are easy to request, but they are still expensive to coordinate, review, and finish.
Why cutdowns damage post-production economics
- The workload hides inside the phrase “just one more version.” A new format usually means reframing, moving graphics, checking captions, exporting, uploading, and another round of review.
- Feedback starts branching. The client approves the landscape master, then changes the first screen only in vertical, then wants that same change back in the main version.
- Finishing work gets underestimated. Safe zones, subtitles, language swaps, end cards, legal text, naming conventions, thumbnails, and delivery packaging look small individually and expensive in total.
That is why these projects often feel confusing rather than disastrous. Nothing explodes. The studio just notices that the job took more effort than expected, the editor stayed late, the producer handled more admin than planned, and the final margin is thinner than it looked on paper.
That means the fix is not heroics. The fix is a workflow where adaptations are treated as production work, not as a free tail after the main edit.
1. Sell a deliverables matrix, not “one video”
If the estimate only says “edit one video,” the studio creates the ambiguity itself. The client sees one thing being purchased and assumes the variations live inside that scope. The team may feel differently, but by then it is already negotiating from a weak position.
A better model is simple. Define the master deliverable first, then list the derivative families separately. For example:
- 60-second master in 16:9
- 30-second cutdown
- 15-second cutdown
- 9:16 vertical version
- 1:1 or 4:5 social version
- captioned version
- clean version without text
- alternate end card version
This is not just a pricing tool. It helps the team see hidden workload before the edit starts. A project with 2 durations, 2 aspect ratios, and 2 language versions is not “a few files.” It is multiple delivery branches with separate review and finishing needs.
What to do: add a dedicated “final deliverables” section to every estimate and kickoff. Do not list only export formats. List every version the team will actually cut, check, approve, and hand over.
2. Approve the master first, then build the adaptations
Studios often try to move faster by sending everything at once. As soon as there is a decent first cut, they export the landscape version, the short version, and the vertical version together. It feels efficient.
Usually it creates a mess. The client starts discussing 3 files at the same time. They like the pacing in one, the first shot in another, and the text treatment in a third. Instead of one decision path, the team now has three parallel conversations.
The editor pays the price first. What is the approved logic of the piece now? The scene order? The opening line? The rhythm? The end card? Once that gets fuzzy, every master change ripples into every derivative version.
The safer sequence is:
- Approve the master for structure, message, and pacing.
- Freeze the core creative decisions.
- Build the cutdowns and platform formats after that.
- Define which adaptation-level tweaks are allowed without reopening the master.
This does not slow the project down. It protects the studio from free re-editing. One approved logic first, derivative versions second is usually the cheapest path in post-production.
3. Separate creative revisions from adaptation revisions
Not every note on a short version is a “small tweak.” If the client asks the 9:16 cut to open on a different promise, remove one argument, rewrite the text card, and land on a different CTA, that is not formatting. That is a new editorial task.
When a studio does not separate revision types, the pattern is predictable:
- the producer promises a quick update;
- the editor ends up rebuilding the cut;
- the client still believes it falls inside the original package.
It helps to define 2 categories upfront.
Adaptation revisions
These do not change the core story:
- moving titles into safe zones;
- reframing for 9:16;
- tightening pauses without changing meaning;
- shifting logo placement;
- swapping an end card in an approved template.
Creative revisions
These change the message or structure:
- a new hook;
- reordered scenes;
- a different core claim;
- rewritten title cards;
- a new offer or CTA.
What to do: put this distinction into the project rules before the first review round. Then the producer has a clean, calm sentence available when needed: “That note changes the editorial direction, so we need to scope it separately.” Without that rule, even strong teams slide into free extra work.
4. Assign one version owner and strict naming rules
Once version count grows, studios often try to solve the problem with attention and goodwill. Everyone promises to be more careful. That works until the first late-night deadline.
You need one owner for the deliverables branch. In a small studio that is usually the producer. In a larger team it may be a post-production coordinator. Their job is not to “help where needed.” Their job is to maintain one clear register:
- which versions belong to the project;
- which versions are in review;
- which ones are approved;
- where the current file lives;
- which comment belongs to which build.
Naming rules matter just as much. If the team still lives in final, final2, and final_final_v7, the cost of confusion is already being paid. A filename should answer 4 questions: project, format, duration, and status. For example: brand-launch_9x16_15s_v03-review.
A system like Basalt makes it easier to keep statuses, versions, comments, and final deliverables attached to one project instead of rebuilding context from folders and chat threads. But the rule is bigger than any software: every version needs an owner and a readable name.
5. Budget by version families, not leftover time
The most expensive sentence in this workflow is: “Let’s finish the master first and then see how long the rest takes.” In practice, that means the rest gets priced from whatever time and patience remain.
A better method is to budget by families of work:
- aspect ratio adaptation;
- duration adaptation;
- language adaptation;
- graphics or end card variation;
- delivery packaging and upload.
This helps both sides. The studio sees margin before production starts. The client sees what creates cost and where volume can be reduced. The conversation stops being about “a couple extra exports” and becomes a clear discussion about additional outputs.
If you do not have reliable benchmarks yet, start with your last 5 projects that included cutdowns or verticals. Review them and count:
- how many distinct files the team actually built;
- how many review rounds each branch required;
- how many hours went into captions, exports, uploads, and communication;
- where unpaid work appeared.
That exercise usually reveals the real pattern fast. Margin is rarely lost in one dramatic step. It disappears through many small actions that nobody scoped properly.
Minimum viable process for this week
If you are not ready to redesign your whole quoting model, start smaller.
For the next project, do only 3 things:
- lock the master deliverable and every derivative file before editing starts;
- stop parallel approval of the master and the adaptations;
- tag every note as either creative or adaptation-level.
That alone is enough to show where the project used to lose control. After 2-3 jobs, you will have your own timing data for cutdowns. That is what makes future estimates and staffing decisions more accurate.
Checklist: are your cutdowns actually under control?
- Every project has a written list of final deliverables before editing starts
- The master version is approved separately from short and vertical adaptations
- The team distinguishes creative revisions from adaptation revisions
- One person owns the deliverables branch
- File names show format, duration, and status
- Adaptations are priced as separate work blocks
- The producer can say which version is current in under a minute
- The client knows which versions are included and which are extra
If 3 or more boxes stay unchecked, the issue is no longer team discipline. The studio is producing many versions while managing them like a single edit.
Summary
Social cutdowns do not kill margin on their own. Margin disappears when the studio keeps treating them like minor cleanup. As long as short versions, verticals, and extra end cards live in the “we’ll just do that quickly” zone, teams will keep giving away real labor.
The good news is that this does not require a massive overhaul. Start with one move: build a full deliverables matrix before the next first cut goes out. That step alone will show how many “small versions” your studio has been shipping for free.