A studio sale is usually announced as good news. The founders have secured investment, the acquiring company has found a talented team and everybody is looking forward to making wonderful games together. There may even be a photograph of several people looking extremely pleased with themselves.

And, to be fair, it may be good news. Building a studio is hard, uncertain work. Finding a buyer who can provide the funding, support or opportunities that a team needs can be a perfectly sensible decision. A founder who has spent years taking that risk is entitled to consider what a sale might mean for them and their family.

But I think there is a question we should ask alongside all the excitement: what happens to the risks when the studio changes hands?

Some of the people who owned the business may now have financial security they did not have before. The people making the games still need the studio to be funded, the projects to remain viable and the new owners to support the decisions required to finish them. The buyer is taking risks too, of course. They have committed money and will have their own expectations about what the acquisition should achieve.

Those risks do not disappear when everyone signs the agreement. They change shape, and they may now be carried by people who have rather less influence over the decisions that affect them.

Why the deal matters to production

It is tempting to think of an acquisition as a financial event that happens above the studio. The teams can carry on making the game while the people in suits sort out the details. That would be convenient, although I am not sure how often game production has shown much respect for convenient assumptions.

The details of a deal can influence the work quite directly. Who decides whether a project continues if its forecast changes? Does the studio still have authority to hire the people it needs? Who owns the intellectual property and the technology? What happens if the new parent decides that another project is a higher priority?

The answers will vary from one agreement to another. An acquisition does not automatically mean that a studio loses all independence, just as a promise of independence does not answer every question about future budgets. A team may retain creative control and still need approval from elsewhere to spend money. It may be encouraged to grow, only to find that the cost of that growth depends on a forecast nobody has revisited for some time.

These are production questions as much as financial ones. They affect the options available when something goes wrong, and that is exactly when we discover whether the authority we thought we had actually exists.

When Acquisition Becomes Risk Transfer. Sequence: deal announcement; security, growth and autonomy promised; new capital; new governance rights and reporting pressure; forecasts meet market reality; portfolio logic takes over; restructure, sale, closure or strategic retreat. Risk lens: the downside often arrives later than the upside.
Infographic: when acquisition becomes risk transfer.

Investment and acquisition are not the same thing

A studio considering outside funding may have more than one option. A minority investor might provide capital while the existing owners retain control. A full acquisition changes ownership altogether. That sounds straightforward, but the practical difference depends on the terms rather than the label on the announcement.

A minority investor may have approval rights or expectations that influence major decisions. A buyer may leave the studio with substantial day-to-day autonomy. In either case, the useful question is not simply how much money comes in. It is what the business has agreed to do in return, who can make which decisions and what happens if the original plan stops working.

Founders may have very good reasons to choose a sale. They might need investment the studio cannot otherwise obtain, want support with publishing or decide that the time has come to step away. I do not think it is helpful to pretend those are easy choices, particularly when the alternative might involve taking on more personal financial risk.

What I do think is worth examining is whether the people making that choice have considered the risks that remain with everyone else. A successful outcome for a seller and a good long-term outcome for a team can happen together, but one does not automatically guarantee the other.

Minority Investment vs Full Acquisition. Minority investment: studio keeps day-to-day control; investor receives rights, reporting and influence; growth expectations increase; milestones and forecasts become more consequential; pressure rises without full control moving. Full acquisition: control moves to parent; studio enters portfolio logic; autonomy depends on governance and parent strategy; creative value competes with margin, debt and strategic targets; restructure risk increases if forecasts or priorities change.
Infographic: minority investment compared with full acquisition.

Following the risk through a fictional studio

Imagine an independent studio that has built a promising game and needs more money to finish it. An established publisher offers to buy the studio, fund development and help it reach a much larger audience. The founders decide the offer gives the game a better chance than trying to finance the next stage alone.

So far, that may be a very reasonable decision. Now suppose the plan depends on the game reaching a particular sales forecast. The studio expands, hires specialists and commits to a more ambitious release. Halfway through development, playtesting reveals that a substantial part of the game needs more work, and the forecast is less convincing than it was when the deal was agreed.

The producer can identify the problem and recommend options. The team can explain what needs to change. But who can approve the extra funding? Can the studio adjust the release plan, or does that decision belong to the parent company? If the parent declines to invest further, is there an agreed way to reduce scope, support the people affected or explore another option?

I have deliberately made this a fictional example. It is not an account of a particular deal, and I do not know what any real agreement would say. The point is that the same development problem can have very different consequences depending on decisions made when the acquisition was negotiated.

A risk register created after the announcement can help the team keep track of the situation. It cannot give the studio authority that it no longer has, or put an obligation into a contract that has already been signed. That is why I think these conversations belong in the deal process, not just in the first production meeting afterwards.

Who is able to carry the consequences?

There is a risk-management concept called moral hazard: someone can make a decision while another person bears some of the consequences. It is a useful lens here, although it is not an accusation that everyone involved in an acquisition behaves badly.

