B

Contest Proposal Auto-Assembler

3.30

Derivation Chain

Step 1 Expansion of public data utilization contests
→
Step 2 Surge in contest participants
→
Step 3 Tools to improve proposal writing efficiency for participants

Problem

Local governments and public institutions hold hundreds of public data utilization contests annually, and college students and startup participants write proposals with similar structures from scratch each time. Since submission formats, evaluation criteria, and required items vary by contest, they spend 2-3 hours just understanding the format, 10-15 hours on actual writing, and an additional 3-4 hours searching for suitable datasets in the public data API list.

Solution

Enter the contest announcement URL, and it automatically parses the evaluation criteria and submission format, recommends suitable datasets from the public data portal API catalog, and auto-generates a proposal draft section by section. It provides a score prediction feature for each evaluation item based on analysis of past winning entries.

Target: College students (20s-30s) participating in public data utilization contests, and early-stage startup teams of 1-3 people.
Revenue Model: Premium model: Free (2 proposals per month), Pro $22 per month (unlimited generation + winning pattern analysis), per-transaction payment $3.75 per proposal.
Ecosystem Role: Infrastructure
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.8/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
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

Backend [medium] AI/ML [medium] Frontend [low]
Dashboard