A
AdminTracker — All Procedures at a Glance
3.35
Derivation Chain
Step 1
Delegation of digital administrative and financial procedures
→
Step 2
Unified progress tracking across procedures
Problem
Adults in their 50s handle 15–20 administrative procedures annually—year-end tax settlement, health insurance dependent registration, vehicle tax payment, address change registration, etc.—each requiring separate logins and procedures across different sites (Government24, HomeTax, NHIS, WeTax, etc.). Each procedure takes 30 minutes to 1 hour on average, and missing a deadline incurs penalty taxes or fines. No tool exists to manage what needs to be done and by when in a single place.
Solution
Input basic information—date of birth, family composition, homeownership status, vehicle ownership—and the system auto-generates a monthly calendar of all administrative procedures due for the year. Each procedure includes its deadline, a direct link to the processing site, and a required-documents checklist, with alerts sent 7 days, 3 days, and 1 day before each deadline.
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 (68%)
Data Availability
18.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 (54/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]