I agree completely that it's a signal. In my past work with marketing automation vendors, I've found that when a pricing model is truly defensible and competitive, they're usually proud to show it off. Hiding it does suggest they know something about the structure won't hold up to scrutiny.
Your point about the finance requirement is crucial. It feels like that policy exists to protect against exactly this kind of ambiguity. If you can't get a comparable document, you technically don't have a valid quote for the process.
But I'm curious about one thing: have you ever seen a situation where, after walking away from a vendor over this, they circled back later with transparent pricing? Or does that stance usually indicate a permanent company policy?
Yeah, the signal is so clear. I've never seen them come back with a transparent offer, honestly. It feels like a core company policy once they dig in on it.
That makes me wonder, when a salesperson says the pricing is confidential, is that usually their own call or a strict rule from their finance team? I've always assumed it was higher up, but maybe some reps use it as a default.
Good question. In my experience, the "pricing is confidential" line almost always comes from a sales enablement or legal playbook, not from the individual rep. It's a formal policy, usually tied to a strategy of extreme deal-by-deal customization.
That said, a junior rep might default to it without understanding the pushback it creates, while a more seasoned account exec might use it selectively as a power move in early talks. The key is their reaction when you challenge it. If they immediately escalate to their manager or legal to defend it, you know it's a company mandate. If they waver and say they'll "see what they can do," there might be some wiggle room, but the culture likely still permits the practice.
That's the exact budgeting challenge I've run into. A non-fixed rate creates a major forecasting gap. If you can't model future costs, you're essentially accepting a variable expense tied solely to the vendor's discretion.
In one case, we got a vendor to agree to a fixed per-unit rate for the initial tier, but they refused to lock in rates for higher volume tiers. That meant our projected costs for growth were just guesses. We had to build multiple budget scenarios, which made the proposal hard to justify internally.
The "price built just for our conversation" feeling is often accurate. It usually means the pricing model isn't standardized, so every renewal becomes a new negotiation with no baseline.
Measure twice, buy once.
You've perfectly described the problem with non-standardized pricing models. It doesn't just create a forecasting gap, it actively removes your ability to plan for success.
In a past evaluation of chatbot platforms, we encountered the exact same issue with tiered pricing. They offered a fixed rate for our current contact volume but explicitly stated that "future tier pricing is subject to change based on market conditions at the time of renewal." That's code for "we will charge you whatever we think we can get away with later." It turned the entire ROI calculation into fiction.
This is why I now insist on seeing the vendor's public or standard price book for at least the next two volume tiers. If that doesn't exist, you're not buying a product with a known cost structure, you're entering a perpetual negotiation. It makes the initial lower rate a trap, not a deal.
Support is a product, not a department.