B

Public Data Cross-Validation Engine

2.85

Derivation Chain

Step 1 #1 in digital government · public data reuse challenge
→
Step 2 Public data reuse services
→
Step 3 Reliability issues with reprocessed data
→
Step 4 Cross-validation tool for multiple public data sources

Problem

Startups (approximately 200-300) running Real Estate, transportation, and safety services built on public data face a problem where different government agencies provide conflicting values for the same subject (e.g., 15-20% discrepancy rate between Ministry of Interior and Ministry of Land building data). This causes 5-10 customer trust complaints per month on average, and manual cross-validation takes about 3 hours per case.

Solution

Automatically matches 2-5 public data sources on the same topic to detect discrepancies, classifies discrepancy types (timing differences, criteria differences, errors) and recommends the 'most reliable value.' Provides a discrepancy status dashboard and customer-facing explanation document templates.

Target: Startups operating B2B/B2C services built on public data (3-20 employees, IT/PropTech/Mobility)
Revenue Model: Free up to 3 data source pairs, ~$37/mo (~49,000 KRW) for up to 10 pairs, ~$89/mo (~119,000 KRW) for up to 30 pairs. Includes auto-generated customer response documents.
Ecosystem Role: Infrastructure
MVP Estimate: 2_weeks

NUMR-V Scores

N Novelty
3.0/5
U Urgency
3.0/5
M Market
2.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 (54/100)

Competition
8.0/20
Market Demand
9.4/20
Timing
14.0/20
Revenue Signals
7.5/15
Pick-Axe Fit
10.5/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

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