B
Lease 3 Act Contract Checklist
3.60
Derivation Chain
Step 1
Existence of land management and financial APIs
→
Step 2
Problem that landlords in their 40s-60s do not accurately know the application criteria of the Lease 3 Act (renewal request right, rent increase cap, reporting system)
→
Step 3
Problem that verifying whether contract clauses comply with legal revisions requires lawyer consultation (over $225)
Problem
A 58-year-old landlord living on monthly rental income after retirement, when receiving a tenant's request for contract renewal, cannot accurately determine the scope of the 5% rent increase cap, grounds for refusal of renewal, and the obligation to report the lease. Internet searches mix pre- and post-revision information, causing confusion, and lawyer consultations cost over $225 per case. A wrong decision to refuse renewal can result in penalties, or conversely, failing to exercise rights can lead to losses of millions of won.
Solution
By entering the contract start date, end date, current rent, renewal request status, and housing type, it automatically determines whether the Lease 3 Act applies and clearly distinguishes 'what you can do / what you must do / what you must not do' in this case. It attaches links to the relevant legal provisions for each item and provides sample clauses to include in the contract.
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 (73%)
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 (57/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]