
Costs
Part of UGC platforms: what five marketplaces sell and what to check
UGC platforms examples for agency campaign briefs
UGC platforms examples for agencies: compare Billo, Insense, Cohley and Aspire, then use campaign-brief patterns to test coverage, claims and rights.
UGC platforms examples can help agencies assess suppliers through portable campaign briefs, not by ranking platforms. The platform shortlist below distinguishes common supplier roles; the named campaigns that follow show specifications for testing a message, filling a media plan, and handling rights. Treat those signals as prompts for evaluation, not sourced performance benchmarks.
UGC platform examples for supplier comparison
These are named supplier examples, not a ranking or a live feature audit. Their broad roles differ:
- Billoa creator marketplace focused on UGC video production. Compare creator matching, video formats, revision terms, and content-use rights.
- Insensea creator marketplace for UGC and influencer campaigns. Compare creator sourcing, campaign workflow, and permissions for paid use.
- Cohleya creator-content platform that includes product sampling. Compare available content formats and sampling workflows, and confirm who secures usage rights.
- Aspirea broader influencer-marketing platform for creator discovery and campaign management. Compare its broader campaign workflow with a brief that only needs UGC assets.
Ask each supplier to confirm current capabilities and contract terms; use the brief patterns below as test cases, not evidence of vendor performance.
What to take away
- Pick the campaign shape from the goal, not from what a supplier is good at producing.
- The specification line in each entry is the sentence most often missing from a real brief.
- Every signal here is observable without a vendor dashboard.
- Rights and disclosure terms belong in the brief, not in a later email.
- A named campaign is a starting point for your own brief, not a template to copy.
Testing a message
These campaigns existed to find out what to say, so they were built for comparison rather than polish.
Duolingo's TikTok owl. The goal was to find which entry point held attention. The specification: one recurring character, many openings, identical body length. The signal was that one opening style separated from the rest under the same media spend.
Ryanair's TikTok. The goal was to learn which register a category responds to. The specification: the same account filming both a straight version and a self-aware version of the same message. The signal was that the self-aware register won consistently, not once.
Gymshark's athlete clips. The goal was to decide where production budget belongs. The specification: raw files delivered, so the cut-down stayed with the brand. The signal was that the native short version did not lose to the recut.
Fenty Beauty's shade-match videos. The goal was to settle whether demonstration beats a stated claim. The specification: exact permitted sentences for the stated version, clean audio on both. The signal was that demonstration earned its production premium.
Liquid Death's ad reads. The goal was to test spoken-to-camera against voiceover. The specification: clean audio on both, no music bed, same length. The signal was a stable difference that survived a second round.
Testing patterns at a glance
Pattern
- Multiple openings, one body
- Find entry point
- Problem vs outcome framing
- Learn register
- Long form vs short native
- Decide budget
- Spoken vs voiceover
- Settle internal argument
- Claim stated vs demonstrated
- Is demo worth cost
Goal
- Multiple openings, one body
- Distinct openings, identical body
- Problem vs outcome framing
- Same person, same length
- Long form vs short native
- Raw files, yours to cut
- Spoken vs voiceover
- Clean audio, no music
- Claim stated vs demonstrated
- Exact permitted sentences
Spec must carry
- Multiple openings, one body
- One opening separates
- Problem vs outcome framing
- Diverge across creators
- Long form vs short native
- Native does not lose
- Spoken vs voiceover
- Stable difference, second round
- Claim stated vs demonstrated
- Earns premium, or not
Signal
- Multiple openings, one body
- Problem vs outcome framing
- Long form vs short native
- Spoken vs voiceover
- Claim stated vs demonstrated
The Fenty row is the one that most often surprises a team, and it is also where the claims list in the brief matters most. A demonstration that implies something you cannot substantiate is a bigger problem than a weaker asset.
Filling a media plan
These are volume briefs. The specification carries more weight than the creative direction, because you are buying coverage of shapes and placements. Volume like this can be sourced through a creator marketplace, including Billo or Insense; matching is handled there, while the brief is still yours. For an agency comparing suppliers, the useful question is whether the marketplace can support the specifications.
Chipotle's #ChipotleLidFlip. The goal was to fill a plan without reshooting per shape. The specification: safe areas per placement, stated individually. The signal was that no asset was unusable in a placement it was ordered for.
Starbucks' Red Cup Contest. The goal was to extend the life of something already performing. The specification: the original license terms, checked before reordering. The signal was that the refresh ran without a new rights negotiation.
Apple's #ShotoniPhone. The goal was to support a considered purchase with several angles. The specification: an agreed sequence and consistent product handling. The signal was that the set could run in any order without contradicting itself.
Airbnb's #LiveThere. The goal was to enter a second market without new production. The specification: caption files rather than burned-in text, territory named in the license. The signal was that a version shipped without a reshoot.
Glossier's repost program. The goal was to populate a plan with varied faces and voices. The specification: disclosure requirements and what may be said about results. The signal was that nothing had to be pulled after review.
Volume briefs and their signals
Pattern
- One product, many placements
- Fill plan, no reshoots
- Seasonal refresh
- Extend a working asset
- Category education set
- Support considered purchase
- Localized versions
- Enter second market
- Testimonial style at volume
- Varied faces and voices
Goal
- One product, many placements
- Safe areas per placement
- Seasonal refresh
- Original license terms
- Category education set
- Agreed sequence, handling
- Localized versions
- Caption files, territory
- Testimonial style at volume
- Disclosure, results rules
Spec must carry
- One product, many placements
- No asset unusable
- Seasonal refresh
- No new rights negotiation
- Category education set
- Runs in any order
- Localized versions
- Ships without reshoot
- Testimonial style at volume
- Nothing pulled after review
Signal
- One product, many placements
- Seasonal refresh
- Category education set
- Localized versions
- Testimonial style at volume
| Chipotle #ChipotleLidFlip | Fill a plan without reshooting per shape | Safe areas per placement, stated individually | No asset unusable where it was ordered | | Starbucks Red Cup Contest | Extend a working asset's life | Original license terms, checked first | Refresh ran without new rights talks | | Apple #ShotoniPhone | Support a considered purchase | Agreed sequence, consistent product handling | The set ran in any order | | Airbnb #LiveThere | Enter a second market without production | Caption files, territory in the license | A version shipped without a reshoot | | Glossier reposts | Populate a plan with varied faces | Disclosure terms and permitted claims | Nothing pulled after review |
Airbnb's row is the quiet money saver. Burned-in text ends an asset's life at one language border; a caption file does not. Starbucks' row fails more often than it should, purely because nobody checked the term before commissioning the refresh. The rights structure behind both is set out in the pillar guide to commissioning short form content.
Rights and compliance
These are the briefs where the specification does legal work as well as creative work.
Daniel Wellington's creator posts. The goal was to buy reach and footage in one booking. The specification: separate permissions for the live post and footage use, plus the disclosure requirement. The signal was that the live post carried the disclosure without being chased.
GoPro's footage-only awards. The goal was to buy production without endorsement. The specification: state that no organic post was expected and that the brief covered footage only. The signal was no confusion about whose audience saw what.
Fashion Nova's creator ads. The goal was to borrow identity as well as material. The specification: a separate permission for the creator's identity in the ad, distinct from the material license. The signal was that the permission was documented before the ad went live.
Nike's long-term athlete assets. The goal was to keep an asset featuring someone for years. The specification: likeness permission on its own clock, recorded separately. The signal was that the asset survived the footage license renewal.
UGC reuse of an organic post. The goal was to amplify something that already worked. The specification: written permission covering paid use, and any music in it. The signal was that the post could run as an ad without re-editing the audio.
The last row is where most unplanned rights problems begin. A post that performed organically was made under whatever permissions the creator had at the time, and music is the usual failure. Payment does not transfer ownership; the U.S. Copyright Office's Copyright Basics explains what copyright protects.
If a creator also posts to their own audience, endorsement obligations apply.
The Federal Trade Commission's Endorsement Guides explain when endorsements need disclosure.
Choosing a brief for supplier comparison
Start from what you do not know. If you do not know what to say, use a testing campaign and accept rougher production.
If you know what to say and need coverage, use a volume campaign and put the effort into the specification.
If the booking involves somebody's audience as well as their camera, use a rights campaign and document the permissions separately.
Which pattern to use
Do you know what to say?
volume pattern, invest in specification
testing pattern, accept rougher production
The common error is running a volume brief before the message is settled, yielding many assets wrong the same way.
The second most common is a testing brief stating only one variable, so results cannot be attributed to anything.
Where the counterparty is represented, the permissions in the last table are negotiated by an agent rather than by the creator, which changes the pace and the price of the conversation. The guide to talent representation sets out how that side works.
Common questions
How many creators should a testing campaign use?
Enough that a difference is not one person's delivery. Two is a story about two people; a handful starts to be about the pattern.
Can one brief cover more than one campaign shape?
It can, and it usually should not. Combining a test with a volume order produces assets that serve neither purpose well and a result nobody can interpret.
Do these campaigns depend on which supplier we use?
No. These are campaign specifications, not platform rankings; they are portable across suppliers. Agencies comparing platforms, agencies, or tools can use them to test whether an offer supports the brief.
What if the signal is ambiguous?
Then the brief had more than one variable in it. Run it again with one, or accept that the round taught you about the process rather than about the message.







