Most in-house video teams start the same way. The company needs more video every quarter, each piece goes to an outside production company at project rates, and each one opens with a week of briefing people who have never used the product.
Eventually someone in marketing looks at a year of invoices and asks whether it would make more sense to hire. Sometimes it does. This guide is for the marketing or communications lead making that call.
In short
- An internal team pays off when most of the company’s videos follow a repeatable format and the list keeps growing.
- Hire a producer-editor first, and rent gear until you know what you keep renting.
- Set up one door for requests and turn each accepted one into a task with a brief and two dates.
- Agree on one approval order for every video, with one person giving the final approval.
- Report once a month, one page per department.
When in-house beats a production company
An internal team pays off when there’s a steady flow of videos that look like each other: onboarding and training modules, product demos, cutdowns for social, event recaps, the CEO’s quarterly message.
The same people make them every month, so they learn the brand, the products and which executive needs three takes. A production company has to be briefed on all of that every time, and a thin brief is where a lot of rework starts.
Speed matters too. When sales wants a 30-second cut of yesterday’s webinar by tomorrow, someone down the hall can start today. An outside company would send a quote first.
It doesn’t pay off when the company makes a handful of large pieces a year, like a brand film or a TV spot, which need a director, crew and gear a small team can’t keep busy the rest of the year.
Demand that comes in bursts, a quiet quarter and then six videos in one week, is hard on an internal team too.
To check, list every video the company made in the last twelve months and mark the ones that followed a repeatable format. If most did and the list keeps growing, an internal team will probably cost less and turn work around faster. If the list is short and full of one-offs, keep the production company.
Hire a producer-editor before you buy gear
Look for someone who edits well and can also run the process: write the brief with a requester, plan a simple shoot, keep the calendar of what’s due and push back on a deadline that can’t be met. The job is half editing and half producing.
A brilliant camera operator who has never handled requests will spend the first months answering messages from five departments, all marked urgent. Most of the early trouble is process. Requests arrive in chat, nobody writes the deadline down and three people believe they approve the final cut.
Gear can wait a few weeks. Rent for the first jobs and buy what you keep renting. For most teams that’s a camera body with two or three lenses, wireless lavs and a shotgun mic, a couple of LED panels, an edit workstation with fast storage and the software licenses.
Put backup storage for the footage in the first budget too.
Roles as the team grows
After the first hire, add people where the queue backs up. An order that works for a lot of companies:
| Next hire | When you notice |
|---|---|
| Second editor | Requests wait more than a week before anyone starts them |
| Motion designer | Most requests need animation, product screens or charts |
| Dedicated producer | The editors spend more time in meetings and email than cutting |
| Camera operator | There’s a shoot almost every week |
Whoever leads the team should own the priority list. When two directors both call their video urgent, someone has to decide which goes first, and it shouldn’t be the editor.
Freelancers and agencies stay in the picture. Bring in freelance editors for peaks, specialists for drone work or 3D, and a production company for the big brand pieces, with the internal team producing those jobs. Our guide to hiring a freelance video editor covers the paid test and what to agree in writing.
One door for requests
Set up one door, a short form or a shared page, and make it the rule that a video starts only once the request is filled in. Without it, requests reach an in-house team in chat messages, at the end of meetings and in emails straight to the editor.
The form asks:
- what the video is for and who will watch it
- where it runs and how long it should be
- the deadline and what happens on that date (an event, a launch, a board meeting)
- who approves it
- what material must go in
The producer then spends fifteen minutes with the requester turning it into a brief. The video brief template fits that conversation on one page.
Each accepted request becomes a task with the brief, the requester and two dates, the one promised to the department and an internal one a few days earlier.
Publish rough turnaround times by type, say a few working days for a social cut and a few weeks for anything with a shoot, so departments plan ahead instead of negotiating every deadline.
Put every task on one board, with a few columns for where the work is and a marker for who each video is waiting on, be it the requester, legal or your own review. The kanban guide covers the columns.
Who approves inside the company
Agree on the order once and use it for every video. An internal video draws more opinions than most client jobs. The requester’s boss, brand, legal and the executive on camera all have a view, and without an agreed order every round collects contradicting notes from all of them.
- The video lead watches first, before anyone outside the team sees a cut.
- Brand and legal review the near-final version, each within their own area, and get a fixed number of days to answer.
- The requester gives the final approval, and only one person per video holds that role. Write the name in the brief.
When two reviewers disagree, take the conflict to the person who approves instead of settling it in the edit. Our post on conflicting feedback from multiple stakeholders has a message you can adapt.
Measuring what the team delivers
Sooner or later leadership asks what the team costs and what it produces. Answer once a month with one page per department: videos and minutes delivered, average time from request to delivery, rounds per video and what’s waiting on whom.
The monthly client report template works as written, with the department in the client’s place.
Track hours by department as well. They show who uses the team most, and you’ll need them when someone compares the team’s cost with the invoices it replaced.
How this works in RecReview
An in-house team uses RecReview the way a production company does, with each department in the place of a client. A client needs only a name and a short code.
Set up Marketing, HR and Sales as clients, and each gets its own video codes (MKT_014), contacts and a portal where the people who asked see the videos you’ve sent them. The portal can open with the link alone, ask for a name and email, or require a code sent by email or a Google sign-in.
Every plan includes unlimited users. The video team joins as Admin, Editor or Member, and freelancers with the Freelancer role. By default only owners, admins and editors approve internally, send a version to the requester or request changes, and owners and admins can change that.
Requesters and their reviewers, like brand and legal, are the department’s contacts and don’t need an account. Turn on contact roles and only the department’s Managers can approve, while Reviewers comment on the frame and request changes.
When you create the workspace, you pick a starting workflow: Video Production, Agency, a basic set of automations or none.
The Agency preset adds a Briefing subtask to every new task, then Creation, Internal Approval and Client Approval as each one is checked off, and an approval moves the task to Delivered. Admins can add their own waiting-on markers, such as Legal.
Each department’s portal has a Metrics tab with deliveries per month, minutes delivered and average review time, and your own Metrics break hours down by client. On the paid Studio plan, your request form can create tasks through the public API. More on the workflow automation page.
