Page 5 of 6
Large organizations can spread risk across projects and support expensive marketing, specialist staff, localization, and ongoing development. Smaller teams may need fewer sales to cover a tightly controlled budget, but they can also be much more exposed to one missed release. None of these reports supplies a comparison of studio profitability that makes one size universally safer.
My expectation is continued experimentation with smaller teams, publishing partnerships, and co-development, alongside major franchises and some very expensive failures. It is a forecast, not a finding that AAA is about to collapse. The vulnerable project is the one whose cost assumes an audience it has not earned. That can happen in a multinational publisher or in a spare bedroom.
What This Means for Amorphous Arts
For Amorphous Arts, the point of this exercise is to change how we make decisions. I would use the evidence to set the following tests before expanding a project.
Describe the player in terms we can test. Identify a few relevant games, what their players value, and what we intend to offer differently. Then put a playable version in front of those people. Enthusiasm from friends is welcome, but it cannot carry the entire demand estimate. We need to learn whether the intended audience understands the game and wants another session.
Give discovery a place in production. A demo, readable screenshots, a useful store description, and a trailer that shows actual play are part of communicating the product. Plan them early enough that feedback can still change the game. Wishlists and positive comments are signals to investigate, not guaranteed purchases.
Build a budget around the whole obligation. Include development, adequate compensation, testing, accessibility, marketing, release work, and support. Estimate how many sales would cover those costs using expected net receipts per sale, allowing for discounts, refunds, platform charges, and any agreed revenue shares. Run a weak-launch case as well as the case we hope for. If survival requires a breakout, we should recognize that before hiring around it.
Buy the capability the project needs. Hire when a role has a funded purpose and an honest duration. A specialist contract or co-development arrangement may fit better than permanent expansion, but its scope and obligations still need to be clear. Equity, autonomy, and revenue sharing can be valuable parts of an arrangement; they do not pay this month’s expenses by themselves.
Protect the parts players will notice. Smaller scope should leave room for good controls, readable interfaces, coherent art direction, stable performance, and a satisfying core experience. Visual fidelity still matters when it serves the game. Adding more assets simply because we can is a poor reason to lengthen production.
These are my operating conclusions, not a recipe validated by the reports. A focused game can fail. A well-run small studio can run out of money. Testing an audience and controlling costs improve the questions we ask; they do not remove uncertainty.
What would change my outlook? Evidence that new releases were capturing substantially more sustained attention, that financing was reaching a broader range of viable teams, or that typical small-studio returns were improving would all matter. More releases and a handful of success stories, by themselves, would not answer those questions.