AI Game Grant Application Builder

3.35

Derivation Chain

Step 1 KOCCA AI game support program restructuring

→

Step 2 Indie game studio grant applications

→

Step 3 Application document automation tool

Problem

Indie game studios with fewer than 5 people applying for KOCCA's AI game support program (up to 300M KRW / ~$225K per project) must prepare 5-7 types of documents including business plans, technical development plans, and budget proposals. Developer teams without grant-writing experience either outsource to administrative agents (2-5M KRW / ~$1,500-$3,750) or spend 2-3 weeks writing themselves, with rejection rates exceeding 60% due to misalignment with evaluation criteria.

Solution

Users input basic project information (genre, AI integration approach, team composition, budget scale) and the system auto-generates draft business plans and technical development plans optimized for KOCCA evaluation criteria using an LLM. Prompts trained on patterns from previously funded projects provide an evaluator-perspective checklist, and budget allocation tables are automatically calculated.

Target: Founders and PMs of 1-5 person indie game studios, first-time AI game grant applicants (ages 20-30)

Revenue Model: Per Transaction at 99K KRW per application set (~$74, includes 3 revisions); Monthly Subscription at 190K KRW/month (~$142, unlimited generation)

Ecosystem Role: Supplier

MVP Estimate: 2_weeks

NUMR-V Scores

N Novelty

3.0/5

U Urgency

4.0/5

M Market

2.0/5

R Realizability

4.0/5

V Validation

3.0/5

NUMR-V Scoring System

N Novelty	1-5	How uncommon the service is in market context.
U Urgency	1-5	How urgently users need this problem solved now.
M Market	1-5	Market size and growth potential from proxy indicators.
R Realizability	1-5	Buildability for a small team with realistic constraints.
V Validation	1-5	Validation signal quality from competition and demand data.

SaaS N=.15 U=.20 M=.15 R=.30 V=.20 Senior N=.25 U=.25 M=.05 R=.30 V=.15

Feasibility (78%)

Tech Complexity

34.7/40

Data Availability

23.3/25

MVP Timeline

20.0/20

API Bonus

0.0/15

Feasibility Breakdown

Tech Complexity	/ 40	Difficulty of core implementation stack.
Data Availability	/ 25	Practical availability and cost of required data.
MVP Timeline	/ 20	Expected time to ship a usable MVP.
API Bonus	/ 15	Bonus for viable public API leverage.

Market Validation (53/100)

Competition

8.0/20

Market Demand

6.2/20

Timing

14.0/20

Revenue Signals

7.5/15

Pick-Axe Fit

10.5/15

Solo Buildability

7.0/10

Validation Breakdown

Competition	/ 20	Signal quality from competitor landscape.
Market Demand	/ 20	Demand proxies from search and mention patterns.
Timing	/ 20	Fit with current shifts in tech, behavior, and regulation.
Revenue Signals	/ 15	Reference evidence for monetization viability.
Pick-Axe Fit	/ 15	How well the concept serves participants in a trend.
Solo Buildability	/ 10	Practicality for lean-team implementation.

Technical Requirements

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

Dashboard