B
Digital Legacy Organizer for Parents
3.55
Derivation Chain
Step 1
Surge in AI and digital services
→
Step 2
Post-mortem organization problem due to the surge in digital accounts among middle-aged and older adults
→
Step 3
A system for individuals to organize their digital asset list during their lifetime and pass it on to family
Problem
Active internet users aged 55-65 have an average of 30-50 online accounts (financial, shopping, social media, subscription services, cloud storage), but in the event of their death, their families are not even aware of these accounts. Unresolved paid subscriptions continue to be auto-charged monthly, and photos and documents stored in the cloud become permanently inaccessible. Currently, there is no Korean-language service to systematically organize this, so people rely on insecure methods like writing passwords in notepads or on paper.
Solution
An encrypted web service that allows users to register their digital accounts, subscriptions, and assets by category and grant designated family members viewing access. Key features: (1) registration and notes by account type (financial/shopping/SNS/subscription/cloud), (2) does not store passwords but only records hints on 'where to find them', (3) sends access instructions to designated family members via email/text. Differentiator: minimizes security risk by not storing passwords themselves.
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. |
N=.15 U=.20 M=.15 R=.30 V=.20
Feasibility (74%)
Data Availability
24.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 (66/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 [medium]
Backend [medium]
Infrastructure [low]