S

FanLedger — Fan Club Dues Manager

4.00

Derivation Chain

Step 1 Trot audition program proliferation
Step 2 Fandom community activation
Step 3 Fan club operations & admin tools
Step 4 Dues & merchandise settlement automation

Problem

Fan clubs for trot singers discovered through audition programs like 'Unknown Legends' are predominantly run by members aged 40–60 who manage dues via KakaoTalk group chats and manual bank transfer verification. Club officers spend 5+ hours per week cross-referencing deposit records against bank statements for 50–200 members, and 3–5 disputes arise monthly over missed or incorrect payments during group merchandise purchases.

Solution

Provides KakaoTalk notification-based dues billing with auto-deposit confirmation, one-click group merchandise order and settlement management, and automatic membership tier benefits (light stick discounts, fan meeting priority booking).

Target: Fan club organizers for trot / Mr. Trot / Unknown Legends performers (ages 40–60, club size 50–500 members)
Revenue Model: Premium $22/month per fan club (up to 200 members), Free Plan (up to 50 members, basic features), group merchandise purchase commission at 2% Per Transaction
Ecosystem Role: Supplier
MVP Estimate: 2_weeks

NUMR-V Scores

N Novelty
3.0/5
U Urgency
4.0/5
M Market
3.0/5
R Realizability
5.0/5
V Validation
4.0/5
NUMR-V Scoring System
N Novelty1-5How uncommon the service is in market context.
U Urgency1-5How urgently users need this problem solved now.
M Market1-5Market size and growth potential from proxy indicators.
R Realizability1-5Buildability for a small team with realistic constraints.
V Validation1-5Validation signal quality from competition and demand data.
SaaS N=.15 U=.20 M=.15 R=.30 V=.20 Senior N=.25 U=.25 M=.05 R=.30 V=.15

Feasibility (69%)

Tech Complexity
29.3/40
Data Availability
19.4/25
MVP Timeline
20.0/20
API Bonus
0.0/15
Feasibility Breakdown
Tech Complexity/ 40Difficulty of core implementation stack.
Data Availability/ 25Practical availability and cost of required data.
MVP Timeline/ 20Expected time to ship a usable MVP.
API Bonus/ 15Bonus for viable public API leverage.

Market Validation (70/100)

Competition
10.0/20
Market Demand
20.0/20
Timing
14.0/20
Revenue Signals
7.5/15
Pick-Axe Fit
10.5/15
Solo Buildability
8.0/10
Validation Breakdown
Competition/ 20Signal quality from competitor landscape.
Market Demand/ 20Demand proxies from search and mention patterns.
Timing/ 20Fit with current shifts in tech, behavior, and regulation.
Revenue Signals/ 15Reference evidence for monetization viability.
Pick-Axe Fit/ 15How well the concept serves participants in a trend.
Solo Buildability/ 10Practicality for lean-team implementation.

Technical Requirements

Frontend [medium] Backend [medium] Infrastructure [low]
Dashboard