Small developers have more routes to market than ever and face harder discovery conditions.
Self-publishing
Full control, full revenue and full responsibility for marketing.
Which most small teams are poorly equipped for.
Indie publishers
Funding, marketing and platform relationships for a revenue share.
Which is the most common route for teams wanting reach.
Platform funding
Storefronts and console holders funding exclusives.
Which trades availability for money and visibility.
Festivals and awards
Recognition producing meaningful discovery.
What a publisher actually provides
Funding, marketing, storefront relationships, localisation, porting, quality assurance and someone who has done this before.
Which for a first-time team is worth a great deal more than the revenue share appears to cost.
Teams who self-publish successfully usually either have marketing expertise already or an existing audience.
Deal terms
Recoup structures, rights and creative control.
Which vary enormously and warrant legal review.
Marketing before release
Building visibility over months rather than at launch.
Which is the single most common thing small teams underestimate.
Demos and playtests
Public builds generating wishlists and feedback.
Realistic expectations
Most games not returning a living wage for the time invested.
What determines whether a small game succeeds
A clear hook that can be understood from a short video, visibility built before launch, and a finished product that reviews well early.
Which is a demanding combination and does not include being innovative or personally meaningful.
Many excellent small games fail on the first of those three, having been designed to be played rather than to be described.
Wishlists as a predictor
Pre-launch interest correlating with early sales.
Which developers track closely.
Press and creators
Coverage from outlets and streamers.
Which is largely earned through the hook.
Scope discipline
Finishing being the hardest part for small teams.
Financial planning
Runway for the full development period.
The uncomfortable arithmetic
A two-person team spending three years on a game needs it to earn several years of salary to have been worth doing financially.
Which the great majority of small releases do not achieve.
That is not a reason not to make games, and it is a reason to go in with the numbers understood rather than discovered afterwards.
Part-time development
Building alongside other income.
Which is how most successful small games actually get made.
Community building
An audience developed during production.
Which is the most reliable predictor of a reasonable launch.
Contracts and rights
Legal review before signing anything.
Which is inexpensive relative to the consequences.
Support organisations
Development networks and grant bodies in many regions.
A note on how this industry reports itself
Games is an unusually opaque business for one with such a visible product. Budgets are rarely disclosed, sales figures are announced selectively, player numbers are quoted in whichever metric flatters, and profitability is almost never stated at all.
Most of what is publicly known comes from court filings, leaked documents, regulatory submissions and former employees speaking after the fact. That material is reliable when it exists and covers a small fraction of the industry, which means any general claim about how games perform commercially rests on a limited and non-random sample.
Why the production side is worth understanding
A great deal of frustration with games comes from decisions that look inexplicable from outside and are entirely predictable once the structure is visible. Why a game shipped unfinished, why a beloved studio was closed after a successful release, why a sequel dropped features the previous game had, why a service shut down two years in.
None of these are mysteries. They are the outcomes of funding structures, platform economics, portfolio decisions and the fact that games are made by people working to schedules set before anyone knew what the game would be. Knowing that does not make the outcomes better; it does make them legible.
Where the better information is
Developer conference archives are the single best public source on how games are actually made, and a large number of talks are freely available. Regulatory filings during acquisitions have disclosed more real financial detail than a decade of press releases. Trade publications with named industry sources are considerably more informative than consumer coverage on business questions.
One thing worth remembering
Games are made by people, mostly people who care a great deal about them, working inside commercial structures they did not design and frequently cannot change.
Criticism of a game is fair. Criticism of the decisions behind it is usually aimed at the wrong floor of the building, and the people who take it are rarely the people who made them.
Further reading
Developer conference archives, postmortems written by the people who shipped the projects, and trade reporting with named industry sources are the three places where this material is covered properly and in public. All three are freely available, and none require any technical background to follow.