“Too expensive” looks like useful customer feedback.

It is not.

At least, not by itself.

When a customer says:

“This is too expensive.”

they have told you what they decided to call the problem.

They have not necessarily told you what caused it.

They might genuinely be unable to afford the product.

They might think a competitor offers a better deal.

They might like the product but use it too infrequently to justify the price.

They might not understand why your product costs more.

They might have expected something different.

They might not trust the product enough to take the risk.

Or they might simply be the wrong customer for the offer.

Those are very different problems.

Yet businesses often put all of them into the same category:

Price objection.

That is where the analysis should begin—not end.

Why Do Customers Say a Product Is Too Expensive?

A customer can say:

“Too expensive.”

for several very different reasons.

A useful starting framework is:

The words are the same.

The business problem is not.

That is why the first task is not:

“Should we lower the price?”

It is:

“What does ‘too expensive’ mean for this customer in this situation?”

Price Is Not the Same as Perceived Value

A common mistake is to treat customer price objections as evidence that the price itself is too high.

But price and perceived value are different.

Consider two customers looking at a $200 product.

Customer A thinks:

“I use this every day. It saves me a lot of time.”

Customer B thinks:

“I'll probably use this twice.”

The price is identical.

The perceived value is not.

This means a price objection can sometimes be better understood as:

value is insufficient relative to the customer's situation.

That does not automatically mean the price is correct.

It means the first hypothesis should be investigated rather than assumed.

Start With the Raw Customer Feedback

Do not begin with:

“Why is our price too high?”

Start with the evidence.

Useful sources include:

• product reviews
• customer support messages
• survey responses
• cancellation reasons
• return comments
• customer questions
• Reddit discussions
• social comments
• competitor reviews

For an initial analysis, ask AI to identify the different ways customers express price resistance.

For example:

Analyze the following customer feedback for price-related objections.

Identify the different ways customers communicate that
the product is too expensive.

For each recurring pattern, identify:

1. What the customer explicitly says
2. What they appear to be comparing the price against
3. Their usage context
4. Their expectations
5. Possible underlying reasons for the objection

Do not assume that every “too expensive” comment means
the same thing.

Separate direct customer evidence from interpretation.

The goal is to discover the different meanings hidden behind the same phrase.

Step 1: Separate the Statement From the Interpretation

Suppose a customer writes:

“I can't justify spending $300 on this.”

The direct evidence is:

The customer does not believe a $300 purchase is justified.

That is not the same as:

The product is overpriced.

Possible explanations include:

• limited budget
• insufficient perceived value
• low usage frequency
• stronger competitor
• lack of trust
• wrong customer segment

Keep those explanations separate until you have more evidence.

Step 2: Ask What the Customer Is Comparing Against

Price is always relative to something.

A customer may compare the product with:

• another brand
• a cheaper model
• a more expensive premium model
• an existing product
• a DIY solution
• doing nothing
• delaying the purchase

For example:

“Why would I pay $200 when another product costs $80?”

The real issue may be:

The customer does not perceive enough differentiation to justify the $120 premium.

That is different from:

$200 is objectively too expensive.

This is why competitor context matters.

Step 3: Investigate the Customer's Usage Context

Usage frequency can dramatically change perceived value.

Imagine:

Product price = $200

Customer A:

Uses it every day.

Customer B:

Uses it once a month.

The price is identical.

The value calculation is not.

A customer may say:

“Too expensive.”

because:

The benefit is not frequent enough for the purchase to make sense.

That can point to:

• product fit
• use frequency
• target audience
• offer design
• positioning

rather than a simple pricing problem.

Step 4: Investigate Expectations

Customers evaluate price against what they expected to receive.

Suppose customers believe a $300 product should deliver:

• premium materials
• high durability
• advanced functionality
• excellent support
• low maintenance

But the product experience feels basic.

The complaint may become:

“Too expensive.”

The real problem may be:

The customer's expectation of the product does not match the experience.

This can be a product problem.

But it can also be:

• a positioning problem
• a communication problem
• an expectation problem

