The price objection is often not a price objection. "It's too expensive" frequently means "I'm not sure the value justifies the cost," which is a different problem. Responding to a value uncertainty with a price cut treats the wrong problem.
The diagnostic before the response:
Ask: "Help me understand — is the concern the total amount, the budget timing, or the value relative to cost?" The answer determines the response:
Budget timing: payment terms, phased implementation, annual vs. monthly structure — these are pricing structure solutions that don't require a price cut.
Value uncertainty: return to the ROI conversation. What would they need to see to feel confident the value is there? This is a customer success conversation, not a pricing conversation.
Competitive comparison: they've seen a cheaper alternative. Now you need to make the differentiation case explicitly. This requires knowing your competitor's weaknesses well.
The price hold responses that work:
Anchor to the ROI you've documented. "Based on the 5 hours per week your team spends on this manually at $60/hour fully loaded, you're spending $78K annually on the problem we solve. Our $48K annual fee returns your investment in 8 months." If the math is right, defend the price with the math.
Reframe the comparison. "Compared to our competitor at $35K, we're 37% more expensive. Our customers who've evaluated both find that we deliver 60% better retention on this workflow, which at your scale is worth $120K annually. Would you like to connect with one of them to validate that?"
Offer value before price reduction. Before you cut price, offer more value. Additional seats, extended implementation support, expanded usage limits. This maintains the price per unit of value while addressing the total cost concern.
Know your floor and hold it with conviction. The seller who gives the impression they'll accept anything gets pushed past their floor. Confidence in your price communicates confidence in your value.