B
Retiree Subscription Auditor
3.05
Derivation Chain
Step 1
Delegating digital administrative and financial procedures
→
Step 2
Difficulty tracking monthly Subscriptions and auto-payments
→
Step 3
Optimizing fixed costs against reduced post-retirement income
Problem
People in their 50s–60s see their income drop after retirement, yet they don't know exactly how much they spend on fixed monthly charges — telecom bills, Insurance premiums, OTT services, app Subscriptions, and auto-debits. Credit card statements only show 'auto-payment,' so figuring out what's being charged requires checking 3–4 card apps and 2–3 banking apps. Canceling requires calling each service's customer center individually. On average, $60–$115 (~8–15만원) per month leaks to unnecessary Subscriptions.
Solution
Users upload their card/bank statement CSV or screenshots, and the system automatically classifies auto-payments and Subscriptions to display: ① total monthly fixed expenses, ② category-level breakdown (telecom / Insurance / OTT / apps / other), ③ cancellation priority ranking (least-used items at top). Each item includes a cancellation method link (customer center number or in-app path).
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 (71%)
Data Availability
19.4/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 (55/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
Frontend [low]
Backend [medium]