Example 1
“Thanks for the proposal. The price is higher than we expected for this scope.”
Pricing decision
Use before replying
Handle price pushback after sending a proposal without discounting too early.
Draft a reply for this situationStart here on this page
2 free drafts
Paste the prospect's exact message, your quote, and the tone you want. Flowdockr will draft a reply that protects your rate without sounding defensive. Start with the exact message, add your quote or scope context, choose the tone, and generate without leaving this scenario page.
Start with the real client message
Paste the prospect's wording, add your quote or scope context, and generate a reply tuned for this pricing situation.
Review the suggested approach and choose the response that best fits your client conversation.
This usually happens after a prospect reviews your proposal and says the price feels high. In many cases, this is a negotiation signal rather than a true rejection.
These are the kinds of pushback messages this page is designed to help you answer.
Example 1
“Thanks for the proposal. The price is higher than we expected for this scope.”
Example 2
“We like the direction, but the quote feels expensive compared with what we had in mind.”
Example 3
“This is more than our budget right now. Is there any flexibility on price?”
When to use: Use when the prospect still seems interested and may simply be testing your flexibility.
When to use: Use when it is unclear whether the objection is strategic or genuinely budget-driven.
When to use: Use when the project may still be workable, but not at the current scope.
Thanks for the honest feedback. If budget is the main issue, we can look at adjusting the scope while keeping the core outcome strong.
Why this works: Use this when you want to acknowledge the objection quickly and test whether budget is the real blocker.
I understand the quote may feel high at first glance. The pricing reflects the scope and level of work involved, but if budget is the main constraint, I'd be happy to explore a leaner version that still gets you the key result.
Why this works: Use this when you want to preserve trust while still holding the line on the original pricing logic.
The quote is based on the scope and standard required for the project. If needed, we can discuss a reduced scope, but I'd prefer not to compromise the quality by lowering the rate without changing the work involved.
Why this works: Use this when you need to reset boundaries clearly and move the conversation toward scope trade-offs instead of discounts.
Most reply quality drops when freelancers concede or over-explain too early.
Usually not. The first step is to understand whether the objection is about budget, scope, or perceived value. Lowering your rate too early weakens your position before you understand the real issue.
Look for specifics. If the prospect can explain the budget constraint clearly, it may be real. If the message is vague and only signals discomfort with price, it is often negotiation pressure.
In most cases, reducing scope is cleaner. It protects your pricing logic and prevents you from doing the same work for less money.
Move to the next decision state instead of dropping into generic related posts.
Paste the prospect's exact message, your quote, and the tone you want. Flowdockr will draft a reply that protects your rate without sounding defensive.
Choose another pricing situation from the decision console.