Lesson 4: Legal Structure & Intellectual Property

You have a concept, a business model, and a budget. Next is putting a simple legal structure in place and protecting your game and brand. This lesson walks you through business structure options, intellectual property (IP) basics, and when to use contracts so your indie studio is set up correctly from the start.

What You'll Learn

By the end of this lesson you will be able to:

Compare common business structures (sole proprietor, LLC, corporation) and when each makes sense
Identify what you own (copyright, trademarks) and what to protect first
Use simple contracts for contractors and partners (work for hire, IP assignment)
Know when to see a lawyer or accountant and what to bring
Document your legal and IP setup in one page

Why This Matters

The right structure protects your personal assets and can simplify tax. Clear IP ownership avoids disputes with contractors, publishers, or co-founders. Doing the basics early is cheaper and less stressful than fixing problems after launch.

Step 1: Choose a Business Structure

Your structure affects liability, tax, and how you work with others.

Sole proprietor

You and the business are the same. No separate entity.
Pros: Simple, minimal paperwork, you keep all profit.
Cons: You are personally liable for business debts and claims; harder to separate personal and business finances.
When it fits: Very low revenue, no employees or contractors, and you accept personal risk.

LLC (or equivalent in your region)

A separate legal entity that can own assets and enter contracts. You are a member/owner.
Pros: Limits personal liability for business debts and many lawsuits; flexible tax (often pass-through); common for indies.
Cons: Some setup and ongoing paperwork; rules vary by country and state.
When it fits: You earn revenue, hire contractors, or want to separate personal and business liability.

Corporation

A separate entity with shares, directors, and officers. More formal than an LLC.
Pros: Clear structure for investment or multiple owners; in some places, different tax options.
Cons: More paperwork and formality; often overkill for a first solo project.
When it fits: You take investment, have co-founders, or plan to scale into a larger studio.

Pro Tip: For a first indie game with any real revenue or contractors, an LLC (or local equivalent) is usually the best balance of simplicity and protection. Check your country and state for formation and annual requirements.

Common mistake: Staying a sole proprietor while hiring contractors or earning significant revenue. If something goes wrong, your personal assets can be at risk. Form an LLC (or equivalent) before you scale.

Step 2: Protect Your Intellectual Property

Your game, name, and brand are assets. Protect them in a way that matches your budget and risk.

Copyright

You automatically own copyright in original code, art, music, and design you create. No registration required for ownership, but registration (e.g. in the US) strengthens enforcement and can help with damages.
Practical step: Mark your game and materials with a copyright notice (e.g. "© 2026 Your Name or Studio"). Keep dated backups and drafts to show when you created work.
Contractors: Use written agreements that assign or license rights to you (work for hire or IP assignment). Without that, they may retain rights and you may not have full ownership.

Trademarks

Trademarks protect names, logos, and other identifiers so others cannot use them in a confusing way in your market.
Practical step: If your game name or studio name matters to you, search existing trademarks (e.g. USPTO, EUIPO) and consider registering. For a first small release, many indies rely on copyright and common law; registration becomes more important as you grow or expand regions.
Avoid: Using a name that clearly conflicts with an existing game or brand. A quick search can prevent a cease-and-desist later.

Licenses you use

When you use an engine, asset pack, or middleware, you are bound by its license (EULA, asset store terms). Check commercial use, royalty obligations, and what you can and cannot do with the content.
Practical step: Keep a list of key licenses (engine, major assets, music) and note any restrictions. Store copies of license agreements in your project or legal folder.

Pro Tip: Put all IP and legal documents in one folder: incorporation docs, contractor agreements, key licenses, and registration confirmations. When you need to check something or hand off to a lawyer or accountant, it is all in one place.

Common mistake: Assuming that because you paid a contractor, you own their work. Without a written assignment or work-for-hire clause, they may retain copyright. Always use a contract that clearly assigns or licenses rights to you.

Step 3: Use Simple Contracts for Contractors and Partners

With contractors (art, audio, code)

