Is your monthly video retainer actually running like a system?
The client doesn't want one campaign film every quarter anymore. They want 8 short videos, 2 internal versions, 1 longer episode, captions, thumbnails, a publishing calendar, and a short performance recap at the end of the month. On the sales call, that sounds like stable recurring revenue. Six weeks later, the producer realizes the team isn't running a retainer. It is running a pile of small projects with no breathing room between them.
The problem usually isn't the editor's skill or the shoot complexity. The problem is the operating model. One-off projects have a pulse: brief, production, delivery, pause. Monthly video retainers have a cycle: planning, batch shooting, steady editing, review, delivery, reporting, then the next cycle. If a studio manages that cycle like a one-off job, margin disappears into status checks, late assets, and "small" extra versions.
What usually goes wrong
- The scope is too broad - "10 videos per month" doesn't define length, format, polish level, platform versions, or raw footage complexity.
- The calendar depends on the client - the studio reserves editing time, but assets arrive across the whole month, so every deadline gets compressed into the final week.
- The shoot isn't tied to a content plan - the crew captures "a lot of options", then post-production discovers there are no clean hooks, vertical takes, or thumbnail frames.
- Revisions are handled one file at a time - every video becomes its own approval thread instead of moving through planned review windows.
- Publishing versions multiply quietly - one approved cut becomes 16:9, 9:16, 1:1, a shorter teaser, a no-caption version, and a file for a sales deck.
That kind of retainer looks busy. Tasks move. Files appear. The client writes often. But busy doesn't mean controlled. A studio needs to know how many hours and decisions each monthly cycle consumes, and whether the package still leaves room for profit.
How to build a working monthly cycle
1. Define the delivery unit
Don't start with price or volume. Start by defining what counts as one deliverable. For recurring video, that definition needs to be concrete: video type, length range, aspect ratio, polish level, export count, revision rounds, and ownership of inputs.
For example, "1 video" might mean a vertical video up to 60 seconds with basic color correction, captions, one approved music track, one 9:16 export, and 2 revision rounds. Anything outside that definition is not forbidden. It is simply a separate line in the monthly plan.
What to do: create a delivery-unit menu: short vertical video, long episode, social cutdown from a long edit, thumbnail, additional export format, rush version. Each unit should have expected hours, a deadline pattern, and a review rule.
2. Split the month into production windows
A retainer should not become an open inbox where the client drops tasks whenever they remember them. The monthly cycle needs windows: planning, preparation, shooting, editing, review, final delivery, and reporting.
A simple calendar for a small studio might look like this:
- Days 1-3 - approve topics, formats, and priorities.
- Days 4-7 - scripts, shot list, props, locations, and talent prep.
- Days 8-10 - batch shoot or asset collection.
- Days 11-20 - first editing pass and rough-cut review.
- Days 21-25 - final revisions, platform versions, captions, delivery checks.
- Days 26-30 - final handoff, publishing plan, recap, next-cycle prep.
The calendar does not need to be rigid. It needs to be shared. If raw footage arrives on day 18 instead of day 8, the problem is no longer "the editor is late." It is a missed input condition.
3. Tie shoot days to a content matrix
Monthly video retainers promise consistency, but consistency can't be captured by accident. The team needs a content matrix: themes, goals, formats, platforms, recurring talent, visual patterns, and required shots.
For one shoot day, a basic matrix might include:
- 4 expert clips with one speaker;
- 3 product demonstrations;
- 2 answers to common customer questions;
- 1 hiring or culture video;
- 10-15 b-roll moments for covers, hooks, and transitions.
Without that matrix, the team may return from the shoot with plenty of footage but not enough editorial decisions. The editor then becomes the writer, producer, and rescue team at the same time.
What to do: check editing needs before the shoot. Do you need vertical takes? Is there clean audio for every point? Are there enough cutaways? What will appear in the first frame of each video?
4. Keep revisions in batches
The biggest retainer trap is continuous feedback. The client watches one video in the morning, 2 more at night, 3 on Friday, then returns to the first after another stakeholder comments. The team switches context all day even though the client sees it as "just a few notes."
Batch review protects focus. Instead of reviewing each file separately, set 2 feedback windows: one for the rough batch and one for the final batch. Inside each window, the client collects notes from every stakeholder. The producer turns those notes into one decision list.
This is not red tape. It protects editing hours from constant context switching. If the client needs an urgent file outside the review window, it gets its own slot, its own deadline, and a price built from the same video editing rate math as the rest of the package.
5. Set limits for versions and formats
In 2026, almost every video lives on more than one platform. But platform adaptation is not a free export button. Sometimes the team has to move captions, reframe the shot, shorten the opening, change the audio mix, or rebuild the end screen.
The retainer should define:
- the master format;
- how many extra formats are included each month;
- what counts as adaptation versus a new edit;
- how rush versions are priced;
- where the final delivery list lives.
A PMS like Basalt for studio teams gives producers one place to track statuses, files, revisions, and deadlines, and the number of people you need inside the cycle usually decides which plan fits. But the rule has to exist before the tool helps: a version without a clear owner and purpose is not a finished deliverable.
6. Make invisible work visible
The client sees the finished videos. They do not see asset sorting, audio checks, duplicate takes, subtitle cleanup, exports, uploads, file naming, thumbnail checks, and technical fixes. If that work stays invisible, the retainer starts to look expensive even when the studio is undercharging.
The monthly recap does not need to be long. It can include:
- how many videos were delivered;
- how many extra formats were prepared;
- how many hours went into asset intake, editing, revisions, and final delivery;
- which delays came from late inputs or changed briefs;
- what should change in the next cycle.
This report helps the studio too. It shows where margin is being lost, not in a vague bucket called "editing", but in specific parts of the production cycle.
A minimum process for next month
If the retainer is already running, don't try to rewrite the whole agreement in one day. Start with a manageable minimum.
Agree on 3 documents with the client: a monthly video plan, asset intake rules, and revision rules. The plan should list each video, format, deadline, and client-side owner. The asset rules should define dates, folder structure, audio requirements, graphics, and brand files. The revision rules should define 2 feedback windows and the person responsible for collecting final notes.
After the month ends, avoid arguing from memory. Compare plan against reality: what shipped, what moved, what was added, and which hours were invisible. From there, the studio can expand the package, adjust price, or reduce the promised volume.
Checklist: is your video retainer ready to run?
- Every delivery unit has a length range, format, polish level, and export count.
- The month is split into planning, shooting, editing, revision, and delivery windows.
- There is a cutoff date after which late assets roll into the next cycle.
- Shoot days follow a content matrix, not a loose idea list.
- Revisions are collected in batches instead of arriving separately for every file.
- Extra versions and platform adaptations are counted separately.
- The client sees a short production recap at the end of the month.
- The team knows where the retainer earns margin and where it leaks hours.
Frequently Asked Questions
What is a monthly video retainer?
It is a working agreement where a studio ships an agreed package of videos every month through a repeating cycle: planning, shooting, editing, review, delivery, and a recap. What separates it from one-off work is rhythm rather than size, because there is no pause between jobs and the whole month has to be managed as a process. It only stays healthy when scope, deadlines, and revision rules are defined before the first cycle starts.
How many videos per month should a retainer include?
Start with the delivery unit instead of the number: video type, length range, aspect ratio, polish level, export count, and revision rounds. Once that unit is defined, volume can be counted in team hours rather than in a vague promise of ten videos a month. Compare those hours against real editing and shoot-day capacity, and leave room for asset intake and final delivery checks.
What should a studio do when a client asks for more videos than the package includes?
Do not refuse it, price it as a separate line in the monthly plan with its own hours, deadline, and cost. Extra formats, rush versions, and platform adaptations are counted apart from the master format, otherwise the package quietly grows while the fee stays the same. If the request arrives outside a review window, it gets its own slot in the calendar instead of a place in the current batch.
How do you keep a video retainer profitable?
Margin usually leaks outside the edit itself, into asset sorting, audio checks, exports, file naming, and constant context switching between notes. Collect revisions in two feedback windows, set a cutoff date after which late assets roll into the next cycle, and track hours by production stage. At the end of the month compare the plan against what actually shipped, then adjust price, scope, or package size from that data.
How do you set up a contract for monthly video production?
The practical minimum is three documents agreed before the first cycle: a monthly video plan, asset intake rules, and revision rules. The plan lists every video with its format, deadline, and client-side owner; the intake rules cover delivery dates, folder structure, audio requirements, graphics, and brand files; the revision rules define the two feedback windows and the person who collects final notes. With those in place, disputes get settled against a document instead of against memory.
Related Reading
- How to price video editing work - so the monthly package is built from real hours instead of gut feel
- Editor capacity planning - how to spread team capacity across cycles instead of into the last week
- A video production brief template - the input conditions that keep a monthly plan from drifting
Summary
Monthly video production can be one of the healthiest offers for a studio: predictable workload, longer client relationships, and fewer sales resets. But a retainer only works when it has rhythm, boundaries, and visible labor.
Start with one step: define the delivery unit for the most common video in your monthly package. If the team and the client understand what one video includes, the next conversation about deadlines, revisions, and price becomes much calmer.