B
Gov24 Document Issuance Navigator
3.35
Derivation Chain
Step 1
Digital government & financial procedure delegation
→
Step 2
Real-time guidance for Gov24 document issuance procedures
Problem
When people in their 50s try to issue documents on Gov24 (Korea's government services portal) — such as resident registration certificates, income verification, or tax payment certificates — they face 5+ authentication methods (joint certificate, financial certificate, simple auth, Digital OnePass, etc.) and the UI changes every year, causing confusion each time. They end up visiting the local government office in person (wasting 30 minutes to 1 hour) or asking their children to do it for them.
Solution
Users select the document they need, and the service provides a step-by-step guide mirroring the actual Gov24 screen flow — showing which buttons to click, which authentication to select, and what to enter, all with screenshot-based visual guides. Includes a pre-requisite checklist for each authentication method and solutions for commonly encountered errors.
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 (72%)
Data Availability
23.1/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 (57/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 [low]
Data Pipeline [medium]