5 Things Video Pros Should Always Invoice (But Usually Eat)

I have watched talented editors quietly go broke. Not because their work was bad. Because they billed for the final export and gave away everything that surrounded it for free.

Here is the contrarian take: the export is the cheapest part of your job. The expensive part is the back and forth, the revisions, the version chaos, the chasing of approvals, the late night re-renders because a client changed their mind on Slack at 11pm. That is where your hours actually go. And that is exactly the stuff most video pros never put on an invoice.

So let me fix that. Here are five things you should always invoice for, and how to make each one easy to defend with a paper trail.

1. Revision rounds beyond the agreed scope

Every project should include a fixed number of revision rounds. Two is normal. Three if the client is paying well. After that, you bill per round, and you say so in writing before you start.

The problem is not setting the limit. The problem is proving when the limit was hit. If feedback arrives as a wall of text in an email, a few voice notes, and a screenshot with a red circle drawn in some phone app, you cannot honestly say which round you are on. The client will swear it was all one note. You will swear it was three. Nobody wins that argument.

This is where structured review changes the math. When comments are pinned to the exact frame and grouped by round, a revision round becomes a countable thing. You can point at it. PlayPause gives you frame-accurate comments with drawing and @mentions, and version stacks so each round sits on top of the last. When you invoice for round four, you have round four sitting right there in the timeline. The conversation ends before it starts.

• State the included revision count in your contract
• Make every change request go through one review link
• Count rounds by version, not by message
• Bill the overage at a flat per-round rate

2. Scope creep disguised as small asks

"Can you just" is the most expensive phrase in this business. Can you just add lower thirds. Can you just make a vertical cut. Can you just swap the music. None of those are small. Each one is a new deliverable wearing a friendly costume.

The reason editors eat these is guilt. The ask feels too tiny to invoice without looking petty. So you do ten of them across a project and you have donated a full day of work.

The move is to log every request the moment it lands, in a place the client can see. When a new ask shows up as a comment or a fresh upload in a shared workspace, it has a timestamp and an author. At the end of the project you are not arguing from memory. You are reading back a list. "These eight items were added after sign off. Here they are." Centralized assets and a single source of truth turn a vibe into evidence.

3. Versioning and project management time

Here is a cost nobody itemizes: keeping the project organized. Naming files. Tracking which cut is current. Making sure the client is reviewing v7 and not the v4 they bookmarked last week. Hunting for the approved version when the client suddenly needs it for a deck.

That is real labor and it scales with project size. On a one minute promo it is trivial. On a six episode series with three stakeholders, it is hours a week. Those hours belong on the invoice, either as a management line or baked into your rate with eyes open.

The smarter play is to make the overhead small enough that you barely spend the time. Version stacks plus side-by-side compare mean the latest cut is always obvious and the old one is one click away for reference. No "FINAL_v3_REALfinal" filenames. No client reviewing the wrong export. You either bill for the chaos or you remove it. Removing it is better for everyone, and it lets you charge for outcomes instead of cleanup.

4. Secure delivery and access control

When you hand off a film, you are also handing off a security decision. Who can see it. For how long. Can they download it. Can they pass the link to people who never signed an NDA. Most editors deliver a raw WeTransfer or Google Drive link and never think about it again. That is fine until it is not.

For anything under embargo, anything with a brand's unreleased product, anything a competitor would love to see early, controlled delivery is a deliverable in itself. Password protection, link expiry, domain restriction, and watermarking are not luxuries on those jobs. They are the reason the client can sleep. And a deliverable that protects the client is something you can absolutely put a number on.

File transfer tools do not do this. Email, WeTransfer, Google Drive, and Dropbox move bytes from A to B. They are not review and approval tools, and they were never built to control who watches your work or to prove who signed off. PlayPause gives you secure share links with passwords, expiry, domain restriction, and watermarking, plus viewer analytics so you can see the film was actually opened before someone claims they never got it.

5. Approvals and sign off as a paid milestone

The most under-invoiced moment in any project is the approval itself. Chasing sign off is work. You write the follow up email. You wait. You write the second one. The client goes quiet, the timeline slips, and somehow that delay becomes your problem and your unpaid time.

Approval should be a milestone with money attached to it, and it should be unambiguous. Not "looks good" buried in a thread. A real, recorded yes. When you tie a payment trigger to a clean approval lock, two good things happen. The client has a reason to actually review the cut, and you have a defensible record of when the work was accepted.

Here is the scenario. You deliver the final. The client opens the review link, leaves a couple of frame-accurate notes, you handle them, push a new version, and the client hits approve. The approval is locked and timestamped. Three weeks later they ask for "one more tiny change." You are not annoyed and you are not guilty. The project was approved on a specific date, that is on record, and this is new work at your new-work rate. The lock did the awkward part for you.

The bottom line

Undercharging is rarely a pricing problem. It is a documentation problem. You are not too cheap. You just have no record of the work that happens around the edit, so you give it away by default.

Fix the record and the invoice fixes itself. Pin feedback to frames so revision rounds are countable. Log every "can you just" the moment it lands. Make versioning effortless so you are charging for the film, not for filing. Deliver securely so protection becomes a billable line. Lock approvals so sign off is a dated, paid milestone instead of a guilt trip.

One more thing on the tool you do this in. Frame.io can run the same playbook, but it charges per seat, so every client, reviewer, and freelancer you add pushes the bill up right when you are trying to protect your margin. PlayPause is flat per workspace, not per seat: Free at 0 dollars, Creator at 9 dollars a month, Agency at 15 dollars a month, Enterprise at 27 dollars a month. Invite the whole client team and your collaborators without watching a meter. Frame-accurate comments, version stacks, approval locks, secure share links, Camera-to-Cloud proxies, and Premiere Pro and After Effects panels are all in the box.

Start free, run your next project through it, and bill for everything you actually do. Try PlayPause free and stop eating the work that should be on the invoice.