Entrar / Registro
About StudioOps

Why StudioOps

StudioOps grew out of a legal guide for game studios. Along the way we kept seeing the same thing: small studios do not fail for lack of talent, but because of production problems that large studios solved long ago with people, processes and tools a small team does not have. These are the problems we have seen, where we learned about each one, and what StudioOps does about it.

We do not name our sources: some are private conversations and others are material we do not have permission to quote. We describe what kind of source each one is.

  1. 01

    Ambition collides with budget and schedule

    SourceA Lead Producer job description at a AAA studio
    What we learned

    The core job of whoever produces a game is balancing what the team wants to make against the money and time available. In a big studio that is a full-time role. In a small one it is done by whoever has time, and almost always too late.

    What StudioOps does

    In Blueprint every game element (character, level, mechanic) becomes tasks with hours and cost. The Budget tab compares what was approved, estimated and spent, and warns you when spending runs more than 15 points ahead of progress.

    See Blueprint
  2. 02

    Managing up and sideways

    SourceA conversation with a producer at a AAA studio
    What we learned

    What changes most when moving from an indie team to a large one is not just scale: a big part of the job is dealing with different levels of stakeholders, up (leadership) and sideways (other studios and departments). Experience weighs the most, but experience from other fields counts too if it shows that. In a team of five there are hardly any levels, so the skill is not practiced. Still, a small studio has people to report to: a publisher, an investor, a government program, a co-development studio. And each one needs a different version of the same project.

    What StudioOps does

    Each level already has its piece. The team: Workflow tasks, who is working on each asset and 1:1s in Meetings. Whoever leads: the Blueprint Budget tab, with approved vs. spent and estimated vs. actual hours. The publisher: a per-build status report from QA and the per-milestone delivery record from the co-development contract. An institution: aggregated indicators for the studios it supports. And the Project report builds, from what you already entered, a version for each level: what it shows each audience and also what it leaves out.

  3. 03

    Jumping between ten tools

    SourceA conference talk by the tools team behind a AAA engine
    What we learned

    Their goal for the editor was that each person could stay in a single program to do their work. Every time someone leaves for another app (a spreadsheet, a board, a chat) context is lost and someone stops being in the loop.

    What StudioOps does

    Design docs, Blueprint, Pipeline, Assets, Storyboard, QA and Budget live in the same project and read from each other. You do not copy data from one tool to another.

    See how they connect
  4. 04

    From spreadsheets to approved versions

    SourceA published case study on the production of a AAA open-world game
    What we learned

    They used to coordinate verbally and with one spreadsheet per team; nobody saw anyone else's progress. When they moved to a shared tool, every asset had its history, corrections were drawn on top, and it was clear which version was approved and when.

    What StudioOps does

    Assets keeps versions, drawn markups and approvals with who and when. Pipeline shows every element by stage, with S/A/B/C quality, image history and who is working on it.

    Not yetAnnotating directly on video.
  5. 05

    Spending before validating

    SourceA public analysis of Steam launches
    What we learned

    Of the self-published games that cost around half a million dollars, roughly one in 75 earned back what was spent. The problem was not that they were bad games: their cost structure needed an exceptional hit just to break even.

    What StudioOps does

    Budget starts with a Phase 0 commercial validation: it compares your game with similar games (their median, not the best sellers) before you commit the money.

  6. 06

    Wishlists are not sales

    SourceA post-mortem by an indie studio with a previous hit
    What we learned

    A good game launched with about 4,000 wishlists and its first week brought in around 8,000 dollars. The demo was its best moment, the Steam festival added little, and contacting hundreds of creators got few replies.

    What StudioOps does

    The marketing readiness check in Budget includes a "Worth considering" block with those risks, to review before you set the date.

  7. 07

    Design docs nobody opens again

    SourceDesign documentation tools we reviewed
    What we learned

    Very complete templates, but separate from production: the document says what game will be made and nothing connects it to what it costs or when it will be ready.

    What StudioOps does

    Game Docs lives inside the project, with the team editing in real time, comments and versions, next to the Blueprint that turns that design into work.

  8. 08

    Cutting scope too late

    SourceWorkbooks and books for producers
    What we learned

    Cutting scope is normal; what is expensive is doing it after the time is spent. To cut in time you need to see early how far actual work drifts from the estimate.

    What StudioOps does

    Every task stores estimated and actual hours. Budget shows the difference per task and per area, and when an area drifts 20% or more it tells you what to multiply your next estimates by.

  9. 09

    Who owns what we made?

    SourceThe legal guide this platform grew out of
    What we learned

    The most common legal problems in small studios are not lawsuits: they are art, music or code with no contract, and nobody knows who owns it when a publisher or a buyer shows up.

    What StudioOps does

    Each asset says where it came from (made by me, a partner, an employee, a freelancer, bought, Creative Commons, AI) and the platform tells you which contract or license is missing. Credits are generated as tasks are completed, not from memory at the end.

    See legal origin

StudioOps is free and is built with feedback from the studios that use it. If you produce games and something here does not match your experience, we want to know.