.png)
1 hour ago
2
A transparent, fair, and scalable system for creative project teams
What Is This?
A well-designed revenue sharing (revshare) system for any teamwork where people expect to get rewarded for their effort in a fair, transparent, robust, flexible, clear, safe and scalable way.
Includes a smart payout calculator, a team tracker for credits and reward tiers, and a comprehensive solution HOW to run a zero-budget revshare project.
Its 100% free, easy-to-use and helps you worry less about how to share money correctly between teammates.
Who Is It For?
Perfect for:
- Gamedev Revshare Projects
- Zero-Budget Dev Teams
- Artist/Freelance Collaborations
- Open/Closed Source Projects
- Any collaborative thing with atleast two or more people working together and wanting to get paid fairly based on importance to project
When To Use It?
After a storefront (Steam, GOG, Itch, Gumroad, etc.) takes its % cut and then sends you, the project leader, the remaining money to a bank account from which you're supposed to share it with your team and yourself.
This web app helps you auto-calculate how to divide the money, keep track of your entire team of paid contributors and non-paid fans who deserve to be added into the project's credits.
Why This System Works
This system solves the classic problem: How do you compensate people fairly when contributions vary wildly in scope and impact? How do you keep it simple long-term without making anyone's head explode?
No contracts, no equity battles, no corporate structure required - just clear math, clean rules, and transparency.
🏆 Tiered Contribution System
Main, Assistant, Special Thanks, and Fan tiers based on lifetime project impact. Once you earn a tier, you keep it forever.
⚖️ Self-Balancing Protection
Math keeps payouts fair no matter how the team grows - main contributors never get drowned out by too many helpers.
💎 Lifetime Rewards
Once you earn a tier, you keep receiving payouts forever. No demotions, no performance anxiety.
📅 Smart Payout Timing
Monthly when revenue is strong, quarterly when lean. Minimizes bank fees and maximizes what your team receives.
📜 Zero Legal Complexity
No lawyers, no contracts, no business entity needed. Works for any team size from 2 to 200+ members.
🔍 Fully Transparent
Everyone can verify calculations and see complete payout history. Share data files with your team for full visibility.
💻 Works Offline
Runs entirely in your browser, no internet required after loading. No cloud dependency, no subscriptions.
🔒 Privacy-First
Your data stays on your device, shared only with team members you choose. No third-party servers involved.
🌍 Remote-Friendly
Ideal for teams of 2 to 200+ members working remotely, asynchronously, and at their own pace without corporate monitoring or artificial deadlines.
Quick Start Guide - Your Complete Journey
Here's the complete flow of how you'll use this system, from your very first time opening it to handling regular payouts. Don't worry - it's simpler than it looks!
1
First Time: Read & Understand
What you're doing: You're here now! Reading this intro to understand what this system is and when to use it.
Why this matters: This system is built on trust and transparency. Understanding the philosophy helps you use it correctly and explain it to your team. Once you're ready to dive deeper, visit the Info & FAQ tab for complete documentation on the tier system, formulas, and philosophy.
Next step: Decide if you're starting fresh or loading an existing project file.
2
Set Up Your "Payout Hub" Account (One-Time Setup)
What you're doing: Create a dedicated bank account, PayPal, or similar account that's ONLY for this project's payouts. Keep it separate from your personal money.
Why this matters: Separation makes accounting crystal clear. When money comes in from game sales, it goes there. When payouts happen, money leaves from there to team members. At the end of each payout cycle, this account returns to €0. This makes it impossible to mix project money with personal money, keeps everything transparent, and makes tax reporting much simpler.
Think of it as: Your project's wallet - money flows in from platforms, gets split among the team, and empties out completely each cycle.
3
Build Your Team List
What you're doing: Go to the Team & Credits tab. Add everyone contributing to the project and assign them to tiers based on their lifetime impact:
- Main Tier = Essential contributors (project wouldn't exist without them)
- Assistant Tier = Valuable contributors (enhance the project significantly)
- Special Thanks = Meaningful contributors (smaller but notable contributions)
- Fan Tier = Minor helpers (get credits but no money - for playtesters, small favors, etc.)
Why this matters: Tier placement determines how much each person earns forever. It's based on lifetime project impact, not current work. Once someone earns a tier, they keep it permanently - no demotions, no performance anxiety. Take your time getting this right.
Important: You can promote people to higher tiers later if they contribute more, but you can't demote them. Tiers are eternal rewards for past contributions.
4
Save Your Team-Project Data File
What you're doing: Click the 💾 Save button at the top of the page. This downloads a JSON file with today's date in the filename (like MyGame_2025-01-15T14-30-00.json).
Why this matters: This web app works entirely offline and doesn't store anything permanently. Your team-project data file is THE source of truth. It contains all your team members, their tiers, complete payout history, and project info. Without this file, all your work disappears when you close the browser.
Critical: Keep this file safe! Make backup copies. Share a copy with your team members so they can verify everything is fair by loading it into their own copy of this web app.
Pro tip: The filename includes the date and time, so if you have multiple versions lying around, they'll sort alphabetically - newest file = latest version.
5
When Sales Come In: Wait & Collect Revenue
What happens: Your game sells on platforms like itch.io, Steam, or mobile stores. The platform automatically takes their cut (itch.io ~15%, Steam 30%, etc.). What's left sits in the platform's system.
What you do: Manually withdraw/transfer this money from the platform into your hub account. Don't do this immediately every time - wait until enough revenue accumulates to justify the transfer fees.
Why timing matters: Bank transfer fees can eat into small amounts. The system recommends monthly payouts when you have €50+ per team member, quarterly payouts for €15-50 per member, and waiting longer if amounts are smaller. This maximizes what your team actually receives.
6
Load Your Data & Calculate the Split
What you're doing: Drag and drop your team-project data file anywhere on this web app (works from any tab!), or click the 📂 Load button to browse for it. Then go to the Payout Calculator tab.
Enter the numbers: Put in the EXACT amount now sitting in your hub account (after platform cuts, after transfer fees). Set the payout date. Add optional notes if you want.
Hit calculate: The web app does all the math using the tier system. It shows you exactly who gets what, applies self-balancing fairness if needed, and gives you payout timing recommendations.
Why this works: The math is transparent and verifiable. Anyone on your team can load the same data file and see the same calculations. No black boxes, no trust issues.
7
Review & Commit (or Just Mock It)
Two options here:
Option A - Just Planning: If you're just checking what a payout would look like (maybe planning ahead, or testing different amounts), just review the numbers and close the tab. Don't commit it. The calculation disappears and nothing is logged.
Option B - Real Payout: If you're actually doing this payout for real, click "Commit Payout to Timeline". This permanently logs it in your History tab and in your team-project data file.
Why the distinction matters: You can run unlimited "what if" scenarios without polluting your actual payout history. Only commit when you're actually sending money.
8
Send Money to Everyone
The tedious part: Manually send money to each team member from your hub account. Use bank transfers, PayPal, Stripe - whatever payment method works for each person.
Document everything: Take a screenshot of EVERY transaction showing the amount, recipient, and date. This proves you sent the money and protects you from disputes.
Why this takes time: If you have many team members, this can take an hour or more of careful data entry. Double-check amounts and payment details before hitting send. One mistake could send money to the wrong person or wrong amount.
Patience is key: This is boring, slow work that requires focus. Don't rush it. Your team is counting on you to get it right.
9
Save, Share & Archive Everything
What you're doing:
- Click 💾 Save at the top to download your updated team-project data file (now includes the new payout in the timeline)
- Go to the History tab and export reports if needed (full report as Markdown, or timeline as CSV)
- Share the updated data file with your team members (via Google Drive, Discord, email - your choice)
- Archive your transaction screenshots in a shared folder so everyone can verify the money was sent
Why transparency matters: Trust is built through verification. When team members can see the calculations, load the data file themselves, and view transaction proofs, there's no room for suspicion or disputes.
Check your hub: Your hub account should now be back at €0. If it's not, you missed someone or made a calculation error.
10
Repeat Forever
The cycle: When enough revenue accumulates again, you repeat from step 5. Load your latest data file, calculate the new payout, commit it, send the money, save everything, share with team.
As your team grows: When new people join or existing members contribute more, update their tiers in the Team tab, save the file, and the new split automatically applies to future payouts.
That's it: You now have a sustainable, fair, transparent revenue sharing system that scales with your project and respects everyone's contributions forever.
Ready to Start?
If you're brand new: Head to the Team & Credits tab and start adding your team members.
If you have an existing file: Drag and drop it anywhere on this page to load it instantly and pick up where you left off.
Want more details? Check the Info & FAQ tab for complete documentation on the tier system, mathematical formulas, philosophy, and answers to common questions.
Manage your project team members and their contribution tiers.
Project Information
Project Name
Project Description 0/500
Export Credits
Export your team credits list for posting on websites, stores, or in-game credits.
Calculate fair revenue distribution based on your team composition.
Revenue Information
Total Revenue (after platform cut) *
€
Enter the amount after the platform has taken their cut (e.g., itch.io 15%, Steam 30%)
Payout Date
Notes (optional) 0/500
📊
Ready to Calculate
Enter the revenue amount above and click "Calculate Distribution" to see how the money will be split among your team members.
Note: You need to have team members added in the Team & Credits tab before calculating payouts.
View payout history, statistics, and generate reports.
Overview
💰
Total Revenue Distributed
€0.00
Export Reports
Generate reports for tax purposes, transparency, and record keeping.
📋
No Payouts Yet
Once you commit payouts from the Calculator tab, they will appear here in a visual timeline.
Learn more about the revenue share system and find answers to common questions.
Core System Documentation
Deep dive into the revenue share system, tier structure, formulas, and the collaborative philosophy that makes it all work.
Project Setup & Management
Essential guides for setting up your project infrastructure and organizing your team for success.
Running Your Revshare Project
Practical strategies for marketing, recruiting team members, and sustaining your project long-term with zero budget.
Marketing & Outreach
Practical guides for getting your game noticed, building community, and reaching content creators who can help spread the word.
📧
Content Creator Outreach Guide
How to approach YouTubers, streamers, reviewers, and journalists to cover your game with email templates and AI-powered workflow.
→🎮
Steam Store Page Optimization Guide
Create a compelling store presence with capsule images, trailers, screenshots, descriptions, pricing strategy, and wishlist building.
→💬
Community Building & Discord Management Guide
Build and manage a healthy community without burnout, handle difficult situations, and celebrate your champions.
→Legal & Philosophy
Understanding the open, collaborative approach to intellectual property and licensing that makes this revshare system work best.
Frequently Asked Questions
Common questions from project leaders and team members about running a zero-budget indie gamedev revshare using this complete system.
Getting Started & Understanding the System
I'm completely new to revshare. What's the absolute minimum I need to understand before using this system?
The tier system (Main/Assistant/Special Thanks/Fan), the self-balancing math that keeps it fair as teams grow, lifetime rewards (no demotions), and the hub account concept. The web app handles all calculations automatically - you just need to understand WHY it works this way.
How is this different from just splitting revenue equally among everyone?
Equal splits don't account for vastly different contribution levels and create perverse incentives (minor contributors get same reward as essential ones). This system rewards impact fairly: someone who builds the entire game engine shouldn't get the same share as someone who created 3 sound effects. The tier system solves this while still being transparent and fair.
Do I need a lawyer, contracts, or a registered business to use this system?
No! This is designed for zero-budget indie teams. You operate on trust, honor, and MIT licensing. You only need a business registration later when moving to Steam/GOG (Phase 2), which happens after you're already earning steady income from Phase 1 platforms (itch.io, Ko-fi, etc.).
What makes this "zero budget" if I still need to set up payment accounts and deal with transfer fees?
Zero budget means no upfront costs - no lawyers, no incorporation fees, no contracts, no equity battles, no office space, no salaries. Payment accounts (PayPal, bank accounts) are free to create. Transfer fees exist but the threshold system minimizes them by only doing payouts when amounts are substantial enough to justify the fees.
Can I modify this system for my team's specific needs?
Absolutely! The tier ratios (1.0 / 0.5 / 0.167), thresholds (€50/€15), and self-adjusting algorithm (30% minimum for main tier) are recommendations that work well. You can adjust these, add more tiers, change currencies, or adapt the philosophy to fit your team culture. The web app is flexible - the system is a framework, not a prison.
Managing the Team & Tiers
How do I decide which tier someone belongs in? What if I get it wrong?
Evaluate based on lifetime project impact: Would the project exist without them (Main)? Do they significantly enhance it (Assistant)? Did they make smaller but meaningful contributions (Special Thanks)? Tiers are permanent and can only be promoted, never demoted. Take your time - it's better to start conservative and promote later than to over-assign initially. When in doubt, start them in Assistant tier and observe their long-term impact.
What if someone joins, does great work, then disappears? Do they keep getting paid forever?
Yes - that's a feature, not a bug! Tiers reward historical contributions, not ongoing performance. If someone built a critical system that powers your game, they deserve ongoing compensation even if they move on to other projects. This creates a healthy culture where people can contribute without fear of being trapped or penalized for life changes. Only actual malicious sabotage results in tier removal.
How do I handle someone who contributes TONS of work but all of it is low quality or unusable?
Tier placement is about impact and quality, not just volume. If their contributions don't meaningfully improve the project or require excessive rework, they might belong in Special Thanks or Fan tier despite high effort. Be honest and kind - volume without value doesn't earn higher tiers. This is why tier assignment is subjective and handled by the project leader's judgment.
Can I have multiple project leaders in Main tier? How do we handle decision-making conflicts?
Yes, you can have multiple Main tier members - the tier is about contribution impact, not authority. However, operationally, only ONE person should be the "project leader" handling the hub account, tier assignments, and payout processing for clarity and accountability. Decision-making conflicts should be resolved through discussion and consensus, or deferred to the designated project leader as the final authority. Define this clearly when setting up your team.
Money, Payouts & Practical Operations
How much money should I realistically expect to make before the first payout?
For a 2-3 person team, aim for at least €100 total revenue (about €30-50 per person) for the first payout. Smaller amounts get eaten by transfer fees. Use the web app's payout frequency recommendations - they're designed to maximize what your team actually receives. Many indie games take 6-12 months post-launch to reach consistent revenue, so be patient and keep building.
What happens if my game never makes any money? Am I still obligated to pay people?
No revenue = no payouts. Everyone joins knowing this is revshare (revenue sharing), not salary. If the game doesn't earn money, nobody gets paid - including you as project leader. You all share the risk together. People still get credited in the game regardless, and they can use that for their portfolio.
How long does processing a payout cycle actually take? The docs mention it could take hours.
For small teams (2-5 people), expect 30-60 minutes to calculate, process payments, document everything, and share updated files. For larger teams (10+ people), this can easily take 2-4 hours due to manual payment processing for each person, verification checks, screenshot documentation, and careful attention to avoid errors. Don't rush it - accuracy matters more than speed.
What if someone on my team lives in a country where PayPal doesn't work or has huge transfer fees?
Explore alternatives: Wise (formerly TransferWise), Payoneer, bank wire transfers, cryptocurrency (though docs discourage bitcoin), or even holding their share until they find a workable payment method. This is one reason to clearly document payment addresses in the Team tab. Be creative and flexible - different team members can use different payment methods.
Using the Web App & Managing Data
I closed my browser and lost all my data! What happened?
The web app works entirely offline with no cloud storage - your data lives in the team-project JSON file you save. If you didn't click "Save" before closing, your work is gone. ALWAYS save your work frequently! The app shows warnings when no file is loaded. Treat your team-project file like the source of truth - back it up, share copies with your team, and save after every change.
How do I share the team-project file with my team for transparency without exposing sensitive info?
The file contains names/aliases, emails, payment addresses, roles, tiers, and payout history. Remove or anonymize sensitive payment addresses before sharing if needed. Store it in a view-only shared folder (Google Drive, Dropbox) that only paid tier members (Main/Assistant/Special Thanks) can access, not Fan tier. Keep the full version with payment details in your private local backup.
Can I use this web app for multiple different projects at the same time?
Yes! Each project gets its own team-project JSON file. Save them with clear names like "MyGame_2025-01-15.json" and "OtherProject_2025-01-20.json". Load whichever file you need to work on. The app doesn't care how many projects you manage - each file is completely independent.
Long-Term Sustainability & Philosophy
This seems great for small teams, but does it really scale to 50+ people? 200+ people?
Yes, with caveats. The math scales beautifully thanks to the self-adjusting fairness algorithm. The operational burden (manually processing 50+ payments, managing that many relationships, handling disputes) is the real challenge. At very large scales, consider splitting into sub-projects with their own teams, or hiring someone specifically to handle payout operations (and placing them in Assistant/Main tier for this critical role). The system CAN scale mathematically; the question is whether YOU can scale operationally.
Why should I trust this system and philosophy? What if the project leader screws everyone over?
Trust is earned, not assumed. As a team member: Ask to see the team-project file, verify calculations yourself by loading it into the web app, request transaction proofs (screenshots), and check the payout history. As a project leader: Provide all of this proactively and communicate clearly. The system is designed for transparency - use it. If a leader refuses to share data or acts shady, that's a red flag to leave. The system works ONLY when everyone operates in good faith.
