Everyone Tells You to Delay the Price Talk. Gong's Data Says Don't.
Conventional wisdom says hold off on pricing until you've built value. Gong's data on real sales calls found win rates run 10% higher when price gets discussed on the first call. Here's how to reconcile the two.
Every sales training I ever sat through said some version of the same thing: don't talk price too early. Build value first. Let them fall in love with the product, then tell them what it costs. I believed this for years, mostly because everyone else seemed to believe it too, which is a bad reason to believe anything.
Gong looked at what actually happens across real recorded sales calls and found win rates run about 10% higher when price gets discussed on the first call, not delayed. That's the opposite of the folklore, and once I sat with it, the reason isn't complicated: avoiding price doesn't make the prospect stop thinking about it. It just means they're thinking about it silently, with no information, while you talk about something else. A prospect doing that math alone tends to assume the worst number.
Why "it's too expensive" usually isn't actually about the number
None of this means you should lead a cold call with a price quote and nothing else. It means the objection, when it does come, is rarely about the number in isolation. When someone says price is the issue, it's almost always standing in for one of three things: they don't yet see the value clearly enough to justify the cost, they're not the person who owns the budget decision, or they're using "too expensive" as a polite way to end a call they've already decided to exit. Arguing the number before you know which of these is true is how a winnable conversation gets lost in the first thirty seconds.
What to actually do when it comes up
Acknowledge without conceding. "Totally fair to ask about cost" costs you nothing and keeps the conversation open, instead of putting you immediately on the defensive.
Ask what "expensive" is being measured against. "Expensive compared to what, the budget you had in mind, or another option you're weighing?" This single question surfaces which of the three real reasons is actually in play, and you cannot respond correctly to a category you haven't identified.
Reconnect to the specific cost they described earlier, not a generic value pitch. If they told you what the problem is costing them, that number is the one doing the actual work, not your pricing page.
Offer a low-commitment next step, not a discount. Discounting on the first objection doesn't just cost margin; it teaches a prospect that your price is negotiable before they've given you a reason to believe the product is worth the original number, and that lesson sticks for the entire relationship.
Why the timing point actually matters for how you open
If Gong's data is right that avoiding price hurts you rather than helps, the practical shift isn't "bring up price the second someone answers." It's "don't treat price as the thing you're protecting the call from." A rep who's visibly dodging the pricing question signals, without meaning to, that the number is something to be embarrassed about. A rep who states it plainly, once real cost-of-problem context exists, signals the opposite, that the number is simply what the value costs, not a weakness to manage around.
Why this is hard to learn from a framework alone
Reading this is easy. Delivering it smoothly, in real time, while a stranger is pushing back and the clock is running, is a different skill, and it only gets built through repetition. That's exactly the kind of moment live AI practice calls are built for: hitting the same price objection over and over, in a realistic voice conversation, until the response stops sounding rehearsed and starts sounding like something you actually believe.