Work for hire or IP assignment – The contract should state that all work created for your project is owned by you (or licensed to you exclusively for the game). Specify deliverables, payment, and that they assign all rights to you.
Confidentiality – They should not share your game design, unreleased assets, or business details without permission.
Credit – Agree how they will be credited (e.g. in-game, in credits, on the store page).

With publishers or partners

Scope and ownership – What they get (e.g. license to publish) and what you keep (e.g. IP, source code). Typical for indies: you keep IP; they get a limited license to publish and promote.
Revenue share and payment – How revenue is split, when you get paid, and how it is calculated.
Term and reversion – How long the deal lasts and what happens when it ends (e.g. rights revert to you, you can take the game elsewhere).

With co-founders

Equity or profit share – Who owns what percentage and under what conditions (e.g. vesting, buyout).
Roles and IP – Who does what, and that all work for the project is owned by the company or assigned to it.
Exit – What happens if someone leaves (e.g. buyout, non-compete, IP stays with the company).

Pro Tip: Use simple, written agreements even with friends. A one- or two-page contract is better than a handshake when money or IP is involved. Templates from your region or a short lawyer review can save a lot of trouble.

Common mistake: Signing a publisher or partner deal without reading the IP and reversion clauses. If the game underperforms or the relationship ends, you need to know you can get your rights back and ship the game elsewhere.

Step 4: When to See a Lawyer or Accountant

See a lawyer when:

Forming an LLC or corporation (they can file and advise on structure).
Signing a publisher or investment deal (they can review and negotiate).
You receive a cease-and-desist or dispute letter.
You have a co-founder and need a founders' agreement or equity split.

See an accountant when:

Forming a business (they can advise on structure and tax).
You have significant revenue or contractors (they can handle payroll, tax filing, and deductions).
You are unsure about sales tax, VAT, or income tax in your region.

What to bring: Your one-pager (concept, business model, budget), a list of contracts you have signed or plan to sign, and any incorporation or IP documents. The more organized you are, the less time they spend and the lower the bill.

Pro Tip: One short consultation per year (e.g. after formation, before a big contract) is often enough for a small indie. Use it to validate your setup and catch issues early.

Common mistake: Avoiding a lawyer or accountant entirely to save money, then facing a dispute or tax problem that costs far more. A single consultation can prevent that.

Mini Challenge

Write down your current or planned business structure (sole proprietor, LLC, or corporation) and one reason you chose it.
List three things you consider your IP (e.g. game name, logo, original code) and whether you have any registration or written assignments.
If you work with contractors or plan to, write one sentence: "I will use a written agreement that assigns all rights in their work to me (or my company) for the project."
Add "Legal and IP" to your one-page business doc: structure, key IP, and where you keep contracts and licenses.

Save this; you will use it when you plan your project timeline in Lesson 5 and when you prepare for marketing and launch later in the course.

Troubleshooting

"I cannot afford a lawyer."
Use reputable templates from your region (e.g. contractor agreement, simple NDA) and fill them in. One short consultation to review key contracts is often affordable and can catch major issues. Some regions offer low-cost legal clinics for small business.

"I am not sure what I own."
You own what you create (copyright) unless you signed it away or hired someone without an assignment. List what you created, what you bought (and under what license), and what contractors did (and what the contract says). That list is your starting point.

"My co-founder and I have not signed anything."
Draft a simple founders' agreement: roles, equity or profit share, IP ownership, and what happens if someone leaves. Even a one-page document is better than nothing. Have it reviewed if you can.

Recap and Next Steps

You have:

Compared business structures (sole proprietor, LLC, corporation) and chosen one that fits your risk and scale.
Identified your IP (copyright, trademarks) and how you protect it (notice, registration, contracts).
Used or planned simple contracts for contractors and partners (work for hire, IP assignment, scope, and reversion).
Known when to see a lawyer or accountant and what to bring.

In Lesson 5: Project Management & Timeline Planning, you will turn your concept, business model, budget, and legal setup into a clear project plan and timeline so you can move from planning to production.

For more on contracts and legal for game dev, see our Business Side of Game Development - Contracts and Legal and The Business of Game Development - Contracts, Legal, and Finance. Bookmark this lesson and revisit your legal one-pager when you hire contractors or sign a deal.