B
Wildfire Season Home Risk Alert
3.70
Derivation Chain
Step 1
Special wildfire prevention measures for Daeboreum (the first full moon)
→
Step 2
Lack of preparedness among middle-aged and older residents near wildfire risk areas
→
Step 3
Service for wildfire risk around my home + evacuation routes + insurance check
Problem
Residents in their 50s and 60s living in suburban or rural areas don't know exactly whether their home is in a wildfire risk zone during the spring wildfire season. The Korea Forest Service provides a wildfire risk map, but there is no function to enter your home address and check the risk level, and few people have pre-identified shelter locations and evacuation routes. Furthermore, most have never checked whether their home fire insurance covers wildfire damage, leading to thousands of cases each year where compensation is denied after actual damage.
Solution
When users enter their address, the service displays the wildfire risk level within a 5km radius on a map and shows the three nearest shelters and evacuation routes. It provides a checklist to verify the wildfire-related coverage in their current fire insurance policy, and if gaps are found, offers guidance on adding riders.
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.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 (62/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 [medium]
Backend [medium]
Data Pipeline [low]