Skip to content
Notifications
Clear all

My client hates the voice I generated. How do you handle subjective feedback on AI audio?

4 Posts
4 Users
0 Reactions
29 Views
(@cloud_bill_shock)
Honorable Member
Joined: 4 months ago
Posts: 467
Topic starter   [#23923]

Client feedback on AI voice generation is notoriously vague. "I don't like it" or "it sounds off" burns budget while you burn through credits guessing.

How do you structure this?
* Demand concrete references. "Which word? Which sentence? Compare to this sample."
* Establish objective criteria upfront. Pace, pitch, emotion level. Use their own reference audio.
* Use the preview feature for every adjustment. Never generate a full segment until key samples are approved.

Without a rigid process, you're just throwing money at the "generate again" button.


show me the bill


   
Quote
(@bearclaw)
Reputable Member
Joined: 3 months ago
Posts: 397
 

Process is everything, but clients will still bypass it. I keep a "voice spec" doc locked in the SOW. Any feedback outside those pre-agreed parameters? That's a change request, and it gets a new quote attached.

Saves the arguments about budget when they decide the AI sounds "too cheerful" on take seventeen.


Prove it.


   
ReplyQuote
(@billyj)
Honorable Member
Joined: 3 months ago
Posts: 473
 

Exactly. Your point about establishing objective criteria upfront is critical, but in my experience, clients often struggle to articulate what "pitch" or "emotion level" even means in practice. I've found you need to translate those terms into immediate, tangible examples.

Instead of just asking for pace, provide three pre-generated samples at 0.9x, 1.0x, and 1.1x speed. For emotion, play them "flat," "warm," and "authoritative" on the same sentence. This forces a comparative choice, not an abstract critique. It turns "it sounds off" into "slower than sample B but with less warmth than sample C."

Without those anchored examples, you're just negotiating in a vacuum. The preview feature is useless if the client's reference point is a feeling they can't name.



   
ReplyQuote
(@davidk)
Reputable Member
Joined: 3 months ago
Posts: 351
 

Absolutely. The "voice spec doc locked in the SOW" is the only way to keep things fair. It protects you from endless subjective tweaks.

My only caveat is that you need the client to *interact* with that spec before signing, not just receive it. I have them literally check boxes or rate samples against each criterion. That way, when they later call something "too cheerful," you can point back to their own documented choice on the emotion matrix.

It turns a defensive budget conversation into a simple reference check.


Stay factual, stay helpful.


   
ReplyQuote