A
Lease Special Clause Risk Decoder
3.85
Derivation Chain
Step 1
Growing interest in Real Estate downsizing
→
Step 2
Adults aged 50-60 transitioning from owned homes to Jeonse/Monthly Rent cannot identify pitfalls in lease special clauses
→
Step 3
Even after identifying clause risks, they don't know what language to use when negotiating revisions with the landlord
Problem
Adults aged 55-65 who sell their large owned homes after their children move out and transition to Jeonse (Lease Deposit) or Monthly Rent face difficulty understanding lease agreement special clauses after decades of being homeowners. They cannot judge whether clauses like 'restoration obligation,' 'exclusion of tacit renewal,' or 'maintenance fees separate' are favorable or unfavorable, relying solely on Real Estate agents. Disputes typically take 6-12 months and cost 2-5 million won (~$1,500-$3,750 USD) in Legal fees.
Solution
Users upload their lease agreement via photo or PDF, and the tool automatically extracts special clauses, displaying a risk level (safe/caution/danger) for each clause. For risky clauses, it provides 'what this clause means' and 'suggested revision language' to help negotiate with the landlord.
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
21.7/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 (56/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]
AI/ML [medium]