B
Voice Phishing Simulation Training Studio
3.85
Derivation Chain
Step 1
Spread of AI voice phishing detection technology
→
Step 2
Demand for voice phishing response training in companies and institutions
→
Step 3
Automated creation tool for training simulation scenarios
Problem
Security managers at financial institutions, local governments, and SMEs (20-200 employees) are required to conduct quarterly voice phishing response training, but creating realistic scenarios takes 3-5 days per case, or 2-5 million KRW (approx. $1,500-$3,750) when outsourced. Failing to reflect the latest tactics reduces training effectiveness, and when actual incidents occur, insufficient evidence of training implementation often leads to criticism from supervisory authorities.
Solution
Based on a database of the latest voice phishing cases and tactics, AI automatically generates customized simulation training scenarios by industry and job level, and aggregates employee response results into reports, producing one-click evidence of training implementation for submission to supervisory authorities. TTS-based simulated phone calls and real-time scoring provide experiential training.
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 (73%)
Data Availability
23.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 (61/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]
AI/ML [low]