Console Certification and Store Submission Desk for Indie Game Studios

The problem

Indie studios build a good game and then lose weeks or months to console certification. Platform holders publish long technical requirement lists (PlayStation TRC, Xbox TCR, Nintendo Lotcheck) covering save handling, suspend and resume, controller disconnect, user account switching, trophy and achievement behaviour, and store metadata. A studio of three to eight people has never read these documents before, submits, fails on items that have nothing to do with gameplay, and misses a marketing beat or a seasonal sale window it already paid for.

Why now

Console porting has become the default revenue expansion for PC indies, and third-party porting quotes commonly sit in the low thousands per platform, which means a lot of studios port but almost none of them staff a compliance specialist. Review cycles for a clean Lotcheck submission commonly run several weeks, so a failed pass is expensive in calendar time, not just money. Meanwhile the requirement documents keep changing with each platform OS update, which rewards someone who reads them full time.

Who pays

Indie and small studios of 2 to 15 people in the US, UK, Canada, and Japan who have a shipped or near-shipped PC game and a console port either in progress or already contracted out, plus small publishers who handle several such titles a year.

How it makes money

Fixed-fee compliance passes per platform, typically a pre-submission audit, a remediation punch list, and a resubmission review. Price per platform in the same band as a porting engagement rather than above it, plus a retainer for studios shipping multiple titles or ongoing patch certification. Rush fees for studios inside a locked launch window.

Market & demand

Order-of-magnitude: thousands of games are approved on each console store per year, and only a fraction of those studios have in-house certification expertise. Capturing a few dozen engagements a year at four figures each supports a two to three person specialist shop; this is a deliberately small, high-margin niche, not a venture-scale market.

Porting has industrialised into a service category with published price ranges, but certification is still bundled loosely inside porting contracts or left to the studio. Handheld and hybrid hardware has added more requirement surface (suspend behaviour, docked and undocked resolution, input remapping). Small publishers increasingly outsource the whole submission chain rather than hire, which favours specialist desks.

SWOT

Competition & the gap

Porting studios such as Kokku and PolyCrunch Games that include some compliance work, dedicated certification QA vendors such as Kudos QA and iXie Gaming, and freelance producers who do this informally. Publishers with in-house cert teams handle it themselves.

The wedge: Certification as a standalone, fixed-price product for studios that already have a port in hand and only need to pass. Most existing options make you buy a whole porting or QA engagement to get compliance help.

Go-to-market

Work in the client's own dev environment and dev kits at first so you do not need your own platform approvals, then apply for developer status once you have references. Publish a free, genuinely useful public checklist of the most common submission failures per platform and let it do the lead generation.

First 10 customers: Do two engagements at cost for studios you meet in indie Discord servers and at events such as GDC, Develop:Brighton, or BitSummit, in exchange for a named testimonial. Then approach small publishers directly, since one publisher relationship yields several titles a year.

How to set it up

1. 1Get approved as a developer on at least one platform and read its current requirement documentation end to end
2. 2Build a per-platform pre-submission audit checklist and a repeatable report template
3. 3Define fixed-fee packages: audit, remediation punch list, resubmission review
4. 4Run two discounted engagements with studios that already have a port underway
5. 5Publish a public common-failures checklist and a short case study per platform
6. 6Approach small publishers for slate-level retainers

How to validate it

First-pass approval rate for clients you audited, studios returning for their next title, publishers moving from single-title to slate retainers, and inbound enquiries citing your public checklist.

Tools & inspiration

Companies in this space: Kokku, PolyCrunch Games, Kudos QA, iXie Gaming

FAQ