Example 1
“Can you do any better on the price?”
Optional analytics and third-party tools
Flowdockr only loads optional analytics, attribution, and third-party support scripts after you allow them. You can read more in our Privacy Policy.
Pricing pressure scenario
A direct discount ask does not need a reflex discount reply.
Paste your client messageStart here on this page
2 free drafts
Paste the exact discount ask and the current offer. Flowdockr will help you reply without slipping into an automatic concession. Start with the exact message and generate without leaving this scenario page.
Review the suggested approach and choose the response that best fits your client conversation.
Your polished reply will appear here
Generate a result to see the send-ready message, the reasoning behind it, and follow-up guidance if the client keeps pushing.
These are the kinds of pushback messages this page is designed to help you answer.
Example 1
“Can you do any better on the price?”
Example 2
“Is there any room for a discount here?”
Example 3
“We like this, but we would need a lower number to move forward.”
When to use: Use when the ask is direct but the reason behind it is still unclear.
Risk: If you sound too stiff too early, the client may read the reply as inflexible posturing.
Example wording: Possibly, depending on what is driving the request. Before I change pricing, I would want to understand whether the issue is budget, scope, or something else in the offer.
When to use: Use when there is likely a real budget issue and the project still looks viable.
Risk: If scope changes are not explicit, you end up conceding twice.
Example wording: If budget is the main constraint, the cleaner route is usually to adjust scope rather than lower the rate for the same work.
When to use: Use when you are open to movement only with a meaningful commitment in return.
Risk: If the trade is weak or vague, the discount becomes a free concession.
Example wording: If there is a reason to revise the offer, I would want to tie that to a concrete trade such as faster approval, simpler scope, or cleaner payment terms.
Possibly, depending on what is driving the request. Before I lower pricing, I would want to understand whether the issue is budget, scope, or something else in the structure.
I understand why you are asking. Rather than cut the same scope immediately, I would first want to clarify whether the real issue is budget, priorities, or the structure of the offer so I can suggest the cleanest path.
I would not reduce the price for the same scope by default. If budget is the concern, the better move is usually to adjust scope or terms rather than compress the work into a lower fee.
Most reply quality drops when freelancers concede or over-explain too early.
Acknowledge the request, understand the reason behind it, and then decide whether to hold, trade, or restructure the offer.
Usually no. You give away leverage before you know whether the request is strategic, budget-based, or just reflex negotiation.
You can ask what is driving the request and offer a scope or terms-based alternative instead of a blind price cut.
Move to the next likely decision path instead of restarting from scratch.
Handle a direct client discount ask without defaulting to a concession or generic negotiation advice.
Trigger stage
mid negotiation
Pressure type
discount pressure
Real risks
lose leverage, damage positioning, low margin trap
Decision goals
hold price, test budget, reduce scope
In scope
Out of scope
Paste the exact discount ask and the current offer. Flowdockr will help you reply without slipping into an automatic concession.
Choose another pricing situation from the decision console.