Inside a Game Studio: What It Actually Looks Like — Making Games Is Fun

Most readers picture a game studio as either a sleek campus with bean bags and a free canteen or a teenager’s bedroom with energy drinks and dual monitors. The reality, in the United Kingdom indie scene at least, sits at neither extreme. This piece offers an editorial composite of what a typical small UK studio actually looks like in operation, drawn from publicly available studio tours, founder interviews, and recurring patterns visible across the BAFTA-nominated indie cohort of the past decade.

It is not a portrait of any one studio. No individual office is being described. Studios on the small-to-medium end of the UK indie scene share enough operational character that a generalised description holds up against most specific examples.

The space

The typical UK indie studio occupies between 60 and 250 square metres of leased commercial space. The location is rarely a shiny office tower; more commonly it is a converted Victorian commercial building, a shared workspace floor with two or three other small companies, a converted seafront flat in Brighton or Margate, or a unit in a small business park on the outskirts of Cambridge or Guildford. Office costs typically consume between eight and fifteen per cent of the studio’s monthly burn, which is enough to matter but not enough to dominate decisions.

Inside the space, the layout is recognisable. Desks are arranged in clusters of two to six, separated by partial-height dividers or simply by aisle space. Each desk has at least two monitors and a desktop tower; laptops exist but are reserved for travel, remote work, and the occasional designer who prefers them. Headphones — usually open-back, frequently audiophile-grade — are standard. Whiteboards cover the walls, often in active use rather than ceremonial. A reasonable number of plants survive the lighting.

The team

UK indie studios with fewer than thirty staff typically organise around a small senior layer of two to six co-founders and a wider layer of mid-career developers and artists. The studios are rarely junior-heavy; the operational economics of small-team development reward developers who can ship across multiple disciplines, which favours mid-career hires over junior ones.

Role boundaries are deliberately loose. A “tools engineer” at a thirty-person studio frequently writes gameplay code two days a week. An “environment artist” frequently contributes to UI design when the UI artist is on holiday. The looseness is not chaos; it is a deliberate design choice. Studios that try to enforce strict role boundaries below a certain headcount tend to ship slower and run out of money first.

Hours vary. The “indie crunch” narrative is real but smaller and more sporadic than the AAA equivalent — a small studio cannot sustain six-month crunches because the team would leave. Crunches in UK indie practice tend to be intense two-to-six-week sprints before a milestone, followed by a mandatory recovery period, and many studios have policies against scheduling them at all.

The work

A typical day inside an indie studio is less varied than outside observers expect. Most developers spend most of their time in their primary tool — Unity, Unreal, Godot, or a proprietary engine — making small incremental changes and waiting for builds to finish. Meetings are short by AAA standards (often fifteen to thirty minutes) and frequent. A typical mid-career developer at a small studio attends between five and twelve meetings a week, most of them voluntary.

Builds, however, dominate the rhythm of the day in a way that surprises people who have not worked in software development before. A clean build of a mid-complexity Unreal project takes between five and forty minutes depending on scale and hardware. During a build, developers do email, code review, design discussions, or simply leave their desks. The build cadence shapes how studios organise their day: morning code reviews while the overnight build deploys, focused work between 10am and lunch, more meetings after lunch when builds are running.

The money

Most UK indie studios operate on one of three financial models. The first is self-funded — the founders use savings or income from contract work to cover early expenses, and the studio aims to reach revenue from its first game before running out of money. This is the most common model among studios under ten people.

The second is grant-funded. Creative Europe, the UK Games Fund, Scottish Enterprise, and various regional development funds together provide several million pounds per year to UK indie studios in non-equity grants. Grant funding rarely covers a studio’s full development costs but can extend a runway by six to eighteen months, often crucially.

The third is publisher-funded, where a publisher (typically Devolver Digital, Annapurna Interactive, Raw Fury, 505 Games, Hooded Horse, or one of several smaller specialists) covers development costs in exchange for a share of revenue. Publisher deals trade financial security for some loss of creative control and a slower studio-side revenue ramp.

A meaningful minority of UK indie studios operate on a hybrid model — self-funded for prototyping, grant-extended through pre-production, publisher-funded for shipping. The shift from one model to another is one of the most consequential business decisions a small studio makes.

What the press tends to miss

External coverage of indie studios — including coverage in technology publications that are otherwise excellent — tends to focus on launch days, individual founders, and the most photogenic offices. The actual operational rhythm of a studio is mostly invisible to readers because there is no obvious narrative hook in “the team finished a sprint and shipped a build to QA, on time, without incident.”

The result is that public perception of game studios is shaped by an unrepresentative sample of moments: launch parties, conference appearances, and the occasional crunch-related controversy. The day-to-day of UK indie development — the build queues, the milestone reviews, the contractor invoices, the slow accretion of features — is not glamorous enough to drive press coverage, but it is what produces the games that get covered.

Frequently Asked Questions

How many people work at a typical UK indie studio? Most UK indie studios have between three and thirty staff. Studios with fewer than ten people are common, particularly at the pre-launch phase; studios above thirty typically transition into “mid-size” terminology.

Do indie game studios have offices, or do most work remotely? Most UK indie studios maintained physical offices through 2024–2026, though hybrid arrangements (two to four office days per week) have become standard. Fully remote studios exist but remain a minority, particularly among those founded before 2020.

How long does it take to develop an indie game? Development cycles for UK indie games typically run between eighteen and forty-eight months from prototype to launch. Smaller projects can ship faster; larger ambitions (procedural systems, dense narrative content) routinely exceed four years.

What software do most indie studios use? Unity and Unreal Engine dominate UK indie game development, with Godot growing as a third option. Specialist studios use proprietary engines, in-house frameworks, or middleware such as Defold or GameMaker depending on project scope.

How do indie studios make money before their game launches? The three main pre-launch funding sources are founder self-funding, non-equity grants (UK Games Fund, Creative Europe, Scottish Enterprise), and publisher development deals. Most studios use a combination across the development cycle.

Is crunch common in UK indie studios? Crunch in UK indie studios exists but is generally shorter and more sporadic than at AAA scale. A typical pattern is two-to-six-week intense periods before milestones, followed by recovery time. Many studios have explicit policies against scheduling crunch and report being able to meet release dates without it.

What is the most common reason indie studios close? The most common cause of UK indie studio closure is running out of cash before shipping the next game, typically because a project takes longer than anticipated, the launch underperforms commercially, or a publisher deal does not materialise as expected.