Gate <13✓ IQ Certified10/10?

How do you handle 'your competitor is 30% cheaper'?

📖 2,615 words🗓️ Published Jul 21, 2026

Direct Answer

When a prospect says a competitor is 30% cheaper, resist the urge to defend your price or offer a discount. Instead, lean into curiosity by asking them to walk through exactly what's included at that price point. This investigative approach reveals that most buyers haven't compared feature-for-feature and often discover the competitor's solution lacks critical components like implementation support, advanced reporting, or compliance features. By reframing the conversation around total cost of ownership rather than sticker price, you can demonstrate that cheaper often means narrower and help the buyer see the full picture before making a decision.

The key is to never match the price, as that signals you had margin to give all along. Instead, ask what the competitor's solution doesn't do that matters to them, moving the conversation from cost to fit. According to Gartner, only 18% of B2B software deals are won on price alone—the rest turn on perceived value, integration fit, and risk reduction. When a buyer understands exactly what they're trading off, they make better decisions.

Why Do Prospects Lead with "30% Cheaper" Instead of Value?

Prospects lead with price because it's the easiest comparison point—they don't have to understand your product's nuances to see a lower number. This is price anchoring in action: the competitor sets a low anchor, and everything else seems expensive by comparison. Research in behavioral economics shows that price anchors work best when the buyer lacks context for comparison. If your prospect can't easily articulate what differentiates your solution, the anchor sticks.

Your job is to break the anchor by introducing a value anchor instead. Ask: "What's the cost to your team if this solution doesn't deliver on X, Y, or Z?" That shifts the conversation from "how much does it cost?" to "what's the risk of choosing wrong?" This reframe is powerful because loss aversion is stronger than gain seeking—buyers will pay more to avoid a painful failure than to achieve a marginal saving. A practical technique is the "Rule of Three": acknowledge the price gap without defensiveness, reframe the value differential, and quantify the cost of switching or underperformance.

How Do You Uncover Hidden Costs in a Cheaper Competitor's Offering?

Cheaper solutions often hide costs that don't appear on the invoice. These fall into three categories: integration debt, training overhead, and opportunity cost. Integration debt means your team spends extra hours making the cheaper tool work with existing systems—hours that aren't billed but are very real. Training overhead multiplies when the cheaper solution has a steeper learning curve, leading to lower adoption. Opportunity cost is the hardest to quantify but often the largest: the revenue or efficiency you don't capture because the cheaper tool lacks a critical feature.

How do you handle 'your competitor is 30% cheaper' — figure 1

Use this diagnostic question with your prospect: "If we assume both solutions work perfectly for your core use case, where does the 30% saving come from? Is it in support, reliability, features, or onboarding?" Most buyers haven't thought about this. They've just seen a lower number. By helping them map where the savings originate, you surface potential risks they hadn't considered. For example, if the competitor saves on support, ask: "What's your current average response time for critical issues? Ours is under 2 hours. Theirs is 24 hours. How does that impact your team's productivity?"

A useful exercise is to ask the prospect to create a simple "total cost of ownership" table with three columns—your solution, the competitor, and hidden costs they might not have considered. Walk through items like implementation time, training hours, customization needs, and ongoing support. When you factor in these intangibles, the 30% gap often shrinks to 10-15% or even flips entirely. This isn't manipulation—it's helping the buyer make a fully informed decision. For more on this approach, see our guide on price compression objections.

How do you handle 'your competitor is 30% cheaper' — figure 2

What If the Competitor Is Genuinely a Better Fit for Their Needs?

Not every price objection needs to be overcome. Sometimes, the competitor is a better fit for a specific segment of the market. If your prospect's needs truly align with a simpler, cheaper solution, pushing back aggressively can damage your credibility. The key is to distinguish between misguided price sensitivity and legitimate budget constraints. The former responds to value education; the latter requires creative deal engineering.

Ask a direct question: "If our solution were the same price as theirs, would you choose us?" If the answer is yes, then price is the only barrier, and you can explore creative deal structures—annual prepayment discounts, phased rollouts, or stripped-down packages. If the answer is no, then the objection isn't really about price—it's about perceived value, trust, or fit. In that case, dig deeper: "What would need to change for us to be your first choice?" Their answer reveals the real blocker.

