Why Indie Teams Fall Apart at Month 6 (And How to Build Around It)

Month 6 is when indie teams quietly implode. Not month 1, when everyone's hyped on the Figma board. Not month 12, when you're already shipping or already dead. Month 6: the exact point where the prototype works, the scope has tripled, the savings account is thinner, and someone on the team has started replying to messages 18 hours late.

I've watched this pattern repeat across dozens of small teams. The trigger isn't talent or ambition. It's structural. Indie game team conflict at month 6 follows a script, and once you see the script, you can write around it.

The Month 6 Cliff Is Predictable, Not Personal

Here's the timeline most 2-to-6 person indie teams actually live through:

• Months 1-2: Vertical slice energy. Everyone overdelivers. Discord is loud.
• Months 3-4: First real disagreements about scope. Resolved by someone (usually the founder) eating the extra work.
• Months 5-6: The fun part is done. What remains is content production, polish, marketing, and the boring middle of the game. Energy collapses.
• Month 6+: Someone goes quiet. Someone else gets resentful. A founding member "takes a break". The team is now 60% of what it was.

The 2024 GDC State of the Game Industry survey, covered by Game Developer, flagged burnout and unclear scope as the top reported reasons devs left projects. That's not a AAA problem leaking down. It's worse at indie scale because there's no HR, no producer, no scheduled retrospective. Just a Discord server going dark.

The mistake is treating this as a people problem. It's a system problem. You designed a team with no shock absorbers, and month 6 is the first real shock.

The Four Root Causes Nobody Names Out Loud

1. Equity Was Decided Before Anyone Did the Work

Most indie splits are set in week 2: "We're three founders, so 33/33/33, cool?" Then by month 6, one person has shipped 80% of the code, another has been MIA since the trailer, and the third quietly took a contract job to pay rent. The cap table no longer reflects reality, and everyone knows it, and nobody wants to be the one to bring it up.

Indie game team conflict almost always has an unspoken equity grievance underneath. The fix is vesting. Even a handshake studio can write a one-page agreement: equity vests over 24 to 36 months, with a cliff. If you leave at month 6, you walk away with a fair slice, not a third of the company you stopped working on. GamesIndustry.biz has covered multiple small-studio postmortems where the founding fracture was, at root, an unvested split nobody renegotiated.

2. Nobody Defined "Done"

ConcernedApe shipped Stardew Valley alone partly because he was the only person who had to agree on what "finished" meant. In a team of four, "the combat feels good" can mean four different things. By month 6, those four interpretations have produced four diverging mental models of the game. Arguments that look like taste fights are actually spec fights with no spec.

Write a one-page design pillar doc. Three pillars, max. Every feature gets weighed against them. When someone proposes "what if we added a roguelike mode", the pillar doc answers, not the loudest voice in the call.

3. The Founder Bottleneck Becomes a Founder Resentment

In months 1-4 the founder reviews everything, approves everything, and rewrites half of it. That feels like leadership. By month 6 it's a bottleneck, and the rest of the team has either checked out ("why bother, they'll redo it") or started shipping around the founder ("I'll just commit it and apologize later"). Both outcomes end the team.

4. The Money Conversation Never Happened

Most indie teams start with "we'll figure out money later". Later is month 6. Someone's savings are gone. Someone else got a freelance offer. Nobody knows if there's a salary plan, a rev-share floor, or just hope. According to industry reporting on GamesIndustry.biz, runway misalignment is one of the most cited reasons small teams dissolve before launch, and it almost always surfaces in the second half of year one.

How to Build a Team That Survives Month 6

Hire (or Co-Found) for the Boring Middle, Not the Vertical Slice

Most indie teams are assembled for the exciting part: prototype, art style, core loop. Then month 6 hits and you realize nobody on the team actually wants to build the inventory UI, write 200 lines of barks, or do the Steam page SEO. Resentment grows because the work that's left is the work nobody signed up for.

When you're forming the team, ask explicitly: who owns the unfun 40%? If the answer is "we'll all chip in", you don't have an answer. If you're a solo founder looking for the right collaborator for the production grind (not just the prototype sprint), you can post a rev-share or paid role and review portfolios on open roles at indie studios on Crewforge. Filter for people whose past work shows shipped games, not just attractive concept art.

Run a Monthly Honest Retro, Even With Two People

30 minutes, once a month, three questions:

• What's draining you right now?
• What do you think the rest of us are getting wrong?
• If you quit this week, what would be the reason?

