Your factory in China is still finalising a new appliance. One studio will animate the internal mechanism and another will render the close-ups. Both quotes look fine until engineering changes the hinge: the question is no longer how many shots each vendor has, but how many shots inherit the same change.
Separate creative control from execution capacity
In its 3 November 2026 announcement, WildBrain described a long-term CG production partnership with EightyEight Pictures. WildBrain and House of Cool retain creative leadership and core production functions in Canada; EightyEight Pictures adds execution capacity within a shared pipeline. Checked on 5 November, the announcement establishes the companies' stated arrangement. It does not provide a basis for estimating savings on a product campaign.
Build an ONCE shot dependency sheet
Ask the producer to group shots that would change together. Give each group an approved asset version, an owner who can issue revisions, and a list of conditions the next shot must preserve. A package boundary is useful only if the inputs and the result can be checked at that boundary.
| Signal | Commissioning decision |
|---|---|
| Several shots depend on an unsettled model or animation | Keep them together or assign a single owner to maintain the shared input and review affected shots. |
| A deliverable uses stable inputs and has a clear acceptance check | Quote it separately if the work can proceed without ongoing upstream decisions. |
| An approved change affects only some shots | Ask for a targeted review and rerender list before approving a whole-package revision. |
Consider a hypothetical appliance lid. An exploded view, a closing action and the matching final close-up must agree on the hinge geometry and where the lid comes to rest. If the mechanism changes, review those shots together even if they were assigned to different artists. A background plate that never interacts with the appliance may be an independent purchase. A material change can still affect reflected surfaces, so check the actual dependency before marking a shot unaffected.
Buy a small revision trial before buying volume
Choose two adjacent shots that share an asset and have the teams process a controlled change. Ask who sends the update, which clips are affected, and who checks continuity in playback. A finished still cannot answer those questions. Record missed changes, unnecessary rerenders and decisions that still require the brand or factory to intervene.
When comparing bids, separate shot execution, shared asset maintenance, joint review and revision work. Independent packages are easier to justify once the model is stable and acceptance criteria are clear; during engineering changes, ownership of the shared asset may matter more than a lower rate per shot. Bring the proposed split and a likely factory revision to ONCE's production team. A managed production library can keep the dependency record for the next campaign, so the brand can scope a change before paying to remake it. The example and trial are proposed methods, not client results.
