A
Property Tax and Comprehensive Real Estate Tax Change Simulator
3.60
Derivation Chain
Step 1
Expansion of public administrative data openness
→
Step 2
Frequent changes in real estate holding tax system
→
Step 3
Multi-home owners in their 50s cannot predict actual tax payments due to annually changing rates and fair market value ratios
Problem
Real estate owners in their 50s-60s (especially those with 2+ homes) face property tax and comprehensive real estate tax that change annually based on the fair market value ratio, tax rate brackets, and official price fluctuations. To calculate the actual expected payment combining these three variables, they must consult a tax accountant (10,000-30,000 KRW per consultation, approx. $7.50-$22.50) or rely on the National Tax Service calculator (which only provides last year's rates). Especially when the government changes the fair market value ratio mid-year, the expected tax can vary by millions of won, but there is no tool to simulate this in advance.
Solution
Register your property address (or enter the official price directly) on the web, and it automatically calculates the expected property tax + comprehensive real estate tax based on current rates. It provides scenario simulations like 'What if the fair market value ratio rises from 60% to 80%?' or 'What if I sell one property?' and sends automatic recalculation alerts when official prices change annually.
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.6/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]