Should You Kickstart Your Indie Game?

Kickstart only if you already have an audience to convert — campaigns amplify existing attention far more than they create it. Budget for the true costs (fees, fulfillment, taxes, a month of full-time campaigning) and treat the campaign as a public commitment you'll carry until every reward ships. That's the short version — the sections below get into the how, the why, and the mistakes worth dodging.

Campaigns convert audiences; they don't conjure them

The consistent pattern across game Kickstarters: most funding arrives from people who knew about the game beforehand — your mailing list, Discord, social following, wishlist overlap. The platform's own browsers contribute a minority. If your current audience is a few hundred people, the math rarely reaches typical goals.

The honest pre-test: an announcement trailer and a 'notify me' landing page. If those can't gather a thousand emails, the campaign isn't ready — and you've learned it cheaply.

The money is smaller than the number

From a funded total, subtract platform and payment fees (roughly 8-10%), failed payments, reward production and worldwide shipping, the inevitable scope of stretch goals, and taxes — the real development budget is often 60-75% of the headline. Physical rewards are the classic trap; they consume absurd time and margin.

Digital-heavy reward tiers, conservative shipping estimates, and a goal that funds the actual game keep the campaign from becoming a fulfillment company with a game attached.

You're signing up for years of accountability

A funded campaign is a public ledger of promises with timestamps. Backers are patient with honest updates and brutal with silence; the monthly update habit is non-negotiable, especially when the news is a delay.

Done well, that accountability is the hidden benefit: a campaign mints your most invested community — playtesters, evangelists, launch-day reviewers — before the game exists. Done badly, it's a permanent comment thread about your failure. The difference is mostly communication.

Protect the downside first

Indie game revenue is lumpy and unpredictable, and most advice quietly assumes a hit. Plan for the median outcome instead: a launch that earns modestly and grows slowly. Keep fixed costs low, keep some runway, and make deals you could live with if the game sells a tenth of your hopes.

None of this is pessimism — it's what lets you take real creative risks. A developer who can afford to miss is a developer who can afford to be interesting.

Get unglamorous things in writing

Splits, deadlines, deliverables, who owns what if the project dies — the awkward conversations are dramatically cheaper before money shows up. A one-page agreement between friends feels like overkill right up until it's the only thing that saves the friendship.

You rarely need a lawyer for a first project, but you do need clarity. Write down what was agreed, date it, and make sure everyone has a copy. Future-you will be grateful.

The quiet work that protects all of this

Everything in this post gets undone by an unstable build. A great store page, a clever marketing beat, a perfect jam entry — none of it survives 'crashed twice, refunded'. Stability isn't a feature players praise, but it's the floor everything else stands on.

Give yourself visibility before you need it: crash reports with stack traces, a simple way for players to flag issues from inside the game, and a habit of fixing the top recurring error before adding anything new.

Putting it to work

Don't try to act on all of this at once. Pick the one change that costs you the least and pays the most this week, do it, and see what actually happens before reaching for the next.

Most of this rewards steadiness over intensity. A small improvement made every week, checked against how real players respond, outruns any single burst of effort — in this corner of game development and every other one.

Make the guesses cheap, the agreements written, and the runway longer than the plan.