CREDITS & PRICING • Variant ledger added · Jul 24, 2026
AI Video Creative Variant Budget: Plan Credits for Campaign Versions
The biggest AI video budget surprise often arrives after the first approved creative. One concept becomes multiple offers, calls to action, aspect ratios, countries, and review requests. Those changes do not always require a whole new film, but they do create additional shot and approval work. This guide helps you scope variants before they become unpriced requests.
Name the variants before estimating them
Build a simple matrix with the message, market, language, format, and audience segments you have promised. Then label each resulting version as a copy edit, an edit-only adaptation, a regenerated shot, or a new concept. A different headline may only need a title card, while a different market can require product, casting, legal, and visual changes that force new generation work. The matrix reveals whether a campaign has five deliverables or fifty combinations before production starts.
Budget by marginal change, not by total video count
A variant should be priced according to the work it adds to the approved master. For each derivative, count only the shots that must be regenerated, the additional review cycles, and any new voice, caption, or edit work outside the generation tool. This avoids two errors: assuming every derivative is free because it shares a concept, or charging every derivative as a full rebuild. The correct unit is the marginal approved output required to create that version.
Build a variant budget ledger before converting it to credits
Use a ledger with one row for every promised version. Give the approved master the ID M0 and each derivative an ID such as V01, V02, and V03. Record Gv for the number of shots that need a new generation, Av for the planned attempts per changed shot, Rv for that variant's review reserve, and Ev for edit-only tasks. The generation-unit plan for a variant is (Gv × Av) + Rv; campaign generation units are the master estimate plus the sum of that expression across all variants. Keep Ev outside the generation-unit formula so a caption replacement or recut does not masquerade as free generation work. Only after the ledger is approved should you convert generation units to tool credits, using the current rate for the exact model, duration, resolution, and mode named in the provider's official documentation. If a variant requires different settings, update that row instead of changing the campaign-wide assumption. The ledger gives the team an auditable answer to three questions: which request added generation capacity, which changed only editing work, and which assumption still needs approval.
Use a first-pass and revision allowance for every variant family
Variants are rarely approved on the first render because a small message change can alter pacing, subject placement, or the visible product. Set a first-pass attempt rate for each regenerated shot, then reserve an additional allowance for the family-level review loop. The reserve should grow when many stakeholders must approve localized or regulated assets. Track actual use by variant family so the next campaign reveals which requests are genuinely low-cost and which consistently trigger rework.
Choose the approval sequence that limits rework
Approve the master narrative and visual system before generating every derivative. Next, approve a representative high-risk variant such as the narrowest aspect ratio or the strictest localized market. Only then expand the remaining matrix. This sequence catches structural problems before they are repeated across every version. It also creates a clear decision record: when a later stakeholder asks for a new version, you can show whether it is inside the planned matrix or a new scope item that needs time and credits.
Use a variant approval packet to prevent scope from disappearing into comments
Create one approval packet for each variant family before batch generation begins. The packet should identify the parent master, the intended audience or market, the output format, the elements that remain locked, the exact requested change, and the work classification: edit-only adaptation, regenerated shot, or new concept. It should also name the approval owner, the included review round, the decision deadline, and the scope status: planned, pending, or out of scope. Link the packet to the ledger row rather than relying on a message thread. When a stakeholder asks for a new combination, compare it with the locked packet first. If it matches a planned row, proceed with that row's reserve; if it changes the master, format, market, or creative direction beyond the packet, record it as a new scope decision before consuming generation capacity. This gives stakeholders a fast way to approve legitimate variants while preserving a visible boundary around unpriced additions.
Editorial note: This framework is general information, not a vendor endorsement. Check the current pricing, terms, and data-handling details directly with the provider before buying.