Fan-vibe content and apps:a 100-piece viral challenge
Fans build it, other fans play and share it, and the official IP's fandom grows. Approval, payments and creator payouts run on Docenty Pay.
Creator and content figures are campaign targets (concept example), not achieved results.
You are “Night Shift Researcher” 🧪
Crunch Lab member match result. See friends' results · Make a remix
This is what fan-made content looks like
All six formats run on the same payment and payout rail. Characters and brands are fictional; figures are targets.
- Trigger
- New product · comeback teaser
- Target
- Share rate 10%
- Revenue
- Supporter pack ₩1,000
- Trigger
- Release day
- Target
- Finish → 4,000 track clicks
- Revenue
- Skin ₩2,000
- Trigger
- Always on · event items
- Target
- Daily return 25%
- Revenue
- Monthly sub ₩3,900
- Trigger
- Concert · fan meeting
- Target
- 2,000 cards made
- Revenue
- ₩500 per card
- Trigger
- Right after the event
- Target
- 2,000 messages
- Revenue
- Digital album ₩5,000
- Today's patch quizDone
- Share result card with friends2/3
- Play 3 fan-made apps1/3
- Watch the broadcast20:00
- Trigger
- Season patch · anniversary
- Target
- Mission completion 45%
- Revenue
- Sponsored campaign
One line in, a submittable app 90 seconds later
Same in the web builder or in the Claude Code / Codex you already use. The agent fetches the IP Pack and rules; the fan writes one line of idea.
- ① Write one line"Make a Crunch Lab member match test"
- ② The agent pulls the Pack and rulesAllowed assets · banned phrases · credits applied automatically
- ③ Preview → submitRule check shown as passed · one button into the approval queue
Approval to payout, one flow
- 01IP approvalYou set the scope of use and review criteria.
- 02Fan creationVibe coders (creators who code with AI) and fans build apps, games, and quizzes.
- 03Play & shareResult cards go to social; official channels feature the best entries.
- 04Pay & settlePayments run on Docenty Pay; creator shares accrue after payment verification and are then settled.
What changes hands when you sign, on one page
- Official IP Pack (assets, allowed/prohibited guide, AI prompts, Skills)
- Campaign landing page + entry and submission page
- Approval queue (AI rule check → staff approval)
- Payment and creator payout rail (Docenty Pay)
- One official-channel announcement timed to the launch or event
- Check the approval queue twice a week (10 min)
- Feature the best entries on official channels once
- N fan-built apps, games, and quizzes stay live and reusable after the campaign
- Result-card shares drive traffic to official pages (measured as targets)
- Participating creators get priority for the next campaign → lower recruiting cost
Production flow — you do only four things
Example schedule (concept)- W0Kickoff (90 min)
- You provide
- Launch / event dates, brand assets, allowed and banned scope
- Docenty + fans
- Build the IP Pack, write License-as-Code, draft the campaign page
- You get
- An IP Pack with an agreed scope + campaign page
- W1Recruit · distribute
- You provide
- One official announcement (copy provided)
- Docenty + fans
- Recruit creators, ship the Pack and AI Skill, swap the demo skin
- You get
- Creator roster, build guide
- W2–3Build · review
- You provide
- Check the approval queue (twice a week, 10 min)
- Docenty + fans
- Fans and vibe coders (creators who code with AI) build; AI rule checks, change requests, gallery
- You get
- N approved fan pieces (rights consent included)
- W4Spread · settle
- You provide
- Feature the winners on official channels
- Docenty + fans
- Result-card spread, payments and creator payouts (Docenty Pay), measurement
- You get
- Participation · share · traffic · payment dashboard, reusable content library
Your total effort: a 90-minute kickoff, one announcement, approval checks twice a week (10 min each), one shout-out of the winners. Docenty runs the rest.
Ads people watch
Produce 20 assets → spend media budget → impressions → done. Content stops when the campaign ends.
Content people join and spread
N fans build N apps → other fans play, share and remix → the best ones are reused at the next comeback or update. Your content library grows.
Timed to launches, relaunches and events
It works best not after you have announced, but while you have an upcoming launch and are still planning the campaign.
| Trigger | When to pitch | What fans build (concept example) | KPIs measured |
|---|---|---|---|
| Game launch / season update | 4–8 weeks out | Character personality quiz, patch quiz, cheer challenge | Wishlists, pre-registrations, return visits |
| New single / comeback | 3–6 weeks out | Lyric puzzle, rhythm mini-game, comeback countdown | Content engagement, streaming traffic |
| Concert / fan meeting / event | 3–5 weeks out | Memory book, seat cheer mission, photocard studio | Event page visits, ticket conversion |
| Existing IP push / new character merch | Always on / 2–4 weeks out | Lore quiz, character maker, merch studio | Product page visits, purchase conversion |
| New product / rebrand (FMCG) | 2–4 weeks out | Mascot matching, recipe app, sampling-program remix | Product page visits, purchase conversion, re-participation rate |
One you can play now, two coming in the next challenge
Bias personality quiz
Early virality. Share the result card → remix. Free to play + a small supporter-pack purchase.
Raise your bias
Ongoing engagement. Daily check-ins grow the character; new items on singles, broadcasts and events. Skins, decor, monthly subscription.
Launch / single mini-game
Timing play. A fan-made rhythm game or lyric puzzle ships with the release. Funded by the campaign budget.
Only the IP you allow, only the way you approve
- Scope6 characters · logo · colors / music and voice-actor audio excluded
- ChannelsWeb apps · social cards / app-store distribution excluded
- Commercial useSupporter packs ₩500–3,000 / anything else needs approval
- Review queue31 submitted · 22 approved · 6 revision requests · 3 rejected
- Non-commercial modeON — payment and payout UI disabled (for large-IP pilots)
Automated review does not replace a legal rights check.
Fan Campaign Simulator
Assumption-basedAssumes each creator makes one piece of content. Share and conversion rates are per use, not unique visitors. Not a forecast or guarantee; amounts are before payment fees, royalties and campaign costs. The creator share is set by the Docenty Pay fee policy.
A different story for each audience
Brands · FMCG
Stop using a sampling panel once and discarding it. Turn it into a brand creator network.
Indie IP · MCNs · Agencies
Monetize fan creation around idle characters and your roster of creators.
Marketing agencies
Include it white-label in your clients' launch proposals.
Same engine, packaged for each buying department
Sister products that run on the same IP Pack, approval and payment rail as Fan Creation Challenge.
AI Content Factory
One asset, 30–100 channel-ready pieces
Fan Ambassador Engine
Fans who keep creating after launch
Official Creator Network
Your IP to 100 partners, still under control
Fan Data Showroom
Fans vibe-code on approved data
IP Creator OS
The IP package manager AI agents trust
Docenty Data Vibe Coding Contest
Your institution’s data. · Apps built in a vibe coding contest.
Request a custom demo for your schedule
Tell us your upcoming launch or event dates and how you run fan marketing today. We'll send a demo timed to that schedule and a 4-week pilot proposal. The custom demo is free (a skin swap on a fictional universe).
See the Fan Creation Challenge proposal structure
Three package tiers · submit → review → vote → announce flow · approval gates · KPI definitions.