For legitimate budget constraints, consider offering a "good-better-best" tiered approach. Position your core offering as the "good" tier at a competitive price point, with premium features available as add-ons. This lets the buyer feel they're getting a deal while preserving your average revenue per customer. Alternatively, propose a pilot or proof-of-concept at a reduced rate, with the full contract contingent on demonstrated ROI. This lowers the perceived risk for the buyer while protecting your pricing integrity. A 3-month pilot at 50% discount is safer than a 30% permanent discount. For more on this, see our playbook on margin defense.

How do you handle 'your competitor is 30% cheaper' — figure 3

How Do You Train Reps to Handle This Objection Without Discounting?

Training reps to handle the "30% cheaper" objection requires shifting their mindset from defense to investigation. The first step is role-playing scenarios where the rep practices staying curious rather than defensive. Start with a simple script: "That's a significant difference. Can you walk me through what's included in their offering at that price point?" This forces the buyer to articulate the scope and often reveals gaps the rep can address.

Next, teach reps to quantify hidden costs without sounding like they're making excuses. Use real-world examples: "At $200/month, that's $2,400/year. But our research shows companies spend an average of $8,000 in year one making competing tools work with their existing stack. Your actual cost with them would be $10,400—versus $6,000 with us, including onboarding." This isn't manipulation; it's helping the buyer see the full picture. According to HubSpot's 2024 State of Sales, reps who lead with discovery questions close at 28% higher rates than reps who lead with feature defense.

How do you handle 'your competitor is 30% cheaper' — figure 4

Finally, create a "never discount" rule in your sales playbook. If a rep feels pressure to drop price, they should escalate to a manager for approval. This builds discipline and prevents margin erosion. Bain's pricing research shows that a 1% price discount destroys approximately 8% of operating profit for the average B2B software company. One reflexive 30% match-discount can wipe a year of margin gains. Instead, if you must offer a concession, do it on terms—annual prepayment, longer commitment, or reduced scope—never on unit price.

What Does a Value-Based Reframe Look Like in Practice?

A value-based reframe moves the conversation from "how much does it cost?" to "what's the cost of not having this capability?" Start by acknowledging the price difference openly: "I understand their price looks attractive. Let's look at what you'd get and what you'd miss." Then, pivot to value by asking: "What does their solution not do that matters to you?" This moves the conversation from cost to fit.

Use concrete math to illustrate total cost of ownership. For example: "If their $200/month tool requires $5,000 in integration consulting and 20 hours of internal IT time to set up, the first-year cost exceeds yours. At $200/month, that's $2,400/year. But with integration costs, it's $10,400 in year one—versus $6,000 with us, including onboarding." This isn't hypothetical; it's data your prospect hasn't seen. Present it as a courtesy, not a scare tactic.

How do you handle 'your competitor is 30% cheaper' — figure 5

Another technique is to offer a feature-limited SKU instead of a discount. If their advantage is genuinely just price, build a Lite tier that delivers core value at a lower price plus one critical thing the competitor can't do. You're not matching their price; you're offering a real alternative. SaaS benchmark data from OpenView's 2023 SaaS Benchmarks shows companies with 3+ pricing tiers grow 38% faster than single-SKU competitors. A Lite tier lets you capture price-sensitive buyers without diluting your premium offering's perceived value.

When Should You Walk Away Instead of Fighting on Price?

You should walk away when the competitor's solution is genuinely sufficient for the prospect's needs and they refuse to acknowledge any trade-offs. If you ask, "If we moved you to Lite at $150/month, would the missing feature cost you elsewhere or slow your team down?" and they say no, they're telling you the cheaper tool is sufficient. The worst outcome is winning a deal where the buyer later resents your pricing; the second-worst is wasting cycles on a deal that was never a fit.

Another sign to walk is when your product is genuinely commoditized—same feature set, same integrations, same support tier. In that case, the value-vs-price reframe is theatrical, and the buyer will see through it. The honest answer in a commoditized market is either match price and compete on operational excellence, bundle services the competitor can't deliver, or accept that you're losing this segment and reposition upmarket. Refusing to discount in a true commodity fight is how mid-market SaaS companies die slowly while telling themselves they're "premium."

