Freelancing as a Game Developer: Lessons from 10 Years on Your Own

What Is It Like to Leave AAA for Freelance Game Development?

Going freelance as a game developer means trading job security for ownership: the freedom to choose your problems, your clients, and your schedule. I left Ubisoft after shipping Eagle Flight VR and Rabbids Coding. Ten years later I've worked with indie studios, advertising agencies, large brands, startups, and academic institutions. This post covers both the wins and the mistakes.

How Do You Survive Your First 90 Days as a Freelance Developer?

The first three months of freelancing are the hardest. The financial runway question is simple but critical: how many months can you survive without income? I recommend a minimum of six months in savings before you go full-time freelance. Three months is the bare minimum and will cause you enormous stress.

Your primary task in the first 90 days is not to do great work: it's to find your first client. That means telling everyone you know that you're available. The most reliable early contracts come from people who already know your work quality.

How Much Should a Freelance Game Developer Charge?

This is the lesson almost every freelancer learns the painful way. Your day rate must cover: your salary equivalent, taxes, health insurance, equipment depreciation, accountant fees, unbilled days spent on business development and administration, and at least two weeks of vacation per year. When you add all of this up, the number that feels "too high" is usually the right one.

A useful exercise: take your desired annual net salary, multiply by 1.5 to account for taxes and overhead, divide by 200 (the approximate number of billable days in a year). Most experienced Unity developers in Western Europe or North America should be billing between €500 and €1200 per day.

• Never discount for "interesting work". Interesting work is its own reward, but it doesn't pay the electricity bill.
• Raise your rates annually. If every client accepts your rate without hesitation, you're undercharging.
• The client who haggles hardest on price is usually the client who causes the most problems.

What Contract Clauses Are Essential for Freelance Developers?

Never work without a signed contract. A basic freelance contract must include:

• Scope of work: Specific, numbered deliverables. "A working game" is not a deliverable.
• Payment terms: I require 30 to 50% upfront for new clients. Net-30 on the balance is standard.
• Intellectual property assignment: All IP created under the contract transfers to the client upon final payment.
• Change order process: Any request outside the agreed scope requires a written change order with agreed additional fee before work begins.
• Kill fee: If the client cancels the project after work has begun, they owe a kill fee (typically 25 to 50% of the remaining contract value).

How Do You Manage Clients as a Freelance Developer?

The hardest skill I've developed isn't technical: it's client management. Learning to say no clearly and early. When a client's request falls outside the contract scope, say it with warmth but firmness: "That's a great idea, but it's outside our current scope, so I'll put together a change order for you to review."

Set clear availability expectations from the start. I do not take calls on Fridays and do not respond to messages outside 9am to 6pm local time unless a project is in active critical incident.

How Do You Build a Sustainable Freelance Game Dev Practice?

After a few years, the goal shifts from survival to sustainability. For me, sustainability meant three things: predictable income, work I actually enjoy, and time to invest in assets and products that generate income without billable hours.

The Asset Store strategy paid off more than I expected. Revenue from plugins covers my base expenses in slow months, which means I can be more selective about client work, taking projects that are technically interesting rather than just financially necessary. That same underlying math knowledge is what I turned into Mathematics for Unity3D, a free ebook covering the vectors, quaternions, and physics fundamentals behind most of the systems I build.

Where Do Freelance Game Development Clients Actually Come From?

The honest answer is that the first five years of clients almost entirely come from your existing network: former colleagues, studio contacts, people who saw your work at a conference or game jam. The channels that generate the most leads, ranked roughly by conversion quality:

• Warm referrals from existing clients: highest close rate, lowest sales friction, usually the best clients.
• Unity Asset Store publisher profile generates both direct product revenue and consulting enquiries.
• LinkedIn: a consistently updated profile with specific project outcomes generates inbound enquiries.
• Game development Discord servers and forums: authentic participation builds a visible reputation over 12 to 18 months.
• Freelance platforms (Upwork, Toptal): lower hourly rates but consistent volume.

How Do You Handle Taxes and Accounting as a Self-Employed Developer?

The mistake that burns most new freelancers: treating all income as spendable income. On every payment received, immediately transfer 30% to a separate tax reserve account. Keep receipts for everything that is legitimately a business expense. An accountant who specialises in freelancers will almost certainly save you more than their fee in optimised deductions and avoided mistakes.

How Do You Prevent Burnout as a Freelance Game Developer?

Freelance burnout is different from employment burnout. There is no manager enforcing leave, no HR policy capping hours. The specific patterns that precede burnout in my experience:

• Running multiple large projects simultaneously because it felt financially safe to say yes to all of them.
• Accepting a client whose requirements were vague because the project sounded interesting.
• Letting the Asset Store maintenance backlog build during a busy client period.

The structural protections that have worked: a firm policy of no more than two active client projects at a time; blocking two full weeks as vacation in advance on the calendar; and a monthly financial review to confirm that the Asset Store income actually covers the base overhead.

How Do You Decide Which Clients to Say No To?

Ten years in, the hardest business skill isn't landing clients, it's turning down the wrong ones before they cost you months. The clearest warning signs I've learned to act on immediately: a prospective client who can't describe what "done" looks like, one who wants to skip the contract "because we trust each other," and one whose first negotiation move is asking for a discount before seeing any work. None of these are automatically disqualifying on their own, but any two together has, in my experience, predicted a difficult engagement close to 100% of the time.

The flip side matters just as much: saying no to bad-fit work only pays off if you can afford to say no, which loops straight back to the runway and Asset Store income points above. Early on I took every client regardless of fit because I couldn't afford not to. That's a legitimate, necessary phase, not a personal failing. The goal is to build toward the point where you can be selective, not to pretend you're already there before the finances support it.

What Tools and Systems Actually Keep a Solo Practice Running?

The operational side of freelancing is unglamorous but it's what separates a hobby from a business. My own stack has stayed deliberately simple: a single shared calendar for all client-facing availability (so I'm never double-booking a call), a project tracker per client rather than one giant board (context-switching between clients is hard enough without also hunting for which task belongs to which contract), and a standing monthly finance review where I check the tax reserve, outstanding invoices, and Asset Store royalty statements against the same spreadsheet every time.

None of this needs to be sophisticated. The failure mode I've seen most often in other freelancers, and made myself, early on, isn't picking the wrong tools: it's not having a fixed cadence for reviewing them at all, so invoices go unchased and tax reserves quietly get spent before the systems catch the drift.

What Advice Would You Give a New Freelance Game Developer?

Stop waiting to feel ready. The client who would have been your first doesn't care that you feel unqualified: they care whether you can solve their problem. Every senior developer I respect was once an anxious junior who said yes before they were sure they could deliver, and then delivered anyway. That's not recklessness: it's how competence is built.