Why Indie Developers Should Start Alone

Gadaleta" />

Defrag Zone

SubscribeSign in

Gamedev<br>Why Indie Developers Should Start Alone<br>Gadaleta's profile" class="pencraft pc-display-contents pc-reset"> Gadaleta" class="pencraft pc-display-flex pc-width-36 pc-height-36 pc-justifyContent-center pc-alignItems-center pc-position-relative pc-reset bg-secondary-UUD3_J flex-auto-j3S2WA outline-detail-vcQLyr pc-borderRadius-full overflow-hidden-WdpwT6 sizing-border-box-DggLA4 container-TAtrWj"> Gadaleta's avatar" srcset="https://substackcdn.com/image/fetch/$s_!ZrDO!,w_36,h_36,c_fill,f_auto,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2F8fb10a92-32ee-4abf-ba49-1ff6eda16563_1080x1105.jpeg 1x, https://substackcdn.com/image/fetch/$s_!ZrDO!,w_72,h_72,c_fill,f_auto,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2F8fb10a92-32ee-4abf-ba49-1ff6eda16563_1080x1105.jpeg 2x, https://substackcdn.com/image/fetch/$s_!ZrDO!,w_108,h_108,c_fill,f_auto,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2F8fb10a92-32ee-4abf-ba49-1ff6eda16563_1080x1105.jpeg 3x" width="36" height="36" draggable="false" class="img-OACg1c object-fit-cover-u4ReeV pencraft pc-reset"/>

Francesco Gadaleta<br>Aug 05, 2026

Share

Image by Lesiakower (pixabay)<br>There are two currencies that get people to show up and do hard work on a project: money and belief. Most of the time we only talk about the first one, because it’s easy to measure. Belief is harder to price, and that’s exactly why it’s worth thinking about carefully, especially if you’re building something like a video game, where belief is often the only currency you have for a very long time.<br>When someone is paid to work on something, the paycheck does the heavy lifting. It doesn’t matter much whether they love the product, the mission, or the codebase. The transaction is clear: hours and skill in exchange for money, on a schedule that doesn’t depend on whether the thing ultimately succeeds. This is how most commercial software gets built. A client hires you to build a system to their requirements, and you get paid whether or not that system changes the world. The risk of “will people actually want this” sits with the client, not with the person doing the work.<br>Belief works differently, and it splits into two very different intensities depending on ownership, probably the only one variable.<br>If you own the idea, if it’s your vision, your name on it, your years sunk into it, then your motivation doesn’t need topping up. You’re not just motivated, you’re responsible. Responsibility is a much stronger fuel than enthusiasm, because it doesn’t run out when the work gets boring or the outcome gets uncertain. You show up on the bad days because there’s no one else whose job it is to show up.<br>If you don’t own the idea, but you’re still asked to work without pay, something has to make up the difference. You need to be recruited into someone else’s vision hard enough that it starts to feel a little bit like your own. That’s an expensive thing to manufacture in another person, and it takes time you often don’t have at the start of a project.<br>So why video games make this worse?<br>Most commercial software has a built-in safety net: you get paid for doing the job, independent of whether the job turns out to matter. Video games, in particular indie ones, without a publisher check landing every month, don’t have that net. Nobody pays you for making the game. They pay you, if at all, for the game succeeding, and you only find out whether it succeeds at the very end, after most of the work is already done.<br>That creates a strange kind of project. It’s creative work, so unlike a lot of enterprise software, “correct” isn’t well defined (a boss fight can be technically finished and still not be fun), and you often can’t tell the difference until it’s in front of a player who owes you nothing. So the commercial outcome is both delayed and uncertain, stacked on top of each other. A contractor building an internal tool can point to a spec and say “I met it.” A game developer can meet every spec on paper and still ship something nobody wants to play.<br>This is a rough environment to ask someone else to be motivated in, unless they own it with you or are being paid regardless of outcome. Eight months into my own game, this is not theoretical. It is in fact, the exact fork in the road every indie project reaches.<br>So yes, go alone first. I found this to be the practical conclusion I’ve landed on. If you’re an indie developer building something you believe in, and you can’t yet pay people, go alone for as long as you possibly can.<br>Not because collaboration is bad. It’s because collaboration has a startup cost, and that cost is paid in the currency of shared ownership, which doesn’t exist yet at day one. Early on, your game is an idea in your head, half-finished mechanics, and a...