Telecom AI PoC Cost Estimation Tool

3.85

Derivation Chain

Step 1 MWC 2026 AI-Telecom Convergence

→

Step 2 Telecom AI Solution Adoption Rush

→

Step 3 Standardization Tool for AI PoC Project Quoting and Cost Estimation

Problem

After MWC, the three major domestic telecom companies and MVNOs are simultaneously issuing PoCs for AI-based network optimization and customer service automation, but the SME SI companies (10-30 employees) that win these contracts lack a standard tool to integrate GPU infrastructure costs, LLM API call volumes, and labor costs, spending an average of 3-5 days per quote. The rate of winning at a loss due to underestimation or losing due to overestimation reaches about 40%.

Solution

Provides a cost estimation engine specialized for telecom AI PoCs. (1) GPU/TPU infrastructure cost simulator (comparing AWS/GCP/on-premise), (2) automatic monthly operating cost estimation based on LLM API call volume, (3) generates quotes within 30 minutes using telecom-specific labor cost and schedule templates.

Target: Sales and PM roles at IT SI/solution companies with 10-50 employees in the telecom and network sector.

Revenue Model: SaaS monthly subscription: 49,000 KRW (~$36.75) per account, 20% discount for annual payment. Includes 10 quotes per month, additional quotes at 3,000 KRW (~$2.25) each.

Ecosystem Role: Infrastructure

MVP Estimate: 2_weeks

NUMR-V Scores

N Novelty

3.0/5

U Urgency

4.0/5

M Market

4.0/5

R Realizability

4.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.

N=.15 U=.20 M=.15 R=.30 V=.20

Feasibility (70%)

Tech Complexity

29.3/40

Data Availability

20.8/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 (72/100)

Competition

10.0/20

Market Demand

20.0/20

Timing

14.0/20

Revenue Signals

10.5/15

Pick-Axe Fit

10.5/15

Solo Buildability

7.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

Frontend [medium] Backend [medium] Data Pipeline [low]

Dashboard