How Indie Game Developers Find Contract Work Between Their Own Projects

Shipping your own game is the dream. But between projects (or while your current title is still months from generating any revenue), you need income.

I have been making indie games for about seven years, and I have spent roughly half of that time doing contract work for other studios and developers to fund the games I actually want to build.

Early on, I found contract gigs the way most indie devs do: scrolling job boards, applying to postings on game industry Discords, and hoping someone would notice my portfolio.

The hit rate was terrible. I was competing against hundreds of applicants for every listing, and the projects that came through often paid poorly or had scope problems that ate months of my time.

What changed my situation was realizing that the people I already knew from game jams, dev communities, and past collaborations were the ones with contract work to offer. They just did not know I was available, or they did not know exactly what I could do for them.

Once I started being intentional about those relationships, the contract work pipeline became steady enough that I could plan my indie projects around it instead of scrambling between them.

Leveraging Your Game Dev Network for Freelance Gigs

The indie game development world is small enough that most of us are one or two connections away from someone who needs help on a project.

The problem is that we rarely talk about availability or capacity. We share devlogs and screenshots, we celebrate launches, but we almost never say “I have bandwidth for contract work next month.”

That silence costs you gigs. A solo dev working on a roguelike needs someone to implement their netcode. A small studio is behind schedule and needs a programmer for three months. A hobbyist developer just got funding and needs to hire their first contractor.

These opportunities circulate through DMs and group chats, and they go to whoever comes to mind first. If you have not signaled that you are available, you are invisible to those opportunities.

How to make your network aware you take contract work

• Be specific about what you do. “I am a game developer available for contract work” is too vague. Instead: “I do gameplay programming in Unity, specializing in 2D platformer mechanics and combat systems, typically on 2-to-4 month contracts.” That specificity makes you referable. When someone in your network hears a studio mention they need a Unity gameplay programmer, your name comes up because the description matches.
• Post about availability in the spaces you already inhabit. The game dev Discords, Mastodon circles, indie dev Slack groups, and Twitter/X communities where you already participate are the right places to mention that you have capacity. A simple post after you ship a milestone on your personal project (“just wrapped the alpha build, taking on a contract gig for Q3 if anyone needs gameplay programming help”) puts you on people’s radar.
• Lead with your shipped work, not just your skills. In game development, a shipped title (even a small one) carries more weight than a resume. When you mention your availability, link to something playable. A game jam entry, a released indie title, a demo: something that proves you can finish what you start. Studios hiring contractors are paying for reliability as much as skill.
• Tell people directly. I keep a short list of developers and studio leads I have worked with before. When I am wrapping up my current project and know I will need contract income, I message them individually: “Hey, finishing up my current build next month. If you have any contract work coming up that needs a programmer, I would love to talk.” This direct approach has landed me more gigs than any public post.

The referral dynamic in game dev

Game development has a natural referral culture that most of us use informally without thinking about it. A programmer gets asked if they know a good pixel artist. An audio designer hears about a studio looking for a level designer.

These introductions happen constantly, but because they are informal, they are also unreliable. People forget, or they do not know someone well enough to make the introduction with confidence.

The developers who get the most contract referrals are the ones who have made it easy for others to recommend them. That means being known for a specific thing, being reliable, and closing the loop when someone does send an opportunity your way.

If a fellow dev introduces you to a studio lead and you never follow up, that dev will not make another introduction.

Referring Art, Audio, and Programming Tasks to Specialists

Here is something I wish I had understood earlier in my career: you do not have to do every task yourself to benefit from every opportunity that comes your way. As an indie dev, you get asked for help with things outside your specialty all the time.

A studio might reach out because they liked your game’s visual style, but what they actually need is a character artist, and you are a programmer. A fellow indie might need music for their trailer, and you know a composer who would be perfect.

Instead of just saying “sorry, that is not what I do,” you can make the connection and, when the relationship supports it, agree on a referral fee for the introduction. This is standard practice in many creative industries, and it works just as well in game development.

Types of tasks that flow naturally to specialists

• Art and animation. Character art, environment art, UI design, sprite animation, 3D modeling. These are among the most frequently outsourced tasks in indie development. If you are a programmer, you probably know artists from game jams or online communities whose work you admire. When a studio asks you for an artist recommendation, that is a referral opportunity.
• Audio and music. Sound design, original soundtracks, voice acting direction. Audio is another area where indie studios regularly bring in specialists. Composers and sound designers often have inconsistent pipelines, so a warm introduction to a studio with budget is genuinely valuable to them.
• Programming specialties. Not every programmer does the same thing. Shader programming, networking and multiplayer infrastructure, procedural generation, AI systems, tool development, porting to consoles. These are all distinct specializations. A studio that needs someone to write a custom shader pipeline is looking for a very different developer than someone building inventory UI. If the request does not match your skills, refer it to someone whose skills it does match.
• QA and testing. As indie projects scale up, testing becomes a real bottleneck. Freelance QA testers who understand game-specific testing (edge cases in physics, save/load integrity, platform compliance) are in demand, and most studios find them through recommendations from other developers.

