B
Parents' Phone Plan Savings Analyzer
3.55
Derivation Chain
Step 1
Accelerating digital transformation
→
Step 2
Smartphone penetration among 60+ surpasses 90%
→
Step 3
Parents in their 60s maintaining expensive plans unsuited to their usage for years
→
Step 4
Children trying to compare and switch parents' plans but struggling to find information
Problem
When adults in their 50s review their parents' (60s–70s) phone bills, it's common to find them paying for 30GB data plans while actually using only 3–5GB. Switching to an MVNO could save $22–$37/month (3–5만원), but checking usage under the parent's name, comparing plans, and handling the number transfer takes 3–4 hours—and with 50+ MVNO providers, comparison alone is overwhelming.
Solution
Users enter their parent's current carrier, plan, and monthly usage (data/calls/texts) on the web. The system compares plans across all carriers including 50+ MVNOs and recommends the top 5 by monthly savings. Includes a number transfer step-by-step guide and a power-of-attorney form for when children handle the switch. Features a 'Show to Parents' mode (large text, essentials only).
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 (59/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]
Frontend [low]
Backend [low]