B
K-Startup MWC Expo Booth Kit
3.50
Derivation Chain
Step 1
SKT MWC26 K-Startup showcase
→
Step 2
Growing Korean startup participation in overseas trade shows
→
Step 3
Trade show booth operations efficiency tools
→
Step 4
Expo lead auto-capture & CRM integration SaaS
Problem
Korean startups (~2,000 per year) participating in overseas trade shows like MWC and CES spend 3–5 days after each event manually transferring business cards and QR leads into spreadsheets, and follow-up emails take an average of 2 weeks to send — causing 60% of leads to go cold. Teams of 1–5 people especially lack the bandwidth to manage booth operations and lead processing simultaneously.
Solution
When booth visitors scan a QR code, their digital business card and areas of interest are automatically captured, and each visitor is auto-tagged by engagement level (dwell time, demo request). Immediately after the event, customized follow-up email templates are auto-generated and sent based on engagement level, and leads are automatically synced to HubSpot/Notion CRM.
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 (69%)
Data Availability
19.4/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 (56/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]
AI/ML [low]