Public Data Cloud Migration Progress Dashboard

3.90

Derivation Chain

Step 1 Public data cloud migration policy

→

Step 2 Rapid increase in SI companies performing migration projects

→

Step 3 Lack of tools for SI companies to manage migration progress, quality, and schedule

Problem

SME SI companies (10-50 employees) performing public data cloud migration projects manually manage the migration progress, data consistency verification results, and security classification status of dozens of datasets in Excel, and a single PM spends 8-12 hours per week preparing weekly reports. When migration omissions or consistency errors are discovered during the client's acceptance inspection, 2-4 weeks of rework are required.

Solution

Import the list of datasets to be migrated, and provide a Kanban dashboard that automatically tracks progress by migration stage (mapping → transfer → verification → security review). Automatically verify data count and schema consistency, display security classification results in real time, and generate weekly reports for the client with one click.

Target: PMs at SME SI companies (10-50 employees) performing public data cloud migration projects

Revenue Model: Project-based license: 199,000 KRW/month per project (up to 100 datasets) (approx. $149). Large-scale projects: 399,000 KRW/month (unlimited) (approx. $299). 15% discount for 6-month prepayment.

Ecosystem Role: Supplier

MVP Estimate: 2_weeks

NUMR-V Scores

N Novelty

3.0/5

U Urgency

5.0/5

M Market

3.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.6/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] Frontend [medium] Data Pipeline [low]

Dashboard