Console certification-readiness tracker automating TRC checklists and test-matrix sign-off for game studio producers and QA leads shipping builds to Steam, Xbox, and PlayStation. · Game Dev Compliance
DEAD SLOW · CAUTIOUS
5.4 ShipScore / 10
Time strongest as productized SaaS; control weakest — platform NDAs own the checklists.
Condition: Three console-shipping studios or porting houses must pre-pay before you touch NDA'd requirement content.
Part I — The Verdict what the instruments read
01 — The ShipScore breakdown
Control
4
C4 — TRC/XR/Lotcheck content sits under Sony/Microsoft NDA control.
Entry barriers
6
E6 — no tracked rival or funded player; platform relationships could become moat.
Need
5
N5 — zero Reddit, X, or corpus signal; idea-level demand unproven.
Time-freedom
7
T7 — SaaS tracker, but per-SDK requirement updates stay manual.
Scale
5
S5 — only a few thousand console-shipping studios worldwide.
What the five commandments measure
C — Control
Do you own the customer, or does a gatekeeper stand between you and revenue?
E — Entry
How hard is this to copy once it works? A rival's existence isn't the question — the durability of their advantage is.
N — Need
Is demand proven with money rather than vibes?
T — Time
Can income detach from your hours, or did you buy yourself a job?
S — Scale
How far does it reach without linear cost?
Scored on the evidence below, against CENTS as we've adapted it plus a Buffett-style moat reading of every rival — the same referee for every idea, including the ones we generate ourselves. The verdict follows the arithmetic: we never relabel a score to make it read better, and the weakest commandment is always named. The exact rubric stays in-house so the scale can't be written for.
02 — The pace test — $1M/yr
At $149/mo (assumed category price), you need 560 subscribers for a $1M/yr pace.
No tracked rivals with verified revenue to benchmark against.
Part II — The Evidence the receipts, good and bad
03 — Rival scan
No similar products found in the radar corpus — either genuinely novel, or too small to track.
No tracked rival in corpus — Empty radar means no validation either — nobody is proving anyone pays here.
Incumbent test-management tools (general knowledge) — QA leads already own TestRail/Jira/Xray seats; cert becomes a template, not a purchase.
Internal spreadsheets and platform partner portals — Free, already NDA-compliant, and the default habit for producers at submission time.
04 — Demand evidence
No radar-tracked similar products found — zero verified MRR anywhere in this space.
No funded companies tracked in or near game dev compliance tooling.
Reddit returned no signals for these keywords; X chatter is explicitly near-zero.
Evidence is thin, not negative: absence of signal here is uncertainty, not proof of no demand.
05 — Risks
TRC/XR requirement text is NDA-protected; hosting or templating it may be legally barred.
Console cert cycles are episodic — studios may buy per-project, not monthly.
Total addressable buyer count is small; sales cycles into studios are long.
Requirements change each SDK release, forcing ongoing manual curation that erodes margins.
06 — Kill switches — what kills this with one decision
Sony/Microsoft/Nintendo developer relations — One NDA-enforcement letter forbids redistributing TRC checklists, gutting the core content.
Platform partner portals adding native cert-tracking — First-party ships it free inside the submission flow; product becomes redundant overnight.
Part III — The Plan if you insist on proceeding
07 — What this scan can't tell you
Cannot tell whether studios budget for cert tooling separately from QA licenses.
Cannot confirm the legal boundary for templating NDA'd TRC/XR requirement text.
No data on how many titles per year hit console cert per studio.
Scores judge the market and business model — not your ability to execute. Verified MRR = independently tracked revenue; reviews/upvotes = platform-reported. Judged 2026-08-31.
08 — The wedge & the next step
Bring-your-own-requirements engine sold to porting houses and co-dev studios who run cert repeatedly across many clients.
Cheapest next step: Book ten calls with console QA leads and porting-house producers this week; ask what their current cert spreadsheet costs them in failed submissions.
Not quite it? Spin the model
Business-model variations of this idea, engineered to beat 5.4 — different vertical, audience, model, or wedge. Same harsh scale. Pro feature.
One evidence-backed gap a day, free
Close — but conditional. Every morning the engine files one mined gap, scored on the same harsh scale as this one. Free at 7am AEST, unedited.
Free forever · one email a day · unsubscribe in one click.
Monitor this idea
Weekly re-scan against the live corpus. If the market moves this ShipScore by a point, or flips the verdict, you hear about it. Free while we're small.