Path 1: Reframe around outcomes
When to use: Use when your process, reliability, quality, or strategic thinking is materially stronger.
- Shift the comparison away from raw price
- Anchor on outcomes and standards
- Stay calm and confident
Pricing decision
Use before replying
Stay out of commodity pricing and bring the conversation back to fit, quality, and outcomes.
Draft a reply for this situationStart here on this page
2 free drafts
Paste the competitor comparison message and your offer details. Flowdockr will help you reply without slipping into a defensive price war. 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 prospect introduces a cheaper competitor into the conversation. Your job is not to win a price war, but to clarify differences and reposition the decision.
When to use: Use when your process, reliability, quality, or strategic thinking is materially stronger.
When to use: Use when you suspect the cheaper quote is not directly comparable.
When to use: Use when the buyer appears to optimize almost entirely for lowest cost.
That makes sense. Pricing can vary a lot depending on scope, process, and level of support, so it may be worth checking whether the deliverables are directly comparable.
Why this works: Use this when you want to acknowledge the objection quickly and test whether budget is the real blocker.
I understand, and it's completely reasonable to compare options. In many cases the difference comes down to scope, level of involvement, and how the work is handled, so I'd be happy to clarify what's included on my side if that helps you evaluate fairly.
Why this works: Use this when you want to preserve trust while still holding the line on the original pricing logic.
A lower quote doesn't always reflect the same scope or standard. If price is the only decision factor, I may not be the right fit, but if you want the outcome this proposal is designed for, I'm happy to walk through the differences clearly.
Why this works: Use this when you need to reset boundaries clearly and move the conversation toward scope trade-offs instead of discounts.
Do not race to match the price. First clarify whether the offers are actually comparable in scope, process, and quality.
Usually not by default. Matching a lower price without clarifying what is different can turn you into a commodity and damage your positioning.
Bring the discussion back to deliverables, standards, support, and results. A useful comparison is rarely about raw price alone.
Move to the next decision state instead of dropping into generic related posts.
Paste the competitor comparison message and your offer details. Flowdockr will help you reply without slipping into a defensive price war.
Choose another pricing situation from the decision console.