B
NeighborScope: Downsizing Lifestyle Impact Preview
2.85
Derivation Chain
Step 1
Real Estate downsizing decision-making
→
Step 2
Beyond Tax concerns, lifestyle change is the psychological barrier
→
Step 3
Compare hospital, grocery, transit, and community access across candidate locations
Problem
When a couple in their 60s considers downsizing from a 1,300 sq ft apartment in Gangnam (Seoul) to a 830 sq ft unit in Gyeonggi Province, they can't compare anything beyond capital gains Tax—specifically, 'how close are hospitals, grocery stores, and subway stations after moving, and how much does daily convenience change?' Naver Real Estate only shows property listings; there's no feature to compare living Infrastructure (access to internal medicine, orthopedics, supermarkets, community centers) between current and prospective locations. This vague anxiety causes decision paralysis.
Solution
On a web app, users enter their current address and candidate moving addresses. The tool generates a Report comparing medical facilities (internal medicine, orthopedics, dental), supermarkets, subway stations, parks, senior welfare centers, and community centers within a 1km radius by category. Results are scored for intuitive comparison: 'hospital access -20% vs. current, grocery access +10%.'
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. |
SaaS N=.15 U=.20 M=.15 R=.30 V=.20
Senior N=.25 U=.25 M=.05 R=.30 V=.15
Feasibility (66%)
Data Availability
16.2/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 (50/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]