Path 1: Reduce scope, keep quality
When to use: Use when the project is promising but the current budget cannot support the full version.
- Trim scope, not standards
- Keep the core outcome intact
- Avoid silent overdelivery
Pricing decision
Use before replying
Protect your pricing logic by reshaping the project, not shrinking your value.
Draft a reply for this situationStart here on this page
2 free drafts
Paste the client's budget, your original quote, and what parts of the project matter most. Flowdockr will help you draft a reply that restructures the work without underpricing yourself. 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.
The client budget is genuinely below your quote. The real decision is whether to restructure the work, not whether to panic-cut your rate.
When to use: Use when the project is promising but the current budget cannot support the full version.
When to use: Use when you want to test how flexible the budget really is.
When to use: Use when the budget gap is too large to make the project healthy.
Thanks for sharing the budget. At that level, the best option would be to reduce scope rather than lower the rate for the current scope.
Why this works: Use this when you want to acknowledge the objection quickly and test whether budget is the real blocker.
Thanks for being transparent about the budget. I don't think the current scope would be realistic at that level, but I'd be happy to suggest a leaner version that still delivers the core outcome.
Why this works: Use this when you want to preserve trust while still holding the line on the original pricing logic.
The current quote reflects the work required for this scope. If the available budget is lower, we'd need to adjust deliverables rather than reduce the rate for the same project.
Why this works: Use this when you need to reset boundaries clearly and move the conversation toward scope trade-offs instead of discounts.
Sometimes, but only if the scope is also reduced. The dangerous move is keeping the same workload while lowering your rate.
Frame it around keeping the project realistic and well-executed. You are not refusing the opportunity, you are adjusting the shape of the work to fit the budget honestly.
That is exactly when a tiered or leaner version makes sense. Good fit alone is not enough if the economics are broken.
Move to the next decision state instead of dropping into generic related posts.
Paste the client's budget, your original quote, and what parts of the project matter most. Flowdockr will help you draft a reply that restructures the work without underpricing yourself.
Choose another pricing situation from the decision console.