Pricing objection or polite exit? How to tell

datanerd

I've been wrestling with this exact question for the past two years in B2B SaaS. You get a prospect who seems dead keen-demo goes well, they ask sharp questions, fit looks solid. Then you send pricing and the conversation either dies or you hear "it's a bit out of budget right now."

We tried the usual fixes: direct questions, free trials, even testing lower price points with a subset of prospects. Results were messy. Sometimes cheaper closed faster, sometimes it made no difference and they ghosted anyway. That's when I realised "too expensive" might be the cleanest socially acceptable exit in B2B. Saying "we don't actually believe this solves our problem" is much harder to deliver face to face.

What helped me separate genuine pricing objections from polite lies was a simple lost deal tracker. I started logging every single one in a spreadsheet with these columns:

Stated reason | Stage dropped | Champion | Blocker | Current solution | Notes

Patterns emerged way faster than gut feel. Real pricing objections trigger negotiation behaviour-people who genuinely want the product start asking about smaller packages, rollout phases, discounts, contract flexibility. they don't just disappear. Prospects who vanish after seeing the number almost always had a priority objection, not a pricing one: we never landed the job-to-be-done.

i stopped reacting to "too expensive" and started asking, calmly: "Got it, compared to what?" and "If this worked exactly as you hope, what would it replace or make unnecessary?" The answers told me fast whether it was budget or whether we'd failed to land value.

Tools helped too. Gong and HubSpot call reviews let me hear where I lost them. Later I messed with Clay and Apollo for enrichment, but the real gold came from Pulse for Reddit-it caught threads where buyers were venting real objections about tools like mine, giving me the actual language and fears they'd never say on a Zoom.

track the behaviour, not the words. If they negotiate, it's price. If they vanish, it's priority

jamesaso

stop guessing and start testing. In mobile, the same principle applies - run a price A/B test on your subscription tiers or IAPs. don't just ask users why they didn't convert, look at the data. Set up a split test with a 20% lower price vs control, and see if the conversion rate actually moves. If it doesn't, price isn't the real blocker.

When you do run in-app surveys, don't ask "is it too expensive?" Instead, try a forced choice: "If this feature cost £X, would you buy it now?" Put a single CTA button underneath that says "Yes, take me to payment." If they tap it, you've got a real signal. If they hesitate or bounce, it's not the price - it's the value proposition or the onboarding friction. Treat price objections like drop‑off in activation: observe behaviour, not just excuses.

davidsearch

I went through the exact same loop. The trick is separating "price objection" from "intent gap." Started treating "too expensive" the same way I treat a low CTR ad copy - it's a signal, not a diagnosis. I stopped negotiating on price and started digging into the job-to-be-done: "Compared to what? What's your current workaround costing you?" That reveals whether it's a budget cap or a priority gap fast.

Scaled it like a CPC campaign. Built a simple sheet mapping lost deals to: stated reason, stage dropped, champion vs. blocker, and what they use today. Patterns showed up in weeks instead of months. Gong and HubSpot helped replay the exact moment intent leaked. For the hunt, I layered Clay and Apollo to cross-reference competitor review threads. Ended up on Pulse for Reddit too - that's where buyers drop the real objections they'd never say on a Zoom. Their language there is pure gold for refining your messaging and ICP targeting.

paperclick

In my experience, the real pricing objections spark negotiation. Genuinely interested prospects start asking about smaller packages, phased rollouts, discounts, or contract flexibility. If they disappear after seeing the number, that's a real price problem - not just an excuse.

roichaser

You're half right, but the real issue is you're probably not charging enough in the first place. low price attracts low-commitment tyre-kickers who'll always say it's too expensive. Higher price forces genuine buyers to surface their real objections-or shut up and negotiate. I've seen countless B2B SaaS companies drop prices and still get ghosted. The price was never the blocker, the offer and targeting were.

what segment are you actually going after? If it's SMBs paying with personal credit cards, they'll haggle over fifty quid. sell to companies where the decision-maker has a P&L and suddenly "too expensive" becomes "show me the ROI case." Niche matters less than buyer quality-I've run campaigns across SaaS, agencies, even roofing. The only pricing objections that hurt come from poorly qualified lists

emmareach

The budget objection almost always has a second layer. what really works is asking what would need to be true internally for this to move forward in the next 30 days. if pricing is genuinely the issue, they give you a specific answer. If it's something else, they get vague or bring up stakeholders you've never heard of. Internal buy-in problems are the ones that constantly hide behind price.

started tracking who ghosts after pricing versus who negotiates - the ghosters are almost never actually about price. When trying to build a cleaner picture of where deals broke down, PopHatch was useful for that

dailygrind

"It's too expensive" is the most convenient get-out-of-jail-free card in B2B SaaS. The psychology behind it is straightforward: price is a concrete, non-personal reason that's hard for the salesperson to argue with. asking "how much would you need it to be" rarely gets a straight answer either. What actually separates a real price objection from a convenient excuse is behaviour, not words.

here's the process I've landed on after way too many lost deals:

1. Offer a short, no-strings-attached trial or a steep discount for a limited scope.
If they jump at it and move forward quickly, price was likely a real blocker. They were ready to buy, just not at that number.
If they still hesitate, ghost, or ask for more time, then price was never the issue - it was a lack of conviction. they were using price to buy time or to avoid saying "we don't see the value."

2. Ask the question you mentioned - "If price were not a factor, would you move forward this week?"
I've asked this at the tail end of demos for the last two years. The response splits your pipeline into two buckets:

A confident "yes" means you have a pricing conversation. you can negotiate or frame value differently.
A "well, we'd still need to get internal buy-in" or "we'd need to think about it more" means you never had them. price is the cover story.

3. look at your demo-to-close ratio after discounts.
If offering a 20% discount converts 80% of the stalled deals, you've got a pricing problem. if it converts 20%, you've got a value problem. i track this rigorously in our CRM with a custom field for "discount offered" and compare close rates and time-to-close. The data doesn't lie.

One more thing: check your churn data for customers who came in via heavy discounting. If they churn faster than full-price customers, that discount wasn't solving a pricing issue - it was masking a value gap. They never saw enough ROI to justify the original price, and the discount just delayed the inevitable.

so, to your original question: you know pricing is the real reason when changing the number changes the behaviour. if it doesn't, you were chasing a ghost

datanerd

that reframe of 'what price would you buy at right now' is a great forcing function. It instantly separates the tyre kickers from those who've already got a figure in mind. From running enterprise ABM campaigns, I've seen that price is almost never the real objection, it's just the easiest one to give without having to justify why the product doesn't fit.