B
Advance Directive Comparison Guide
3.55
Derivation Chain
Step 1
Digital legacy & account organization
→
Step 2
Expansion to overall end-of-life preparation
→
Step 3
Lack of understanding about advance directive options
Problem
Although Korea's Life-Sustaining Treatment Decision Act (enacted 2018) allows people to write advance directives, less than 4% of those in their 50s-60s have done so. People delay or avoid it because they don't understand what 'withdrawing life-sustaining treatment' specifically means—which of CPR, mechanical ventilation, dialysis, or chemotherapy they're refusing. Families also avoid the conversation entirely. Even at registration agencies (public health centers, hospitals), the explanation is completed within 20 minutes, leading many to sign without sufficient understanding.
Solution
The system explains each of the 4 life-sustaining treatment options (CPR, mechanical ventilation, dialysis, chemotherapy) and available hospice types through scenarios showing 'what happens if you choose/refuse this.' A 'conversation guide' for families to review together is provided, and once the user confirms their intent, they are connected with nearby registration agencies and appointment scheduling.
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 (79%)
Data Availability
18.8/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 (50/100)
Solo Buildability
10.0/10
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 [low]