B

Public Data Mashup Business Plan Builder

3.35

Derivation Chain

Step 1 #1 Digital Government · Public data reuse mandate
→
Step 2 Government policy promoting public data-driven startups
→
Step 3 Automated business plan generator for aspiring entrepreneurs

Problem

Aspiring entrepreneurs preparing public data-driven startups (approximately 2,000 annual competition participants) spend an average of 3-4 weeks figuring out which combinations of data.go.kr's 20,000+ APIs can be assembled into viable services. The need to separately verify API specs, pre-validate data quality, and design revenue models causes a 60%+ dropout rate at the initial planning stage.

Solution

Enter industry and target customer keywords to auto-match relevant public data APIs, then generate 3-5 service ideas per data combination using LLM. For the selected idea, produce a draft business plan (PDF) within 30 minutes—including technical implementation difficulty, estimated costs, and revenue model.

Target: Public data startup competition applicants; solo developer aspiring entrepreneurs (ages 20-30s, IT sector)
Revenue Model: ~$7.50 per business plan generated; unlimited monthly plan ~$29. Competition season (Mar-May, Sep-Nov) promo price ~$5/plan
Ecosystem Role: Education
MVP Estimate: 2_weeks

NUMR-V Scores

N Novelty
2.0/5
U Urgency
3.0/5
M Market
3.0/5
R Realizability
4.0/5
V Validation
4.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.4/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 (60/100)

Competition
8.0/20
Market Demand
9.4/20
Timing
14.0/20
Revenue Signals
10.5/15
Pick-Axe Fit
10.5/15
Solo Buildability
8.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 [low] AI/ML [medium]
Dashboard