B
Lease Contract Expiration Response Coach
3.85
Derivation Chain
Step 1
Public administration and land management data
→
Step 2
Lack of information for tenants in their 50s on contract renewal and expiration response
→
Step 3
Simulation of renewal request right and deposit return scenarios based on user's contract conditions
→
Step 4
Generation of legal procedure timeline for deposit non-return
Problem
Tenants in their 50s must decide whether to exercise the renewal request right, the limit on deposit increases, and the process for returning the deposit when the lease expires, but it is difficult to accurately understand the complex regulations after the implementation of the three lease laws. In particular, cases such as 'when the renewal request right has already been used once vs. not used', 'how to respond when the landlord refuses renewal due to actual residence requirements', and 'the procedure for a lease registration order when the deposit is not returned on time' are difficult to judge without legal consultation (300,000-500,000 KRW / $225-$375).
Solution
By entering the contract start date, deposit/monthly rent, renewal request right usage history, and current situation (wish to renew / planning to move / deposit not returned) on the web, the service provides: (1) a comparison of legal rights and option scenarios tailored to the user's situation, (2) a timeline of actions to take before expiration (e.g., date to send a content certification, confirmation of fixed date), and (3) a step-by-step guide for procedures when the deposit is not returned, such as lease registration order → payment order → small claims court.
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 (70%)
Data Availability
20.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 (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
Backend [medium]
Frontend [medium]
Data Pipeline [low]