My Neighborhood Civic Request Tracker

3.40

Derivation Chain

Step 1 Seo Myeong-ok ethics committee complaint

→

Step 2 Tracking National Assembly member activities

→

Step 3 Tracking how my civic complaints are actually processed

Problem

When residents in their 50s file complaints with local government or the national e-People portal, they receive only a submission confirmation text and have no way to track progress afterward. Average processing takes 14-30 days, but there is no visibility into which department has stalled the case or how many similar complaints have been filed. People end up either resubmitting the same complaint repeatedly or giving up entirely.

Solution

Enter a complaint reference number to visualize the processing stages, and view the number of similar complaints filed in the area, average processing time, and resolution rate. A 'Me Too' button allows users to boost the priority of similar complaints by aggregating support.

Target: Ages 45-60, residents who frequently file civic complaints about apartment management, roads, noise, parking, and other daily issues; participants in local residents' councils

Revenue Model: Free web service. B2B Monthly Subscription for local governments and apartment management offices: complaint analytics dashboard at 49,000 KRW/month (~$37/month). Complaint category statistics Report

Ecosystem Role: Consumer

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

4.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 (68%)

Tech Complexity

29.3/40

Data Availability

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

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

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

Dashboard