Public Service Change Alert Board

2.95

Derivation Chain

Step 1 UX disruptions in digital government and financial services

→

Step 2 Missed filing deadlines due to authentication and menu changes

→

Step 3 Advance change alerts + procedural screenshot guides

Problem

A 55-year-old Self-employed business owner tries to file VAT returns on HomeTax, only to find that last month's UI was redesigned — the 'e-Filing' menu moved and it now requires a financial certificate instead of the old joint certificate. The change notice was buried in an announcement board no one checks, and they miss the filing deadline by two days, incurring a 3% late penalty. This happens 2–3 times a year across five major services including Government24, HomeTax, and mobile banking apps.

Solution

Users register the public and financial services they frequently use (HomeTax, Government24, National Health Insurance, primary banking app, etc.) on the web. The service then sends advance notifications via KakaoTalk alerts or email summarizing UI changes, authentication method changes, and key deadlines. Updated procedures are delivered as screenshot-based step-by-step guides.

Target: Self-employed or retirees aged 45–60 who use HomeTax, Government24, and mobile banking directly, and file taxes themselves without a tax accountant

Revenue Model: 3 service alerts per month free. Monthly Subscription ~$7.50 Premium (unlimited service registration + screenshot guides + deadline calendar sync).

Ecosystem Role: Infrastructure

MVP Estimate: 2_weeks

NUMR-V Scores

N Novelty

4.0/5

U Urgency

3.0/5

M Market

3.0/5

R Realizability

2.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 (56/100)

Competition

8.0/20

Market Demand

9.4/20

Timing

14.0/20

Revenue Signals

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

Data Pipeline [medium] Backend [medium] Frontend [low]

Dashboard