Why the contract is the procurement pivot point

Most enterprise video conversations get the strategy right, the budget approved, and the partner selected before procurement and legal see the contract. The result is that contract review happens under time pressure, with everyone wanting the program to start, and structural risks get accepted because the alternative is delaying the program by a month.

The seven clauses below are the ones that matter most in 2026 enterprise video contracts. None of them are radical. All of them are negotiable with reputable vendors. Knowing them in advance turns the contract review from a delaying step into a quick confirmation.

The seven clauses that matter most

1. IP ownership and asset transfer

Customer owns finished video, raw footage, project files, brand templates and all derivative assets. Unconditionally. From day one. No "we own the project files until you have paid for 12 months" structure. No "raw footage is our property" carve-out. No "you license the finished video, we retain copyright" trick.

This is the single most important clause because it is the one most often abused. Some agencies hold raw footage hostage at renewal time, knowing that the cost of re-shooting is high enough that the customer will renew. A clean unconditional IP transfer clause removes the lever entirely and is the modern enterprise standard.

2. Exit clause and notice period

90-day exit standard. No penalty. All IP transfers at exit. Pre-paid fees prorated and refunded if the program is sized monthly. This caps the buyer's downside on a bad-fit engagement to one quarter of cost, and signals that the vendor is confident the work will earn renewal on its own merits rather than on lock-in.

The exit clause should be unilateral on the buyer's side. Mutual exit clauses (where the vendor can exit on 90 days too) sound balanced but actually expose the buyer to mid-program vendor abandonment. The exit right is the buyer's; the vendor's commitment is to deliver.

3. Exclusivity and non-compete

Neither side should lock the other in. The customer should be free to use additional vendors as needed (specialty production, regional supplementation, parallel pilots). The vendor should be free to serve other customers including sector competitors. Both restrictions limit market efficiency and rarely produce real protection.

Non-compete on the vendor is often requested by buyer procurement teams but rarely justified. The protection it offers (preventing the vendor's editor team from working on a competitor's account) is usually weaker than the cost it imposes (vendor cannot scale, has to charge more to cover lost opportunity, may decline to work with you because the restriction is too broad). Most reputable vendors decline these clauses politely.

4. Indemnity and liability caps

Mutual indemnity for IP infringement is the modern standard. If the vendor produces work using a third-party asset that infringes a copyright, the vendor indemnifies. If the customer briefs the vendor to use a customer-supplied asset that turns out to be infringing, the customer indemnifies. Mutual structure reflects the actual risk distribution.

Liability caps should be proportionate to the annual fee paid (typical structure: cap at 12 months of fees for direct liability, exclude consequential damages). Unlimited liability is uncommercial for the vendor; no cap or token caps are uncommercial for the buyer. A proportionate cap is what most enterprise legal teams settle on.

5. Data security and confidentiality

Per-project NDAs. ISO-aligned security controls (ISO 27001 alignment, SOC 2 for vendors operating in US). SSO-ready authentication. Role-based access control inside the production platform. Data residency clauses where required (EU customer data resident in EU; APAC customer data resident in APAC). Per-project access tiers for sensitive content (executive scripts, regulatory disclosures, change comms).

For regulated sectors, additional clauses cover sector-specific requirements (HIPAA for US healthcare, FCA-aligned controls for UK financial services, MAS-aligned for Singapore FS). Most reputable vendors have these clauses pre-drafted; ask for them at the start of contract review rather than negotiating them in.

6. Dispute resolution

Mediation-first dispute resolution. If mediation fails, arbitration in a mutually agreed venue. Governing law in the customer's primary region for most engagements. The mediation step is important because most disputes are misunderstandings that resolve quickly with a neutral facilitator; jumping straight to arbitration is expensive and adversarial.

For multi-region engagements, the governing law clause can get complex. A common structure is one MSA with governing law in the customer's HQ jurisdiction, with regional sub-agreements that defer to local law where required by data residency or labor regulation.

7. Pricing and volume commitment

Annual fixed fee or annual envelope (number of finished videos per year at a stated tier). Burst capacity priced openly with predictable per-unit rates above the envelope. Quarterly QBR reviews actual usage and recalibrates tier if needed. No surprise overages, no per-incident charges that drift.

