Revenue Split Agreements for a Small Indie Game Team
Our first commercial game made $1,140 in its first month. Four of us had worked on it, and nobody had written down who got what.

Our first commercial game made $1,140 in its first month. Four of us had worked on it, and nobody had written down who got what. It took a two hour call and some hurt feelings to settle a revenue split that, honestly, should have taken ten minutes before we wrote a line of code.
Small game teams almost never fight over big money. They fight over small money that arrived without a plan. This is how we now set up a revenue split for a small indie game team: the common models, the numbers we actually use, the clauses that prevent arguments and the one piece of popular advice we ignore.
Agree on a Revenue Split Before Anyone Opens the Engine
The best time to talk about money is when there is none. Before the first prototype, everyone is optimistic and nobody has a sense of who worked harder. After launch, every person remembers their own late nights more clearly than anyone else's.
We now write a one page agreement in the first week of any project with more than one person. It covers four things: who is on the team, how revenue is divided, what happens if someone leaves and who owns the game itself. It is not a legal contract drafted by a lawyer, though for anything that earns real money you should get one. It is a shared record that stops memory from rewriting history.
Three Common Ways Small Teams Split Revenue
Equal split
Everyone gets the same share. It is simple, it feels fair at the start, and it works well when all members commit similar hours for the whole project. It breaks when one person drops to weekends halfway through.
Points based on contribution
The team agrees on a pool of points, often 100, and assigns them by role and expected effort. A lead programmer working full time might hold 35 points, while a composer delivering eight tracks holds 10.
Hours tracked
Each person logs time, and shares follow the hours. It is the most precise, and in our experience the most stressful. People start arguing about whether an hour of bug fixing equals an hour of concept art.
| Model | Best for | Main risk |
|---|---|---|
| Equal split | Two or three people, similar commitment | Uneven effort later on |
| Points | Mixed roles and part timers | Arguments when points are first set |
| Hours tracked | Longer projects with changing teams | Bookkeeping fatigue, hour value disputes |
What Comes Off the Top Before Anyone Gets Paid
New teams often divide the gross number on the store dashboard. That is a mistake. A lot leaves before the money is really yours.
- Store fees. Steam takes 30 percent on most sales. itch.io lets you choose, with 10 percent as the default.
- Refunds and chargebacks. Expect a few percent of early sales to come back.
- Taxes. Withholding and local tax depend on where each person lives. Every member handles their own.
- Shared costs. Asset packs, the store submission fee, a domain, a capsule art commission.
We agree that shared costs are repaid first, to whoever paid them, before any split happens. On that $1,140 month, after fees and paying back $210 in assets, the real amount to divide was about $590.
Why We Do Not Use "Everyone Gets an Equal Share"
A lot of indie advice says equal shares are the friendliest choice, because they avoid ranking people. We tried it and moved away from it. Equal shares quietly reward whoever does least, and they make the people carrying the project resent it by month four.
What we use instead is a points system with a review checkpoint. Points are set at the start, then reviewed once at the midpoint milestone, and only then. Anyone can propose a change at that review, and it needs everyone's agreement. After the review, points are locked until release. This gives the team one fair chance to correct a bad guess without turning every week into a negotiation.
If the team is two people of equal commitment, ignore all of this and split 50/50. The overhead is not worth it.
The Clauses That Prevent Most Arguments
These are the lines in our one page agreement that have actually mattered:
- Leaving early. If someone leaves before release, they keep points for work already delivered, scaled by how much of their planned role they completed. We write the formula down.
- Who owns the game. One person or a simple shared entity holds the store account and the code repository. Ownership by "all of us" with no structure means nobody can sign anything.
- Payout schedule. We pay quarterly, after the store's own payout lands. Monthly payouts of $14 each are not worth the transfer fees.
- Sequels and ports. Does the split carry over to a sequel using the same characters? Decide now, even if it feels premature.
- Minimum payout. Balances under a set amount roll over to the next quarter.
Tracking Money Without Hiring an Accountant
For a small team, a single shared spreadsheet is enough. Ours has three tabs: income by month with store reports attached, shared costs with who paid them, and the payout calculation. Anyone on the team can see every number. Transparency matters more than the format; the fastest way to sour a team is one person holding all the numbers and announcing results.
Once a year, export everything and save it with each member's payout total. When tax season arrives, every person needs that number, and nobody wants to rebuild it from store emails. Setting this up is part of running the studio side well, a theme we wrote about in how small game studios actually collaborate.
FAQ
Should a contractor paid upfront also get a revenue share?
Usually not. If an artist is paid a fair flat fee, the work is done and the deal is complete. Some teams offer a small share instead of a lower fee, which can work, but write down which arrangement it is.
What if the game never earns anything?
Then the split costs nothing and you lose nothing by having written it. Most small games earn little, which is one reason we argue small finished games beat big unfinished ones.
Do we need a company to split revenue?
Not to start. One person can receive payouts and transfer shares. Once yearly revenue becomes meaningful, a proper entity and legal advice protect everyone, especially the person whose name is on the store account.
The Practical Takeaway
Before your next team project, write one page that lists the members, the split model, what comes off the top, the leaving rule and who owns the game. Have everyone confirm it in writing, even in a chat message. It takes an evening and saves the friendship that made the game possible.
More in Studio
Studio
Handling Player Support as a Two Person Game Studio
Our second game sold about 1,200 copies in its first three weeks, and we were not ready for the mail that came with it.
Studio
What a Small Game Studio Spends in Its First Year
Someone in our Discord asked what it costs to start a studio, and the answers he got ranged from nothing to thirty thousand...
Studio
A Game Release Checklist for a Small Indie Studio
Launch week is when small studios find out what they forgot.