What In-House Playtest Researchers Actually Cost (And What Studios Do Instead)
Photo by on Unsplash
Hiring a full-time playtest researcher sounds like the mature, responsible move. You ship better games, you catch problems early, you build institutional knowledge. All true. But the studios that have done the math often arrive at a more complicated answer, and most of them wish they'd run the numbers before posting the job.
What a Playtest Researcher Actually Costs to Hire
The salary is the easy part. According to industry salary data from Game Developer, a mid-level games user researcher in a major market earns somewhere between $80,000 and $120,000 annually. Senior practitioners in competitive cities push higher. Add benefits, payroll taxes, equipment, software licenses, and onboarding time, and you're realistically looking at 1.3x to 1.5x the base salary as your true annual cost.
That's not a criticism of the role. A strong researcher earns every dollar. The question is whether a studio's current slate and headcount actually justify that spend year-round.
The Hidden Costs Nobody Budgets For
Salary is just the start. Before a new research hire can run their first proper session, they need infrastructure. That includes participant recruiting pipelines (which take months to build reliably for niche game audiences), testing software and observation tools, a physical or remote lab setup, and internal buy-in from the teams they'll work with. Many studios underestimate this ramp time by six months or more.
There's also the problem of utilization. Games research isn't a constant-throughput function. There are heavy periods, right before a milestone or leading into beta, and long stretches where a dedicated researcher has limited work to fill a full week. If your studio is between projects or in early pre-production, you're paying for capacity you can't fully use.
A 2023 survey from the Game User Research Special Interest Group (GRUX) found that researchers at smaller studios frequently cited "not enough work to fill my role" as a key frustration, alongside limited resources to recruit the right participants. Both problems compound each other: without robust recruiting infrastructure, the research you can run is limited, which makes the role feel underutilized, which makes it harder to justify headcount in the next budget cycle.
What the In-House Model Gets Right (When It Works)
To be fair, there are studios where in-house research is a genuine competitive asset. When a team is shipping multiple titles per year, when they have a defined live service operation requiring continuous feedback loops, or when research is embedded deeply into sprint cycles rather than bolted on at the end, a dedicated researcher (or a small research team) pays for itself.
The institutional knowledge argument is real too. A researcher who has lived with your game, your players, and your team's working style for a year can catch things an outside partner might miss in a four-week engagement. They know which features have a troubled history. They know which lead designer needs direct data to change their mind and which one trusts a qualitative summary. That context is genuinely valuable.
The trouble is that most studios aren't in that position when they first start thinking about hiring a researcher. They're usually responding to a pain point, a bad launch, a retention problem, an upcoming milestone with no feedback data, and they're making a long-term structural decision to solve a short-term problem.
The Outsourced Alternative: What You Actually Get
Working with an external research partner doesn't mean handing over control. The best setups keep the studio firmly in the driver's seat on questions, priorities, and interpretation, while offloading the parts that drain internal bandwidth: finding the right players, running the sessions, synthesizing hours of footage and survey data into something actionable.
For most studios below a certain headcount or release cadence, the math favors this approach. You pay for research capacity when you need it, not when you don't. You get access to pre-built recruiting infrastructure rather than spending six months assembling one from scratch. And you're not carrying a full-time salary through periods of low research demand.
The VGM team, for example, works with studios specifically to match the right players to the right test at the right moment in production, without the studio having to build that capability internally. If you're curious what that actually looks like in practice, the VGM services page is a reasonable starting point.
A Simple Framework for Making the Call
Before you post a job listing or sign a research contract, answer these four questions honestly:
How many titles are you shipping in the next 18 months? One title with a defined launch window probably doesn't justify a full-time hire. Two or more concurrent projects with overlapping research needs changes the calculation.
Do you have an existing participant pool? If the answer is no, you're not just hiring a researcher. You're building a recruiting operation from scratch alongside them. That's a much bigger investment than the salary line suggests.
What's your current research rhythm? If you're running one or two playtests per quarter and relying on ad hoc feedback the rest of the time, an external partner can cover that cadence at a fraction of the fully-loaded cost of an in-house hire.
Are you solving a structural problem or a timing problem? If you're scrambling because a launch is six weeks away and you have no data, hiring a researcher won't fix that, they won't be ramped up in time. That's an outsourced engagement situation. If you're planning for sustainable research across a multi-year roadmap, in-house starts to make more sense.
The Decision Isn't Binary
Many studios end up in a hybrid arrangement: one internal researcher who owns the relationship and synthesis, supported by an external partner for recruiting, session facilitation, and surge capacity around major milestones. That model captures the institutional knowledge benefits of an in-house hire while keeping costs variable enough to match the actual research workload.
Whatever you decide, the worst outcome is delaying the decision until there's a fire. Studios that build even a minimal, consistent research habit before they desperately need it almost always get better data and make better decisions with it.
Frequently Asked Questions
How much does it cost to hire a games user researcher?
Salaries for mid-level games user researchers in major markets typically range from $80,000 to $120,000 per year, with senior practitioners earning more. When you factor in benefits, tools, and recruiting infrastructure, the true annual cost is usually 1.3x to 1.5x the base salary figure.
When does it make sense to hire an in-house playtest researcher?
In-house research hires make the most sense when a studio is shipping multiple titles per year, running a live service that requires ongoing feedback, or has a defined research cadence embedded in sprint cycles. If research needs are sporadic or project-specific, outsourcing is usually more cost-effective.
What does an outsourced game research partner actually handle?
A good external partner handles participant recruiting, session facilitation, data synthesis, and reporting, the time-consuming operational work that pulls developers away from building. The studio stays in control of the research questions, priorities, and how findings are applied.
How long does it take to build an in-house research capability from scratch?
Most studios underestimate this timeline significantly. Building reliable recruiting pipelines, setting up testing infrastructure, and getting a new researcher fully integrated into production workflows typically takes six months or more before you're seeing consistent, high-quality output.
Can a small indie studio afford regular playtesting?
Yes, though the format matters. Smaller studios often benefit most from focused, milestone-based engagements with an external partner rather than continuous in-house capacity. Even two or three well-timed sessions across a production cycle can surface the problems that would otherwise cost far more to fix after launch.