B
Apartment Energy Performance Comparison Report
3.05
Derivation Chain
Step 1
Expansion of environmental and weather data utilization
→
Step 2
Growing interest in apartment energy efficiency
→
Step 3
Integration of apartment energy performance assessment infrastructure with real estate transactions
Problem
Prospective apartment buyers find it difficult to assess maintenance fee levels in advance. The Ministry of Land, Infrastructure and Transport's public housing management information system (K-apt) discloses energy usage data, but it is impossible to compare across complexes after adjusting for differences in area, number of households, and heating method. A monthly difference of 100,000 KRW (approx. $75) in maintenance fees amounts to 24,000,000 KRW (approx. $18,000) over 20 years, yet there is no way to know this before purchase.
Solution
Collects K-apt data to calculate energy efficiency grades (A-F) adjusted for area, number of households, heating method, and year of completion, and provides comparison reports with similar complexes in the same region. Differentiation: integrates with real estate listings to support purchase decisions, and predicts seasonal maintenance fees.
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 (67%)
Data Availability
17.9/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 (51/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
Data Pipeline [medium]
Backend [medium]
Frontend [low]