S
Real-Life Voice Phishing Simulation for Parents
4.10
Derivation Chain
Step 1
Soaring gold prices + war anxiety + cryptocurrency surge
→
Step 2
Environment of increasing financial fraud
→
Step 3
People in their 50s think they 'know' phishing tactics but actually fall for them
→
Step 4
Lack of hands-on simulation training
Problem
With soaring gold prices, war anxiety, and cryptocurrency hype, financial scams (voice phishing, investment fraud texts) have become more sophisticated. People in their 50s and 60s think 'I won't fall for it,' but when they actually experience phishing scenarios, over 70% are deceived in their first reaction. According to police statistics, victims in their 50s and 60s account for over 40% of total damages. Existing education merely delivers knowledge like 'these are the tactics,' which is completely different in effectiveness from experiencing real phone and text simulations.
Solution
Users experience the latest voice phishing scenarios (prosecutor impersonation, child impersonation, courier impersonation, investment fraud, etc.) interactively on the web. They see real phishing texts and choose among 'report it / click the link / ignore it,' and in phone scenarios, choose among 'yes / no / hang up.' Each choice provides results and correct answer explanations. After the experience, a 'phishing defense score' is calculated and vulnerable types are identified.
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 (75%)
Data Availability
23.1/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 [low]