Imagine an overseas brand commissioning product footage from a team in China. Two market leads want different edits, while the central team sees an opportunity to share the shoot. Before anyone books production, one decision remains: whose budget funds the work both markets need?
Reusing footage is a creative opportunity. Funding and approving the shared work is an operating choice. ONCE recommends agreeing the common scope and each market's additional work before treating separate requests as one production programme.
A shared balance does not allocate the work
Superside's current Assign a budget to a team guide describes allocating part of an account's recurring budget to teams, with unassigned funds in a Shared balance. Its Transfer balance between teams guide limits transfers to administrators and to the originating team's unused balance. The company's FAQ separately describes scoping a project by service, estimated work and team composition before its approved charge is deducted.
These pages were checked on October 25, 2026. The help guides show relative update labels rather than confirmed publication dates, so this is an analysis of a current service structure, not a new-feature announcement. It establishes one supplier's published arrangement, not a universal pricing model or proof of savings.
Moving funds can support a decision. It does not establish that another market can use an existing shot, that a new request is included, or that someone has accepted responsibility for the shared asset.
Separate the supplier quote from internal allocation
For a scope-based proposal, ONCE suggests three categories:
- B, the shared base: agreed development, product footage or assets that the participating teams can actually use. Assign a budget owner and a common approver.
- Lᵢ, market-specific additions: genuinely additional shooting, language review, voice work, editing or other adaptation for that market. Assign its local approver.
- G, additional shared work: coordination, version maintenance or common-use charges not already included elsewhere. State who buys and approves them.
These are agreed service charges, not the supplier's internal costs. G is not an automatic management surcharge: coordination already included in B or a local quote must not be counted again. Market-specific usage charges can sit with that market; common-use charges follow the actual agreement.
Where both parties adopt this structure, the total agreed quote is B plus all Lᵢ plus G. It is a reconciliation method, not a savings formula. Package pricing, licensing and other commercial models require their own explicit breakdown rather than forced arithmetic.
Choose an owner before the first market pays
Central funding of the shared base is one option when headquarters has a genuine common need, budget and management capacity. Another is a lead market funding the initial work with participation terms agreed before other markets join. Separate procurement remains an option.
Whichever route is chosen, agree who approves the shared scope, how the organisation allocates the quote, and whether later participation adds work or usage charges. Paying first should not silently grant one team authority to change every shared shot.
Internal allocations should reconcile to the approved project amount, not make one common charge appear as several new commissions. There is no inherently correct equal split by country: market count is not production workload, and expected use is not realised benefit. Formal accounting, intercompany charges and tax treatment belong with the brand's qualified advisers; this framework concerns production scope and approvals.
Price the change that is actually required
In this fictional launch, a shared close-up might work for both markets while one edit needs additional approved explanatory copy. That is a candidate for a local addition. Different plugs, packaging or features, however, may require new product footage. Necessary reshooting is not a failure to reuse.
If a market asks to change the shared product treatment, identify the affected shots and downstream versions. The common approver can decide whether to change the base or commission a local branch. Do not automatically bill every change to whoever noticed it: correction of a production error and a change to an approved brief require different treatment under the actual agreement.
A new market should trigger checks of suitability, usage scope and adaptation work. Existing footage does not mean zero effort; additional effort does not automatically mean another complete shoot fee. Quote the specific changes in images, language, sound and intended use.
Compare two complete production plans
Compare shared and separate procurement against the same deliverable requirements, including essential market differences, usage, revisions, coordination and maintenance. Shared production is not necessarily the better choice when coordination outweighs useful common work or requirements remain unstable.
Do not report savings merely because a shoot line disappeared. A defensible comparison needs equivalent-scope proposals or another checkable basis, followed by a review of work actually performed. Budget allocation also does not establish schedule feasibility.
For ONCE, the promising ongoing service is to maintain a usable view of what has been made, where it can be used and who approves a change—not merely to accumulate monthly video counts. Shared-work records and actual local additions could inform future estimates and reuse. That is a service-design proposal, not a claim about an existing ONCE system, client test or improved margins.
Before asking a production partner for a multi-market quote, provide the common purpose, required local differences, budget owners and approvers. Agree who is responsible for which work before negotiating the number of videos.
