Skip to main content
GullySystem
Other industries

Estimate/Quotation Management for Animation studios

Keep itemised estimates and their approved revisions together.

Finance & Accounting

Does this function belong in your operation?

Use when scope and prices are agreed before an order.

A buyer asks for pricing before confirming work.

A pitch for a thirteen-part children’s series is priced by shot count, asset builds and render time. Revisions to the quote keep earlier versions beside the new one. Producers send the client the version agreed.

Bring the records the workflow depends on.

  • Items and units
  • Rates and tax settings
  • Approval terms

Outputs to check

  • Versioned estimate document
  • Approval and acceptance history
  • Accepted billing or order input

Follow the estimate/quotation management workflow.

Use this sequence to compare your current process with the proposed module. Agree the owner, permission and exception at each step.

  1. 1. Record the requirement

    Capture scope, quantities and the customer's requested terms.

  2. 2. Prepare the estimate

    Use approved units, rates and tax settings.

  3. 3. Review exceptions

    Approve discounts, exclusions and nonstandard terms.

  4. 4. Issue and revise

    Retain the version sent and each subsequent change.

  5. 5. Record acceptance

    Link the agreed version to order creation or final billing.

Who uses the module, and who approves?

Keep responsibilities distinct even when one person holds more than one role.

Sales executive

Sees quotes waiting to be sent, quotes waiting on the client, and today’s follow-up list.

Estimator

Builds the costing behind the quote from measurements, material and labour, and keeps it beside the drawing.

Owner

Sees what went out this week, at what margin, and which discounts were given without being asked for.

Decide how exceptions are handled.

These business rules belong in configuration and testing. A normal transaction alone does not demonstrate that the workflow is ready.

Customer changes quantity

Save a revision and recalculate affected lines before acceptance.

Expired validity

Require the price and terms to be reviewed before using the estimate.

Discount beyond authority

Hold the revision for approval and retain the original proposed amount.

Can this work independently?

An estimate can be prepared independently from entered items and rates. Item catalogues, pricing and tax settings improve consistency when connected. Order creation and invoicing are downstream processes; acceptance should preserve the agreed version rather than overwrite the estimate with later rates.

Systems and records it connects with

  • Lead management: Enquiry sources, owners and qualification decisions.
  • Proforma invoice: Provisional supply amounts and related advance requests.
  • Invoice management: Issued invoice references, line amounts and outstanding balances.
  • Price lists and schemes: Effective-dated rates and customer eligibility rules.

Configure, test and introduce the workflow.

  • We read quotations you sent recently. You pass over the rate list and a few finished quotes, and we sketch the screen layout.
  • Items, units, discount limits and standard terms go in. Proofreading the list is yours. The printed quotation is matched to your letterhead. A draft PDF is sent for your comments.
  • Executives raise real quotes in parallel with the old method. Mismatches are logged and discussed. New enquiries start in the system. Estimators and executives get a short session each.

Check the result before rollout.

Apply these checks to a sample from the agreed workflow, then repeat with an exception. Keep the expected result beside the test record.

  • Earlier revisions remain available.
  • Totals use approved settings.
  • The accepted version is identifiable.
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.

See the full industry workflow, reports and implementation plan →

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.

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.

How work flows across this business

This module sits within a wider operating process. Use the sequence to identify the other teams and records affected by a change.

  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.

Industry reports to connect with

  • Bid against actual cost by sequence
  • Shots by stage and past due
  • Retakes per sequence and artist
  • Artist bookings and free capacity

Questions before implementation.

When should animation studios consider estimate/quotation management?

Use when scope and prices are agreed before an order. A buyer asks for pricing before confirming work.

What should we bring to the requirements discussion?

Bring anonymised examples of Items and units; Rates and tax settings; Approval terms. Show who creates, checks and changes each record. Use only records from an activity that meets the suitability conditions above.

Does this replace our existing business software?

The starting point is your current system and the gap you need to close. Keep itemised estimates and their approved revisions together. Configuration, a connected module or a custom build are evaluated against that gap before a replacement is proposed.

What is outside this module?

An estimate is not a tax invoice or proof of acceptance.

How are scope, price and rollout decided?

The proposal follows a review of your records, user roles, branches and existing software. Data migration, connections, training and support are scoped separately where needed. Earlier revisions remain available. Use this check when reviewing the first working version.

Talk to us

Discuss estimate/quotation management for your business.

Tell us which workflow needs attention and which systems your team uses. The next step is a requirements discussion and a written scope.

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