Should you push back on a client using that exact wording? Usually not -- not because the underlying business position is wrong, but because the word itself is not always the safest client-facing choice.
Saying "we will push back on your discount request" directly to a client can sound adversarial, even though the identical wording is completely natural in an internal strategy note. A client-safe message should state the boundary and offer a concrete alternative instead.
The same position, two audiences
The word is not always the safest client-facing wording, even when it's the correct internal description of the move. The same underlying business position can be communicated two ways depending on who is reading it.
"Internal (fine): 'We should push back on the 20% discount request by tying our position to implementation scope and support costs, while giving the client a smaller phased option to review.'"
That sentence is exactly right for a strategy note among colleagues. It names the move plainly.
"Client-facing (safer, avoids the phrase): 'We cannot support a 20% discount, but we can review a phased rollout that keeps the first-year scope lower.'"
Same position, same offer of an alternative -- but nothing in the client version uses the word "push back" or frames the client's request as something being resisted.
The common mistake: sending the internal version outward
The mistake is sending the internal-register sentence straight to the client, or swinging to the opposite extreme with a blunt "we refuse your discount request." Both risk damaging a relationship that a pricing negotiation needs to keep open.
Want to learn "Push Back" in depth?
Lyra Practice teaches advanced non-native professionals the nuance of high-value expressions like this one, then has you practice using them in realistic work scenarios.
Start learning for free →The internal version names the move; the client version names the outcome and the alternative. When you are drafting a client-facing message, it is worth asking whether "push back" (or any synonym that frames the client as an obstacle) has crept into a sentence that a client will actually read -- and, if so, rewriting it around the boundary and the alternative instead.
Why the audience, not the honesty, is what changes
Nothing about this rule asks you to be less honest with a client -- both versions of the discount sentence say the same thing: no to 20%, yes to a phased option. What changes is which half of the sentence is foregrounded. The internal version foregrounds the team's strategic reasoning, because colleagues need to understand the reasoning to execute it. The client version foregrounds the boundary and the alternative, because that's what the client actually needs to make their own decision.
This distinction generalizes beyond pricing. Any internal planning language that describes the process of resisting a request -- "push back," "hold the line," "resist," "fight for" -- tends to read as adversarial once it lands in front of the person the process was about. The safer external habit is to describe the outcome of that process instead: what you can do, what you can't, and what's on the table as a result.
A quick check before sending: read the client-facing draft and ask whether it describes your internal stance toward the client, or the actual offer available to them. If it's the former, it likely needs a rewrite.
Practice scenarios
Practice using push back in situations like:
- translating an internal pricing pushback into client-safe wording before sending it
- catching 'push back' language that has crept into a draft client email
- offering a concrete alternative alongside a boundary in a negotiation
Useful practice phrases:
- "We cannot support..., but we can review..."
- "We should push back on... by tying our position to..."
- "internally: push back / externally: state the boundary and offer an alternative"