What a Fractional Head of Growth Does for a Game Studio
A fractional operator sits inside your rituals part-time, owning the system while the team owns the execution. It works best for studios past product-market fit and before a full leadership layer.
What is a fractional head of growth?
An experienced operator who works inside your company part-time — usually two days a week or so, for a minimum of a few months — owning how growth and monetization decisions are made, while your team owns the day-to-day execution. It sits between a consultant (outside, bounded) and a full-time executive (inside, indefinite).
When does it work best?
- The game works. There is product-market fit or a clear soft-launch signal; the question is how to scale it well.
- The team is capable but thin at the top. Strong UA, AdOps or analytics people, no one owning the whole loop.
- The next 6–12 months hold big decisions — scaling, mediation, new markets, a web shop, a raise.
- You are not ready to define the full-time role. The fractional period does the work and writes the job description.
What does the role actually do?
- Runs the weekly growth and monetization review: what moved, why, and what we decide.
- Sets evidence bars for spend decisions and guardrails for monetization tests.
- Builds the metric architecture and review cadence — see the KPI Tree tool.
- Coaches the team and makes the calls that need cross-functional judgment.
- Manages key partner relationships where experience matters.
What does it not do?
Run campaigns day to day, manage every placement, or replace the team. If the need is execution capacity, an agency or a hire is the better fit — see Consultant, Agency or Full-Time Hire?.
How do you judge whether it is working?
After the first month you should see faster, clearer decisions and fewer recurring arguments. After a quarter: a working review rhythm, agreed definitions, tests that ship with guardrails, and measurable progress on the one or two numbers that matter most. At the end, the team should be able to run the system without the operator.
This is what I call the Embedded role — typically two days a week with a three-month minimum, scoped on the first call. I built and ran a 24-person team across AdOps and monetisation, UA and creative, ASO, analytics and MIS at Games2win, and the lesson that carries over is simple: the system has to work when you are not in the room.