Lesson 16: Studio Expansion & Future Projects

You have shipped a game, run the business side, and used data to optimize. This final lesson helps you decide what comes next: stay solo and do it again, grow a tiny team, or treat your first game as a stepping stone to a different kind of studio. The goal is to choose a path that fits your goals and energy, not to follow a generic "scale up" script.

What You'll Learn

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

Decide whether to stay solo, hire, or partner for your next project based on revenue, energy, and goals
Plan your next game using lessons from your first launch (scope, timeline, marketing, metrics)
Identify when and how to bring in help: contractors, part-time roles, or first hires
Avoid common traps: scaling too fast, repeating the same mistakes, or burning out on "what's next"
Document what worked and what to change so your next project is smarter, not just bigger

Why This Matters

After one launch, you have something most aspiring indies do not: real experience. Revenue, reviews, and your own energy level tell you what you can sustain. This lesson turns that into a clear set of options so you can expand (or not) on purpose.

Step 1: Decide Your Next Shape - Solo, Tiny Team, or Pivot

Stay solo

When it fits: Revenue and energy are acceptable; you prefer full control and do not want to manage people.
What to do: Plan your next game with a realistic scope and timeline. Reuse systems, tools, and audience from the first game. Keep business overhead low.
Pro tip: Your second game can be smaller in scope but higher in polish if you reuse tech and avoid "first game" mistakes.

Grow a tiny team

When it fits: You have consistent revenue or savings to pay someone; you have clear tasks (art, music, marketing, code) that you want to hand off; you are willing to manage contracts or one or two people.
What to do: Start with contractors or fixed-scope work (e.g. one artist for assets, one composer for music). Define deliverables and pay per project or per milestone. Only consider a part-time or full-time hire when you have at least several months of runway and recurring need.
Common mistake: Hiring too early or for vague roles. "Help with the game" leads to confusion. "20 character sprites by March" is clear.

Pivot or pause

When it fits: Revenue or energy is low; you want to try a different genre, platform, or business model; or you need a break before committing to another full project.
What to do: Support your first game with small updates and discounts while you prototype or learn. You do not have to start the next big thing immediately. A small follow-up (DLC, port, or tiny second game) can keep the business alive while you figure out the next move.

Step 2: Plan Your Next Game Using What You Learned

Your first launch is a dataset. Use it.

Scope and timeline

What took longer than you expected? (Art, marketing, polish, QA?) Plan more time for those next time.
What scope did you cut or regret? Either plan for it from the start or accept that it stays out. Do not assume "next time I will do everything."

Marketing and launch

Which channels drove wishlists or sales? Double down there. Which did almost nothing? Reduce or drop them.
When did you start marketing? Many indies start too late. Plan a longer pre-launch runway for the next game (e.g. 3–6 months of visibility building).

Business and operations

What legal, tax, or contract surprises did you hit? Fix them before the next project (accountant, contracts template, proper entity).
What metrics did you ignore or check too often? Pick 2–3 and a review rhythm (e.g. monthly) and stick to it.

Pro tip: Write a short postmortem (1–2 pages): What went well, what went wrong, what you will do differently. Do it while the launch is fresh. Use it when you pitch the next game to yourself or to partners.

Common mistake: Starting the next game without writing down lessons. You will forget. A simple doc saves you from repeating the same mistakes.

Step 3: When and How to Bring In Help

Contractors

Best for: Art, music, UI, localization, trailers, specific code (e.g. networking). You pay for a defined deliverable.
How: Clear brief, milestone payments, and a simple contract (work for hire, ownership of assets). Use platforms (e.g. itch.io jobs, Twitter, Discord) or your existing network.
When: When you have budget and a clear scope. Do not hire for "help" without a concrete output.

Part-time or first hire

Best for: When the same type of work recurs (e.g. community management, marketing, or art) and you have at least 6–12 months of runway.
How: Start with a fixed-term contract or trial. Define role and hours. Prefer someone who can own one area (e.g. "all our social and Discord") so you are not managing every task.
When: When revenue or savings support it and you have already tried contractors. Hiring too early is a fast way to run out of money.

Partners or co-founders

Best for: When you want to share risk and reward and have a clear split (e.g. design/code, business/creative). Harder to unwind than contractors.
How: Clear agreement on ownership, roles, and what happens if someone leaves. Get it in writing early.
When: When you have worked together before (e.g. game jam, small project) and trust is already there. Do not partner with someone only because they are available.

Step 4: Document What Worked and What to Change

Before you dive into the next project, capture:

What worked

Marketing channels that drove wishlists or sales
Scope and features that shipped and got positive feedback
Tools, pipelines, or habits that saved time or stress
Business choices (pricing, store, discounts) that matched your goals

What to change

Scope that was too big or too vague
Timeline assumptions that were wrong
Marketing that started too late or targeted the wrong audience
Metrics you ignored or obsessed over
Legal, tax, or contract gaps

One-pager for the next game

Target platform and audience
Rough scope (features you will and will not do)
Timeline (with buffer)
Budget (your time + any contractor cost)
Top 3 marketing channels from the first game
Top 3 things you will do differently

Use this when you feel lost or when someone asks "what's your next game?" It keeps you honest and focused.

Troubleshooting

Problem: We made some money but not enough to live on. Should we still plan a second game?
Solution: Yes, if you want to. Many indies do a second game while keeping a job or other income. Plan scope and timeline so the project is sustainable. Your first game can fund part of the next (assets, contractors, marketing) without needing to replace full income.

Problem: We want to hire but we are not sure for what.
Solution: List the tasks that take the most time or that you dislike. The first hire or contractor should take one of those off your plate with a clear deliverable. "General help" is hard to manage and measure.

Problem: We are burned out and do not want to start another big project yet.
Solution: You do not have to. Maintain the first game (small updates, sales, community) and take a break. Prototype small ideas, learn a new skill, or do a tiny game (e.g. game jam style) without the pressure of a full launch. The business can stay small and healthy.

Problem: Our next idea is much bigger than the first game.
Solution: Bigger scope usually means longer timeline and more risk. Consider a "middle" project first: same genre or tools, smaller scope, faster ship. Use it to fund and de-risk the big one.

Pro Tips

Tip 1: Second Game Scope
Your second game often benefits from reusing tech, audience, and lessons. Aim for "smaller and sharper" rather than "bigger and riskier" unless you have budget and runway to support a long project.

Tip 2: Runway Before Hiring
Do not hire with only one game's revenue unless you have months of runway. Contractors are lower risk: you pay for output, and when the work is done, the cost stops.

Tip 3: Revisit Your Postmortem
When you start the next project, open your postmortem again. It is easy to forget what hurt the first time. A short doc keeps "do not do that again" in front of you.

Recap

Next shape – Stay solo, grow a tiny team (contractors first, then maybe a hire), or pivot/pause. Choose based on revenue, energy, and goals.
Next game – Plan using lessons from the first: scope, timeline, marketing, and metrics. Write a postmortem and a one-pager for the next game.
Bringing in help – Use contractors for clear deliverables; consider part-time or first hire only when you have runway and recurring need; partner only when roles and trust are clear.
Document – What worked, what to change, and what you will do differently. Use it so your next project is smarter, not just bigger.

Course Complete

You have finished Launch Your First Indie Game. You went from concept and market research through legal structure, development, marketing, launch, revenue optimization, and now studio expansion and future projects. You have a framework to treat your first game as a real business and to plan what comes next with clarity.

What you can do next:

Revisit Lesson 1: Game Concept & Market Research when you start your next idea
Use Lesson 15: Revenue Optimization & Analytics to keep steering with data
Bookmark the course overview and share it with others starting their first indie business