Public VOC AI Training Data Builder

3.55

Derivation Chain

Step 1 Public institution AI VOC Platform deployment

→

Step 2 AI VOC model training data supply

→

Step 3 VOC labeling and anonymization automation pipeline

Problem

Public institutions like Seoul Metro are rapidly adopting AI-based VOC (Voice of Customer/citizen complaint) analysis Platforms, but building training data requires manual personal information anonymization and category labeling. Labeling 300,000 VOC records costs over $37,500 (50 million KRW) in outsourcing fees and takes 3-4 months, with the risk of personal data protection law violation penalties if anonymization is missed.

Solution

Public institutions upload raw VOC text (citizen complaint content), and the system performs LLM-based automatic PII masking (names, phone numbers, addresses) + automatic category labeling + sentiment tagging, providing a semi-automated pipeline where human reviewers only need to verify results. Privacy audit logs are generated automatically.

Target: IT departments at public institutions (local governments, public corporations), PMs at SI firms building AI VOC systems (ages 30-45)

Revenue Model: Per Transaction Billing at $0.04/VOC record (50 KRW), dropping to $0.02/record (30 KRW) for 10,000+ records. Minimum monthly fee of $225 (300,000 KRW).

Ecosystem Role: Supplier

MVP Estimate: 2_weeks

NUMR-V Scores

N Novelty

4.0/5

U Urgency

4.0/5

M Market

3.0/5

R Realizability

3.0/5

V Validation

4.0/5

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 (74%)

Tech Complexity

29.3/40

Data Availability

24.4/25

MVP Timeline

20.0/20

API Bonus

0.0/15

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)

Competition

8.0/20

Market Demand

9.4/20

Timing

16.0/20

Revenue Signals

10.5/15

Pick-Axe Fit

12.0/15

Solo Buildability

5.0/10

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] AI/ML [medium] Frontend [low]

Dashboard