Across our recent calls into finance and AI-heavy accounts, we heard two kinds of no. On a dialer they sound almost identical. They aren’t, and they call for opposite responses.
A cost objection is a no to the current bill. A policy objection is a no to the whole category. If you treat them the same, you either give up on a buyer who would have listened or keep pitching at a wall.
The clearest cost case came from a finance technology director who told us their AWS Bedrock setup was sufficient. We didn’t argue. We asked how spend was split across models and which requests could move to a cheaper route without anyone noticing. Once the conversation shifted to cost optimization and smart routing, they agreed to a 20-minute intro. The product didn’t change between those two moments. The question did.
A similar pattern showed up at an IT services firm with 12,000 to 14,000 developers. Their VP of software engineering and AI already ran an internal platform for routing, cost tracking, and governance. He was skeptical that we’d add much on top. He still agreed to review a comparison against hyperscaler tooling, and he declined a meeting the following week. That isn’t a dead lead. It’s a buyer who wants evidence before a conversation, so we send the document and let him come back on his terms. The 755-second call was enough to find that out.
Policy blockers sounded different. In two other financial-services calls, one owner opposed AI outright over privacy and cybersecurity. Another prospect said company policy barred them from discussing internal infrastructure at all. Neither objection was about price, routing logic, or proof points. No discovery question changes a rule someone else wrote.
So we now run a simple test in the first two minutes of every call. Does the prospect answer with a number, a tool name, or a current cost? Keep going. That’s a cost objection, and it opens the door.
Does the prospect answer with a rule, a risk, or “we’re not allowed to talk about that”? Exit. Thank them, ask who owns the decision, and stop selling.
Log the exact phrase they used in the CRM so the next rep doesn’t dial into the same wall.
The payoff is time. A rep who spots a policy block early moves to the next account. A rep who spots a cost wedge early spends the saved minutes on the one question that earns the 20-minute intro.