S

Public Cloud Migration Cost Estimator

4.85

Derivation Chain

Step 1 Sensitive public data migration to private cloud
→
Step 2 Surge in public agency cloud transition demand
→
Step 3 Migration cost and timeline pre-estimation tool

Problem

With the decision to shut down the Daejeon National Information Resources Service by 2030, hundreds of public agencies must migrate their systems to private cloud infrastructure. However, agencies cannot pre-estimate migration costs and timelines based on their on-premises system scale, security classifications, and data categorization, causing budget planning delays. SI vendor quotes vary by 2–5x, and it takes 4–8 weeks from quote request to receipt.

Solution

Input the agency's server count, storage capacity, security classification, and data categorization level, and the AI automatically calculates estimated costs, timelines, and staffing requirements based on a database of similar migration cases. It also auto-generates comparison tables across CSAP-certified cloud vendors and security compliance checklists.

Target: IT officers at central government ministries and local governments; project managers at public sector SI companies (20–100 employees)
Revenue Model: Per-estimate report at $142 (190,000 KRW); annual subscription for public agencies (unlimited estimates) at $3,600/year (4,800,000 KRW)
Ecosystem Role: Supplier
MVP Estimate: 2_weeks

NUMR-V Scores

N Novelty
4.0/5
U Urgency
5.0/5
M Market
5.0/5
R Realizability
5.0/5
V Validation
5.0/5
NUMR-V Scoring System
N Novelty1-5How uncommon the service is in market context.
U Urgency1-5How urgently users need this problem solved now.
M Market1-5Market size and growth potential from proxy indicators.
R Realizability1-5Buildability for a small team with realistic constraints.
V Validation1-5Validation signal quality from competition and demand data.
Each dimension is scored 1-5 and weighted into grade S/A/B/C/D.
SaaS N=.15 U=.20 M=.15 R=.30 V=.20 Senior N=.25 U=.25 M=.05 R=.30 V=.15

Feasibility (72%)

Tech Complexity
29.3/40
Data Availability
23.1/25
MVP Timeline
20.0/20
API Bonus
0.0/15
Feasibility Breakdown
Tech Complexity/ 40Difficulty of core implementation stack.
Data Availability/ 25Practical availability and cost of required data.
MVP Timeline/ 20Expected time to ship a usable MVP.
API Bonus/ 15Bonus for viable public API leverage.
Total 100 points; below 50% is filtered out.

Market Validation (68/100)

Competition
8.0/20
Market Demand
9.4/20
Timing
20.0/20
Revenue Signals
10.5/15
Pick-Axe Fit
15.0/15
Solo Buildability
5.0/10
Validation Breakdown
Competition/ 20Signal quality from competitor landscape.
Market Demand/ 20Demand proxies from search and mention patterns.
Timing/ 20Fit with current shifts in tech, behavior, and regulation.
Revenue Signals/ 15Reference evidence for monetization viability.
Pick-Axe Fit/ 15How well the concept serves participants in a trend.
Solo Buildability/ 10Practicality for lean-team implementation.
Total 100 points; below 50 is filtered out.

Technical Requirements

Backend [medium] AI/ML [medium] Frontend [low]
Dashboard