GoWindGoWind
Home
Framework
GoWind Toolkit
  • Open Source

    • GoWind Admin (Admin Platform)
    • GoWind CMS (Content Management)
    • GoWind UBA (Behavior Analytics)
    • GoWind Shop (E-commerce)
    • GoWind Kanban (Kanban Boards)
    • GoWind Ledger (Personal Finance)
    • GoWind ShortPlay (Short Drama)
    • GoWind Ops (Operations Platform)
    • RushWind (Rust Ecosystem)
  • Open Core (Community + Enterprise)

    • GoWind OA (Office Collaboration)
    • GoWind ERP (Procure-to-Pay)
    • GoWind WMS (Warehousing)
  • Commercial

    • GoWind IM (Instant Messaging)
    • GoWind IoT (IoT Platform)
    • GoWind Edu (AI Education)
    • GoWind MES (Manufacturing Execution)
    • GoWind CDC (Data Pipeline)
    • GoWind SDP (Zero-Trust Gateway)
    • GoWind Quant (Quant Research)
    • GoWind Trade Radar (Export Sourcing)
    • GoWind Game Radar (Game Greenlight)
  • 简体中文
  • English
GitHub
Home
Framework
GoWind Toolkit
  • Open Source

    • GoWind Admin (Admin Platform)
    • GoWind CMS (Content Management)
    • GoWind UBA (Behavior Analytics)
    • GoWind Shop (E-commerce)
    • GoWind Kanban (Kanban Boards)
    • GoWind Ledger (Personal Finance)
    • GoWind ShortPlay (Short Drama)
    • GoWind Ops (Operations Platform)
    • RushWind (Rust Ecosystem)
  • Open Core (Community + Enterprise)

    • GoWind OA (Office Collaboration)
    • GoWind ERP (Procure-to-Pay)
    • GoWind WMS (Warehousing)
  • Commercial

    • GoWind IM (Instant Messaging)
    • GoWind IoT (IoT Platform)
    • GoWind Edu (AI Education)
    • GoWind MES (Manufacturing Execution)
    • GoWind CDC (Data Pipeline)
    • GoWind SDP (Zero-Trust Gateway)
    • GoWind Quant (Quant Research)
    • GoWind Trade Radar (Export Sourcing)
    • GoWind Game Radar (Game Greenlight)
  • 简体中文
  • English
GitHub
  • GoWind Game Radar

    • GoWind Game Radar
    • Small-Studio Greenlight Math

Small-Studio Greenlight Math

This page is written from the perspective of producers, publishers, and lead designers. It explains the three decision tools Game Radar designs specifically for small teams: the niche-survival scan, same-tier survival math, and the greenlight sandbox (portfolio/single-bet). It contains no genre-specific conclusions and no performance figures.

Big studios play the macro game: head genres, mature tracks, long-term operations. Small teams face an entirely different problem — limited budgets, limited headcount, and possibly no second chance after a failure. Game Radar breaks this into three computable questions:

  1. Where do we stand — the niche-survival scan
  2. Can we survive there — same-tier survival math
  3. Should we build, how many, and how much each — the greenlight sandbox

1. The Niche-Survival Scan: Where Do We Stand

Each genre root gets a 0-100 "survival score", combined from four components:

ComponentQuestion it answers
Demand heatAre people discussing and searching this genre
Supply gapHow many teams are already building in it — is supply saturated
Head-brand breakabilityThe more scattered the leaders' buzz share (CR1), the wider the entry gap
Small-team-won evidenceAre there surviving games in the genre with small review counts — direct evidence that "a small team has won here"

The total is then discounted by three factors: supply floods (upcoming releases piling up), big-studio siphons (head titles sucking away buzz), and overall market cooling.

How to use: the decision weekly serves the survival-score TOP3 directly — not an abstract "genre popularity board", but a board of positions where a small team can stand. The companion same-tier survival math calculator lets you run break-even figures on any single candidate.

2. Same-Tier Survival Math: Can We Survive There

Enter three numbers: budget, price, and the benchmark genre. The system computes a break-even chain:

Budget → break-even units → break-even review count (converted via the ownership/review ratio) → compared against the review distribution of same-tier benchmarks (titles within 1/3× to 3× of the reference size) → a CLEAR / TIGHT / BELOW verdict:

  • CLEAR: teams of comparable size have survived on similar review counts — you can compute your margin
  • TIGHT: right on the break-even line, with almost no room for trial and error
  • BELOW: breaking even would require performance beyond same-tier common sense — proceed with caution

How to use: in greenlight meetings, don't debate "I think it can work" — debate "in this BELOW verdict, which assumption do we beat the benchmark teams on". Subjective disagreement gets forced onto concrete assumptions.

3. The Greenlight Sandbox: Which Games, How Much Each, When to Start

Portfolio mode

Enter total budget and planning horizon; get a portfolio recommendation:

  • Scored and ranked by scorecard × backtest × forecast, three factors
  • UA poison excluded with one veto
  • At most 2 projects per genre, staggered 60 days around supply floods
  • 80-20 budget allocation (capped at 40% per item)

Single-bet mode (the small studio's all-in view)

Only one recommendation, with a GO / WAIT / NO-GO verdict: the adopted item takes the full 80% pool without splitting, and reserves are used only for rescue — discipline before optimism. Suited to studios that can only run one project at a time.

4. Fake-Ad Concept Tests: One More Check Before Greenlight

Is the genre momentum real or inflated? Test it at the lowest possible cost:

  1. Register concept creatives (attached to entities/channels/images)
  2. AI creative brief: selling-point hooks, fake-trailer directions ×3, channel audiences, CTR baseline rules
  3. Backfill impressions/clicks per channel
  4. Auto-summarized, color-coded CTR, cross-checked against the signals' virtual backtests

If nobody clicks the concept art, the genre is cold no matter how hot it looks — data precedes investment.

5. The Greenlight Lens in the Decision Weekly

The scheduled decision weekly carries a dedicated "small-studio greenlight lens":

  • Survival-score TOP3: this week's most watchable niche positions
  • Lifecycle candidates: which lifecycle stage each candidate genre is in (emerging/rising/mature/declining), answering "will demand still be there when we finish"
  • Siphon timing alerts: when head titles will suck away buzz, so you avoid the head-on window
  • Single-bet discipline: whether an all-in project still meets its single-bet preconditions

Headed by an AI editor's note (publishing-director persona): who to【launch now】and who to【avoid】this week, a one-sentence scheduling verdict — turning the weekly from an information digest into a scheduling ruling.

Edit this page
Last Updated:: 11/4/26, 11:00 AM
Contributors: Bobo
Prev
GoWind Game Radar