B
AI-Era Job Survival Years Prediction Report
3.05
Derivation Chain
Step 1
AI adoption leads to half of employees being laid off
→
Step 2
Self-diagnosis of the probability that my job will be replaced by AI
→
Step 3
Providing expected job survival years + alternative job transition roadmap
Problem
Although AI layoff news is reported daily, office workers aged 45-55 have no objective basis to determine 'exactly how many years until my job becomes at risk.' McKinsey and Goldman Sachs reports are in English and don't align with Korean job classifications, and the Korea Employment Information Service's occupational outlook is updated every two years, failing to reflect the pace of AI change. Many either rush into retirement out of vague anxiety or, conversely, fail to recognize the crisis and are laid off without preparation.
Solution
(1) Enter job title, industry, and main tasks to score AI replacement potential based on the O*NET job analysis framework, (2) provide an 'automation risk index' along with three alternative jobs that can be transitioned to from similar roles, (3) present a roadmap of certifications, training programs, and estimated costs needed for each alternative job. It reflects the Korean context by linking to the Ministry of Employment and Labor's employment trends by occupation.
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 (70%)
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 (55/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
Backend [medium]
Frontend [low]
Data Pipeline [medium]