Finally, walk away if the buyer's organization treats integration costs as somebody else's problem. In organizations where engineering is a separate cost center, the buying team often discounts integration burden because it's someone else's P&L. Be ready to switch to risk-of-failure framing: "If the integration fails, who's accountable for the remediation?" This shifts from abstract company cost to personal career risk, which is a much stronger motivator. For more on qualifying out fast, see our guide on when to walk vs. fight.

FAQ

What if the competitor really is 30% cheaper? Cheaper usually means they've cut something—scope, support, reliability, or features you actually need. Ask the prospect: "What does their solution not include that matters to your team?" The gap often makes the price difference irrelevant. If there's genuinely no gap, consider whether this deal is worth pursuing.

How do I reframe the conversation without sounding defensive? Acknowledge the price difference openly, then pivot to value. Say: "I understand cost matters—let's look at what you'd get and what you'd miss." This keeps you credible and shifts focus to fit, not fighting on price. Avoid phrases like "but we're better"—let the buyer draw their own conclusions.

What if the competitor's product is actually good enough for them? Then it's not about price—it's about priority. Probe what "good enough" means for their specific use case. Many buyers later find hidden costs in switching, training, or missing integrations that weren't obvious upfront. Ask: "What happens if their solution fails during a critical period?"

Can I ever match the price to win the deal? Matching price rarely works long-term—it trains buyers to negotiate every time. Instead, offer a tailored scope or payment terms if needed, but keep your core pricing intact. The goal is to win on value, not discounts. A one-time discount becomes an expectation.

How do I prove my solution is worth the premium? Use case studies, ROI calculators, or a pilot period. Show how your product solves a specific pain their cheaper option ignores. Buyers pay more when they see direct impact on their revenue, time, or risk reduction. Quantify the impact in their terms, not yours.

What if they're already using the competitor and happy? Respect their choice, but ask: "What's one thing you wish their product did better?" That often reveals an unmet need you can address. Even happy users switch when they find a solution that fills that gap without extra cost. Frame it as "what would make your life easier?"

How do I handle procurement teams that demand a discount? Shift the conversation from price to terms. Offer annual prepayment, longer commitments, or reduced scope instead of a unit price discount. Procurement teams often have flexibility on payment structure but less on unit price. This preserves your margin while giving them a win.

What if I've already discounted and now the buyer expects more? Reset expectations by tying future pricing to demonstrated ROI. Say: "We offered that discount to get started. Going forward, our pricing reflects the value we deliver. Let's set a review point to measure impact." This maintains your pricing integrity while rewarding adoption.

How do I handle this objection in a discovery call? Stay curious and ask: "That's interesting—can you tell me more about what led you to that comparison?" This buys you time and reveals their thought process. Then ask about specific features, support, and outcomes to uncover gaps in the competitor's offering.

What if the competitor is a well-known brand with lower prices? Acknowledge their brand recognition, then ask: "What specific outcomes are you hoping to achieve that their lower price might not cover?" Well-known brands often have broad but shallow offerings. Your deeper capabilities in specific areas can justify the premium.

Sources

flowchart TD A["Prospect says competitor is 30% cheaper"] --> B{Is this a legitimate budget constraint?} B -->|Yes| C[Explore creative deal structures] C --> D[Annual prepayment, phased rollout, or Lite tier] D --> E[Preserve pricing integrity] B -->|No| F[Is it about perceived value or fit?] F --> G["Dig deeper: 'What would need to change?'"] G --> H{Is there a real differentiation gap?} H -->|Yes| I[Quantify hidden costs and TCO] H -->|No| J[Let them go gracefully] I --> K[Reframe around value, not price] K --> L[Win on value or walk]

quadrantChart x-axis Low Cost --> High Cost y-axis Low Value --> High Value Your Solution: [75, 80] Competitor: [30, 45] Lite Tier: [50, 70] Enterprise: [85, 90] !["How do you handle 'your competitor is 30% cheaper' — figure 6"](/assets/qa/q67-b6.jpg)

Related on PULSE

[Should I Hire a Fractional CRO If I Am Losing Deals to a Cheaper Competitor?](/knowledge/q16073)
[How do you coach a rep to handle a competitor comparison objection?](/knowledge/q13917)
[How do you align sales and marketing on a shared lead scoring model in 2027?](/knowledge/q19155)
[What is the bull case for Salesloft 2027?](/knowledge/q1839)

