B
Fandom Goods Limited Edition Alert
3.15
Derivation Chain
Step 1
Evangelion 30th anniversary limited goods / IP content revival
→
Step 2
Limited-edition merchandise resale market
→
Step 3
Limited-edition goods integrated alert & authentication SaaS
Problem
As limited-edition merchandise from popular IPs like Evangelion's 30th anniversary is released through scattered channels such as theaters and events, fandom collectors in their 20s–30s must constantly monitor 5–10 channels including Twitter, fan communities, and official websites. Missing a release leads to buying at resale prices (2–5x retail) or losing the purchase opportunity entirely, occurring 2–3 times per month with additional costs of 50,000–200,000 KRW (~$37–$150) per item.
Solution
Automatically aggregates limited-edition merchandise release information across channels by IP, delivering real-time alerts based on user interests. Core features: (1) Cross-channel release info crawling from official sites, social media, and communities, (2) Personalized alerts by IP and category (via KakaoTalk/push notifications), (3) Release calendar and one-click purchase link integration. The differentiator is cross-channel aggregation spanning both Japanese and Korean IPs.
NUMR-V Scores
NUMR-V Scoring System
| N Novelty | 1-5 | How uncommon the service is in market context. |
| U Urgency | 1-5 | How urgently users need this problem solved now. |
| M Market | 1-5 | Market size and growth potential from proxy indicators. |
| R Realizability | 1-5 | Buildability for a small team with realistic constraints. |
| V Validation | 1-5 | Validation 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 (78%)
Data Availability
23.1/25
Feasibility Breakdown
| Tech Complexity | / 40 | Difficulty of core implementation stack. |
| Data Availability | / 25 | Practical availability and cost of required data. |
| MVP Timeline | / 20 | Expected time to ship a usable MVP. |
| API Bonus | / 15 | Bonus for viable public API leverage. |
Market Validation (54/100)
Validation Breakdown
| Competition | / 20 | Signal quality from competitor landscape. |
| Market Demand | / 20 | Demand proxies from search and mention patterns. |
| Timing | / 20 | Fit with current shifts in tech, behavior, and regulation. |
| Revenue Signals | / 15 | Reference evidence for monetization viability. |
| Pick-Axe Fit | / 15 | How well the concept serves participants in a trend. |
| Solo Buildability | / 10 | Practicality for lean-team implementation. |
Technical Requirements
Data Pipeline [medium]
Backend [low]
Frontend [low]