De-MS Migration Estimator

2.65

Derivation Chain

Step 1 Government institutions moving away from Microsoft toward digital independence

→

Step 2 Demand for MS Office to open-source transitions

→

Step 3 Transition cost and risk pre-estimation SaaS

Problem

Following Denmark's move away from Microsoft software, Korean public institutions are also exploring digital independence, but there is no tool to pre-calculate transition costs and risks based on each institution's MS product usage (license count, macro dependencies, Exchange integrations, etc.). External consulting costs $15,000-$37,500 per engagement and takes 2-3 months, causing many institutions to abandon the evaluation altogether.

Solution

Upload the institution's MS license inventory (CSV/Excel) and complete a usage pattern survey (15 questions) to automatically calculate transition costs, timelines, and risk scores for alternatives like LibreOffice, Hancom, and Google Workspace, then generate a phased migration roadmap PDF.

Target: IT officers at public institutions and local governments with 50-500 employees, small IT consulting firms (5-15 people)

Revenue Model: Per-transaction billing: Basic diagnosis ~$150/institution, detailed roadmap included ~$375/institution. Monthly flat rate for IT consulting firms ~$740 (unlimited diagnoses).

Ecosystem Role: Infrastructure

MVP Estimate: 2_weeks

NUMR-V Scores

N Novelty

3.0/5

U Urgency

2.0/5

M Market

2.0/5

R Realizability

3.0/5

V Validation

3.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 (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	/ 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 (53/100)

Competition

8.0/20

Market Demand

9.4/20

Timing

10.0/20

Revenue Signals

10.5/15

Pick-Axe Fit

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

Dashboard