Download:

## Direct Answer

When a prospect says a competitor is 30% cheaper, resist the urge to defend your price or offer a discount. Instead, lean into curiosity by asking them to walk through exactly what's included at that price point. This investigative approach reveals that most buyers haven't compared feature-for-feature and often discover the competitor's solution lacks critical components like implementation support, advanced reporting, or compliance features. By reframing the conversation around total cost of ownership rather than sticker price, you can demonstrate that cheaper often means narrower and help the buyer see the full picture before making a decision.

The key is to never match the price, as that signals you had margin to give all along. Instead, ask what the competitor's solution doesn't do that matters to them, moving the conversation from cost to fit. According to Gartner, only 18% of B2B software deals are won on price alone—the rest turn on perceived value, integration fit, and risk reduction. When a buyer understands exactly what they're trading off, they make better decisions.

## Why Do Prospects Lead with "30% Cheaper" Instead of Value?

Prospects lead with price because it's the easiest comparison point—they don't have to understand your product's nuances to see a lower number. This is price anchoring in action: the competitor sets a low anchor, and everything else seems expensive by comparison. Research in behavioral economics shows that price anchors work best when the buyer lacks context for comparison. If your prospect can't easily articulate what differentiates your solution, the anchor sticks.

Your job is to break the anchor by introducing a value anchor instead. Ask: "What's the cost to your team if this solution doesn't deliver on X, Y, or Z?" That shifts the conversation from "how much does it cost?" to "what's the risk of choosing wrong?" This reframe is powerful because loss aversion is stronger than gain seeking—buyers will pay more to avoid a painful failure than to achieve a marginal saving. A practical technique is the "Rule of Three": acknowledge the price gap without defensiveness, reframe the value differential, and quantify the cost of switching or underperformance.

## How Do You Uncover Hidden Costs in a Cheaper Competitor's Offering?

Cheaper solutions often hide costs that don't appear on the invoice. These fall into three categories: integration debt, training overhead, and opportunity cost. Integration debt means your team spends extra hours making the cheaper tool work with existing systems—hours that aren't billed but are very real. Training overhead multiplies when the cheaper solution has a steeper learning curve, leading to lower adoption. Opportunity cost is the hardest to quantify but often the largest: the revenue or efficiency you don't capture because the cheaper tool lacks a critical feature.

![How do you handle 'your competitor is 30% cheaper' — figure 1](/assets/qa/q67-b1.jpg)




Use this diagnostic question with your prospect: "If we assume both solutions work perfectly for your core use case, where does the 30% saving come from? Is it in support, reliability, features, or onboarding?" Most buyers haven't thought about this. They've just seen a lower number. By helping them map where the savings originate, you surface potential risks they hadn't considered. For example, if the competitor saves on support, ask: "What's your current average response time for critical issues? Ours is under 2 hours. Theirs is 24 hours. How does that impact your team's productivity?"

