AI dubbing cost per approved minute equals total in-scope production cost divided by language-minutes approved for release. The total should include generation, review, revisions, rejected output, and version updates when they fall within the measurement period.
Ollang, the AI language execution layer, brings dubbing and review into an orchestrated workflow. If you are evaluating production approaches, book an Ollang demo to examine that workflow against your cost model.
A low generated-minute rate can still result in an expensive approved minute. The difference depends on how much work each usable minute requires.
Why Generated-Minute Pricing Misses Production Costs
Generated-minute pricing measures production activity, not finished output. It may leave out preparation, review, corrections, and versions that never receive approval.
Consider two providers that each generate the same amount of dubbed content. If one delivers a greater share of approved output, their generation rates alone cannot explain the difference in usable minutes.
Scope also changes the meaning of a “minute.” A translated subtitle, an approved overdub, and a lip-synced video are different deliverables. Audio description and localized on-screen text add work when required.
Define the deliverable before comparing rates. Specify the content type, target language, dubbing style, review standard, and final files. Then calculate cost against minutes that meet that same definition.
For multilingual programs, count each approved language version separately. A video approved in several languages produces an approved language-minute total for each version. Counting only the source video’s duration understates the output delivered.
Generated minutes remain useful because they show production volume. Approved minutes show what an organization can publish, use for training, or distribute. Both belong in a buying discussion, but approved minutes provide the denominator for finished-output cost.
Count Reviews, Revisions, Rejected Output, and Version Updates
An approved-minute model starts by defining where work enters and leaves the process. Track direct costs for each order, then allocate shared costs consistently.
Include these categories when they apply to your scope:
- Source preparation: Script cleanup, terminology decisions, and source-audio fixes.
- Automated production: Transcription, translation, voice synthesis, and audio processing.
- Review: Linguistic, brand, accessibility, and stakeholder checks required for approval.
- Revisions: Corrected translations, regenerated audio, remixing, and repeat reviews.
- Rejected output: Production work that does not result in approved minutes during the measurement period.
- Version updates: Changes after source scripts, product screens, or policies change.
- Workflow overhead: Coordination, integration upkeep, and other allocated operating costs.
Rejected output is not an extra fee by definition. Its production cost already sits in the numerator. Its effect on unit cost appears because rejected minutes do not enter the approved-minute denominator.
Treat revisions similarly. Count the work they require, but count a finished minute only once per approved version. Otherwise, repeated attempts can make output appear larger than it is.
Set a clear period for version updates. For example, measure initial production separately from ongoing maintenance. An updated video can then have its own approved-minute calculation without obscuring launch costs.
Approval criteria affect yield. A customer-facing campaign may require different checks from internal training. Document those checks before starting a pilot rather than changing them after seeing the results.
Finally, separate platform spending from team time without ignoring either. Finance teams may track them in different accounts, but the unit calculation needs both when both are necessary for release.
Build a Comparable Approved-Minute Calculation
Use the same accounting boundary for every approach under review. This checklist creates a repeatable baseline:
- Define one approved minute. Identify its language, version, dubbing style, and required deliverables.
- Set the approval standard. Record who reviews accuracy, tone, timing, and cultural fit.
- Choose a measurement period. Separate initial releases from ongoing maintenance.
- Record all in-scope costs. Include automated steps, human work, revisions, and allocated overhead.
- Count final approved minutes. Exclude unfinished and rejected versions.
- Calculate the unit cost. Divide total in-scope cost by approved language-minutes.
- Report yield alongside cost. Compare approved minutes with generated minutes for context.
Cost per approved minute = Total in-scope production cost Ă· Approved language-minutes
For an illustrative calculation, suppose a pilot generates 100 language-minutes and approves 75. If its combined generation, translation, review, revision, coordination, and allocated integration costs total $1,900, the cost is $25.33 per approved minute. Approval yield is 75%. These hypothetical figures are not Ollang prices or expected results.
Use a comparison table to inspect where each approach places costs. The questions are prompts for a pilot, not claims about guaranteed outcomes.
| Approach | Cost boundary to inspect | Approval and revision question |
|---|---|---|
| Ollang’s execution layer | AI Dubbing, review, QC, and workflow costs | How do review criteria and revisions affect approved output? |
| Traditional language service providers | Quoted production, changes, and internal coordination | Which approval rounds and updates fit the quoted scope? |
| Translation management systems | System costs plus connected media production and review | Where are dubbing production and approval tracked? |
| Single-model AI tools | Generation plus preparation and review | Who resolves issues and approves the finished dub? |
| Point-solution dubbing tools | Dubbing plus upstream and downstream work | How are subtitles, on-screen text, and updates handled? |
| Internal manual workflows | Staff time, tools, production, and review | How much coordination does each release require? |
Keep quality and scope beside the unit figure. A lower cost is not comparable if it omits required review or delivers a different asset. Record cycle time and reasons for rejection as supporting measures, not substitutes for approved-minute cost.