How game development companies build, ship, and scale modern games
A mid-size studio pitching a survival sandbox to publishers does not need the same pipeline as a 50-person team polishing a narrative adventure, and both look very different from a mobile studio shipping a live-service update every two weeks. The phrase game development companies covers a wide range of structures, from a single founder working with freelancers to multinational organizations with multiple internal studios, support teams, and dedicated research arms. What they share is a set of recurring decisions about engines, staffing, production cadence, outsourcing, and quality assurance that determine whether a project reaches release on a healthy footing.
This article walks through how modern game development companies actually operate. It explains the roles inside a typical studio, the engines and tools that shape technical choices, the production frameworks teams use to keep work moving, and the trade-offs studios face when they decide what to build in-house and what to hand off to external partners. The goal is to give readers a realistic picture of the decisions and constraints that define day-to-day work at a game studio, not a generic overview of the industry.
What a game development company actually does
A game development company is an organization that plans, produces, and ships interactive software. That covers more ground than many readers expect, because shipping a game is closer to producing a feature film than to launching a typical mobile app. A studio usually owns the concept, the design, the technical implementation, the art and audio production, quality assurance, certification on console platforms, and the post-launch support cycle. Some studios also handle publishing, marketing, and community management. Others hand those responsibilities to a separate publisher and focus on development alone.
The most useful way to understand a studio is to look at the work it takes on across the life of a project. A practical breakdown reads like this:
- Concept and pre-production: pitching ideas, prototyping mechanics, and writing design documents.
- Vertical slice: producing a small but representative section of the game to test scope, mood, and technical risk.
- Production: building the full game in passes, with regular internal builds and milestone reviews.
- Alpha and beta: feature-complete builds that go through structured testing and, in many cases, external playtests.
- Submission and certification: console platforms require technical certification before release, with specific rules per platform holder.
- Launch and live operations: releasing the game and supporting it with patches, seasonal content, and balance updates.
Studios differ in how much of that pipeline they keep inside the building. A common pattern is to keep design, engineering, and core art internal while outsourcing specialized tasks such as motion capture cleanup, localization, or parts of environment art to external vendors.
How studios are structured
Studios rarely operate as a single flat team. Most organize around disciplines, each with a lead who reports up to a studio head or production director. The shape of that structure depends on the size of the studio and the type of game being built.
A typical mid-size team includes engineering, design, art, animation, audio, production, and quality assurance. Larger studios add specialized sub-teams: technical art, gameplay engineering separated from engine engineering, separate online services groups, dedicated tools teams, and a research or R&D group that experiments with new techniques before they reach a shipping project.
| Discipline | Primary responsibility | Typical tools |
|---|---|---|
| Engineering | Gameplay systems, engine integration, tools, networking | Unity, Unreal Engine, C++, C#, proprietary engines |
| Design | Mechanics, levels, systems, balancing, player progression | In-engine editors, spreadsheets, scripting tools |
| Art | Concept, characters, environments, props, UI | Photoshop, Blender, Maya, ZBrush, Substance |
| Animation | Rigging, keyframed and motion-captured animation, facial work | Maya, MotionBuilder, proprietary rigs |
| Audio | Sound design, music, implementation, mixing | Wwise, FMOD, REAPER, Pro Tools |
| Production | Scheduling, scope tracking, milestone reviews, communication | Jira, ShotGrid, Hansoft, Miro |
| Quality assurance | Test planning, regression passes, certification support | TestRail, in-engine debug tools, dev kits |
Within each discipline, leads set technical direction, review work, and resolve conflicts. Producers translate between disciplines and the external stakeholders, whether those are publishers, platform holders, or internal leadership. The closer a studio sits to a publisher, the more visible the reporting lines become.
The engine decision that shapes everything else
Engine choice is one of the first technical decisions a studio makes, and it tends to stick for years. A studio can switch engines, but the cost of rebuilding a project, retraining staff, and rewriting tools is severe. Most studios pick an engine early in pre-production and live with the trade-offs.
Unreal Engine and Unity dominate the commercial landscape, with a long tail of proprietary engines built by large studios that need full control over rendering, networking, or tooling. Godot has grown in visibility for smaller projects, and CryEngine still appears in specific niches. The decision usually comes down to platform targets, team skills, licensing terms, and the features the engine exposes for the type of game being made.
| Engine | Common use | Strengths | Trade-offs |
|---|---|---|---|
| Unreal Engine | AAA, mid-tier, cinematic third-person, shooters | High-end rendering, Blueprint, large toolset | Steep learning curve, heavier builds |
| Unity | Mobile, indie, mixed 2D and 3D, XR | Flexible scripting, broad platform support | Visual quality requires more custom work for top-tier targets |
| Proprietary engines | Large studios with long-running franchises | Total control, deep optimization, custom workflows | High maintenance cost, smaller talent pool familiar with the stack |
| Godot | Indie, small teams, education, prototypes | Open source, lightweight, easy to learn | Smaller ecosystem, fewer AAA references |
Engine selection also affects hiring. A studio running Unreal can pull from a large pool of C++ and Blueprint developers, while a proprietary engine team trains most of its staff internally. This is one reason studios that invest in proprietary engines often grow slowly and keep staff for years.
Production frameworks that keep work moving
Game projects are too large and too interdependent for ad-hoc coordination. Studios rely on production frameworks to track tasks, manage dependencies, and surface risk early. The exact framework varies, but the underlying logic is similar across the industry.
Milestone-based production is the most common structure for funded projects. The studio agrees on a series of milestones with the publisher or internal leadership, and each milestone represents a defined slice of work: a prototype, a vertical slice, an alpha, a beta, a release candidate, and a gold master. Each milestone has acceptance criteria, and missing those criteria can trigger scope discussions or, in extreme cases, a project reset.
Scrum and Kanban are widely used inside teams, even when the studio reports milestones upward. Daily standups, sprint planning, and retrospectives help engineering, design, and art stay aligned week to week, while milestone reviews keep leadership informed. Larger studios often run multiple Scrum teams in parallel and add a production layer that coordinates across teams.
Risk management is the part of production that receives the least public attention but matters most. A few practices are common:
- Maintain a visible risk register that tracks technical, scope, staffing, and external risks.
- Hold regular playtests with the full team, not just designers, to surface issues early.
- Use feature flags to ship code that is incomplete without breaking the build.
- Track frame time, memory, and load times on target hardware as part of the definition of done.
- Review dependencies between teams every week to avoid late surprises.
These practices do not eliminate risk. They make risk visible, which is what lets leadership make informed calls about scope or staffing.
Art, audio, and animation pipelines
The visible surface of a game depends on art, audio, and animation, and the pipelines that produce them are often more elaborate than the code pipelines they sit next to. A single character can move through modeling, retopology, UV layout, texturing, rigging, skinning, animation, and engine integration before a player ever sees it on screen.
Art teams usually work in DCC tools, then export to the engine through formats such as FBX or USD. Studios invest heavily in naming conventions, asset validation, and version control because a single broken import can block a daily build. Source control with Git LFS or Perforce is standard, and the choice between them often comes down to file size and team scale.
Audio production is similar in structure. Sound designers build libraries in DAWs, then implementation engineers wire those sounds into the engine through Wwise or FMOD. Mixing happens late in production, when the rest of the game is stable enough to balance the soundscape against actual gameplay. Music often follows a separate path, with composers working to briefs and delivering stems that can be mixed dynamically inside the engine.
Animation crosses every discipline. Technical animators set up rigs that designers and animators can use, gameplay engineers integrate those rigs into the engine, and animators produce the actual movement. The most expensive animation work in modern studios is often facial performance, especially for projects that rely on cinematic storytelling.
Quality assurance and certification
Quality assurance is one of the largest line items in a production budget, and it scales with the size and complexity of the project. A typical AAA project runs several hundred testers during peak production, working in structured passes that target specific features, platforms, and risk areas.
Test planning usually starts in pre-production. The QA lead works with design and engineering to identify testable features, define acceptance criteria, and schedule test passes around the milestone plan. During production, testers focus on regression and block-finding. During the certification window, the team shifts to platform-specific checks, stability testing, and submission preparation.
Console platforms require formal certification before a game can be sold. Each platform holder publishes a technical requirements document that covers error handling, store compliance, controller behavior, save data, and more. Missing certification can delay a launch, so the final weeks of a project are usually dedicated to clearing known issues and verifying the build against the latest checklist.
Live service games add a long tail to QA. Every patch, seasonal update, and balance change needs regression testing, and a single bad update can break the player experience. Studios that operate live services often keep a substantial QA team employed well after the initial launch.
Outsourcing, co-development, and external partners
Most game development companies work with external partners in some form. Outsourcing is not a sign of weakness. It is how studios handle peaks in workload, access specialized skills, and keep internal headcount stable across a project. The work that goes outside the studio ranges from entire art pipelines to short, targeted tasks like audio mastering or localization.
A useful way to look at outsourcing is by the part of the pipeline involved. Studios most often outsource art and asset production, especially environment work, prop modeling, and texture cleanup. Specialized audio and motion capture work is also common. Engineering is less frequently outsourced, partly because code is the hardest part of the project to hand off cleanly, and partly because it is the area where studios want to keep the most institutional knowledge.
Co-development is a heavier model. In a co-development setup, an external team shares responsibility for a major system or feature alongside the internal team. This requires strong documentation, regular integration, and a clear technical lead on each side. Co-development is common in mid-tier and larger projects, where a single internal team cannot cover the full scope on its own.
For readers who want a deeper look at how external software stacks fit into modern production, an overview of game development software from an outsourcing studio lays out the categories of tools studios rely on and the trade-offs that come with each.
When choosing a partner, studios typically evaluate:
- Past work and references on similar projects.
- Time zone overlap and communication practices.
- Engine fluency and ability to integrate with the internal pipeline.
- Security practices for handling unreleased builds and assets.
- Capacity to scale up or down without long-term commitments.
A good partner is one that treats the studio’s IP and timeline as seriously as the internal team does. Cost matters, but the cheapest option rarely survives contact with the realities of a live production.
How studios make money
Revenue models shape a studio’s structure as much as the technology does. Premium games sell a finished product, often through retail and digital storefronts, and the studio’s revenue is front-loaded. Live service games earn revenue over time, through in-app purchases, season passes, and DLC, which keeps the studio employed on the same project for years.
Publisher funding is still the most common way a mid-tier or large studio finances a project. The publisher covers development costs in exchange for a share of revenue, and provides marketing, distribution, and platform relationships. Self-funded studios either use savings, loans, or outside investment, and they keep more of the upside when the game sells.
Smaller studios often combine funding sources. They might take a publisher deal for a major project, fund a smaller experimental title with revenue from a previous release, or work on contract work for other studios to smooth out cash flow. This is one reason so many studios offer services like porting, art outsourcing, or work-for-hire in addition to their own games.
Choosing a game development company to work with
Whether a reader is a brand looking for a custom game, a publisher scouting studios, or another studio considering a co-development partner, the same evaluation framework applies. The most useful signals are past work, team stability, and the clarity of the studio’s process.
A short checklist helps separate strong candidates from the rest:
- Look at shipped titles in the same genre or platform, not just portfolio pieces.
- Ask who actually worked on those projects and whether the core team is still in place.
- Request a walkthrough of the production process, including milestone definitions and review cadence.
- Check engine fluency with the specific version and platform in question.
- Confirm QA capacity, certification experience, and post-launch support model.
- Verify references from publishers or partners who worked with the studio on a real project.
Process and people matter more than slide decks. A studio that can describe how it handles scope changes, technical risk, and post-launch support will usually be easier to work with than one that talks only about its creative vision.
Working conditions and the limits of what studios can promise
Game development has a reputation for long hours, and the industry has started to address it more openly than in the past. Crunch is not universal, and many studios plan for it explicitly, schedule buffers into milestones, and pay overtime when it does occur. Others still treat long hours as a default, and that is one of the harder things to evaluate from outside the building.
It is also worth being honest about what a game development company can and cannot guarantee. No studio can promise a hit, and even strong projects fail commercially. Production is unpredictable because game design is unpredictable, and the cost of building a modern game is high enough that a single miscalculation can derail a project. Studios can promise process, transparency, and engineering quality, but the market decides the rest.
Frequently asked questions
What does a game development company actually do day to day?
A game development company plans, designs, builds, tests, and ships interactive software. Day to day, that means engineers writing and reviewing code, designers iterating on mechanics and levels, artists producing and integrating assets, animators building movement, producers tracking schedules, and QA running test passes. Larger studios add support teams for tools, online services, and live operations.
How do game development companies choose a game engine?
Engine choice usually comes down to platform targets, the type of game being built, the team’s existing skills, and licensing terms. Studios that need high-end rendering and cinematic output often pick Unreal Engine. Studios that target mobile, indie, or mixed 2D and 3D work often pick Unity. Large studios with long-running franchises sometimes build and maintain their own engines to keep full control over rendering and tooling.
What is the difference between a publisher and a game development company?
A game development company builds the game. A publisher funds development, handles marketing, distribution, and platform relationships, and takes a share of revenue. Some studios publish their own games, and some publishers own internal development studios, but the roles are distinct even when they sit under the same corporate roof.
Do most game development companies outsource part of their work?
Yes. Outsourcing is a normal part of modern production. Studios most often outsource art production, motion capture, audio mastering, and localization. Co-development with external teams is also common in mid-tier and larger projects. The areas that stay internal are usually design, core engineering, and the parts of the project where the studio wants to keep institutional knowledge.
How long does it take a game development company to ship a game?
Timelines vary widely. A small indie title can ship in under a year, while a mid-tier project often runs two to four years. Large AAA projects routinely run four to seven years, and franchises with live operations may keep a core team on the same game for a decade. The timeline depends on scope, team size, platform targets, and how much of the work is being done internally.
What should a publisher look for when hiring a game development company?
The most useful signals are past shipped titles, team stability, engine fluency on the target platform, and the clarity of the studio’s production process. Publishers should also evaluate QA capacity, certification experience, and the studio’s approach to post-launch support. References from other publishers or partners usually reveal more than a portfolio reel.
How do live service games change how a studio is organized?
Live service games extend the production timeline well past the initial launch. Studios that operate them keep a substantial team employed on the same project for years, with structured content pipelines, regular patching, seasonal updates, and continuous balance work. QA, community management, and customer support become permanent parts of the studio rather than phases that wind down after release.
Can a small studio compete with larger game development companies?
Small studios can compete in specific genres, art styles, and design niches where a tight team can move faster and take more creative risks than a large organization. They are usually at a disadvantage on large-scale production, high-end rendering, and platform certification, which is why many small studios partner with a publisher for marketing and distribution while keeping development in-house.
What skills are most useful for someone who wants to work at a game development company?
Useful skills depend on the discipline, but a few are common. Strong fundamentals in math and programming help in engineering. Visual taste, modeling, and animation skills help in art. Systems thinking and player empathy help in design. Communication and planning help in production. Across all disciplines, the ability to work in a team, take feedback, and iterate on a long-running project matters as much as raw technical skill.