Most typical phrasing
“We found someone cheaper.”
Optional analytics
FlowDockr only loads optional analytics and third-party tools after you allow them. Read the Privacy Policy.
Use this scenario when a client brings up a cheaper competitor and you need to protect your positioning without sounding threatened or defensive. Get a reply you can adapt and send.
Start with 2 free drafts. No subscription required.
Typical client message
“We found someone cheaper.”
Situation snapshot
The client is testing whether you will race to the lowest number. You need to differentiate clearly without sounding threatened.
Reply goal
Acknowledge the comparison without attacking the other option or racing to the lowest number.
Client message generator
Copy a professional reply that compares scope, process, and fit without sounding threatened by a cheaper option.
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.
Why this works
What it protects
Acknowledge the comparison without attacking the other option or racing to the lowest number.
How it sounds
I understand. If price is the only decision factor, the cheaper option may be the better fit, but if it helps, I can also show what is different in scope, process, or support so you can compare the offers on more than just the number.
Next step
Reframe around scope, reliability, and fit, or offer a smaller package if the budget truly differs.
These are the real wording patterns this scenario is built to handle.
Most typical phrasing
“We found someone cheaper.”
Other ways this shows up
“Another freelancer offered a lower price.”
Reply playbook
Use this when the search intent is "client says they found someone cheaper what to say" and the client message matches this negotiation stage. It also covers searches like "client found someone cheaper what to say".
Step 1
The client is testing whether you will race to the lowest number. You need to differentiate clearly without sounding threatened.
Step 2
Acknowledge the comparison without attacking the other option or racing to the lowest number.
Step 3
Reframe around scope, reliability, and fit, or offer a smaller package if the budget truly differs.
Concise
I understand comparing options. Pricing differences usually come down to scope, process, and reliability, so I'd rather help you compare what is actually included than try to match a lower number blindly.
Best for: Use when you need a short reply that keeps the thread moving.
Warm
Lower rates can make sense for a different scope or delivery model. If budget is the main issue, I can suggest a narrower option so you're comparing like for like.
Best for: Use when you want to preserve trust while still keeping the boundary clear.
Firm
Acknowledge the comparison without attacking the other option or racing to the lowest number. If the client wants a different path, make the tradeoff explicit before you continue.
Best for: Use when the client is repeating the pressure or treating the boundary as optional.
Acknowledge the comparison without attacking the other option or racing to the lowest number.
Use a softer tone when the client is still collaborative and the pressure looks like uncertainty rather than bad faith.
Reframe around scope, reliability, and fit, or offer a smaller package if the budget truly differs.
Client says your quote is too high
You sent a detailed proposal with scope, timeline, and price. The client replies saying the quote is higher than expected, but they have not given you a real budget yet.
Client wants the same scope for a lower price
The client is not asking to reduce scope, timeline, or revision count. They simply want the same work at a lower price.
Client asks if you can meet their budget
The client finally gives a real budget number, but it sits below your quote. You need to respond without compressing the same work into a smaller fee.
More client replies for rate objections, discount requests, and budget pushback.
Close variants of this client conversation that need a similar kind of reply.
Client says your quote is too high
You sent a detailed proposal with scope, timeline, and price. The client replies saying the quote is higher than expected, but they have not given you a real budget yet.
Client wants the same scope for a lower price
The client is not asking to reduce scope, timeline, or revision count. They simply want the same work at a lower price.
If the client keeps pushing on price, these are the next pricing conversations likely to follow.
Client asks for a lower rate after your proposal
You already sent a proposal with a defined scope, and now the client wants a cheaper version of the same plan. You need to protect the original quote without stalling the deal.
How to respond to discount requests professionally
The client wants a discount before committing. Sometimes they frame it as a long-term opportunity, but the immediate pressure is still to cut price first and define terms later.
Client asks if you can meet their budget
The client finally gives a real budget number, but it sits below your quote. You need to respond without compressing the same work into a smaller fee.