Skip to main content
GullySystem
Other industries

Business solutions for Animation studios

Explore software for work such as “A clear scope and revision policy in every proposal”. Review each business function below, including when it fits and what to check before implementation.

Animation studios

How the business operates.

An animated production is a pipeline. A storyboard becomes an animatic, the animatic becomes a list of shots, and every shot needs characters, backgrounds and props that must be built first. Each stage belongs to a different artist, who may be a freelancer on a short contract joining in the middle of the production and leaving before the final render.

Bid and budget by shot

Price the job by minute, episode or shot, and compare artist hours and render charges with that bid as work proceeds.

Script, storyboard and animatic

Hold each sequence from script breakdown to board and animatic, with the approved version and its running time.

Shot list and status board

List every shot with its stage, artist, frame count, due date and retake count in one grid.

Asset library and versions

Track characters, props, backgrounds and rigs with their versions and the shots that use each one.

Artist booking and timesheets

Plan staff and freelancers week by week, record hours against each shot, and see who has room before a delivery date is promised.

Review notes and retakes

Record director and client notes against a shot and frame, assign the retake and show it when resubmitted.

Render queue and delivery

Log render hours per shot and tick the formats, audio and subtitles the client asked for at delivery.

Voice and music cue sheet

Dialogue lines, voice actors and music cues are listed for each scene. Sound editors see which lines are recorded. Fees for talent and composers link back to the cue.

Outsourced shots and partner studios

Shots sent to partner studios are logged with the vendor, the brief and the return date. Producers compare delivered shots against what was ordered. Vendor invoices are matched to the shots listed.

Software licences and seats

Licences for modelling, rigging and compositing packages are recorded with seat counts and renewal dates. The pipeline lead sees which artists hold a seat. Idle seats are reclaimed before renewal.

The records that hold the operation together.

  • Bids and budgets by shot. Price a production by minute, episode or shot, and compare artist hours and render charges with the bid as work proceeds.
  • Script breakdown and boards. Break the script into sequences and shots, and keep storyboard and animatic versions with their running time and approval.
  • Shot list and status grid. List every shot with stage, artist, frame count, due date, retake count and the assets it needs.
  • Asset library and versions. Track characters, rigs, props, backgrounds and textures with version history and the shots that use each one.
  • Artist booking and capacity. Book staff and freelancers by week and skill, and see who is free before a due date is promised.
  • Timesheets and freelance rates. Log hours by shot and stage, apply each artist’s rate and currency, and list what is payable for the period.
  • Review sessions and retake notes. Capture notes against a shot and frame during review, assign the retake and show the resubmitted version beside the note.
  • Render queue and farm charges. Record render jobs per shot with hours, farm and charge, and flag a sequence that has used its estimate.

Operational bottlenecks to check

Shot status lives in a spreadsheet

A coordinator updates the sheet each evening, after a shot has already moved a stage, so the supervisors plan the next morning from rows that are no longer true.

Assets are used in the wrong version

A rig is fixed after the character’s costume changes. Two animators work on shots with different versions, and the difference surfaces in review.

Retake notes are scattered

The director’s note is spoken in a review, written in chat and typed again by a coordinator. The artist receives it a day later. The shot slips.

Artist bookings clash

A freelance animator is promised to two shows for the same fortnight. The conflict is found when one of them does not arrive. Schedules slide.

Cost per shot is unknown until the end

Hours are tracked by week and render charges arrive on a monthly invoice. The bid is compared with actual cost only after the last shot is delivered.

Follow the work across teams.

This is a planning flow. Confirm the steps, owners and approval rules against your actual operation.

  1. 1. Bid and set-up

    The producer prices the job by minute, episode or shot, and the production is opened with its pipeline stages and a rate card.

  2. 2. Script and boards

    The script is broken into sequences and shots. Storyboards and the animatic are saved as versions with the director’s approval.

  3. 3. Asset build

    Characters, props and backgrounds are assigned to modellers, riggers and painters, then published as versions that shots can use.

  4. 4. Shot production

    Each shot is assigned to an artist and moves through layout, animation, effects, lighting and compositing, with hours logged at each stage.

  5. 5. Review and retakes

    Notes from the director and the client are recorded against the shot and frame, and the retake returns to the artist.

  6. 6. Delivery

    Renders, audio, subtitles and metadata are checked against the client’s specification, and final cost is compared with the bid.

Roles and responsibility boundaries.

For producers

See cost against the bid, shots behind schedule, artists booked and invoices due on milestones.

For production managers and coordinators

Keep the shot grid, assign artists, chase retakes and check which assets are ready.

For directors and supervisors

Run review sessions, write notes against frames and check the retake count for each sequence.

For artists

Open assigned shots with layout, audio, notes and the latest asset versions, and log hours as you work.

For pipeline and render technicians

Monitor render jobs, farm hours and the shots queued, and record failures for resubmission.

Reports your managers need.

  • Bid against actual cost by sequence
  • Shots by stage and past due
  • Retakes per sequence and artist
  • Artist bookings and free capacity
  • Render hours and farm charges by shot
  • Freelance hours payable by period
  • Delivery checklist status by client

Connections to scope

  • Email
  • Spreadsheet import
  • Accounting export
  • Cloud storage links
  • Calendar
  • Chat notifications
  • Shot-tracking tool import

Confirm data access, record ownership and the exchange method for each connection. Inclusion here does not mean every connection is available in a standard package.

Setup decisions and adoption risks.

Use these requirements to plan phases, data migration and user training. Agree the release sequence after reviewing your current systems.

Your pipeline stages

Layout, animation, effects, lighting and compositing are named and ordered the way your studio works, whether 2D, 3D or stop-motion.

Rate cards and currencies

Day and hourly rates are entered per role and per freelancer, and the currency and tax treatment for each country is checked during implementation.

Shot lists brought across

Spreadsheets holding shot grids, asset lists and artist rosters are imported, and the production manager checks each sheet before the first show goes live.

Links to your pipeline tools

File paths and status updates can connect to the tools your artists already use. Which tools get linked is settled during scoping.

Hosting and changes

GullySystem hosts the system, and your scene files stay on your own storage. GullySystem staff edit stage lists, forms and reports when you ask.

Limitations to settle before implementation

  • A one-artist studio making occasional short pieces can manage with a task list and a timesheet.
  • A studio that only needs a render manager and file versioning will find a pipeline tool fits that part better.

Choose the operation you want to improve.

Use these activities to explain your scope. Your business does not need every function in the directory.

  • A clear scope and revision policy in every proposal
  • Series and IP pitches for producers
  • Approval and feedback tracking
  • A visible freelancer and team structure
  • Proposal follow-up
Talk to us

Start with the problem your team can describe.

Bring a sample record and show where information is copied, missed or waiting for approval. Scope the first useful change from there.

What happens after you share your requirements

  1. We review your brief and the systems you already use.
  2. We clarify the workflow, missing information and the work to consider first.
  3. The proposed scope sets out the deliverables, responsibilities and dependencies.
  4. Review the scope and commercial terms before deciding whether to proceed.

Start with your requirements

Describe your current process, the people involved and the change you need. Start with the details you know; we can clarify the rest together.

Share your requirements