Why a two person video team cannot serve a company sized video queue
A two person video team is the standard staffing model at companies with thousands of employees. It is what happens when video grows from a channel into the default format while headcount stays flat. The team ends up declining real requests, and the declined ones tend to sit closest to revenue.
Why does a small video team decline sales requests first?
Sales requests arrive in volume, carry no ceremony, and repeat forever. One deal wants a tailored demo cut, then thirty do. A two person team saying yes to the first is committing to the next twenty nine, and they know it while they are answering.
So the team declines the category outright. A video lead at an employee recognition platform described the decision in exactly those terms:
"We've said no, a lot, to sales because it's kind of like opening a can of worms."
That is a rational call given how the work was routed. Every sales request is bespoke by default, so saying yes once creates an obligation with no ceiling. The problem is that the category being refused is the one with the clearest line to pipeline.
What is actually scarce on a two person video team?
Judgment, not editing capacity. Those two people are the only ones in the building who know what good looks like inside your brand. Every hour they spend resizing, captioning, and swapping a logo spends that judgment on work that needs none of it.
Capsule's own figure for this is that creative teams lose roughly 30% of their time to tedious video tasks. On a two person team that is most of one person, spent on work no one would staff a role for if it were written down as a job description.
| Request type | Needs creative judgment | Right home |
|---|---|---|
| Brand film, launch hero | Yes, entirely | The video team |
| New template or motion system change | Yes | The video team |
| Resize, caption, localized cut, logo swap | No | A locked template, self served |
| Sales demo cut, enablement snippet | No, once the shape is set | The requesting team |
Which video requests should you hand off first?
Start with the request type that arrives most often and varies least. Usually that is sales enablement cuts, product demo snippets, or social resizes of an existing hero video. Build one template, expose four or five fields, and let the requesting team serve itself.
The sequencing matters. Teams that try to template everything at once spend three months in setup and lose the momentum that funded the project. One template, one requesting team, one month, then copy the pattern. Our sales use case shows one requesting team working from a single template.
Does handing off video work shrink the creative team?
It has gone the other way at every company we have watched try it. A team that owns the system governs every video the company ships, rather than the fraction it personally cut, which is more scope rather than less.
The role changes from producing assets to defining what good looks like, building the templates that encode it, and sampling output to confirm the system still holds. That is a more senior job than queue management, and it is usually easier to defend at budget time.
How long does the first handoff take?
Weeks rather than quarters, assuming the motion system already exists. The template build is the real work and it draws on After Effects files your team has already made.
Then plan for onboarding rather than a link to a help doc. Video is a new skill for most of the people receiving it, and the difference between a program that sticks and one that dies in week two is whether somebody sat with the first cohort. Capsule runs that session in under an hour with a dedicated CSM, which is a deliberate design choice rather than a support tier.
FAQ
How many people should an enterprise video team have?
For a queue model, more than you can afford at almost any enterprise scale. For a system model, two is often enough, because the team is building and governing templates rather than producing every asset.
How do you say no to video requests without blocking the business?
Stop saying no and start routing. Publish which request categories are self serve, give those teams a locked template, and reserve the queue for work that genuinely needs creative judgment.
What happens to quality when non-editors make video?
Quality moves into the template. A non-editor working inside a locked motion system cannot ship something off brand, because the type, motion, color, and layout decisions were made once by the people qualified to make them.
Which video request should a small team template first?
Whichever arrives most often and varies least. Frequency times sameness is the payback formula, and it usually points at sales enablement cuts or social resizes.