Your production partner in China has delivered the first color range. A seasonal launch adds one more finish, using the same footage. The question is not simply what another video costs. It is which preparation remains available—and what the new order actually needs to buy.
ONCE recommends separating finished colorway clips from the ability to continue the work. A supplier may retain that ability internally, offer access through a service agreement, or provide an agreed handover package. Those are different purchases.
A useful service signal, with limited claims
Checked on October 26, 2026, Fix The Video’s Color Variants From One Shoot page says its retainer plans retain isolation and tracking work for later color additions. Its described inputs include an existing clip and target-color references.
The commercially interesting feature is the treatment of preparation as something that can support another order. This is the provider’s own description—not proof of universal savings, production quality or an industry-wide shift. ONCE has not tested the service and does not adopt its pricing or turnaround claims.
Adobe’s Projects documentation, updated March 27, 2026, provides a useful technical distinction: an After Effects project stores compositions and references to source files. Collect Files gathers a project copy and copies of used assets into a folder. That function is not a guarantee that a particular supplier’s package is complete, licensed for another party or compatible with a different workstation.
For procurement, “we kept the project” is therefore the beginning of a discussion, not the acceptance criterion.
Write the continuation order before buying the retention
ONCE proposes a colorway continuation brief. This is a purchasing method, not a report of measured client results.
First, identify the material that can be continued: the source clip, edit version and shot ranges. Ask what happens if framing, timing or the product changes. A reusable preparation commitment needs a defined object.
Second, specify what is retained. Is it an editable project, isolated elements and tracking data, or merely the previous rendered clips? Do not assume every intermediate file exists in every workflow. Request a description of the actual setup rather than prescribing a fictional production process.
Third, define the calling conditions: who can commission the next version, what new references are required, and what must be reassessed. A new finish may require fresh judgment rather than a routine color substitution.
Finally, state the retention term and the exit route. What survives a pause in the relationship? What does reactivation cost? Which project-specific materials can be transferred, with which dependencies and permitted uses?
One practical acceptance option is a limited continuation check: reopen the agreed version and produce a short new-color sample against an approved reference. This is a proposed check, not a test conducted for this article. Passing one sample does not establish that all future colors will work without additional preparation.
Compare future commitments on the same basis
Consider a hypothetical lighting brand adding shell colors while keeping its existing rotating product shots. Retaining preparation may be worth pricing. If the next launch changes the body geometry, camera movement or material, that assumption needs to be revisited. This is an illustration, not an ONCE client case.
Compare two quotations over the same planning period:
- Retained-work route: initial preparation and outputs, retention or maintenance, subsequent adaptation and review, new exports, and any exit handover.
- Order-by-order route: initial outputs, followed by the preparation, adaptation, review and exports required for each later order.
Use the same shots, targets and deliverables for both. Do not assume ad hoc work always restarts from zero, or that retained work always carries forward unchanged. Ask the supplier to separate reusable work, new work and work contingent on a sample review. No standard saving or industry-average cost is assumed here.
Past spending is not a reason to renew by itself. Retention makes more sense when there is credible future demand and the retained setup remains usable. With uncertain launches or a major product redesign ahead, a one-off purchase can be sensible.
Retention is not ownership or portability
Internal storage, a contractual ability to order further work, and a usable transfer to another team should be described separately. A vague promise to include “source files” does not settle the scope. Project-specific outputs, general supplier methods and third-party dependencies require explicit treatment in the agreement; this article makes no legal ownership determination.
For ONCE, this suggests a productized offer built around first production, defined continuation support and an optional exit handover. Its value should come from maintaining useful preparation, not withholding files to manufacture dependence. That is a service-design inference, not a margin forecast.
Before asking for the price of another colorway, identify the source version and the retained work. Then the quotation can explain what is genuinely new—and which earlier investment is still doing a job.
