B

Public Data Startup Guide

3.30

Derivation Chain

Step 1 Distribution of public data disclaimer guide
→
Step 2 Entry barrier for 40-60s retirees using public data for startups
→
Step 3 Automatic matching of public APIs to my business idea + usage guide

Problem

A person in their 50s preparing for a solo startup after retirement who wants to find usable APIs for their business idea on the public data portal (data.go.kr) must manually browse through over 2,000 APIs, and understanding API specs, obtaining authentication keys, and testing calls takes an average of 3-5 days. Although a public data disclaimer guide has been distributed to reduce legal burden, there is no practical guidance on 'what data can be used and how,' so most give up.

Solution

Enter 'my business idea' in natural language on the web (e.g., 'pet walking routes in my neighborhood'), and it automatically recommends 5-10 highly relevant APIs from over 2,000 public APIs, providing step-by-step guidance on each API's easy explanation, usage examples, and how to obtain an authentication key. It also presents 3 'service examples you can build with this data' to inspire you.

Target: Retirees or pre-retirees in their 50s-60s, solo startup aspirants who are not IT majors but interested in web services, and those interested in using public data but feeling the entry barrier.
Revenue Model: Free API recommendations and basic guide. Business plan auto-generation + API integration code snippet package at 5,000 KRW per transaction (approx. $3.75).
Ecosystem Role: Education
MVP Estimate: 2_weeks

NUMR-V Scores

N Novelty
3.0/5
U Urgency
3.0/5
M Market
3.0/5
R Realizability
4.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.
N=.15 U=.20 M=.15 R=.30 V=.20

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

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