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.
NUMR-V Scores
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 (74%)
Data Availability
24.4/25
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 (56/100)
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
AI/ML [medium]
Backend [medium]
Frontend [low]