Public SI Maintenance Knowledge Bot

3.65

Derivation Chain

Step 1 Korea Agency for Public IT Service maintenance insourcing initiative

→

Step 2 Spread of public institution IT maintenance insourcing

→

Step 3 Legacy system knowledge transfer tool for maintenance insourcing transitions

Problem

When public institutions bring outsourced SI maintenance in-house, the institutional knowledge held by former vendors (incident response manuals, configuration histories, undocumented workarounds) fails to transfer properly. During the first 6 months after insourcing, average incident response time triples, and onboarding new staff takes 3–6 months.

Solution

Upload existing maintenance documentation (incident tickets, operations manuals, configuration change logs) and let AI build a per-system knowledge base accessible via a natural language Q&A chatbot. Enter incident symptoms to instantly retrieve similar past cases and resolution procedures, with automatic detection of undocumented areas prompting remediation requests.

Target: Public institution IT departments (5–15 staff), public enterprise IT operations teams (pursuing maintenance insourcing)

Revenue Model: Initial setup KRW 3,000,000 (~$2,250) + SaaS monthly flat rate at KRW 490,000/month (~$367/month) per system, additional document upload at KRW 50,000 (~$37) Per Transaction

Ecosystem Role: Education

MVP Estimate: 2_weeks

NUMR-V Scores

N Novelty

3.0/5

U Urgency

4.0/5

M Market

4.0/5

R Realizability

4.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 (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	/ 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 (57/100)

Competition

8.0/20

Market Demand

9.4/20

Timing

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

AI/ML [medium] Data Pipeline [medium] Frontend [low]

Dashboard