A
Technical License Renewal Alert Service
3.90
Derivation Chain
Step 1
171 public APIs in the industry and employment sector
→
Step 2
License management issues for mid-to-senior technical license holders
Problem
50s technical workers hold multiple essential licenses such as construction safety engineer, electric engineer, and fire equipment engineer, but each has different renewal cycles (3-5 years), continuing education deadlines, and career reporting deadlines. Management agencies are dispersed (HRD Korea, Korea Fire Safety Institute, Korea Electric Association), so missing renewal deadlines leads to license suspension, making them unable to work on site and causing income loss of millions of won. Many 50s technicians miss 1-2 renewal deadlines each year.
Solution
On the web, users input their list of licenses and acquisition dates, and the service manages renewal deadlines, continuing education deadlines, and career reporting deadlines for each license in an integrated calendar. It sends step-by-step alerts (email/KakaoTalk) at D-90, D-30, and D-7, and automatically provides available continuing education schedules and application links at those times.
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. |
N=.15 U=.20 M=.15 R=.30 V=.20
Feasibility (77%)
Data Availability
22.5/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 (58/100)
Solo Buildability
10.0/10
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]
Data Pipeline [low]