Project management for 3D and animation studios, 2 to 10 people
A studio of two to ten people needs a shot list, versions, a review step and a deadline for each one. Production trackers do that very well and cost more setup than a small studio has time for. Here is what to use instead, with the trade-offs.
The short answer
A small 3D or animation studio needs a list of shots or assets, a version history for each, a review step where the client comments on frames, and a deadline per item. Under about ten people, that fits in a board tool or a project app. ShotGrid (now Autodesk Flow Production Tracking), ftrack and Kitsu are built for pipelines with departments, pipeline integrations and hundreds of shots. They work for a studio of five, but you pay in setup and per-user fees.
The rest of this guide covers what to track, where each option breaks and what we would pick at each size. For a wider tool comparison, see best project management software for 3D studios.
What a 3D studio tracks that a normal agency does not
A web design agency tracks tasks. A 3D or animation studio tracks things that have versions.
- Shots or assets. A 40-second spot might have 14 shots (SH010 to SH140), each with its own artist, status and deadline.
- Versions. SH030_v001.exr, SH030_v002.exr, SH030_v003.exr. The client needs to know which one they are looking at.
- Render time. A 4K frame at 18 minutes, 240 frames, is 72 hours of machine time. Someone has to know that before the Friday deadline.
- Client rounds on frames. "Frame 112, the logo is too small" is the unit of feedback.
- Freelancers. A rigger for two weeks, a compositor for four shots, in another time zone and another currency.
A generic task board has a card per task and a due date. It has no notion of a version or a frame. That is the gap the production trackers fill, and the gap you work around with naming rules if you pick something simpler.
Shots, assets and versions
Pick the unit of work first. For an animated spot it is the shot. For a product or archviz job it is the view or the asset. Make one ticket per unit, and give it a name that matches the file: SH030, not "Hero close-up".
Use the same code in three places: the ticket, the folder and the file name. If the artist exports `SH030_anim_v004.mov`, the ticket for SH030 holds that version and nothing else. Studios that skip this end up with "final_v2_REAL.mov" and a client commenting on the wrong cut.
Keep statuses short. Five is enough for most small studios: not started, in progress, ready for review, with client, approved. More than that and nobody updates them.
Render queues without a render manager
Small studios mostly render on their own machines or on a farm such as Deadline or a rented cloud service. A project tool does not manage the queue. It needs to hold three facts: what is rendering, when it should finish and what waits on it.
The simple way is a ticket per render job or a line in the shot ticket: "SH030 final, 240 frames, about 18 min a frame on 3 machines, done Thursday 06:00". When a render fails at frame 190, the ticket shows what slips. Estimate render time per shot at the quote stage as well. A studio that quotes 14 shots without checking that 6 of them are heavy fluid sims is the studio that works a weekend.
Client rounds on frames
The expensive part of animation is not the first pass. It is round three, when the client sends a PDF saying "make it feel warmer" with no frame number.
Fix this in three steps.
- Put the number of rounds in the quote: two included, the third billed at the day rate.
- Send each round as a new version with a number, and keep the old versions.
- Take comments on the frame or the second, in one place, not in email.
Tools that do frame comments: ShotGrid and ftrack have their own review, and Frame.io, Filestage and others are review-only products. Whichever you pick, one person on the client side collects the notes into one list. The video side is covered in video review and approval for small studios.
Freelancers
Most small studios run on a core of two to four people plus freelancers booked by the job. The question is whether a freelancer needs a paid seat.
In a pipeline tracker, a freelancer is usually a named user. That is $390 a year in Flow Production Tracking for one rigger who works two weeks. In ftrack, external collaborators are free for review. In a board or project app, you can often share one project or one ticket by link.
Give the freelancer the ticket, the brief, the reference and the file naming rule, and one place to upload. Pay by deliverable, not by hour, and write it down. For more on briefs and handover, see managing freelancers in a 3D studio.
Why ShotGrid and ftrack are often too much
ShotGrid, ftrack and Kitsu solve problems a ten-person studio mostly does not have: dozens of departments, hundreds of shots, artists who publish from Maya or Nuke into a database, and a producer who needs a daily dashboard.
The cost is setup. Someone has to define entity types, statuses, templates and the naming scheme before the first shot is tracked. In a studio with no pipeline TD, that someone is you, on a Sunday. If you do have pipeline code that publishes versions automatically, that setup pays for itself. If you do not, you are typing into a database that does nothing a spreadsheet could not.
Prices as of November 2026, from each vendor's pricing page (details in ShotGrid pricing and cost):
| Tool | Price per user | Five users, one year |
|---|---|---|
| Flow Production Tracking | $390 a year, or $50 a month | $1,950 yearly |
| ftrack Studio | $25 a month billed yearly, $30 monthly | $1,500 yearly |
| Kitsu (CGWire) | EUR 20 a month billed yearly | EUR 1,200 yearly |
| OIO Studio | $99 a month for 5 seats | $1,188 at the monthly price |
Kitsu is open source, and you can self-host the code for free if someone on the team will run a server. Read the head-to-head pages for ShotGrid, ftrack and Kitsu before deciding.
Spreadsheets, Trello, Notion and OIO
Here is what the simpler options do well and where each one breaks.
A spreadsheet is the fastest start. One row per shot, columns for artist, status, version, due date and render notes. It works for one job and 20 shots. It breaks when you have three jobs at once, when two people edit the same row and when the client needs to comment. There is no review and no history of who changed what.
Trello is a board with a card per shot. Cards take attachments, checklists and due dates, and a freelancer can see one board. It is cheap and quick to learn. It has no review on frames, no budget per project and no invoice, so the money lives in another app. The free tier has limits that change, so check Trello's pricing page the day you decide.
Notion gives you a database of shots with whatever properties you define, plus a doc per project. It is flexible and it takes an afternoon to build and a month to maintain. Like Trello, it has no frame-level review.
OIO is project management for client work. Each job is a project page with tickets (one per shot or view) on a board or timeline, files, a deadline, a budget and hours. The client opens a link without an account, pins comments on stills or comments at the second on a video, and clicks Approve this version. Each round is a new version on the ticket. A freelancer works from a link to their ticket and uses no seat. The quote and the invoice come from the same project. Plans: Free for 1 project, Lite $5, Solo $19, Studio $99 for 5 seats, with a 7-day trial. Lite is a personal plan without client tools, so the review features start at Solo.
OIO does not have what the production trackers have. There is no shot and asset database, no integration with Maya, Blender or Nuke, no render farm management and no drawing on the frame. If you need those, use a tracker.
What we would use at each size
- One or two people, one job at a time: a spreadsheet and a shared folder. Add a tool when the second client arrives.
- Three to ten people, several jobs, clients who give feedback: a project app with review built in, or a board plus a review tool. Count the number of apps you would have to keep in sync.
- Ten or more people with a pipeline TD and publish scripts: Kitsu, ftrack or Flow Production Tracking.
Before you pay for anything, run your next job in it for two weeks. Track every shot, send every round through it and invoice from it. Count how often you went back to email.
Set-up checklist for the next job
- List the shots or views and give each a code (SH010, SH020).
- Put the file naming rule in the project: `CODE_task_vNNN`.
- Write the rounds into the quote: two included, third billed.
- Add a deposit of 30% before the scene file opens, and the rest net 14 after delivery.
- Estimate render time per shot and put the heavy ones on the schedule first.
- Give each freelancer one ticket, one brief and one upload place.
- Name one person on the client side who collects the notes.
Use the day rate calculator to get the number the quote starts from.
Questions
What is the best project management software for animation studios?
For ten people or fewer, a project app with versions and client review is enough, and a production tracker is not needed. Above that, or with pipeline scripts that publish versions, Kitsu, ftrack or Flow Production Tracking fit better.
Is ShotGrid worth it for a small studio?
Only if you have artists publishing from Maya or Nuke and someone to set the database up. Flow Production Tracking costs $390 a year per named user as of November 2026, so five users is $1,950 a year before setup time.
Can I use Trello or Notion for a 3D studio?
Yes, for tracking shots and deadlines. Neither has frame-level client review or invoicing, so you add a review tool and an invoicing tool next to them.
How do I track render times in a project tool?
Put the frame count, the time per frame and the finish date in the shot ticket. The tool will not manage the queue, but it shows what slips when a render fails.
Do freelancers need a paid seat?
In Flow Production Tracking a freelancer is a named, paid user. Some tools share a project or ticket by link without a seat, which suits a freelancer who works on one job for two weeks.