B
Heavy Snow Gig Worker Match Board
2.90
Derivation Chain
Step 1
Heavy snow warnings in Chungcheong & Gyeongsang regions
→
Step 2
Emergency demand for snow removal & recovery workers
→
Step 3
Disaster season gig worker-to-demand matching Platform
Problem
When heavy snow warnings are issued, municipalities, apartment management offices, logistics centers, and large retailers urgently need snow removal, safety management, and delivery support workers, but existing Recruitment Platforms focus on regular hiring and cannot handle same-day or next-day emergency matching. Calling local staffing agencies often results in already-full rosters or no answer, with only 40-60% of needed workers actually secured.
Solution
Integrates with the Korea Meteorological Administration warning API to automatically notify registered gig workers in the affected area 24-48 hours before warnings are issued. Demand-side clients (municipalities, management offices, logistics centers) register required headcount, hourly rate, and hours, and the system performs real-time matching. Location-based priority matching within a 5km radius and instant settlement upon work completion are provided.
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 (57/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]