Path 1: Clarify the real constraint
When to use: Use when the question is too vague to classify immediately.
- Ask what is driving the request
- Do not assume budget immediately
- Slow the decision down usefully
Pricing decision
Use before replying
A common question - but not always the same decision problem underneath.
Draft a reply for this situationStart here on this page
2 free drafts
Paste the exact message and Flowdockr will help you figure out whether this is price pushback, budget mismatch, or discount pressure - then draft the right reply. 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 is a broad, everyday pricing question. The real job of this page is to help the user identify whether the issue is generic pushback, real budget mismatch, or direct discount pressure.
When to use: Use when the question is too vague to classify immediately.
When to use: Use when the request seems budget-related but not necessarily a hard no.
When to use: Use when the work is already tightly priced and lowering further would damage quality or margin.
Possibly, depending on what part of the scope matters most. If budget is tight, the cleanest option is usually to reduce scope rather than lower the rate for the same work.
Why this works: Use this when you want to acknowledge the objection quickly and test whether budget is the real blocker.
That may be possible, depending on what outcome matters most to you. Rather than simply lowering the price, I'd usually suggest adjusting scope so the project still works properly.
Why this works: Use this when you want to preserve trust while still holding the line on the original pricing logic.
I wouldn't reduce the rate for the same scope, but I'd be happy to discuss a lighter version if budget is the main concern.
Why this works: Use this when you need to reset boundaries clearly and move the conversation toward scope trade-offs instead of discounts.
It can mean very different things: a general price objection, a real budget problem, or a direct push for a discount. That is why this question needs clarification before you react.
Not by default. A quick discount often solves the wrong problem and weakens your position before you know what the real issue is.
Ask what the current budget range is or what outcome matters most. Real budget issues tend to become more concrete once you ask one focused question.
Move to the next decision state instead of dropping into generic related posts.
Paste the exact message and Flowdockr will help you figure out whether this is price pushback, budget mismatch, or discount pressure - then draft the right reply.
Choose another pricing situation from the decision console.