GDnD Wiki

GDnD Wiki

This site is for Ulster University students and staff. Enter the class access password to continue.

Game Industry Realities

10 min read

Summary

The commercial and career realities of game development are frequently obscured by availability bias. We remember the successes, not the failures. This page covers the practical business side of making games: how money flows through a project, what different career paths look like, what the data says about crunch and why market luck matters more than the industry usually admits.

(Hiwiller, Players Making Decisions, Ch. 33–34, see source-players-making-decisions)

Profit and loss basics

A Profit and Loss (P&L) statement maps expected revenues against expected costs across a range of scenarios. Hiwiller’s worked example is a hypothetical mobile racing game priced at $2:

Worst caseAverageBest case
Units sold5,00020,000500,000
Sales$10,000$40,000$1,000,000
Less platform cut (30%)(3,000 USD)(13,333 USD)(300,000 USD)
Total revenue$7,000$27,667$700,000
Staff costs$900,000$960,000$960,000
Production costs$10,000$10,000$10,000
Marketing costs$90,000$90,000$90,000
Total costs$1,060,000$1,060,000$1,060,000
Profit / (Loss)($1,053,000)($1,032,333)($360,000)

Even the best-case scenario results in a loss for a 9-person team over a year. This is a small project (96 man-months). The table illustrates why commercial game development requires either substantial investment, a very small team, or a free-to-play model with strong conversion.

Key cost inputs

  • Platform cut: Apple App Store and Google Play both take 30% of revenue. Similar cuts apply to console platforms (Sony, Microsoft, Nintendo). This is non-negotiable for most developers.
  • Man-month cost: A widely-used heuristic is $10,000 per staff member per month. This includes salary, health benefits, payroll taxes and per-seat software licences, not take-home pay alone. It varies by role and location.
  • Marketing: Organic discovery is extremely difficult in a market where thousands of games release monthly. Cost of acquiring a single user who opens an app three or more times was estimated at 90,000, with no guarantee of sustained performance.
  • Sales estimates: Use comparable titles in the same genre and platform as the basis for unit projections. Do not use gut feel.

The cash flow trap

A studio can be building a profitable game and still go insolvent. The mechanism is cash flow: the gap between when money goes out and when it comes in.

Worked example (Hiwiller, Ch. 33):

A team releases a game through a publisher. Publisher royalties are paid 60 days in arrears (January revenue arrives in March). The game doubles its user base every month. Server costs scale with users at 100k/month fixed. Team starts with $2M in reserve.

JanFebMarAprMay
Users100k200k400k800k1.6M
Starting balance$2,000,000$1,800,000$1,500,000$1,200,000$700,000
Publisher payment$0$0$200,000$400,000$800,000
Staff costs($100,000)($100,000)($100,000)($100,000)($100,000)
Server costs($100,000)($200,000)($400,000)($800,000)($1,600,000)
Ending balance$1,800,000$1,500,000$1,200,000$700,000($200,000)

In month 5, the studio cannot make payroll despite having a growing, profitable game. The P&L looks healthy. The bank account is empty. This is not a hypothetical failure mode: cash flow crises have closed real studios with good games in the market.

Implications:

  • Publisher payment terms (60–120 day delays) are a structural risk for small studios
  • Rapid user growth can accelerate insolvency if server/infrastructure costs scale faster than revenue arrives
  • Studios need either significant cash reserves, a line of credit, or publishing advances to survive the lag
  • When evaluating a deal, ask two questions: “how much?” and “how soon?”

Break-even exercise

Break-even is the point where net revenue has covered the project’s cost. It is not the same as total sales revenue, because the platform, taxes, refunds, discounts and publisher recoup can all reduce the money that reaches the developer.

Use this simplified teaching version first:

InputValue
Development budget£30,000
Launch price£12
Platform cut30%
Net revenue per full-price sale£8.40

Calculation:

net revenue per unit = price * (1 - platform cut)
net revenue per unit = £12 * 0.70 = £8.40
 
break-even units = budget / net revenue per unit
break-even units = £30,000 / £8.40 = 3,571.43

The game needs 3,572 full-price sales to break even in this simplified model.

Practice

Recalculate the same project under two conditions:

  1. The game launches at a 25% discount.
  2. The team spends an extra £5,000 on localisation and trailer editing.

Assume platform cut stays at 30% and ignore tax for the exercise.

Answers

  1. Discounted price is £9. Net revenue per unit is £6.30. Break-even is £30,000 / £6.30 = 4,761.90, so the team needs 4,762 sales.
  2. New budget is £35,000. At full price, break-even is £35,000 / £8.40 = 4,166.67, so the team needs 4,167 sales.
  3. If both conditions apply, break-even is £35,000 / £6.30 = 5,555.56, so the team needs 5,556 sales.
  4. The practical lesson is that discounts and extra costs move the target quickly. A student pitch should name these assumptions rather than hide them behind optimistic sales numbers.

(Hiwiller, Players Making Decisions, Ch. 33, see source-players-making-decisions)

Career paths

AAA digital game development

A viable middle-class career is possible in art, animation, programming, design, QA, and production management at established studios. Pay is competitive but typically lower than equivalent roles in tech or finance. Studios generally provide health benefits and fringe benefits.

The crunch problem: “Crunch” means extended working hours, sometimes up to 16 hours a day and seven days a week. It is endemic to AAA development. Causes include poor planning, scope creep, management dysfunction, disrespect between disciplines and schedule pressure from publishers.