Again, the phrase alone does not tell you which one.

Step 5: Investigate Perceived Value

Ask:

What benefit does the customer believe they are paying for?

For example:

“This isn't worth $500.”

The next question is:

Worth what?

Perhaps the customer expected:

significant time savings

but experienced:

only a small convenience.

Or they expected:

professional-level performance

but got:

consumer-level performance.

The price may be acceptable.

The perceived outcome may simply be insufficient.

Step 6: Investigate Trust and Risk

Sometimes customers say:

“Too expensive.”

when what they really mean is:

“I'm not confident enough to risk this amount.”

This can happen when:

• the brand is unfamiliar
• product reviews are limited
• the warranty is unclear
• returns are difficult
• the product is new
• product claims are difficult to verify
• the customer's expected outcome is uncertain

The customer is not necessarily saying:

“I could never afford this.”

They may be saying:

“I do not have enough confidence to spend this much.”

That is a very different problem.

Step 7: Investigate Customer Fit

Some customers are simply not the right customers for the offer.

A premium product may be perfectly priced for:

frequent users who value performance.

But overpriced from the perspective of:

occasional users who need only a basic solution.

If you lower the price to satisfy the second group, you may unnecessarily damage the economics of the first.

So ask:

Which customer is calling it expensive?

This question is often more useful than:

“How many customers call it expensive?”

Step 8: Segment the Price Objection

Do not treat every price objection as one group.

For example:

Price Objections
       │
       ├── Affordability
       ├── Low Perceived Value
       ├── Better Competitor Offer
       ├── Low Usage Frequency
       ├── Trust / Risk
       ├── Expectation Gap
       └── Customer-Product Fit

Then investigate each group separately.

This is where AI can provide useful analytical leverage.

Instead of summarizing 2,000 price objections, it can help identify different objection structures.

Step 9: Compare What Customers Say With What They Do

Words are useful.

Behavior can add another layer.

For example:

Customers say:

“Too expensive.”

But:

• they repeatedly return to the product page
• they compare several variants
• they read many reviews
• they add to cart
• they purchase after a discount

That behavior might suggest:

strong interest with price sensitivity.

Another group might never engage with the product at all.

That could indicate:

weak relevance rather than price resistance.

The customer language and behavioral data together are more informative than either one alone.

Step 10: Cross-Validate the Explanation

Suppose AI finds:

Customers complain about price because they do not perceive enough differentiation.

Before changing the price, look for other evidence.

Check:

• reviews
• support questions
• competitor reviews
• product comparisons
• customer behavior
• return reasons
• customer segments

For example:

Reviews:
“Why is this so expensive?”

Customer questions:
“What does this do that the cheaper version doesn't?”

Competitor research:
Lower-priced alternatives explain similar features more clearly.

Behavior:
Price-sensitive customers compare alternatives before leaving.

Hypothesis:
The issue may be perceived differentiation rather than
absolute affordability.

That gives you a stronger basis for deciding what to test.

The Same “Too Expensive” Comment Can Hide Different Problems

Consider five customers.

Customer A

“I can't afford it.”

Likely issue:

affordability.

Customer B

“The cheaper version seems to do the same thing.”

Likely issue:

perceived differentiation.

Customer C

“I only need this once or twice.”

Likely issue:

usage frequency.

Customer D

“I expected better quality at this price.”

Likely issue:

expectation gap.

Customer E

“I've never heard of this brand. I'm not paying that much for something I haven't tried.”

Likely issue:

trust and perceived risk.

The same objection label:

Price.

Five different investigations.

Why Lowering the Price Is Often the Wrong First Move

Suppose customers say:

“Too expensive.”

A common response is:

Discount.

But if the real issue is:

lack of perceived value,

the discount may only partially improve conversion.

If the issue is:

lack of trust,

a discount does not automatically create confidence.

If the issue is:

poor customer fit,

a lower price might attract even more customers who are not a good fit.

If the issue is:

unclear differentiation,

the customer may still choose the competitor.

The right first question is:

What does the customer believe they are buying for this price?

