Not an AI hackathon.Fans make 100 launch pieces.
In an executive briefing, a hackathon reads as an event expense. Say that at launch, instead of producing 20 ad assets, fans will build 100 micro-apps they play and spread themselves, and it reads as a marketing investment.
The one page your executive gets in four weeks
Not the results of 20 ad creatives, but N fan-built apps and the traffic, payments and lists they produced.
Fan Creation Challenge · 4-week results
Period: D-28 → D+030 creators · 30 approved pieces · 12,000 visits · 0 violations
- 📱Apps30 approved fan piecesTests, mini-games, cards, memory books. Rights cleared
- 🗃️LibraryReusable library for the next campaignOnly an update at the next comeback or patch
- 💳PayoutsPayment and creator payout statementDocenty Pay · accrued after verification
- 👥List30 creators + participant segmentsFirst pick for the next challenge
- 01Launch / comeback weekOfficial channel features winners → result cards spread
- 02Product / pre-order pageApps send fans to the official page
- 03Next eventLibrary update + creator re-invite
- Content lifespanToday0 after campaignIn 4 weekslibrary of 30
- Official page trafficTodaymedia spendIn 4 weeks1,500 shares → 12,000 visits
- Fan payments (optional)TodaynoneIn 4 weeksGMV target ₩300,000 (₩1,000 × 300 · hypothesis)
- Re-recruiting costToday100%In 4 weeks60%
Three campaign package tiers
- Creator target10
- Content target10
- Campaign length2 weeks
- Official promoOptional
- Results dashboardBasic
- IP approval & reviewBasic
- Creator target30
- Content target30
- Campaign length4 weeks
- Official promoIncluded
- Results dashboardAdvanced
- IP approval & reviewIncluded
- Creator target100
- Content target100
- Campaign length6 weeks
- Official promoIncluded
- Results dashboardAdvanced
- IP approval & reviewIncluded
All figures are early sales hypotheses; participants and outputs are targets, not guaranteed results. Prizes, external ad spend, extra production and rights fees are negotiated separately.
Apply, build, compete — on the IP and its data
Deadlines, prizes and a leaderboard like a hackathon, using only the official IP Pack and approved data. Apply → build → submit → judging and votes → awards.
- ✓ Official Pack only
- ✓ Approved data only
- ✓ Rule check before submit
- ✓ Private judging
Submit → review → vote → announce, on screen
Your team sees only three screens: IP Pack approval, the approval queue and selection. Fans and Docenty handle the rest.
- ✓ Allowed: 6 characters · colors · lore
- ✕ Banned: audio · voice actors · real-person composites · recolors
- ◻ Commercial use: supporter packs ₩500–3,000
- ⚙ AI prompts · Skills included (Claude/Codex)
🏆 5 Fan Creation Challenge winners revealed! Congrats to @vibecoder_minji for the Night Shift Researcher quiz. Play it now →
What remains after 4 weeks
It stays in the library after the campaign and gets updated at the next comeback or patch. 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
What changes hands when you sign
- 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.
Submit → review → vote → announce
- 01Announce & recruitIP owner's official channels + Docenty channels. Distribute the allowed/prohibited guide and IP Pack.
- 02Build & submitVibe coders (creators who code with AI) and fans build apps, games and quizzes. Submit a URL.
- 03Review & approveAI rule check (before) → IP owner approval (after). Rejection reasons are logged.
- 04Showcase & announceShowcase approved entries, fan voting, official feature of the best. Open paid items.
Only what you allow, only the way you allow it
IP usage scope (License-as-Code)
- · Usable assets: characters, logo, colors / excluded: music, voice actors, real-person likeness
- · Allowed channels: web apps, social cards / excluded: app-store distribution
- · Commercial use: a defined range of small paid items, or non-commercial mode
- · AI-generated output: allowed / conditional / prohibited — the IP owner decides
- · Anything rules can't decide stays marked 'approval required'
Review criteria
- · Brand-rule violations (prohibited wording, distortion) auto-flagged
- · Features that undermine game fairness excluded (game IP)
- · Secondary use of entries requires explicit consent
- · Sponsorship and affiliate disclosures inserted automatically (Korea FTC guidelines)
- · Automated review does not replace legal review
Not views, but people who reached the official page
Participating creators · submitted and approved content
Plays · shares · remixes · official channel features
Unique visits to the official site · new participants · return rate
Wishlists · pre-orders · purchases · paid conversion rate
Creation that doesn't stop when the event ends
A structure where every piece of content consumed triggers the next creation.
- 1Fan A builds a new-single quiz and shares it
- 2Fan B plays it and posts the result on social
- 3Fan C remixes the quiz into another version
- 4The official IP account features popular content
- 5Another creator builds a character game or fan calendar
- 6Existing apps get updated at the next comeback
Get a proposal timed to your schedule
Tell us your launch, comeback or event dates and we'll send a 4-week pilot proposal and a custom demo.