B

Municipal Competition Management SaaS

3.05

Derivation Chain

Step 1 Public data utilization island expo
→
Step 2 Competition operations administration
→
Step 3 Integrated competition submission, judging, and announcement management Platform

Problem

When local governments run public data competitions, they handle submissions (email/mail), judging (Excel), and results announcements (manual website posting) through separate channels. Each competition requires 2-3 government staff members dedicated to administrative work for 4-6 weeks, with an average of 2-3 incidents per year involving missed submissions, duplicates, or scoring errors.

Solution

Handles the entire workflow — from competition announcement creation, online submission, judge assignment, blind evaluation, to automated results publication — within a single SaaS Platform. Features include automatic submission numbering, automated judge conflict-of-interest detection, and auto-generated results statistics.

Target: Local government culture & tourism departments and IT officers (running 2-5 competitions per year), public institution innovation support teams
Revenue Model: 800,000 KRW (~$600) per competition (based on 100 participants); annual unlimited license at 3,000,000 KRW (~$2,250)
Ecosystem Role: Supplier
MVP Estimate: 2_weeks

NUMR-V Scores

N Novelty
2.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 Novelty1-5How uncommon the service is in market context.
U Urgency1-5How urgently users need this problem solved now.
M Market1-5Market size and growth potential from proxy indicators.
R Realizability1-5Buildability for a small team with realistic constraints.
V Validation1-5Validation signal quality from competition and demand data.
Each dimension is scored 1-5 and weighted into grade S/A/B/C/D.
SaaS N=.15 U=.20 M=.15 R=.30 V=.20 Senior N=.25 U=.25 M=.05 R=.30 V=.15

Feasibility (70%)

Tech Complexity
29.3/40
Data Availability
20.6/25
MVP Timeline
20.0/20
API Bonus
0.0/15
Feasibility Breakdown
Tech Complexity/ 40Difficulty of core implementation stack.
Data Availability/ 25Practical availability and cost of required data.
MVP Timeline/ 20Expected time to ship a usable MVP.
API Bonus/ 15Bonus for viable public API leverage.
Total 100 points; below 50% is filtered out.

Market Validation (59/100)

Competition
8.0/20
Market Demand
9.4/20
Timing
14.0/20
Revenue Signals
10.5/15
Pick-Axe Fit
12.0/15
Solo Buildability
5.0/10
Validation Breakdown
Competition/ 20Signal quality from competitor landscape.
Market Demand/ 20Demand proxies from search and mention patterns.
Timing/ 20Fit with current shifts in tech, behavior, and regulation.
Revenue Signals/ 15Reference evidence for monetization viability.
Pick-Axe Fit/ 15How well the concept serves participants in a trend.
Solo Buildability/ 10Practicality for lean-team implementation.
Total 100 points; below 50 is filtered out.

Technical Requirements

Backend [medium] Frontend [medium] Infrastructure [low]
Dashboard