A
Post-Closure Unemployment Benefits Navigator
4.25
Derivation Chain
Step 1
Small business closure and transition management
→
Step 2
Post-closure tax settlement completed
→
Step 3
Unable to assess eligibility for self-employed unemployment benefits and restart support funds after closure
Problem
Self-employed individuals aged 45-60 don't know whether they qualify for self-employed unemployment insurance benefits after closing their business. The requirements are complex — minimum 24 months of enrollment, revenue decline criteria (3 consecutive months of losses), proof of involuntary closure, etc. — and there's no way to self-assess before visiting an Employment Center. Many miss out on up to 1.98 million KRW/month (~$1,485) for up to 7 months, totaling approximately 14 million KRW (~$10,500).
Solution
On the web, users enter their employment insurance enrollment history, closure reason, revenue trends, and business type, and the service: (1) pre-assesses eligibility for self-employed unemployment benefits, (2) identifies unmet requirements and guides users on how to fulfill them (e.g., revenue decline documentation), and (3) generates an Employment Center visit document checklist plus estimated benefit amount and duration.
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 (73%)
Data Availability
20.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 (59/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 [low]
Backend [medium]