Disagreement is a comparison moment, against the brief, not your worth.
8 min readFeedback types compared
| Feedback type | What it means | Best next step |
|---|---|---|
| Preference change | They want a different direction | Change order if outside agreed look |
| Missed requirement | Something in scope was incomplete | Fix inside agreed revisions |
| New requirement | Extra feature after acceptance | Quote before more work |
| Vague dislike | No concrete criteria | Ask for examples tied to the brief |
Why disagreements happen
Most fights are not about quality. They are about different memories of what "done" means.
Filipino VAs often work async. The client imagined one thing. You built another. Without a saved brief, both sides feel right.
Your job is to turn emotion into facts on the same thread as the original agreement.
FRAME Protocol for disagreements
Salag's FRAME Protocol helps you respond calmly:
- Facts: Quote what they said and what you delivered.
- Reference: Link the onboarding email, SOW, or approval note.
- Assess: Name hours, deadline impact, and whether it is in scope.
- Message: Offer options in writing.
- Execute: Revise only after they pick a path.
What to say (scripts)
First disagreement
Thanks for the honest feedback. Our brief on [date] listed [X]. Your note asks for [Y]. I can revise [specific items] within the original scope by [date], or we can treat [Y] as a change order at [rate]. Which do you prefer?
"This is not what I wanted"
I hear you. Can you point to the part of the brief that [new ask] was based on? I want to match your vision. If direction changed, I am happy to quote the extra work separately.
Repeated revision loops
To keep quality high, our agreement includes [N] revision rounds. We are on round [N+1]. I can continue at [rate] per round or pause until we lock an updated brief.
Common mistakes
- Apologizing for everything even when you followed the brief.
- Revising for free without noting it is out of scope.
- Going silent out of fear. Silence reads as guilt.
- Arguing in voice notes with no written summary after.
Final thoughts
A disagreeing client can still be a good client. Handle it with documents and options. You protect your time and often earn more respect, not less.
How Salag helps
- Freelance Readiness Checker. Make sure your briefs and revision terms are set before disputes start.
- Late Fee Calculator. Model cost when disagreements delay approvals and push timelines.
- Scam Pattern Detector. Spot clients who use endless not-quite-right feedback to avoid paying.
Move safer. Not faster.
In short
When client disagrees freelance work, compare their feedback to the written brief, not to your ego. Ask what changed. Point to what was agreed. Offer a clear path: revise within scope, bill extra for new direction, or reset expectations in writing.
Common questions
When client disagrees freelance work, compare their feedback to the written brief, not to your ego. Ask what changed. Point to what was agreed. Offer a clear path: revise within scope, bill extra for new direction, or reset expectations in writing.
Write down what you agreed on and what changed. Do not start new work on vague terms.
Use plain English, confirm in writing, and set clear hours. Clients hire you for reliability, not cheap labor.
Put the basics in your agreement or a recap email before billable work starts. Bigger projects need fuller terms.
Stay warm but firm. Offer options inside a clear process, like a change order or a short written recap.
FRAME means: capture facts, compare to your agreement, name tradeoffs, confirm in writing, and save the decision for next time.
Escalate when the same problem repeats: unpaid extras, late approvals plus new asks, or refusal to confirm in writing.
Yes. A clear email with tasks, dates, price, and limits beats a verbal yes every time.
Salag gives you tools and templates so you can set boundaries before small problems grow.
Use written recaps, scope trackers, and Salag tools like agreement builders and scope detectors.
Most recaps take five minutes after a call. That small step saves hours of arguing later.
Yes. Retainers need weekly change logs. Projects need milestone gates. Always compare new asks to written terms.
Pause billable work on unclear items. Send a narrow summary of what you will do. Save their reply either way.