Teacher AI Training Compliance Hub

3.20

Derivation Chain

Step 1 Public education AI transformation

→

Step 2 Mandatory teacher AI training (Education)

→

Step 3 Teacher AI competency training tracking + certification management SaaS

Problem

As education offices push AI education transformation, teacher AI training has become effectively mandatory. However, training records are scattered across multiple providers (KERIS, provincial education training centers, private vendors), forcing school administrators to spend 5–8 hours per month tracking each teacher's AI competency status. Education office–level AI training completion aggregation takes 2–3 weeks, creating bottlenecks for policy planning.

Solution

Automatically collects and consolidates teacher AI training records via cross-referencing across training providers, presented in a unified dashboard. Includes school-level and subject-level AI competency metrics + automatic alerts for teachers with incomplete training + one-click aggregate reports for education offices.

Target: K–12 school administrators (vice principals, research department heads), provincial education office training supervisors

Revenue Model: Per-school license $44/month per school (up to 50 teachers); education office annual contract $22/month per school (100+ schools); 1-month Free Trial

Ecosystem Role: Education

MVP Estimate: 2_weeks

NUMR-V Scores

N Novelty

3.0/5

U Urgency

4.0/5

M Market

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

Competition

8.0/20

Market Demand

3.8/20

Timing

16.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] Data Pipeline [low]

Dashboard