That clip is now running against a media budget that is, in some cases, bigger than the original integration fee. And the creator — the person whose face, voice, and endorsement are carrying the ad — never agreed to it.
That's not a grey area. That's a separate license you didn't buy.
A paid integration covers one thing: the creator producing and publishing a video on their owned channel for their organic audience. Anything after that — paid social, pre-roll, landing pages, retail screens, OOH — is a different deal with a different price.
Why this keeps happening
Most brand-side creator contracts are written by the brand. The template says "content produced under this agreement." The paid media team reads that and assumes "content we paid for, ours to use."
The creator's read is the opposite. They produced a video for their audience. They got paid for that performance. The idea that the clip would later run as a pre-roll in markets they've never heard of, targeted to demographics they don't address, wasn't part of the conversation.
Both sides walk out of the deal thinking they understood it. Neither side wrote down the part that mattered.
What informed creators now charge
Creators who have been burned once don't make that mistake twice. They now quote usage rights as a separate line, calibrated by three variables: duration, channels, and geography.
Organic Integration Only
- Video lives on creator's channel
- Creator's audience, creator's context
- Base fee: $5,000
- No additional license required
- Standard 60–90 second integration
Integration + Paid Media License
- Clip reused in paid social & pre-roll
- Brand's targeting, brand's context
- Base $5K + 50–100% usage fee
- Duration, channels, geos defined
- Whitelisting or dark-post access scoped
A 3-month paid social license on a $5K integration often runs 50–100% of the base fee. A 12-month license across paid social, pre-roll, and OOH can easily double or triple it. That's not creator greed. That's what it costs to license someone's face in media they don't control.
The quiet cost of getting it wrong
When a brand repurposes creator content without negotiating rights, three things happen — roughly in this order.
The creator finds out
Creators track mentions of their own name. Their community screenshots things. Someone's going to see your pre-roll, recognize the face, and send them the link. Usually within a week of launch.
The relationship ends
Sometimes loudly, sometimes quietly. Either way, the creator won't work with you again, and — because creators talk to each other in private channels — neither will three or four of their peers.
In the worst case, a takedown or a claim
The cleanest creators just DMCA the ad and move on. The less-clean ones send the brand a licensing invoice for a multiple of what negotiating would have cost. A few pursue it further. None of those outcomes are good for the brand.
What to actually do about it
This isn't complicated. It just has to be explicit.
Before the integration goes live, the contract should say, in plain language: what channels the content will run on, for how long, in which geographies, and with what whitelisting access. Each of those is a priced line item. The creator knows what they're agreeing to. The brand knows what it owns. The paid media team can later clip, boost, or whitelist within the scope that was actually paid for — and not a millimetre beyond.
If that scope changes six months in, the contract gets amended and the creator gets paid for the extension. That's it.
The takeaway
Usage rights aren't an upsell. They're the thing that separates "a video the creator made" from "a media asset your brand can deploy." Those are two different products with two different prices.
If your contract template doesn't break them apart, your paid media team is either leaving the asset on the table — or using something they didn't actually buy. Neither is a position you want to be in.
Pull one creator contract from the last six months. Can you point to the clause that says where and for how long you can run that content in paid? If not, you already have the answer.