How referral fees work in this context

Some developers formalize referral arrangements with a percentage of the contract value, typically 5% to 15%, though many keep things informal and simply trade referrals over time.

In my partnerships where we do use a fee structure, it works like this: you connect a studio with a specialist, and if the specialist gets hired, you receive an agreed-upon percentage.

On a $3,000 character art contract, a 10% referral fee means $300 for making the connection. On a $15,000 audio contract for a full soundtrack, the same percentage is $1,500.

This works because the specialist gets a gig they would not have found on their own, the studio gets a vetted recommendation from someone they trust, and you earn something for the introduction.

The key is that the referral fee comes from the specialist’s side (they factor it into their pricing) or is agreed upon separately. The studio is not paying extra.

Agree on the terms before making the introduction. A quick message like “I have a studio looking for a character artist for a 6-week project. If I connect you and you land it, I would take 10% as a referral fee. Does that work for you?” keeps everything clean.

No ambiguity, no awkward conversations after the fact.

Building Relationships with Studios That Outsource Development Tasks

Small and mid-sized studios outsource specific development tasks constantly. They might have a strong core team for design and programming but need to bring in contractors for art production, porting, localization tooling, or specialized systems like multiplayer networking.

Understanding how studios think about outsourcing helps you position yourself as the person they call when the need arises.

Why studios prefer referrals over job postings

Posting a contract gig publicly means reviewing dozens or hundreds of applications, most of which are a poor fit. Studios working under deadline pressure (which is basically all of them) would rather ask a trusted developer “do you know someone who can do this?” and get a name they can contact directly.

A referred contractor comes pre-vetted, which saves the studio time on evaluation and reduces the risk of a bad hire that sets the project back.

This is why building direct relationships with studio leads and producers matters. You do not need to know hundreds of studios. Three to five contacts at studios that regularly outsource work is enough to keep a steady flow of contract opportunities.

Where to find and connect with studios

• Game industry events and expos. GDC, PAX Dev, local game dev meetups, and indie showcases are where you meet studio founders and producers in person. The conversations that lead to contract work rarely happen during formal sessions. They happen at the after-parties, in the hallways, and at the demo booths. Bring a business card or a QR code that links to your portfolio and a playable build.
• Developer communities with studio presence. Some Discord servers and forums have a mix of indie solo devs and small studio teams. The IGDA chapters, regional game dev groups, and engine-specific communities (Godot, Unity, Unreal) all have studio representatives who participate. Being a helpful, visible presence in these spaces puts you on their radar.
• Past collaborators who joined or started studios. Some of the best studio relationships I have come from game jam teammates who later started their own studios. They already know how I work, what I am good at, and that I deliver on time. When they need a contractor, I am the first person they think of. This is the long game: the relationships you build now with other indie devs will pay off for years.

What studios look for in a contract game developer

1. Relevant shipped work. Studios want to see that you have completed projects in a similar genre, engine, or scope. A portfolio full of prototypes is less convincing than two or three finished games, even small ones.
2. Clear communication. Contract work lives and dies by communication. Studios need to know you will give regular progress updates, flag blockers early, and be responsive during working hours. In interviews and early conversations, your communication style matters as much as your technical demo.
3. Defined scope and rates. Studios outsourcing tasks want to know exactly what you will deliver, how long it will take, and what it will cost. Experienced contractors provide clear estimates and are upfront about what is and is not included. Vague pricing signals inexperience and makes studios nervous.
4. Engine and tooling proficiency. If a studio runs on Unreal and you only have Unity experience, it is usually not a match. Be honest about your toolchain. Studios respect a contractor who says “that is not my engine, but I know someone great for Unreal work” more than one who overpromises and underdelivers.

Turning Game Jam Connections into Professional Referral Partnerships

Game jams are the single best relationship-building tool in indie game development. You work intensely with people for 48 to 72 hours under real pressure, and you learn exactly who is talented, reliable, and easy to collaborate with.

That information is gold, and most developers waste it by never following up after the jam ends.

Why game jam relationships are uniquely valuable

A game jam is like a compressed work trial. In a normal professional context, you might work with someone for months before you understand their strengths, their communication style, and whether they deliver under pressure. A jam gives you all of that in a weekend.