A useful exercise is to ask the prospect to create a simple "total cost of ownership" table with three columns—your solution, the competitor, and hidden costs they might not have considered. Walk through items like implementation time, training hours, customization needs, and ongoing support. When you factor in these intangibles, the 30% gap often shrinks to 10-15% or even flips entirely. This isn't manipulation—it's helping the buyer make a fully informed decision. For more on this approach, see [our guide on price compression objections](https://pulserevops.com/knowledge/q324).

![How do you handle 'your competitor is 30% cheaper' — figure 2](/assets/qa/q67-b2.jpg)




## What If the Competitor Is Genuinely a Better Fit for Their Needs?

Not every price objection needs to be overcome. Sometimes, the competitor is a better fit for a specific segment of the market. If your prospect's needs truly align with a simpler, cheaper solution, pushing back aggressively can damage your credibility. The key is to distinguish between misguided price sensitivity and legitimate budget constraints. The former responds to value education; the latter requires creative deal engineering.

Ask a direct question: "If our solution were the same price as theirs, would you choose us?" If the answer is yes, then price is the only barrier, and you can explore creative deal structures—annual prepayment discounts, phased rollouts, or stripped-down packages. If the answer is no, then the objection isn't really about price—it's about perceived value, trust, or fit. In that case, dig deeper: "What would need to change for us to be your first choice?" Their answer reveals the real blocker.

For legitimate budget constraints, consider offering a "good-better-best" tiered approach. Position your core offering as the "good" tier at a competitive price point, with premium features available as add-ons. This lets the buyer feel they're getting a deal while preserving your average revenue per customer. Alternatively, propose a pilot or proof-of-concept at a reduced rate, with the full contract contingent on demonstrated ROI. This lowers the perceived risk for the buyer while protecting your pricing integrity. A 3-month pilot at 50% discount is safer than a 30% permanent discount. For more on this, see [our playbook on margin defense](https://pulserevops.com/knowledge/q45).

![How do you handle 'your competitor is 30% cheaper' — figure 3](/assets/qa/q67-b3.jpg)




```mermaid
flowchart TD
    A[Prospect says competitor is 30% cheaper] --> B{Is this a legitimate budget constraint?}
    B -->|Yes| C[Explore creative deal structures]
    C --> D[Annual prepayment, phased rollout, or Lite tier]
    D --> E[Preserve pricing integrity]
    B -->|No| F[Is it about perceived value or fit?]
    F --> G[Dig deeper: 'What would need to change?']
    G --> H{Is there a real differentiation gap?}
    H -->|Yes| I[Quantify hidden costs and TCO]
    H -->|No| J[Let them go gracefully]
    I --> K[Reframe around value, not price]
    K --> L[Win on value or walk]
```

## How Do You Train Reps to Handle This Objection Without Discounting?

Training reps to handle the "30% cheaper" objection requires shifting their mindset from defense to investigation. The first step is role-playing scenarios where the rep practices staying curious rather than defensive. Start with a simple script: "That's a significant difference. Can you walk me through what's included in their offering at that price point?" This forces the buyer to articulate the scope and often reveals gaps the rep can address.

Next, teach reps to quantify hidden costs without sounding like they're making excuses. Use real-world examples: "At $200/month, that's $2,400/year. But our research shows companies spend an average of $8,000 in year one making competing tools work with their existing stack. Your actual cost with them would be $10,400—versus $6,000 with us, including onboarding." This isn't manipulation; it's helping the buyer see the full picture. According to [HubSpot's 2024 State of Sales](https://www.hubspot.com/state-of-marketing), reps who lead with discovery questions close at 28% higher rates than reps who lead with feature defense.

![How do you handle 'your competitor is 30% cheaper' — figure 4](/assets/qa/q67-b4.jpg)




Finally, create a "never discount" rule in your sales playbook. If a rep feels pressure to drop price, they should escalate to a manager for approval. This builds discipline and prevents margin erosion. [Bain's pricing research](https://www.bain.com/insights/) shows that a 1% price discount destroys approximately 8% of operating profit for the average B2B software company. One reflexive 30% match-discount can wipe a year of margin gains. Instead, if you must offer a concession, do it on terms—annual prepayment, longer commitment, or reduced scope—never on unit price.

## What Does a Value-Based Reframe Look Like in Practice?

A value-based reframe moves the conversation from "how much does it cost?" to "what's the cost of not having this capability?" Start by acknowledging the price difference openly: "I understand their price looks attractive. Let's look at what you'd get and what you'd miss." Then, pivot to value by asking: "What does their solution not do that matters to you?" This moves the conversation from cost to fit.

Use concrete math to illustrate total cost of ownership. For example: "If their $200/month tool requires $5,000 in integration consulting and 20 hours of internal IT time to set up, the first-year cost exceeds yours. At $200/month, that's $2,400/year. But with integration costs, it's $10,400 in year one—versus $6,000 with us, including onboarding." This isn't hypothetical; it's data your prospect hasn't seen. Present it as a courtesy, not a scare tactic.

![How do you handle 'your competitor is 30% cheaper' — figure 5](/assets/qa/q67-b5.jpg)




Another technique is to offer a feature-limited SKU instead of a discount. If their advantage is genuinely just price, build a Lite tier that delivers core value at a lower price plus one critical thing the competitor can't do. You're not matching their price; you're offering a real alternative. SaaS benchmark data from [OpenView's 2023 SaaS Benchmarks](https://openviewpartners.com/2023-saas-benchmarks-report/) shows companies with 3+ pricing tiers grow 38% faster than single-SKU competitors. A Lite tier lets you capture price-sensitive buyers without diluting your premium offering's perceived value.

```mermaid
quadrantChart
    x-axis Low Cost --> High Cost
    y-axis Low Value --> High Value
    Your Solution: [75, 80]
    Competitor: [30, 45]
    Lite Tier: [50, 70]
    Enterprise: [85, 90]

![How do you handle 'your competitor is 30% cheaper' — figure 6](/assets/qa/q67-b6.jpg)



```

## When Should You Walk Away Instead of Fighting on Price?

You should walk away when the competitor's solution is genuinely sufficient for the prospect's needs and they refuse to acknowledge any trade-offs. If you ask, "If we moved you to Lite at $150/month, would the missing feature cost you elsewhere or slow your team down?" and they say no, they're telling you the cheaper tool is sufficient. The worst outcome is winning a deal where the buyer later resents your pricing; the second-worst is wasting cycles on a deal that was never a fit.

Another sign to walk is when your product is genuinely commoditized—same feature set, same integrations, same support tier. In that case, the value-vs-price reframe is theatrical, and the buyer will see through it. The honest answer in a commoditized market is either match price and compete on operational excellence, bundle services the competitor can't deliver, or accept that you're losing this segment and reposition upmarket. Refusing to discount in a true commodity fight is how mid-market SaaS companies die slowly while telling themselves they're "premium."

Finally, walk away if the buyer's organization treats integration costs as somebody else's problem. In organizations where engineering is a separate cost center, the buying team often discounts integration burden because it's someone else's P&L. Be ready to switch to risk-of-failure framing: "If the integration fails, who's accountable for the remediation?" This shifts from abstract company cost to personal career risk, which is a much stronger motivator. For more on qualifying out fast, see [our guide on when to walk vs. fight](https://pulserevops.com/knowledge/q89).

## Related questions

### How do you quantify hidden costs in a competitor's pricing?
Ask the prospect to walk through what's included in the competitor's offering at that price point, then map potential gaps in support, integration, training, and features. Use a simple TCO table to reveal costs like implementation time and ongoing maintenance.

### What if the competitor's product is actually good enough for their needs?
Probe what "good enough" means for their specific use case, then ask about hidden costs like training overhead or opportunity cost from missing features. Many buyers later find the cheaper solution fails during critical periods.

### Can I ever offer a discount to match the competitor's price?
Matching price rarely works long-term—it trains buyers to negotiate every time. Instead, offer a tailored scope, annual prepayment, or pilot program at a reduced rate while keeping your core pricing intact.

### How do I train my sales team to handle this objection?
Role-play scenarios where reps practice staying curious rather than defensive. Teach them to ask discovery questions like "What does their solution not do that matters to you?" and quantify hidden costs without sounding like they're making excuses.

### What if the buyer's organization doesn't care about integration costs?
Switch to risk-of-failure framing by asking who's accountable if the integration fails. This shifts from abstract company cost to personal career risk, which is a stronger motivator, especially in organizations where engineering is a separate cost center.

## FAQ

**What if the competitor really is 30% cheaper?**  
Cheaper usually means they've cut something—scope, support, reliability, or features you actually need. Ask the prospect: "What does their solution not include that matters to your team?" The gap often makes the price difference irrelevant. If there's genuinely no gap, consider whether this deal is worth pursuing.

**How do I reframe the conversation without sounding defensive?**  
Acknowledge the price difference openly, then pivot to value. Say: "I understand cost matters—let's look at what you'd get and what you'd miss." This keeps you credible and shifts focus to fit, not fighting on price. Avoid phrases like "but we're better"—let the buyer draw their own conclusions.

**What if the competitor's product is actually good enough for them?**  
Then it's not about price—it's about priority. Probe what "good enough" means for their specific use case. Many buyers later find hidden costs in switching, training, or missing integrations that weren't obvious upfront. Ask: "What happens if their solution fails during a critical period?"

**Can I ever match the price to win the deal?**  
Matching price rarely works long-term—it trains buyers to negotiate every time. Instead, offer a tailored scope or payment terms if needed, but keep your core pricing intact. The goal is to win on value, not discounts. A one-time discount becomes an expectation.

**How do I prove my solution is worth the premium?**  
Use case studies, ROI calculators, or a pilot period. Show how your product solves a specific pain their cheaper option ignores. Buyers pay more when they see direct impact on their revenue, time, or risk reduction. Quantify the impact in their terms, not yours.

**What if they're already using the competitor and happy?**  
Respect their choice, but ask: "What's one thing you wish their product did better?" That often reveals an unmet need you can address. Even happy users switch when they find a solution that fills that gap without extra cost. Frame it as "what would make your life easier?"

**How do I handle procurement teams that demand a discount?**  
Shift the conversation from price to terms. Offer annual prepayment, longer commitments, or reduced scope instead of a unit price discount. Procurement teams often have flexibility on payment structure but less on unit price. This preserves your margin while giving them a win.

**What if I've already discounted and now the buyer expects more?**  
Reset expectations by tying future pricing to demonstrated ROI. Say: "We offered that discount to get started. Going forward, our pricing reflects the value we deliver. Let's set a review point to measure impact." This maintains your pricing integrity while rewarding adoption.

**How do I handle this objection in a discovery call?**  
Stay curious and ask: "That's interesting—can you tell me more about what led you to that comparison?" This buys you time and reveals their thought process. Then ask about specific features, support, and outcomes to uncover gaps in the competitor's offering.

**What if the competitor is a well-known brand with lower prices?**  
Acknowledge their brand recognition, then ask: "What specific outcomes are you hoping to achieve that their lower price might not cover?" Well-known brands often have broad but shallow offerings. Your deeper capabilities in specific areas can justify the premium.

## Sources

- [Gartner B2B Buyer Sentiment Study](https://www.gartner.com/en/sales/insights/b2b-buying-journey)
- [HubSpot 2024 State of Sales](https://www.hubspot.com/state-of-marketing)
- [Forrester Total Economic Impact Research](https://www.forrester.com/research)
- [OpenView 2023 SaaS Benchmarks Report](https://openviewpartners.com/2023-saas-benchmarks-report/)
- [Bain & Company Pricing Research](https://www.bain.com/insights/)
- [Salesforce Research](https://www.salesforce.com/research/)
- [Harvard Business Review on Pricing Strategy](https://hbr.org/topic/pricing)
- [McKinsey & Company on Pricing Tactics](https://www.mckinsey.com/capabilities/growth-marketing-and-sales/our-insights)
- [U.S. Small Business Administration Pricing Guide](https://www.sba.gov/business-guide/manage-your-business/pricing-your-products)
- [Investopedia on Value Propositions](https://www.investopedia.com/terms/v/valueproposition.asp)

## Related on PULSE

- [Should I Hire a Fractional CRO If I Am Losing Deals to a Cheaper Competitor?](/knowledge/q16073)
- [How do you coach a rep to handle a competitor comparison objection?](/knowledge/q13917)
- [How do you align sales and marketing on a shared lead scoring model in 2027?](/knowledge/q19155)
- [What is the bull case for Salesloft 2027?](/knowledge/q1839)

Was this helpful?

Sources cited

joinpavilion.comhttps://www.joinpavilion.com/compensation-report bridgegroupinc.comhttps://www.bridgegroupinc.com/blog/sales-development-report bvp.comhttps://www.bvp.com/atlas/state-of-the-cloud-2026 news.crunchbase.comhttps://news.crunchbase.com/

⌬ Apply this in PULSE

Pillar · Deal Desk ArchitectureFrom founder override to scaled governance Gross Profit CalculatorModel margin per deal, per rep, per territory

Kory White

How do you handle 'your competitor is 30% cheaper'?

Why Do Prospects Lead with "30% Cheaper" Instead of Value?

How Do You Uncover Hidden Costs in a Cheaper Competitor's Offering?

What If the Competitor Is Genuinely a Better Fit for Their Needs?

How Do You Train Reps to Handle This Objection Without Discounting?

What Does a Value-Based Reframe Look Like in Practice?

When Should You Walk Away Instead of Fighting on Price?

Related questions

How do you quantify hidden costs in a competitor's pricing?

What if the competitor's product is actually good enough for their needs?

Can I ever offer a discount to match the competitor's price?

How do I train my sales team to handle this objection?

What if the buyer's organization doesn't care about integration costs?

FAQ

Sources

Related on PULSE

Two scores — Gate vs IQ