A
Reusable Cup Inventory Tracker SaaS
3.70
Derivation Chain
Step 1
Starbucks reusable cup open-run / limited-edition goods craze
→
Step 2
Limited-edition goods resale market activation
→
Step 3
Limited-edition inventory and price tracking tool for resellers and small distributors
Problem
Individual resellers and small-scale distributors who resell franchise limited-edition goods (reusable cups, collaboration merchandise, etc.) spend 2-3 hours daily manually monitoring communities and secondhand platforms to track store-by-store inventory and resale prices. Failed open-run attempts mean missed acquisition opportunities, and misjudging prices leads to repeated losses of $7.50-$37.50 per item.
Solution
Provides a store-by-store limited-edition inventory dashboard via franchise official app/community crawling + automatic price tracking on Bungaejangter and Karrot (Korean secondhand platforms) + open-run schedule alerts and price change push notifications, reducing reseller decision-making time by 90%.
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 (72%)
Data Availability
22.5/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 (62/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
Backend [medium]
Frontend [low]
Data Pipeline [medium]