A founder, buyer and employee may all want the studio to succeed and still have very different exposure if it does not. Founders may receive payment when they sell, although some may retain financial obligations or depend on future performance. Buyers can lose their investment. Employees may face changes to their work, their project or their employment without having had a say in the transaction.

We should be careful about pretending that every acquisition produces the same result. One study using Canadian data across industries found that workers at acquired firms experienced earnings losses after mergers and acquisitions, driven by those who moved to other firms. It was not a study of games studios, and it cannot tell us what will happen in a particular deal. It does, however, give us a reason to take the possible effects on employees seriously rather than treating them as an afterthought.

People at the studio may also have less information than the people negotiating the agreement. Some details will legitimately be confidential. That makes it more important, not less, to explain what can be explained and to avoid turning uncertainty into reassurance that nobody is actually able to guarantee.

Risk

If/then wording

Owner

Mitigation

Autonomy risk

If autonomy is only informal, then portfolio pressure may override studio judgement.

Founder / Board.

Define autonomy period, reserved matters and decision rights.

Staffing downside risk

If forecasts miss after shareholders realise value, then staff may absorb the later downside.

Board / People Lead.

Agree retention, severance and consultation protections.

Strategic drift

If parent priorities change, then the studio may lose support despite strong delivery.

Studio Head.

Define strategic review gates and fallback plans.

Integration risk

If shared services are imposed too quickly, then local delivery systems may slow or break.

Integration Lead.

Phase integration and preserve critical local workflows.

IP/tooling risk

If the parent cancels the project, then the team may lose reusable technology or creative value.

Legal / Studio Leadership.

Negotiate reuse, licensing or buyback rights where possible.

Forecast risk

If the deal model assumes aggressive growth, then later correction may require layoffs or closure.

CFO / Portfolio Lead.

Use staged hiring, milestone confidence reviews and downside scenarios.

Questions worth asking before the deal is done

If you are considering a sale, I would want to understand the assumptions behind the buyer’s plan. Is the proposed investment sufficient if development takes longer? What commitments are firm, and what depends on future performance or approval? If the business needs to change direction, who has the authority to make that call?

I would also look carefully at the things the studio relies on to make games. What happens to the teams, the tools and the intellectual property? Which decisions remain with the people running the studio, and which move to the parent? What does integration actually involve for the people who will have to do it alongside their existing jobs?

There may be ways to negotiate protections, transition arrangements or clearer decision rights. Whether those are available depends on the deal and the parties’ bargaining positions. A sensible discussion with appropriate legal and financial advisers is rather more useful than assuming that a friendly conversation will settle every question for the next few years.

For the people working at a studio, it is reasonable to ask what the change means for the current projects, reporting lines, working practices and future decisions. You may not receive every answer immediately. It is still worth knowing which decisions have been made, which remain open and when you can expect an update. Employment rights and consultation requirements also vary by jurisdiction, so questions about those need advice appropriate to your situation.

Question

Why it matters

What is the buyer really buying: IP, team, technology, market access, revenue, optionality or credibility?

It clarifies what must be protected after the deal.

What assumptions justify the valuation?

It exposes the forecast fragility inside the transaction.

What happens if those assumptions fail?

It tests whether downside planning exists.

Who can change the studio strategy after close?

It identifies control risk.

What decision rights remain local?

It protects operating autonomy.

What protections apply to staff if the parent changes direction?

It tests whether the language of security is real.

Can the studio survive in another form if the deal fails?

It creates alternatives before closure becomes the only visible option.

Talking honestly with the team

I can understand why leaders want to announce a deal positively. They may have spent months working towards it, and they may genuinely believe it offers the best future for the studio. But if the people listening are worried about their jobs or the game they are making, a list of exciting opportunities might not answer the question they are actually asking.

Tell people what has been agreed, what is expected to change and what is not yet known. If a decision belongs to the new owner, say so. If the answer depends on a later review, explain what that review will consider and when people should hear more. There will be limits to what can be shared, but those limits are easier to understand when they are acknowledged rather than disguised as certainty.

None of this requires a studio to be pessimistic about an acquisition. It requires the people involved to think seriously about the future they are asking the team to help create.

Communication item

Purpose

Initial deal explanation.

Explain why the deal happened and what changes now.

Decision-rights summary.

Clarify who owns what after the transaction.

Integration risk update.

Make operational changes visible.

Milestone confidence review.

Show whether the plan still holds.

Staff protection update.

Revisit commitments made at announcement.

Portfolio context update.

Explain parent-company changes that affect the studio.

A risk worth discussing early

I am not arguing that studios should never be sold, or that founders should feel guilty for receiving a return on something they have built. I am arguing that an acquisition changes the production environment, sometimes in ways that are difficult to reverse once the paperwork is complete.

If we care about the studio after the deal, we need to look beyond the announcement and consider how it will work when the plan meets the usual complications of making a game. Who has the information, who can make a decision and who will live with the consequences if that decision turns out to be wrong?

Those questions are worth asking while there is still an opportunity to influence the answers.

For more on the way I approach these conversations, my book Risk Management for Video Game Professionals and Studio Risk Management course cover risk management in game development.