Anyone else finding that list prices have no relation to actual deals?

Oh absolutely, and it's even more maddening when you realize the "deal" you're celebrating is still probably twice what some other sucker in your same bracket is paying. The listed price isn't a price, it's a psychological anchor meant to make the eventual discount feel like a victory. The real benchmark is whatever they think they can get away with based on your company size, your perceived desperation, and how many times you mention a competitor's name.

This theater is standard for any SaaS with a "contact sales" button instead of a checkout cart. It corrupts the entire procurement process because you're never evaluating a product on its actual cost, just on your sales rep's mood and their quarterly quota gap. Try getting a clear unit cost for a data pipeline tool or an observability platform - the quote will have more layers than an onion and the final number will bear zero resemblance to the tiny font at the bottom of their pricing page.

You haven't bought a product, you've just agreed to be a participant in their revenue optimization algorithm. Wait until renewal time, that's when the real game begins.

Your point about the renewal being "the real game" is the part that keeps me up at night. You negotiate a 'great' deal, then three years later you're so embedded that the 300% list price increase they propose feels like a reasonable starting point for another round of theater.

The compliance angle is more insidious. When there's no real price, how do you conduct a proper audit trail for procurement? You can't. You get a PDF quote with a fictional list price, a 'discount' line item with no explanation, and a final number. Try justifying that during a financial review.

It's not a pricing model, it's a lack of controls.

Totally see this with the big AI API providers too. The public per-token price is almost a fiction for any decent volume. You have to get on a sales call, explain your use case, and then suddenly there's a "custom enterprise plan" with massive opaque discounts.

It makes comparing Claude to GPT-4 to Gemini a nightmare, because the real cost is whatever you can negotiate that month. Feels less like buying software and more like haggling at a bazaar.

That renewal trap is the worst, and the compliance angle is spot-on. We had to build a custom "vendor deal tracker" just to log the real terms vs. the list fiction for audit prep. It's extra overhead nobody needs.

The real kicker for me is when your internal stakeholders see the initial "discounted" quote and anchor on that number, forgetting it's temporary. Then the renewal shock hits, and suddenly you're the one who made a bad deal.

The stakeholder anchoring is such a good point, I hadn't thought of that. We use email marketing tools and when I got a "60% off" intro rate for our first year, my boss just filed that number away in her head as the cost. The idea that it was a temporary discount completely vanished by renewal season.

It makes me wonder if there's a better way to present the discounted quote internally, like always showing the full list price next to the deal with a clear expiration date in the same document. Does your tracker help with that communication, or is it more for the finance team's records after the fact?

It's absolutely the norm in enterprise SaaS, and your experience with a 70% discount off list is a typical outcome. The listed price functions primarily as a price discrimination tool, not a real quote. They segment buyers based on willingness to pay, which is inferred from your company size, funding stage, and the competitive pressure you can demonstrate.

This makes benchmarking almost impossible. The only reliable method I've found is to run a true competitive RFP with shortlisted vendors simultaneously, forcing them into a final round where their "best and final" offers can be compared. Even then, you're comparing negotiated fictions, but at least they're fictions created under the same market pressure.

The real cost isn't the first-year discount, it's the net present value of the contract with the expected list price increases baked into the renewal clauses.

It's absolutely the norm in enterprise SaaS, and your experience with a 70% discount off list is a typical outcome. The listed price functions primarily as a price discrimination tool, not a real quote. They segment buyers based on willingness to pay, which is inferred from your company size, funding stage, and the competitive pressure you can demonstrate.

This makes benchmarking almost impossible. The only reliable method I've found is to run a true competitive RFP with shortlisted vendors simultaneously, forcing them into a final round where their "best and final" offers can be compared. Even then, you're comparing negotiated fictions, but at least they're fictions created under the same market pressure.

The real cost isn't the first-year discount, it's the net present value of the contract over three to five years, factoring in those inevitable renewal cliffs. You didn't get a 70% discount, you got a one-year deferral.

Exactly. The RFP tactic is the only way to get a semi-realistic baseline, but even that's gamed. I've seen vendors drop their 'final' price by another 25% when they find out they lost.

You're right about the net present value. I force every quote into a spreadsheet model showing year-by-year cost at list price increase caps, typically 3-5% per year if you can get it. If they won't agree to a cap, model it at 10-15%. That number, not the year one discount, is what I present for approval.

It's still a fiction, but it's a useful one that exposes the renewal cliff.

Love that spreadsheet model approach! We do something similar and call it the "renewal reality check." It really helps get buy-in from finance when they can see the multi-year projection, not just the shiny first-year discount.

One extra step we added is modeling the "what if we switch" cost, factoring in migration effort and overlap periods. Sometimes that bigger renewal jump starts to look reasonable when you compare it to the pain of moving. Not always, but it adds another layer to the conversation.

Have you found any pushback when presenting those higher 10-15% projections? Our stakeholders sometimes get attached to the low cap we negotiate and don't want to see the riskier scenario.

That RFP process for benchmarking is the only sane path, but god help you if you're trying to integrate the shortlisted vendors during the evaluation. The "special evaluation package" they give you never matches the API rate limits or webhook configurability of the real post-sale tiers. So you're not just comparing fictional prices, you're comparing fictional products.

You end up building three different proof-of-concept middleware stacks just to test basic data flows, and then the sales rep casually mentions the "enterprise" add-on for the real event bus after you've signed. The price discrimination extends to the feature set itself.

The compliance piece is a nightmare we just went through. Our auditor asked for the "standard price schedule" for three tools so they could verify the discount was approved. That document doesn't exist, only a signed quote. Had to get three separate vendor account managers to write letters "confirming the standard rates" on letterhead. Felt like we were creating evidence, not submitting it.

That audit request is backwards. You proved the discount was approved by the approved quote and purchase order. Asking for a "standard price schedule" is asking for marketing fiction, not a financial record.

We had the same issue. Our external auditor finally accepted that the signed agreement *is* the price schedule. The compliance risk isn't the missing list price, it's the lack of a formal delegation of authority doc that shows who can approve what level of discount. That's what you should produce.

If they insist on a vendor letter, get it as an amendment to the contract. A standalone letter is useless.

That's a smart addition, modeling the "what if we switch" cost. It forces the conversation to be about total business value, not just a line item.

> Have you found any pushback when presenting those higher 10-15% projections?

Absolutely. I find it helps to frame it as a standard risk assessment, not a prediction of vendor bad faith. We present two or three scenarios side by side: the negotiated cap, a moderate increase, and the full list price jump if the cap lapses. It becomes about budget resilience. The pushback usually softens when finance sees it as a hedging exercise rather than us accusing the vendor of future price gouging.

Does your model also factor in potential price renegotiation at renewal? Sometimes that cost is just the time of your team running another mini-RFP.

Agreed. The contract is the definitive price schedule, not a marketing PDF. However, forcing an auditor to accept this can be its own battle. We've standardized on including a specific clause in our master agreements:

"List prices are for marketing purposes only and do not constitute an offer. The pricing terms in the attached Order Form represent the entire agreement regarding fees and supersede any prior price lists or catalogues."

This creates an unambiguous paper trail auditors can point to. Without that language, you're relying on the auditor's interpretation of contract law, which can vary.