A
Advance Directive Comparison Guide
3.80
Derivation Chain
Step 1
Parental care administration
→
Step 2
Parental healthcare decision-making
→
Step 3
Advance directive item-by-item comparison and family discussion guide
Problem
When adults in their 50s try to discuss advance directives with their parents in their 70s-80s, the specific meaning of each item on the directive form (CPR, mechanical ventilation, hemodialysis, chemotherapy, etc.) is difficult for laypeople to understand. The National Agency for Management of Life-Sustaining Treatment website only provides the form without explaining the practical implications of each choice (pain levels, survival duration differences, costs), causing people to make critical decisions without understanding or postpone them indefinitely.
Solution
A web service that provides plain-language, medically accurate explanations of what happens when you select each item on an advance directive (CPR, mechanical ventilation, hemodialysis, chemotherapy, hospice). It compares the expected outcomes, pain levels, and cost ranges for each choice in a table format, and provides a family discussion guide so relatives can read through it together and have meaningful conversations.
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
17.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 (51/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 [low]
Data Pipeline [low]