You send the final files, feeling good about the work, and the reply comes back cold: "This isn't what I expected" or "I don't think this works for us." No specifics, no examples, just flat rejection of something you spent real hours on. The instinct is either to get defensive or to start reworking blindly, guessing at what might have gone wrong. Neither helps.
Here is how to respond to this specific moment, get the feedback you actually need to fix it, and figure out whether this is a real quality miss or a scope-and-expectations problem wearing a quality complaint's clothes.
Do not react to the tone, respond to the content
A blunt or disappointed message from a client is unpleasant to receive, but reacting to how it was said instead of what it actually says wastes the one useful thing available right now, information. Reply calmly and specifically: "Thanks for the honest feedback, I want to get this right. Could you tell me more specifically what isn't landing, is it the direction, the execution, or something particular in the details?" This does two things at once, it keeps the conversation professional regardless of how the client's message read, and it forces the vague complaint to become something concrete you can actually act on.
Resist replying immediately if you feel defensive. A message sent in the first five minutes after "I hate this" rarely reads as calm even when you intend it to. Wait an hour if you need to, then send the specific, professional version above.
Get the complaint down to something you can point to
"I don't like it" is not actionable. "The color palette feels too corporate for our brand" or "the copy doesn't sound like how we actually talk to customers" is. If the client's first response stays vague after your follow-up, ask directly for one or two specific examples: "Could you point to a specific section or element that isn't landing, so I know exactly what to adjust?" Most clients can get specific once asked directly, even if their first message wasn't.
A client who genuinely cannot name anything specific after being asked twice is a different situation entirely, worth reading as a signal about fit or expectations rather than a real quality problem with the work itself. See the guide on freelance client red flags to spot before you sign for what a pattern of vague, hard-to-satisfy feedback across multiple projects usually means about a specific client relationship.
Check the complaint against what was actually agreed
Once you have something specific, compare it against the brief, brand guidelines, or reference examples the client originally approved, not against what you personally think would be better. If the work matches what was agreed and the client simply wants something different now, this is not a quality failure on your part, it is new scope, and should be treated as a separate conversation about additional work and additional pay, not absorbed silently as a mistake you need to fix for free.
If the work genuinely does not match the brief, an off-brand color choice, a tone that ignored the reference examples provided, that is a real miss worth owning directly: "You're right, looking back at this against the brief, I missed the mark on [specific thing]. Let me revise this." Owning a real miss plainly, without over-apologizing, is what actually rebuilds confidence fastest.
Revise with a specific plan, not a guess
Once you know exactly what is wrong, tell the client what you are going to change before you start the revision, not after: "Based on your feedback, I'm going to [specific change]. Does that direction sound right before I dive in?" This one extra check prevents a second round of "still not it," since it catches a misread of the feedback before hours go into the wrong fix rather than after.
If your contract has a defined revision limit, this exchange still counts toward it in most cases, but a genuine miss against the agreed brief is usually worth an exception even if you are technically over the limit, since insisting on a paid extra revision for your own error damages the relationship more than the lost time costs you. See the guide on negotiating a freelance contract for how revision limits should actually be structured to prevent this ambiguity in the first place.
Rinto keeps notes and file attachments linked to each client, so when a disagreement about the delivered work comes up, pulling up the original brief or reference files takes a quick look rather than digging through old email threads to remember the specifics. See the roundup of best tools for freelancers in India for what else helps keep client history organised enough to actually settle a disagreement quickly.
Frequently Asked Questions
What should I say when a client says they hate my work?
Reply calmly and ask for specifics rather than reacting to the tone of the message: "Thanks for the honest feedback, could you tell me more specifically what isn't landing?" A vague complaint like "I don't like it" cannot be acted on, but most clients will get concrete once asked directly, and a specific complaint is something you can actually fix rather than guess at. Waiting an hour before replying, if you feel defensive, is fine, since a rushed response rarely reads as calm even when you intend it to.
How do I know if a client's complaint is a real quality issue or just scope creep?
Compare the specific complaint against the original brief, brand guidelines, or reference examples the client already approved. If the delivered work genuinely does not match what was agreed, that is a real miss worth fixing without extra charge. If the work matches the brief and the client simply wants something different now, that is new scope, a separate paid conversation, not a mistake you need to absorb for free. This check only works if you have the original brief on hand to compare against, so keep it saved somewhere you can actually find later.
Should I revise the work for free if a client says they hate it?
Only if the work genuinely fails to match what was originally agreed. A real miss against the brief is worth fixing without additional charge, since it protects the relationship and your reputation. But if the complaint amounts to the client wanting something beyond the original scope, treat it as new work with its own conversation about time and payment, rather than silently absorbing it as if it were your error. Absorbing scope creep as if it were a quality mistake trains a client to expect the same free expansion on every future project.
What if a client cannot give specific feedback about what is wrong?
Ask directly for one or two specific examples, most clients can get concrete once pushed even if their first message was vague. If a client still cannot point to anything specific after being asked twice, treat that itself as useful information about the relationship rather than a genuine quality problem with the work, since work that is actually flawed is usually easy for a client to point to once asked. A pattern of vague, hard-to-satisfy feedback across more than one project is worth watching closely rather than dismissing as a one-off.
Should I confirm my revision plan with the client before starting the fix?
Yes, briefly. State what you are about to change based on their feedback and ask if that direction sounds right before doing the actual work. This single check prevents a second round of disappointment caused by misreading vague feedback, since it catches a wrong interpretation before hours go into a fix that still misses what the client actually meant, which is far more costly than the few minutes the confirmation message takes.