B

Legacy UI Modernization Diagnostic Report

3.30

Derivation Chain

Step 1 Re-examination of Windows 95 UI case studies (UX engineering interest)
Step 2 Demand for legacy system UI modernization
Step 3 Automated UX audit and improvement roadmap generation for UI to be modernized

Problem

When IT agencies and SI companies with 10–100 employees win UI modernization projects for legacy systems (10–20-year-old WinForms/MFC/JSP) from public institutions and mid-sized enterprises, analyzing current UX issues costs 5–20 million KRW in consultant fees (approx. $3,750–$15,000) and takes 2–4 weeks. For small projects, this initial analysis cost makes it difficult to break even.

Solution

Upload screenshots or screen recordings of the legacy system, and AI automatically performs UX heuristic evaluation (based on Nielsen's 10 principles), generating a diagnostic report with screen-by-screen improvement priorities, estimated effort, and a modernization roadmap. Automatically generates a PDF for proposal attachments.

Target: UX/planning managers at IT agencies and SI companies with 10–100 employees
Revenue Model: Per-transaction billing: 99,000 KRW per project (approx. $74, up to 20 screens); monthly subscription: 199,000 KRW/month (approx. $149, unlimited); 20% discount for annual billing.
Ecosystem Role: Supplier
MVP Estimate: 2_weeks

NUMR-V Scores

N Novelty
3.0/5
U Urgency
3.0/5
M Market
3.0/5
R Realizability
4.0/5
V Validation
3.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.
N=.15 U=.20 M=.15 R=.30 V=.20

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

Market Validation (56/100)

Competition
8.0/20
Market Demand
6.2/20
Timing
14.0/20
Revenue Signals
10.5/15
Pick-Axe Fit
10.5/15
Solo Buildability
7.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.

Technical Requirements

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