Cheap generation changes what you can test.
When a motion attempt costs cents rather than a creator reshoot, you can:
- test more hook mechanics;
- keep one approved creator and try several performances;
- regenerate the specific failed clip;
- build variations around a winner;
- reserve expensive finishing for the branches that earned it.
That is the useful thesis behind low per-second pricing. Ghostfeed's first-frame approval step makes the economics better by moving an obvious quality decision before video generation.
The mistake is treating the provider price as the cost of a finished creative.
“AI video costs one cent per second” sounds precise.
It is usually the least useful number in the workflow.
It prices a successful provider response.
You need to price an accepted, deployable, decision-useful creative.
Those are not the same thing.
The denominator is doing the trick
Per-second price:
Cost per accepted asset:
Cost per useful test:
The third number is what the growth team should care about.
A cheap render can be expensive
Suppose Model A charges $0.15 for a 15-second attempt.
Across 100 attempts:
Sounds absurdly cheap.
Now add:
If review labor is valued at $60/hour:
Before editing, rights, storage, orchestration, or media:
The provider price is real.
It just is not the production price.
Calculate the whole funnel
Track cost at every stage.
| Stage | Example cost |
|---|---|
| Research and brief | $180 |
| Script/shot planning | $120 |
| Creator or likeness rights | $300 |
| Generation attempts | $42 |
| Automated evaluation | $18 |
| Human review | $240 |
| Editing/assembly | $160 |
| Publishing/operations | $40 |
| Test media | $1,200 |
| Analysis | $120 |
| Total | $2,420 |
If the batch yields 20 deployed creatives:
If only 12 receive enough comparable delivery:
The $42 generation line is not the economic story.
Separate fixed and variable costs
Fixed or step-fixed:
- research;
- offer and audience definition;
- creator setup;
- rights negotiation;
- template engineering;
- integration;
- experiment design.
Variable:
- model calls;
- retries;
- per-asset review;
- editing;
- storage/egress;
- publishing;
- media spend.
At higher volume, fixed cost per asset falls.
Variable cost does not disappear.
Include rejects
Acceptance rate:
Expected generation attempts:
For 50 accepted assets:
| Acceptance | Attempts required |
|---|---|
| 80% | 63 |
| 50% | 100 |
| 25% | 200 |
A renderer that costs four times more and accepts at 80% may beat a cheap renderer accepting at 25%.
Measure it on your shot types.
Include repair time
Common repair:
- lip sync;
- wrong product UI;
- unstable hands;
- subtitle timing;
- color mismatch;
- audio cleanup;
- incorrect packaging;
- claim or disclosure edit.
Track minutes by failure code:
This tells you whether a failure should be regenerated, composited, or avoided in the shot plan.
Include rights
A synthetic character is not always rights-free.
Cost may include:
- performer compensation;
- digital-double license;
- voice license;
- usage term;
- paid-media rights;
- geography;
- renewal;
- legal review.
These costs can be more important than generation—and should be.
The person whose likeness creates the value should not disappear from the spreadsheet.
Include review capacity
If one reviewer can make 12 sound decisions per hour:
“Generate 500” is not a production strategy unless the review system can absorb 500.
The response to cheap generation should often be a stricter candidate gate, not unlimited output.
Cheap variants can weaken the test
More variants do not automatically create more learning.
Failure modes:
- variants change too many things;
- concepts are near-duplicates;
- each gets too little delivery;
- the audience differs;
- winners are selected on early noise;
- the test budget is spread too thin;
- no primary metric exists.
Example:
If $20 cannot produce enough delivery for a useful read, the cheaper production created a worse experiment.
Test breadth must fit media capacity.
Price learning
Define:
Questions:
- Does product-first outperform creator-first for this audience?
- Does a licensed creator beat a fictional avatar?
- Does real UI proof improve qualified click-through?
- Does objection handling improve trial completion?
If a 50-variant batch changes six variables per ad, it may resolve zero questions.
Use a cost ledger
Roll it up by:
- model;
- shot family;
- creator;
- format;
- campaign;
- client;
- experiment question.
Compare vendors on accepted output
Evaluation table:
| Metric | Renderer A | Renderer B |
|---|---|---|
| Provider price/attempt | Low | Higher |
| First-pass acceptance | 32% | 76% |
| P95 latency | 18 min | 9 min |
| Repair minutes/accepted | 11 | 3 |
| Exact UI success | 8% | 12% |
| Cost/accepted talking head | $9 | $7 |
| Cost/accepted product interaction | $28 | $19 |
Neither may be right for exact UI. Compositing could win.
Routing becomes empirical:
Price incidents
At volume, include:
- duplicate generation from retry bugs;
- orphaned provider jobs;
- expired URLs;
- broken callback handling;
- publishing failures;
- wrong account or version;
- emergency takedowns;
- compliance rework.
An incident ledger turns operational sloppiness into visible cost.
Do not confuse production savings with profit
Even if creative production becomes nearly free:
- paid distribution still costs money;
- product conversion can fail;
- retention can fail;
- attribution can lie;
- the offer can be weak;
- customer support still exists.
Cheap creative expands the search space.
It does not create product-market fit.
A useful weekly report
Then ask:
- Which failure code consumed the most time?
- Which model/shot pairing had the lowest accepted cost?
- Which test resolved a decision?
- What should stop being generated?
Where Ghostfeed fits
One video. Hundreds of posts only has leverage if the variants remain attributable, reviewable, and useful.
Ghostfeed reduces the operational work around creators, source frames, generation, and variants. The honest metric is not “seconds generated.”
It is how efficiently the system turns evidence into approved creative and approved creative into learning.
Per-second pricing belongs in the ledger.
It should not be the headline.