What the data actually says: The Game Outcomes Project analysed a wide database of commercial projects and found, unambiguously, that crunch worsens outcomes:

Projects made without crunch scored higher on both subjective outcomes (team satisfaction with the game) and objective outcomes (Metacritic score, financial return on investment). — Game Outcomes Project, Part 4 (Tozour, 2015)

Multiple studies confirm: extended hours provide a brief early boost in output, fully offset by reduced productivity later. A greater-than-40-hour week does not increase net productivity. Henry Ford understood this by 1914.

The industry’s demographic profile reflects the cost: 70% of game developers are under 34. Many experienced professionals leave the industry when family responsibilities make the hours unsustainable. They have not necessarily lost interest in games.

What great teams do (Game Outcomes Project, Part 5):

  • Maintain a clear, shared vision of the game, the single most important factor in project success
  • Understand and manage risk rather than deferring it
  • Actively avoid crunch as a cultural norm. Teams that accept crunch as normal consistently underperform
  • Create psychological safety so team members can flag problems and experiment without fear
  • Give team members autonomy over how their work is executed
  • Resolve conflicts promptly rather than letting them accumulate
  • Minimise turnover because institutional knowledge is irreplaceable
  • Provide timely, relevant feedback on work (including code reviews)
  • Hold themselves consciously accountable to high standards

These are measurable, learnable practices. They are also a useful checklist for evaluating potential employers during a job search.

Indie digital game development

Independent development offers creative freedom and direct ownership of intellectual property at the cost of financial security. The economics are shaped by power law distribution:

App Store (iOS) distribution (2015 data):

  • Top 870 apps out of 1.2 million (0.07%) earned 40% of all revenue
  • Fewer than 3,200 apps (0.26%) generated enough revenue to match the median US household income
  • Bottom 47% of apps earned under 100 USD/month

The median indie game earns very little. The existence of Minecraft (Markus Persson sold Mojang to Microsoft for 50,000/day in ad revenue at peak) or Canabalt does not change the underlying distribution. Power laws produce extreme outliers, which makes the average misleading. The median is the honest reference point.

Viable models for indie sustainability:

  • Contract/freelance work alongside personal projects. Canabalt’s Adam Saltsman used this model
  • Crowdfunding (Kickstarter, etc.): competitive and requires audience before launch
  • Grants and fellowships: increasingly available but competitive
  • Work-for-hire / ports: reliable income with limited creative ownership

Tabletop game development

The analogue game design market is significantly smaller than digital. Approximately 20 people worldwide make a full-time living as tabletop game designers (Tom Vasel, The Dice Tower, estimated). Payment is typically royalty-based, similar to book publishing. The market for tabletop games, while growing, remains niche relative to digital.

Most tabletop designers operate as hobbyists or part-time workers. Pursuing tabletop game design as a primary income without supplemental income is not prudent at this stage of the market’s development.

Market luck

The industry has a structural bias toward survivorship: Game Developers Conference (GDC) talks are dominated by studios whose games succeeded that year. The talks are not titled “we got lucky”. They are titled with advice that implies their success was reproducible. This is confirmation bias combined with selection bias.

“Every GDC is glutted with talks about how an indie studio was successful that year with the hidden subtext — although often not hidden, nor subtext — that if you just complete the same steps as they did, you’ll be successful too.” — Hiwiller, Ch. 34

Games that were well-made and commercially unsuccessful, or commercially successful but poorly designed, are systematically underrepresented in industry discourse. We do not name the thousands of well-polished games that failed in the same market conditions that launched an unlikely hit.

Over 11,000 games were submitted to the iOS App Store in February 2015 alone. If good design and execution were sufficient conditions for commercial success, the average game would earn a sustainable income. It does not.

The honest position: Hard work on design and implementation is a necessary condition for success. It is not sufficient. Market timing, platform visibility, social graph position, critical coverage and pure chance all have material effects. Temple Run was lucky in a crowded market of endless runners. Its clones, even mechanically superior ones, largely failed. Flappy Bird’s viral growth was not reproducible by design.

This is not a reason to stop making games. It is a reason to:

  • Not internalise commercial failure as evidence of design failure
  • Not treat commercial success as proof of a reproducible formula
  • Seek sustainability through multiple income streams rather than betting everything on a single release
  • Build skills and portfolio rather than chasing trends, because trends are already over by the time you see them

Implications

  • A realistic P&L, built from comparable titles rather than wishful assumptions, is the first design document for any commercial project.
  • Cash flow management is a survival skill distinct from profitability management. Know your payment terms before signing anything.
  • Crunch is not a necessary cost of making great games. The data shows the opposite. Studios that normalise crunch are both exploiting workers and making worse games.
  • The Pareto distribution of game revenue means that career sustainability in games almost always requires either diversified income (freelance, contract, teaching) or institutional employment (AAA studio, publisher), not single-product indie revenue.
  • Market luck is real and substantial. Build resilience, not dependence on a single outcome.

These implications connect directly to the newer pipeline pages: publishing-and-funding for choosing between self-publishing, publishers and crowdfunding, game-marketing-fundamentals for audience-building reality and legal-and-business-basics for the ownership, payment-term and credit issues that often become visible only when projects become commercial.

Open questions

  • As AI tools reduce production costs and timelines, will the economics of small-team indie development improve, or will the market flood with more titles and maintain the power law?
  • The Game Outcomes Project data is from 2015. Does it hold in a post-pandemic, post-crunch-awareness industry where many studios have made public commitments to sustainable development?

Graph View

Backlinks