When Clients Ask for AI Video at Half the Old Rate, Sell the Script Review First
If a client anchors the retainer to a per-video price that only template assembly can hit, what should the agency commit to before signing? Write the script direction, hook selection, and editorial review into the statement of work as named, billed line items before you accept a per-video price that only assembly tools can meet.
By InnovaAI ResearchPublished
“If a client anchors the retainer to a per-video price that only template assembly can hit, what should the agency commit to before signing?”
Write the script direction, hook selection, and editorial review into the statement of work as named, billed line items before you accept a per-video price that only assembly tools can meet.
Quoting a per-video rate that reflects render time and platform seats, then discovering the client is paying for judgment they never agreed to buy, so every revision round is unbilled and the account turns unprofitable by month two.
Template and avatar platforms have pushed the marginal cost of a finished cut toward zero, so the defensible margin sits in the judgment layer: which hook, which claim, which cut gets killed. The same pattern shows up across the wider AI stack, where implementation and review work is where agency margin lives rather than in the tool license itself, and where client-facing capability claims now need documented evidence rather than vendor summaries. Assembly-only pitches read as templated within one delivery cycle, which is the fastest route to losing the retainer.
- •A prospect arrives with a competitor quote that undercuts your current per-video rate by 40% or more
- •The client's stated deliverable is volume (for example 20 short-form cuts a month) rather than a campaign outcome
- •Your team plans to route the work through avatar or template assembly tools such as AI Studios, BIGVU, or Viddyoze with no named reviewer
- •The client has already seen one AI-generated sample and called it 'fine' without commenting on the message
- •The scope document lists render counts but no line item for script direction, hook testing, or editorial sign-off