A Better AI Prompt for Price Objections

Analyze the following customer feedback containing price-related objections.

For each recurring pattern:

1. Quote the customer's direct price-related statement.
2. Identify the customer's usage context.
3. Identify what the customer appears to compare the price against.
4. Identify their expected outcome.
5. Identify possible reasons they perceive the price negatively.
6. Separate affordability from perceived value.
7. Consider competitor, trust, expectation, usage-frequency,
   and customer-fit explanations.
8. Identify supporting evidence.
9. Identify contradictory evidence.
10. State what additional evidence would help validate each explanation.

Do not conclude that the product is overpriced simply because
customers mention price.

Treat the underlying explanation as a hypothesis unless the evidence
supports a stronger conclusion.

A Useful Analysis Table

You can structure the output like this:

This forces the analysis to remain evidence-driven.

Price Objection Does Not Necessarily Mean Price Sensitivity

This is another useful distinction.

Someone may say:

“It's expensive.”

but still purchase.

Another customer may say:

“It looks expensive.”

and leave immediately.

Another may say:

“It's expensive, but worth it.”

Those are different customer states.

Therefore:

Price language should not be treated as a direct measurement of price sensitivity.

You need context and behavior.

The Commercial Question

After analyzing the objection, the important business question becomes:

What decision should this evidence change?

Possible decisions include:

Change the price

Only when evidence supports a pricing issue.

Improve value communication

When customers do not understand the benefit.

Improve product differentiation

When competitors appear to offer more for less.

Improve trust

When the real barrier is risk.

Narrow the target customer

When the offer is valuable only to a particular segment.

Change the product

When the product genuinely under-delivers relative to expectations.

Do nothing

When the objection comes primarily from customers the business does not need to serve.

This is why:

“Too expensive.”

is not an answer.

It is a research starting point.

A Practical Price Objection Investigation

Customer says:
“Too expensive.”
        ↓
What are they comparing it against?
        ↓
What are they trying to accomplish?
        ↓
How frequently will they use it?
        ↓
What did they expect?
        ↓
What value do they perceive?
        ↓
What risks do they see?
        ↓
What alternatives do they have?
        ↓
Which explanation has the strongest evidence?
        ↓
What should be validated next?
        ↓
What business decision could this affect?

The Real Reason Behind "Too Expensive"

Sometimes the answer really is:

The price is too high.

But that should be a finding, not an assumption.

Other times the answer is:

The customer does not see enough value.

Or:

The customer compares the product with a cheaper alternative.

Or:

The customer does not trust the product enough.

Or:

The product is not a good fit for the customer's use case.

Or:

The customer expected something different.

These problems look similar when reduced to:

Price objection.

They are not similar once you investigate the evidence.

Final Framework

When customers say a product is too expensive, investigate:

Price Objection
      ↓
Customer Context
      ↓
Usage Scenario
      ↓
Customer Expectation
      ↓
Alternative / Comparison
      ↓
Perceived Value
      ↓
Risk / Trust
      ↓
Customer Fit
      ↓
Evidence
      ↓
Alternative Explanations
      ↓
Validation
      ↓
Business Decision

The objective is not to convince customers that the product is worth the price.

The objective is to understand:

What does “too expensive” actually mean to this customer?

AI can make that investigation faster by analyzing large amounts of customer language, comparing different objection patterns, and surfacing competing explanations.

But the final conclusion should remain grounded in evidence.

Because:

“Too expensive” is a customer statement.

It is not necessarily a diagnosis.

Related Research

How to Analyze Customer Reviews With AI →

Customer Feedback Analysis →

How to Find Customer Pain Points in Reviews With AI →

How to Find Customer Needs in Reviews With AI →

How to Analyze Negative Reviews for Customer Insights →

Continue Investigating Customer Objections

The same approach can be applied to other customer statements:

“I need to think about it.”

“I'm not sure.”

“It's not worth the money.”

“I'll compare some other options.”

“I don't trust this brand yet.”

The surface language changes.

The underlying decision problem may be very different.

Miyeta's goal is to investigate the difference.