Minimum View Clause: The Risk Mitigation Tool Every Brand Needs
Imagine paying a creator $4,000 for a sponsored post that gets 12,000 views when their average is 200,000. That's a CPM of $333. No brand would knowingly accept those terms — but without a minimum view clause (MVC) in your contract, that's exactly what can happen. And it does happen, more often than brands want to admit.
The minimum view clause is the single most underused risk management tool in influencer marketing. It creates a floor on the media value you receive from a deal. At The Viral App, every contract we sign for managed clients includes a properly structured MVC, and it has saved campaigns from catastrophic budget waste on multiple occasions.
This guide explains exactly what MVCs are, how to set the right thresholds, how to structure the remedy provisions, and how to introduce them in negotiations without alienating good creators.
What Is a Minimum View Clause?
A minimum view clause is a contractual provision that establishes a minimum number of views a creator's sponsored post must achieve within a defined timeframe. If the post underperforms against that threshold, the brand is entitled to a specific remedy — typically a partial refund, a free reshoot, or an additional post at no charge.
MVCs acknowledge a fundamental truth about influencer marketing: even good creators have bad posts. Algorithm changes, off-peak timing, topic mismatch, or simply an unlucky week can cause a post to significantly underperform a creator's historical average. The MVC doesn't punish creators for normal variance — it protects brands from the tail risk of severe underperformance.
A well-structured MVC isn't adversarial — it's a shared expectation. Creators who are confident in their content welcome it. The ones who resist it are often the ones you should worry about most.
How to Set the Right MVC Threshold
The most common mistake brands make with MVCs is setting the threshold too high — at or above the creator's stated average. Creators will reject this because it creates too much risk for natural variance. The right threshold is calibrated to protect against genuine underperformance, not normal fluctuation.
The 50/70 Rule
At The Viral App, we use a tiered threshold framework based on the creator's 30-day average view count:
| Creator Average Views | MVC Threshold (Recommended) | Measurement Window | Remedy If Unmet |
|---|---|---|---|
| Under 50,000 | 50% of 30-day average | 14 days post-publish | Free reshoot or 50% refund |
| 50,000–200,000 | 60% of 30-day average | 14 days post-publish | Free reshoot or 40% refund |
| 200,000–1M | 65% of 30-day average | 21 days post-publish | Free reshoot or 30% refund |
| Over 1M | 70% of 30-day average | 30 days post-publish | Free additional post or 25% refund |
The rationale: smaller creators have more volatile view counts — a single underperforming post is less statistically meaningful. Larger creators have more consistent algorithmic performance, so a 70% threshold is fair and protective.
Calculating the 30-Day Average
Before finalizing any deal, pull the creator's last 10–15 posts and calculate a true average view count. Do not trust the creator's stated average — always verify against actual post data, which you can access through platforms like Modash, Klear, or HypeAuditor, or by asking the creator to share their analytics screenshots.
Also look at the distribution: if their average is 150,000 views but half their posts are under 30,000 and the other half are over 300,000, you have a high-variance creator. Adjust your MVC threshold accordingly — or negotiate a lower fee to account for the risk.
Structuring the Remedy Provisions
The remedy section is where most MVC clauses fall apart. Vague language like "brand will receive compensation for underperformance" is unenforceable and creates disputes. Be specific.
Option 1: Reshoot Remedy
The creator produces an additional piece of content at no charge within 14 days of the underperformance being confirmed. The reshoot should use the same brief as the original, unless both parties agree to a modified approach. This is the preferred remedy when the relationship is ongoing — it maintains budget efficiency and keeps the creator motivated to deliver.
Option 2: Partial Refund
A pro-rated refund calculated as: Refund = Fee × (1 - Actual Views / MVC Threshold). Example: fee is $2,000, MVC threshold is 100,000 views, actual views are 60,000. Refund = $2,000 × (1 - 60,000/100,000) = $2,000 × 0.40 = $800 refund. This is cleaner for one-off deals or when you don't want to continue working with the creator.
Option 3: Credit Toward Future Campaigns
A hybrid approach: rather than a cash refund, the brand receives a credit against future content. This works well with high-volume creator relationships where you're booking 4–8 posts per quarter. It reduces the creator's cash flow risk while still protecting the brand's ROI.
How to Introduce MVCs in Negotiations
Framing matters enormously. Introduce the MVC as a standard clause that all brand partners use — not as a personal statement of distrust. Here's language that works well in creator outreach:
"Our standard agreement includes a minimum view clause — it's something we include with all creator partnerships. Essentially, if a post underperforms your historical average by more than 40%, we'd either request a free reshoot or apply a partial credit to future campaigns. For creators who consistently perform at their average, this clause never comes up. We find it actually gives creators more confidence in the deal structure because it shows we're invested in the content performing well."
This framing positions the MVC as mutual protection — the brand is signaling it cares about performance, which actually increases the creator's confidence that the brand will invest in a quality brief and proper support.
Creators who have been burned by brands that paid late, gave terrible briefs, or disappeared after signing are often the most open to MVCs — because it signals that this brand has a professional, systematic approach to partnerships.
MVC Variations for Different Deal Structures
Pay-Per-View Deals
In PPV (pay-per-view) deals, the MVC is baked into the pricing structure itself — you literally only pay for views delivered. A typical PPV rate is $3–$6 per 1,000 views for TikTok micro-creators, with a minimum guaranteed base payment of $150–$300. This structure eliminates the need for a separate MVC because the payment model is already performance-based.
Hybrid Flat + Performance Deals
A flat fee of 50–60% of the creator's normal rate, plus a CPM-based bonus for views above the MVC threshold. Example: Normal rate is $1,500. Flat fee: $800. If post exceeds 80,000 views (the MVC threshold), brand pays an additional $4 per 1,000 views above 80,000. This aligns incentives beautifully and often results in creators promoting the content more aggressively to hit the bonus tier.
Real-World MVC Scenarios
Here's how MVCs play out in practice across different situations we've encountered at The Viral App:
- Algorithm penalization: A creator posts on a day TikTok's algorithm is deprioritizing their niche. Post gets 15,000 views vs. their 90,000 average. MVC triggers. Creator provides a free reshoot — second post gets 140,000 views. Net result: brand gets 155,000 views for the original price.
- Content quality issue: Creator submits content that was technically approved but underwhelms. 20,000 views on a 150,000-average account. MVC triggers partial refund of $600 on a $1,500 deal. Relationship maintained, brand protected.
- Bought followers detected: A creator with 200,000 followers averages 8,000 views per post — a massive engagement discrepancy. MVC threshold based on their stated average exposes this. Without MVC, brand would have paid for 80,000 guaranteed views and received 8,000.
- Viral overperformance: MVC provides zero friction — creator posts, gets 600,000 views on a 100,000-average account, both parties are thrilled, brand rebooks immediately.
The MVC infrastructure becomes exponentially more powerful when combined with a broader influencer contract framework that covers content rights, exclusivity windows, FTC compliance, and payment timing. There's a specific contract template structure that handles all of these together — and knowing which provisions to prioritize for app marketing vs. e-commerce vs. SaaS changes the calculus significantly. Want to see the full contract architecture?