B
Anonymous Career Transition Archive
3.20
Derivation Chain
Step 1
Career transition matching
→
Step 2
Network-dependent career transition information
→
Step 3
Anonymous sharing of actual post-career paths by industry and position peers
Problem
Pre-retirees aged 50-60 at large or mid-sized companies want to know 'where did people with similar careers go after leaving,' but this information circulates only through personal networks. LinkedIn adoption among Koreans in their 50s is under 5%, and job portal reviews skew toward people in their 20s-30s. As a result, they spend 6-12 months exploring career transition paths and end up choosing suboptimal options from a limited set of alternatives they're aware of.
Solution
Builds an anonymous database where contributors share 'previous industry/position/tenure → post-retirement path (re-employment, entrepreneurship, Freelancer, teaching) → current satisfaction and income level.' Searchers filter and view career transition cases from profiles similar to their own. A contribute-to-access model rewards case contributors with credits to view other cases, driving data accumulation.
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 (70%)
Data Availability
20.6/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 (50/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 [medium]
Infrastructure [low]