The Back-Office Overhaul Nobody Sees on the Store Page
A finance lead at a mid-size studio has three browser tabs open at once: the ad platform showing yesterday's user acquisition spend, a spreadsheet tracking royalty splits for a co-developed title, and an ERP screen still waiting on a vendor bill from a mocap house that closed two weeks ago. Nothing ties. The campaign dashboard doesn't match the general ledger, the royalty spreadsheet is on version 14, and the vendor bill has a manual note attached because the PO template has no field for the way that contract was structured.
This is a Tuesday. It's also, more and more, the reason a lot of game companies are rebuilding their back office.
The shift doesn't show up in trailers or launch announcements. It shows up in job postings for controllers, in RFPs for new finance platforms, and in the decision to retire a stack of tools the studio outgrew two years ago. Here's what's driving it, and what studios are changing.
Why Are Studios Touching This Now?
Growth used to hide operational sloppiness. When revenue climbed every quarter, nobody minded that finance closed the books eleven days late, or that the CRM and the billing system disagreed about who the customer was.
Growth has slowed while costs have kept climbing. A Workday study on studio operations put it plainly: many studios expanded fast without ever fully building out the back-office functions to match, and the inefficiencies that were tolerable during the boom are now the thing eating margin.
The layoff cycle made it worse. When EA cut roughly 670 jobs in early 2024, it was part of a wider contraction that has continued in fits and starts across the industry. Smaller teams inherited the same reporting requirements, the same vendor list, the same publisher royalty schedules, with fewer people to run them. Something had to give, and for a lot of studios what gave was the tolerance for manual work.
What Do Studios Actually Need That They Don't Have?
Most studios don't need a fancier accounting screen. They need the operating layer underneath to stop pretending each department lives on its own planet. The recurring complaints sound the same across companies of very different sizes.
- One version of the customer. Marketing, billing, and support each hold a different record for the same player or licensee, and none of them reconcile without a person in the middle.
- Project-level cost visibility. Finance can see total spend by month but can't cleanly answer what a single title cost to build once outsourced art, contract engineering, and platform fees are folded in.
- Royalty and revenue-share accuracy. Co-dev deals, publisher splits, and storefront cuts live in spreadsheets that break every time a contract term changes.
- A vendor process that scales. AP still runs through inboxes and PDFs, so onboarding a new outsourcer or paying a milestone on time depends on who happens to be watching the folder.
Where Is the Money Actually Getting Lost?
Ad spend is the loudest offender. User acquisition is often the single largest line on a mobile studio's income statement, and it moves by the hour. When the media buying tools live in one system and the booked revenue lives in another, the studio ends up managing a very expensive channel on lagging data.
Campaigns get killed too late. Winners get scaled too slowly, and the finance team writes a monthly attribution memo that everyone politely ignores.
The other leak is vendor management. Modern productions run on a long tail of external contributors: outsourced art, localization houses, QA farms, contract engineers, voice talent, mocap. Every one of them sends an invoice with its own quirks. When the AP process is a shared inbox and a folder of PDFs, something usually slips, whether it's a duplicate payment, a missed early-pay discount, or a contractor who falls off the payroll six months late.
What Are Studios Replacing the Old Stack With?
The direction of travel is toward fewer systems that share the same underlying record. Instead of a CRM, a billing platform, an FP&A tool, a data warehouse, and a homemade royalty calculator, studios are moving to platforms where sales, operations, finance, and analytics sit on one graph. A recent ERP.io coverage on sina.com.hk describes exactly that approach: an AI-native ERP and CRM built as a single system rather than two products bolted together after the fact. Whether a studio picks that platform or another, the pattern is the same. Consolidate the record, put automation on top of it, and stop paying people to move data between tabs.
The AI piece isn't magic; it's a reader. Agents that can pull a vendor bill out of an inbox, code it against the right project, check it against the PO, and route it for approval remove the exact busywork that grows fastest as a studio scales.
The controller still owns the close. The AI just stops making them do the coding by hand.
What Should a Studio Do Before Buying Anything?
None of this shows up in the credits. It shows up in the runway. Studios that get the back office right buy themselves the time and the margin to make the next game, and when the next contraction comes, they're not the ones scrambling to figure out what they actually spent.
