CompYa Tournament Management Tool

3.40

Derivation Chain

Step 1 CompYa (computer programming baseball) search volume surge

→

Step 2 Growing demand for amateur eSports tournaments

→

Step 3 SaaS for automating small-scale tournament operations

Problem

Organizers (YouTubers, community managers) hosting amateur tournaments in niche eSports communities like CompYa currently manage participant recruitment, bracket generation, match result recording, and prize settlement manually using Excel and Discord. Running a single 32-64 person tournament takes 10-20 hours of operational time, and bracket errors or settlement disputes are frequent.

Solution

A one-stop SaaS for small-scale eSports tournament operations that provides participant recruitment forms, automatic bracket generation, real-time match result entry, automatic leaderboard updates, and prize settlement. Includes Discord bot integration for automatic tournament notifications and result posting, plus a live dashboard URL sharing feature.

Target: Organizers of amateur eSports tournaments in niche games like CompYa and FIFA Online, gaming YouTubers and streamers, school and club tournament staff

Revenue Model: Free (up to 16 participants) + Premium (32+ participants) 19,000 KRW (~$14) per tournament, Pro (unlimited + custom branding) 49,000 KRW (~$37) per month

Ecosystem Role: Supplier

MVP Estimate: 2_weeks

NUMR-V Scores

N Novelty

4.0/5

U Urgency

3.0/5

M Market

2.0/5

R Realizability

5.0/5

V Validation

2.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.

N=.15 U=.20 M=.15 R=.30 V=.20

Feasibility (69%)

Tech Complexity

29.3/40

Data Availability

19.4/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 (52/100)

Competition

8.0/20

Market Demand

6.2/20

Timing

10.0/20

Revenue Signals

7.5/15

Pick-Axe Fit

10.5/15

Solo Buildability

10.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 [medium] Infrastructure [low]

Dashboard