The artist who produced stunning sprites under a 48-hour deadline is someone you can confidently recommend to a studio. The sound designer who delivered a full set of effects and a theme track in two days is someone you know can handle a real contract.

This firsthand knowledge is what makes your referrals credible. When you tell a studio “I have worked with this artist, they are fast and their work is excellent,” you are not guessing. You have seen it. That carries weight.

How to turn jam teammates into referral partners

• Follow up within a week of the jam. Send a message to your teammates: “That was a great jam. Your pixel art was incredible. I would love to stay in touch. I regularly hear about projects that need artists, and I would be happy to send opportunities your way if you are open to contract work.” This one message sets the foundation for a professional referral relationship.
• Keep a running list of jam contacts and their specialties. I maintain a simple list: name, discipline, engine/tools, portfolio link, and a note about what they were like to work with. When someone asks me if I know a good Godot programmer or a 3D environment artist, I can pull up a name in seconds. This is not a CRM. It is a text file I check whenever a referral opportunity comes up.
• Do jams regularly, not just once. I try to do at least two or three game jams a year, specifically choosing ones with team formation so I meet new people. Ludum Dare, Global Game Jam, and smaller themed jams all introduce you to developers you would never encounter otherwise. Each jam expands your referral network by three to five people.
• Collaborate on post-jam polish. Some of the strongest professional relationships I have came from jam teams that decided to polish and release the jam game afterward. Working together for a few more weeks beyond the jam deepens the relationship and gives both sides a better sense of what a real collaboration would look like.

The reciprocal nature of game jam referrals

The best part about referral partnerships with jam contacts is that they naturally go both ways. The artist you refer to a studio for character work will think of you when they hear about a project that needs a programmer.

The composer you connected with a team will mention your name when a studio asks if they know any good gameplay developers.

Each referral you send out increases the likelihood that referrals come back to you, not as a strict exchange, but as a pattern of mutual support that builds over time.

The Numbers: What Contract Work Looks Like for an Indie Dev

Let me share some rough numbers from my experience over the past two years. I track where every contract comes from so I can see what is actually working.

• Contracts from direct network referrals: 5 projects, average value $8,000, average duration 6 weeks. These came from other devs I know personally recommending me to studios or fellow indies who needed help. Close rate on these introductions was about 75%. When someone vouches for you, the conversation starts at trust instead of evaluation.
• Contracts from studio relationships: 3 projects, average value $12,000, average duration 2 months. Two of these were repeat contracts from the same studio that initially hired me for a smaller task. Studios that have a good experience with a contractor come back.
• Referral fees earned on work I sent to specialists: 4 referrals to artists and audio designers, earning about $2,800 total. These were projects that did not match my skills but matched someone I knew from game jams or dev communities.

The referral-sourced contracts started faster, had clearer expectations because the introduction came with context, and led to repeat work more often.

If you want to see how this referral dynamic works in adjacent tech fields, this post on how app developers get clients without ads covers similar principles from a mobile development perspective.

Getting Started: Your First Steps

If you are an indie game developer who relies on job boards or cold applications for contract work, here is what I would do this month:

1. Message three developers you have worked with before. Game jam teammates, past collaborators, people whose work you have admired in dev communities. Let them know you are available for contract work and tell them exactly what you do. Be specific about your engine, discipline, and the types of projects you are looking for.
2. Make one referral. Think about a request you have seen recently that did not fit your skills but would fit someone you know. Make the introduction. You have just started a referral relationship that can generate opportunities in both directions.
3. Sign up for an upcoming game jam with team formation. Go with the intention of meeting two or three new people whose work impresses you. Follow up with them after the jam. These are your future referral partners.
4. Reach out to one studio you admire. Not with a cold pitch for work, but with genuine engagement. Comment on their devlog, play their game and share thoughtful feedback, attend their community events. When they eventually need a contractor, you want to be someone they recognize.

None of this requires spending money on marketing or competing in a race to the bottom on freelance platforms. It requires being intentional about the relationships you already have and the ones you are building through the work you are already doing.

The indie game developers who maintain steady contract income between their own projects are not the ones with the flashiest portfolios. They are the ones whose peers think of them first when an opportunity comes up.

If you want a straightforward way to manage referral agreements and track payments when you are connecting studios with specialists or receiving contract referrals from your network, PureIntro is built for tech and digital professionals like game developers.

This post reflects one professional’s experience and is for informational purposes only. It is not business, legal, financial, or professional advice. Results described are individual and not guaranteed. Referral fee arrangements may be subject to state and local regulations. Consult a qualified professional for guidance specific to your situation. PureIntro facilitates referral tracking and payment processing but does not guarantee payments between users or any particular business outcome.