For multi-year MSAs, year-on-year pricing should be either fixed or pegged to a transparent index (typically CPI in the customer's region). Open-ended pricing escalators are red flags because they create renewal pressure without performance accountability. We covered the pricing model in more detail in the business case for enterprise video.

Get a Free Consultation →

Four red flags that should trigger pushback

1. IP transfer contingent on contract continuation

The vendor agrees to transfer IP, but only at the end of the contract or only if the customer has paid 12 months of fees. This is the "raw footage hostage" pattern, common in older agency contracts. Push for unconditional transfer that takes effect on delivery of each piece, not on contract milestones.

2. No exit clause, or 12+ month termination notice

Long lock-ins suit the vendor's revenue forecasting, not the buyer's risk profile. 90-day exit is the modern standard for subscription vendors in every adjacent category (SaaS, professional services, training platforms). A video production vendor refusing to offer 90 days is signaling that they cannot retain customers without lock-in, which is itself useful information.

3. Per-incident overage pricing without a cap

The contract sizes a baseline volume; anything above the baseline is billed per-incident at the vendor's discretion. Invoice variability becomes a finance problem because the line item is unforecastable. The fix is either a cap on overages or a tier move that absorbs them into a predictable larger envelope.

4. Non-compete on the vendor preventing them from serving competitors

The buyer's procurement or legal team requests it; the vendor agrees because the deal is large. Outcome: the vendor cannot scale, has to charge more to cover lost opportunity, and the relationship gets fragile because the vendor's incentives are no longer aligned. Most reputable vendors will push back; if they do not, the contract is probably bad for both sides.

Project SOW vs subscription MSA: structural difference

The contract structure should match the engagement structure. Two clear patterns.

Project SOW

One Statement of Work per project. Best for low-volume programs (under 6 to 8 videos a year) where each engagement is genuinely scoped and discrete. Trade-offs: every project triggers a new procurement event, a new IP transfer, a new security review and a new brand setup. Spend is unpredictable. Brand templates do not amortize because each project rebuilds them.

Subscription MSA

One Master Services Agreement, multi-year (typically 1, 2 or 3 years initial). All seven clauses negotiated once. Standing IP transfer terms apply to every project. One security review covers the relationship. Predictable annual fee. Brand templates load once and apply to every project. Best for 12+ videos per year, recurring program with multiple stakeholders.

For most enterprise video programs in 2026, the MSA structure is the right fit because it removes the per-project procurement overhead that fragmented project SOWs create. The MSA can still be structured to allow per-project flexibility (sub-statements of work for unusual scope, regional sub-agreements for multi-jurisdiction programs).

What "good" looks like in negotiation

A reputable production partner will agree to all seven clauses without significant pushback. Most of them are not negotiable from the partner's side - they are standard for the market in 2026 and any vendor refusing them is signaling that their business model depends on something the modern standard does not allow.

Where genuine negotiation usually happens: liability caps (proportionate vs higher), data residency (specific jurisdiction requirements), pricing escalator (fixed vs CPI-indexed), termination of MSA without cause (90-day vs 60-day standard). These are real negotiation points and most settle without drama.

Where negotiation should not be required: IP ownership, exit clause existence, mutual indemnity, basic security controls. If a vendor wants to negotiate these, ask why. The answer reveals more about the vendor than about the clauses.

What to do if you are already in a bad contract

Three practical moves.

Wait for renewal and renegotiate. Most bad contracts in this category are 12 or 24 month terms. The renegotiation at renewal is the natural moment to introduce the missing clauses. The vendor's incentive to keep the customer usually moves the contract closer to the modern standard.

Use the IP gap as leverage. If your current vendor refuses to transfer raw footage or project files at the end of the term, that is itself a renewal-time conversation. Show the vendor the seven-clause baseline and ask which ones they object to and why. The conversation often surfaces issues that get fixed.

If the contract is genuinely unworkable, scope a parallel pilot with a different vendor on modern terms. After 90 days you have evidence on what working under a clean contract looks like, and you can use it to either renegotiate or transition cleanly. We covered the pilot structure in how to pilot a video production partner.

Frequently asked questions

What is Shootsta's standard contract structure?

Multi-year MSA with annual subscription pricing and per-project sub-agreements where needed. All seven baseline clauses pre-negotiated. 90-day exit clause unilateral on the buyer side. Full IP transfer on delivery of each piece. Mutual indemnity with proportionate caps. ISO-aligned security controls and per-project NDAs. Mediation-first dispute resolution. Pricing fixed for the initial term, CPI-indexed thereafter.

How long does contract negotiation typically take?

For enterprise customers, 2 to 6 weeks depending on legal team availability and any sector-specific clauses required. We provide the standard MSA up front so legal review can start before commercial terms are fully agreed. Most negotiation focuses on liability caps, data residency, and pricing escalator rather than on the baseline clauses above.

What happens to assets if Shootsta goes out of business?

All customer assets sit in the customer's Shootsta Workspace, which is backed by S3-equivalent infrastructure with documented data export procedures. Customers can extract their full asset library at any time through the platform. We also document escrow arrangements for project files on request from regulated customers.

Can we structure the contract per region for multi-region operations?

Yes. Common structure is one global MSA with regional addenda covering local data residency, governing law and billing currency. Procurement signs one MSA; regional finance handles regional invoicing. We covered the multi-region operating model in how to scale video across global offices.

What about insurance?

Shootsta carries professional indemnity, public liability and cyber insurance at enterprise-appropriate levels in each jurisdiction we operate in. Certificates of insurance are available to customers on request as part of procurement.

How do you handle SOC 2 or ISO 27001 audit requirements?

Standard for enterprise customers in regulated sectors. We share the most recent audit report under NDA during procurement. For customers requiring their own audit access (financial services typically), we work through a documented audit protocol that respects other customers' confidentiality.

Does the contract cover AI usage in production?

Yes. The Shootsta AI use policy is referenced in the MSA and covers which AI capabilities are used at each tier, how customer content is handled (not used for model training), and IP attribution. We covered the broader AI framing in how AI fits inside enterprise video workflows.

Where to go next

For the pilot structure that proves the contract terms hold up in practice, read how to pilot a video production partner. For the brand-control framework that the IP transfer clause supports, read brand control with a video production partner. For the budget framework the pricing clause maps to, read the business case for enterprise video.

To request the Shootsta standard MSA for legal review, book a consultation.