B
Family Agreement Log for Inheritance Dispute Prevention
3.50
Derivation Chain
Step 1
AI data depletion — unstructured decision-making within families
→
Step 2
The problem of inheritance disputes after parents' death for those in their 50s
→
Step 3
The lack of tools to record and share family agreements before disputes arise
Problem
People in their 50s experience conflicts among siblings over inheritance of elderly parents' assets (real estate, deposits, insurance). Verbal agreements made during parents' lifetime are often denied after death ('I never said that'), escalating into legal disputes. Lawyer consultations cost 300,000 to 500,000 KRW per session (approximately $225 to $375), and there is no tool to record sensitive family conversations, leaving no documents that can be used as evidence.
Solution
Provides a web-based 'Family Agreement Log' accessible jointly by family members. Input parent asset list → draft distribution plan → each member gives electronic consent (identity verification) → timestamped record. While not legally binding, it serves as reference material to prove intent of agreement in future disputes. Also provides guidance for notarization.
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 (63%)
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 (50/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
Backend [medium]
Frontend [medium]