B

Limited Edition Drop Calendar

3.30

Derivation Chain

Step 1 Starbucks reusable cup limited-edition open-run phenomenon
→
Step 2 Spread of limited-edition collecting/purchasing culture
→
Step 3 Unified limited-edition release calendar

Problem

Limited-edition release schedules from brands like Starbucks, Nike, LEGO, and Pokémon are scattered across individual brand apps, social media, and community forums, causing collectors to miss drops and lose open-run opportunities. On average, limited-edition collectors spend 3–5 hours per week searching for release info, and fail to even learn about 3 out of 10 drops.

Solution

Automatically aggregates limited-edition release schedules from major brands like Starbucks, Nike, and LEGO into a unified calendar. Users register interest by brand and category to receive alerts 3 days before and on the morning of each release. Shares online stock availability by store and offline store locations with community-sourced queue-line updates.

Target: Limited-edition collectors in their 20s–30s; trend-conscious consumers who attempt 2+ limited-edition purchases per month
Revenue Model: Premium Subscription at 2,900 KRW (~$2.20)/month (Free: 5 brands, Premium: unlimited brands + stock alerts + store queue info)
Ecosystem Role: Consumer
MVP Estimate: 2_weeks

NUMR-V Scores

N Novelty
1.0/5
U Urgency
3.0/5
M Market
3.0/5
R Realizability
5.0/5
V Validation
3.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.
Each dimension is scored 1-5 and weighted into grade S/A/B/C/D.
SaaS N=.15 U=.20 M=.15 R=.30 V=.20 Senior N=.25 U=.25 M=.05 R=.30 V=.15

Feasibility (78%)

Tech Complexity
34.7/40
Data Availability
23.1/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.
Total 100 points; below 50% is filtered out.

Market Validation (51/100)

Competition
8.0/20
Market Demand
6.2/20
Timing
14.0/20
Revenue Signals
7.5/15
Pick-Axe Fit
7.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.
Total 100 points; below 50 is filtered out.

Technical Requirements

Data Pipeline [medium] Backend [low] Frontend [low]
Dashboard