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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
Usamos Google Analytics para medir visitas y mejorar el sitio. ¿Aceptas el seguimiento?
Aviso de Privacidad
Última actualización: noviembre 2026
Responsable: Indie Games México — indiegamesmexico.com — contacto: hello@indiegamesmexico.com
Datos que recopilamos
Este sitio usa Google Analytics 4 (GA4), un servicio de analítica web de Google LLC. GA4 recopila de forma automática: dirección IP anonimizada, tipo de navegador y dispositivo, páginas visitadas, tiempo de permanencia, ubicación geográfica aproximada (país/ciudad) y eventos de interacción.
Si creas una cuenta, guardamos tu correo y los datos que tú capturas en tu estudio y tus proyectos, solo para darte el servicio. No vendemos ni compartimos datos con terceros fuera de los proveedores que hacen funcionar el sitio.
Finalidad
Entender cómo se usa el sitio, mejorar su contenido y operar tu cuenta. No usamos los datos para publicidad ni perfilamiento.
Usa modo incógnito o un bloqueador de scripts (uBlock Origin)
Elige "Solo esenciales" en el aviso de cookies
Tus derechos (ARCO)
Puedes ejercer tus derechos de Acceso, Rectificación, Cancelación u Oposición escribiendo a hello@indiegamesmexico.com. Responderemos en un plazo de 20 días hábiles conforme a la LFPDPPP.
Ref: LFPDPPP — Reglamento de la LFPDPPP
Last updated: November 2026
Data controller: Indie Games México — indiegamesmexico.com — contact: hello@indiegamesmexico.com
Data we collect
This site uses Google Analytics 4 (GA4), a web analytics service by Google LLC. GA4 automatically collects: anonymized IP address, browser and device type, pages visited, time on page, approximate location (country/city) and interaction events.
If you create an account, we store your email and the data you enter in your studio and projects, only to provide the service. We do not sell or share data with third parties beyond the providers that run the site.
Purpose
To understand how the site is used, improve its content and run your account. We do not use the data for advertising or profiling.
Use private browsing or a script blocker (uBlock Origin)
Choose "Essential only" in the cookie banner
Your rights
You can request access to, correction or deletion of your data, or object to its use, by writing to hello@indiegamesmexico.com. We will reply within 20 business days, as required by Mexican data protection law (LFPDPPP).
Ref: LFPDPPP — LFPDPPP Regulations
Última actualización: noviembre 2026
Importante: GameDev Legal MX es un recurso educativo informativo. El contenido y las herramientas de este sitio no constituyen asesoría legal, fiscal ni contable y no reemplazan la consulta con un profesional.
1. Naturaleza del sitio
GameDev Legal MX y StudioOps son una guía educativa y un conjunto de herramientas gratuitas para desarrolladores de videojuegos. La información tiene carácter divulgativo y orientativo.
2. De dónde sale el contenido y las herramientas
Las guías, calculadoras, simuladores, plantillas, generadores y herramientas de producción se basan en la investigación, la capacitación y la experiencia práctica de las personas que los crearon, y en fuentes públicas consultadas en su momento. No son productos profesionales certificados. Las leyes, tarifas, plazos y precios cambian, y una herramienta puede no reflejar tu situación particular.
3. Tu responsabilidad
Cada persona y cada estudio es responsable de cómo usa la información y las herramientas. Antes de firmar un contrato, presentar un trámite, declarar impuestos o tomar una decisión de negocio, revisa el resultado, adáptalo a tu caso y confírmalo con un profesional (abogado, contador) y con las fuentes oficiales. Las plantillas de contratos y documentos son modelos base, no documentos listos para firmar.
4. Sin garantía
Las herramientas se ofrecen "tal cual", sin garantía de exactitud, disponibilidad ni resultados (por ejemplo, que se apruebe un registro de marca, que un presupuesto se cumpla o que un juego venda). Podemos cambiar, mejorar o retirar funciones en cualquier momento.
5. Limitación de responsabilidad
Indie Games México no es responsable por decisiones legales, fiscales, laborales o comerciales tomadas con base en el contenido o las herramientas de este sitio, ni por los datos o documentos que cada usuario captura, sube o genera.
6. Sin relación abogado-cliente
El uso de este sitio, incluida la participación en talleres o programas con instituciones, no crea ninguna relación de asesoría legal, contable ni de representación.
7. Conducta
Pedimos un trato respetuoso en los comentarios, mensajes y reportes que envías a la plataforma y a su equipo. Podemos suspender cuentas que usen lenguaje ofensivo, acoso o amenazas.
8. Propiedad intelectual del contenido
El contenido, diseño y código de este sitio son propiedad de Indie Games México. Puedes compartir o citar con mención de la fuente para fines educativos no comerciales. Lo que tú capturas en tus proyectos es tuyo.
9. Contacto
hello@indiegamesmexico.com
Last updated: November 2026
Important: GameDev Legal MX is an informational educational resource. The content and tools on this site are not legal, tax or accounting advice and do not replace consulting a professional.
1. Nature of the site
GameDev Legal MX and StudioOps are an educational guide and a set of free tools for game developers. The information is for general guidance and educational purposes.
2. Where the content and tools come from
The guides, calculators, simulators, templates, generators and production tools are based on the research, training and hands-on experience of the people who created them, and on public sources consulted at the time. They are not certified professional products. Laws, fees, deadlines and prices change, and a tool may not reflect your particular situation.
3. Your responsibility
Each person and each studio is responsible for how they use the information and the tools. Before signing a contract, filing a procedure, reporting taxes or making a business decision, review the result, adapt it to your case and confirm it with a professional (lawyer, accountant) and with official sources. Contract and document templates are base models, not documents ready to sign.
4. No warranty
The tools are provided "as is", with no warranty of accuracy, availability or results (for example, that a trademark is approved, that a budget holds or that a game sells). We may change, improve or remove features at any time.
5. Limitation of liability
Indie Games México is not liable for legal, tax, labor or business decisions made based on the content or tools of this site, nor for the data or documents each user enters, uploads or generates.
6. No attorney-client relationship
Using this site, including taking part in workshops or programs with institutions, does not create any legal, accounting or representation relationship.
7. Conduct
We ask for respectful communication in the feedback, messages and reports you send to the platform and its team. We may suspend accounts that use offensive language, harassment or threats.
8. Intellectual property of the content
The content, design and code of this site belong to Indie Games México. You may share or quote them with attribution for non-commercial educational purposes. What you enter in your projects is yours.