That last question is the one. Ask it before month 6, not after. The point isn't to manufacture drama, it's to surface the silent grievances that compound into a month 6 exit. Postmortems on GDC Vault from solo devs and small teams repeatedly hit the same note: "we didn't talk about it until it was too late."

Write the Operating Agreement Even If You're Best Friends

One page. Covers:

• Equity split and vesting schedule
• What happens if someone leaves at month 3, 6, 12, 18
• Who owns the IP if the studio dissolves
• How decisions get made when you can't agree (tiebreaker, domain ownership, or veto rules)
• Money: when does anyone get paid, from what pool, in what order

This document feels paranoid in month 1. It feels priceless in month 7. Lucas Pope works solo partly because he's seen how messy the alternative gets without these guardrails. You don't need a lawyer for v1. You need a shared Google Doc that everyone signs digitally and revisits every six months.

Decouple Identity From Role

On a four-person team, the "programmer" is also the build engineer, the localization manager, the analytics person, and the one who fixes the website. By month 6, that programmer is exhausted in five different directions and has no clean win to point at. Define primary and secondary roles. Acknowledge that one person wearing five hats isn't a flex, it's a fragility.

What Healthy Small Teams Actually Do Differently

Sokpop Collective has shipped dozens of games as a four-person collective because their structure assumes individual ownership. Each member can lead a project. They don't all touch every game. Conflict is reduced because territory is clear. That's a design decision, not a personality fit.

Increpare Games (Stephen Lavelle) and ConcernedApe both default to solo because they've optimized for zero coordination cost. That's a valid answer too. If you can't build the team structure to survive month 6, the rational move might be staying solo and contracting out the gaps, not forcing a co-founder relationship that will combust.

If you're between those poles, a hybrid model works: one or two core founders with vested equity, plus rotating contractors paid per milestone. The itch.io ecosystem and Steam Next Fest (next edition October 2026) are full of games shipped this way. Stable core, flexible edges.

The Communication Cadence That Prevents the Cliff

Most indie teams over-communicate in month 1 (constant Discord pings) and under-communicate by month 5 (only async commits, no real conversation). Flip the pattern:

• Weekly: 30 min sync. What shipped, what's blocked, what's next. No vibes, just status.
• Monthly: The honest retro described above.
• Quarterly: Scope review. Look at the original plan. Compare to reality. Cut something on purpose. If you cut nothing every quarter, you're not actually scoping, you're accumulating debt.

This rhythm catches indie game team conflict early, when it's still a sentence in a retro doc and not a Slack DM that ends with "I think I need to step back from the project."

If You're Already at Month 6 and It's Cracking

First: it's not over. Most teams that survive a month 6 crisis end up stronger because they finally had the conversation. The teams that die are the ones that pretend everything's fine until someone just stops showing up.

Concrete moves, in order:

1. Call a 90-minute meeting with one agenda item: "are we still aligned?" No game design talk. No sprint planning. Just: does each person still want to ship this game with this team?
2. Put the cap table on the table. If the original split no longer reflects contribution, renegotiate. A 40/35/25 split that everyone believes in beats a 33/33/33 that two people resent.
3. Cut scope by 30% minimum. Not 10%. Not "we'll see". A real cut. The features you cut in month 6 are the features your players never knew they were missing.
4. Decide the money question explicitly. Who's still all-in financially? Who needs to go part-time? Who needs to be paid a stipend from a publisher advance or a grant? If the answer is "nobody can keep going at this rate", that's the answer, and pretending otherwise just delays the collapse by two months.
5. If you need to replace a role, do it now, not in month 9. A founder leaving is survivable. A founder leaving while you're three weeks from a Steam Next Fest demo deadline is not. If you need to bring someone in fast, create a studio profile and post the role with honest expectations: this is a project in month 6, here's the state, here's what we need.

Authoritative postmortems on Game Developer and indie project archives on IndieDB are full of teams that hit this exact wall and either rebuilt or quietly disbanded. The difference between the two outcomes is rarely talent. It's whether anyone called the meeting.

The Uncomfortable Takeaway

Indie game team conflict at month 6 is not a sign you picked the wrong people. It's a sign you built a team for the easy half and never designed the hard half. The fix is structural: vesting, written agreements, honest retros, scope discipline, and an explicit conversation about money before anyone runs out of it.

Pick one of these to do this week. Not all five. One. The vesting agreement, or the monthly retro, or the 30% scope cut. Indie studios don't die from one big mistake at month 6. They die from five small ones that were all fixable in month 3.

Open the doc. Write the page. Send it to your team tonight.