How long is too long to spend on your indie game?
Practitioner analysis using release intervals as a proxy
Cole argues for smaller projects using a Steam release-history analysis. The useful methodological question is whether time between a studio's releases measures development time: overlapping projects, ports and different teams can break that assumption.
Use it forUse actual team schedules and staffing when estimating scope; treat release intervals as a research lead, not a verified production duration.
Do not concludeThe cohort excludes low-review games and first-project durations are unknown. A single observed release does not establish that a developer quit. The article's review-threshold claim is not adopted here as an official Steam rule.
Apply in a small-team experiment · 2 steps
Our proposed experiment—not a result measured by this article.
- Record development start, team changes and overlapping projects where disclosed.
- Preserve the article's review-count and release-date filters when discussing its sample.
References & how we used them
2 source references. “Used for” identifies where this page relies on each source; it does not mean the author endorses our interpretation. Historical access notes are not fresh verification.
- How long is too long to spend on your indie game?
Used for: Original article summarized in this research note; hard-data statements retain the source scope
Metadata from our earlier source note; not rechecked in this update. Public full article; older article newly added to the library. Check date: 2026-09-07.
https://gamemarketing.substack.com/p/how-long-is-too-long-to-spend-on - https://gamemarketing.substack.com/archive
Used for: Supporting context; our application steps are separate proposals
Article title, author and date not yet recorded; follow the exact URL.
https://gamemarketing.substack.com/archive
Public full article; older article newly added to the library