Get a Free Consultation →
The predictable enterprise spike calendar
Most spikes are not surprises. The same four windows show up in almost every enterprise calendar, and they can be planned for instead of fought.
Q1 (January to February): Sales kickoff and year-plan launch
Strategy videos, leadership intros, regional summaries, sales enablement updates. Typical Q1 spike: 2 to 3x baseline for 4 to 6 weeks. Most enterprise programs that handle Q1 well start scoping the work in November of the previous year.
Q2 (April to May): Mid-year town halls and reviews
CEO updates, progress recaps against the annual plan, employee comms around any reorganization, mid-year recognition pieces. Typical Q2 spike: 1.5 to 2x baseline for 3 to 4 weeks. Lower amplitude than Q1 but it cuts into normal work that does not stop.
Q3 (June to August): Conference and event season
Keynotes, partner summits, customer events, recap reels. For organizations that run a flagship annual event, this is the biggest spike of the year. Typical Q3 spike: 3 to 5x baseline for 4 to 8 weeks, with heavy concentration around the event itself.
Q4 (October to December): Product launches and end-of-year
Launch reels, customer stories, year-in-review pieces, EOY thank-yous, results videos for board and investor audiences. Typical Q4 spike: 2 to 4x baseline for 6 to 10 weeks. Less predictable than the other three because launches slip.
What "elastic capacity" actually looks like in practice
The mechanics matter. Subscription production with elastic capacity is not a generic "burst at any volume" promise; it is a specific contract structure that flexes within a defined range.
The annual subscription is sized to your expected annual output, which is roughly the area under your demand curve across 12 months. In baseline months you use a fraction of the subscription capacity. In spike months you use more than the per-month average, drawing forward against capacity that was set aside earlier. The annual total stays roughly the same; the monthly consumption flexes.
For unplanned spikes that exceed the annual envelope, burst capacity is priced per finished video at the appropriate tier rate. There is no overage shock as long as the annual sizing is right; the partner absorbs reasonable variability inside the agreement. Heavy unplanned use beyond the agreement is scoped during the QBR rather than billed by surprise.
What an in-house team is for, and what a partner is for
The clearest way to think about the split: the in-house team owns the work that compounds over time. Brand decisions. Stakeholder relationships. Creative direction. Strategic comms. The work where institutional knowledge matters more than capacity.
The partner owns the work that scales linearly with volume. Editing, post-production, multilingual versions, social cutdowns, motion graphics, captioning, recap edits. The work where reliability and brand consistency matter more than artistic signature, and where capacity is the constraint.
Spikes are almost always volume problems, not strategy problems. Conference season needs 30 recap videos cut to brand inside two weeks. That is editing capacity, not creative direction. Q4 launches need 12 product cutdowns in 5 languages each. That is multilingual production, not brand strategy. The in-house team should not be the bottleneck on either.
How burst capacity is priced
Three approaches Shootsta uses depending on the customer's predictability of demand.
Fixed annual tier with flex
For programs with a known annual envelope (typical 24, 36 or 60+ videos a year), the subscription price is fixed and capacity flexes within the year. Spike months use more capacity, baseline months use less. This is the cheapest model when annual demand is reasonably predictable.
Baseline tier plus burst pricing
For programs with high variability or where leadership wants a smaller annual commitment, a smaller baseline tier covers normal months and burst capacity is priced per finished video above that. Burst rates are at standard tier pricing, not premium. This model works for organizations early in their video program when annual demand is genuinely uncertain.
Event-based burst packages
For predictable annual events (the conference, the all-hands, the launch), a scoped burst package handles the event window specifically. Crew, editors, on-site capacity for same-day cuts, multilingual versions, social distribution edits. Priced as a fixed event fee. Useful for programs that mostly run small in-house and need a specific reinforcement once or twice a year.
Frequently asked questions
What if our spike is bigger than 5x baseline?
Most spikes that look like 10x are actually 3x to 5x when you map them across the full spike window instead of the worst day. For genuinely event-scale spikes (a global conference with 80+ session recaps), Shootsta Premier sits alongside subscription for the project-scale burst and is scoped per event.
How fast can the partner ramp during a spike?
Capacity is already in the system. The Production Team Lead activates the additional editor capacity in your dedicated team within 24 hours of a confirmed brief volume increase. The 48-hour first-cut bar holds during spikes, often with second-shift overnight editing across the global rota. We covered the speed model in how a video partner ships in 48 hours.
Do you charge a premium for spike work?
No, for spikes inside the annual envelope. Spike months draw forward against capacity that baseline months under-consumed; the annual price covers it. Burst above the annual envelope is at standard tier rates, not premium. Rush turnaround within 24 hours is a separate priority service.
What happens to the partner cost if demand drops?
Subscription tier scales down at renewal. The partner agreement is not headcount; it does not have the same friction to right-size. Most customers adjust tier annually based on the next-year forecast; some adjust quarterly when demand shifts materially. The point of the model is that capacity tracks demand, in both directions.
Can we just rely on freelancers for spikes?
Some programs do, and it works at low volume. The challenges at scale: freelancers each interpret brand differently, the same freelancer is not always available when you need them, onboarding a new freelancer for a 2-week spike burns half the spike in setup, and quality varies. A dedicated brand-trained team that flexes inside an agreement avoids those three friction points.
How do you forecast our annual envelope?
We work backwards from your last 12 months of actual video output (across all teams, including the work you outsourced ad-hoc) and forward from the next 12 months of known events, launches and campaigns. The resulting annual envelope is usually 40 to 80% higher than what teams initially estimate, because the ad-hoc work and the regional work is often invisible in central counts.
How we built the numbers in this post
The spike calendar, capacity model and cost ranges in this piece are anchored to Shootsta's own enterprise customer data plus public benchmarks for editor salary and time-to-hire. Sources by claim.
- 60 to 150 finished videos per year in a typical enterprise program. Shootsta benchmark across enterprise customers in financial services, professional services, technology and aviation. Mature programs sit at the top of the range; emerging programs at the bottom.
- ~50% of annual volume lands in 3 to 4 spike months. Shootsta production data: spike-month volume in Q1 (sales kickoff), Q2 (mid-year town halls), Q3 (events) and Q4 (launches) consistently outweighs baseline-month volume by 2x to 5x.
- $110K USD loaded per in-house editor, 5 finished videos per editor per month. Public salary data (US Bureau of Labor Statistics, Glassdoor, LinkedIn Talent Insights) plus typical employer overhead. Output benchmark from Shootsta delivery data. The same assumptions used in how a video partner extends your in-house team.
- Spike amplitudes (2x to 5x baseline by quarter). Shootsta production data: Q1 sales kickoff typically 2 to 3x baseline, Q2 mid-year 1.5 to 2x, Q3 event season 3 to 5x, Q4 launches 2 to 4x.
- Annual envelope forecasts run 40 to 80% above initial team estimates. Shootsta onboarding benchmark. The under-estimate comes from invisible ad-hoc and regional work that does not appear in the central video team's count until a procurement audit catches it.
Editorial standards
- Numbers cited are the most up-to-date figures we had at the time of writing. The "last updated" date on this page is when the numbers and sources were last reviewed.
- External benchmarks come from publicly available salary, labor and industry data. We name the source where possible and summarize where the underlying data sits behind a paywall.
- Internal benchmarks come from Shootsta's own production data across 70,000+ videos delivered for enterprise customers since 2015. Ranges reflect the middle 80% of customer outcomes; outliers excluded.
- Where ranges are given, they cover variability across sector, geography and program maturity. Treat them as starting hypotheses for your own program, not warranties.
- Spotted a number you would challenge? Let our editorial team know what you are seeing in your business and the data behind it. Material updates get credited in the post footer.
Where to go next
For the working pattern alongside an existing in-house team, read how a video partner extends your in-house team. For the budget framing leadership cares about, read the business case for enterprise video. For the speed model that lets spikes ship in 48 hours instead of weeks, read how a video partner ships in 48 hours.
To scope a baseline subscription tier plus burst capacity for your team, book a free consultation.