B
SME Senior Talent Board
2.70
Derivation Chain
Step 1
Experience-based re-employment matching
→
Step 2
Limitations of seniority-based filters on existing platforms
→
Step 3
Decomposing 'industry-specific know-how' needed by SMEs into skill-unit matching
Problem
An owner of an SME with 50 or fewer employees wants to hire a 30-year veteran manufacturing quality control expert, but filtering for '20+ years experience' on job portals like Saramin or JobKorea only surfaces high-salary candidates from large corporations. What they actually need is a micro-skill match like 'ISO 9001 audit experience + small factory line design.' Headhunters charge 20-30% of annual salary as fees, which is prohibitive for SMEs.
Solution
Senior job seekers register their careers decomposed into 'industry × job function × specific skill tags,' and SMEs search and match by 'required skill tags' on a web board. Since matching is skill-based rather than salary-based, part-time, advisory, and project-based contracts are naturally facilitated.
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.3/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
Frontend [medium]
Backend [medium]
Data Pipeline [low]