No usable source links are available for this idea. Its signal notes and scores need independent verification.
When working professionals in their 50s try to apply for welfare benefits for their parents in their 70s-80s, benefits from the central government (Basic Pension, Long-term Care for the Elderly), local governments (Senior Center Programs, Care Services), and the private sector (telecom discounts, transportation support) are scattered across different websites. Bokjiro (bokjiro.go.kr) offers integrated search, but without knowing the parents' exact conditions (whether they receive basic living subsidies, long-term care grade, residential local government), it's impossible to find suitable benefits, and missing application deadlines can cost hundreds of thousands of KRW (approx. $150-$675) annually. In particular, benefits unique to each local government are only announced on the district office's website, making them nearly impossible to discover.
When users enter their parents' basic information (age, residential local government, income level, long-term care grade, major conditions) on the web, the service (1) compiles a list of available central + local + private benefits on one screen, (2) provides application deadlines, methods, and required documents for each benefit, and (3) sends email/KakaoTalk reminders at D-30 before the deadline. When conditions change (e.g., care grade upgrade, address change), the benefit list is automatically updated.
| 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. |
| 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. |
| 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. |