Skip to content
Notifications
Clear all

Hot take: you should always ask for a discount even if you have budget

5 Posts
5 Users
0 Reactions
0 Views
(@infra_auditor_nina)
Reputable Member
Joined: 5 months ago
Posts: 269
Topic starter   [#24180]

Let's start with a foundational truth: budgets are a fiction agreed upon by finance and procurement to make their lives easier. They have zero bearing on the actual market value of the service you're buying. I've seen teams pay a 40% premium because "it was in the budget" and they wanted a smooth renewal. That's not smooth; that's negligent.

As an auditor, my rule is simple: every quote is an opening bid. Treating it as a final price is leaving money—often a *lot* of money—on the table for no reason other than politeness. The vendor's entire sales structure is built around expecting you to ask. Their first number includes that buffer.

Here’s the bare minimum you should do, every single time, even if you're swimming in cash:
* **Always, always ask.** "What's the best you can do?" or "That's above our benchmark, can you sharpen it?" The silence after that question is worth thousands.
* **Benchmark against *something*.** Even if it's a public pricing page for a different service tier or a competitor's list price. You need a script. Example:
> "I see your list price for the Enterprise tier is $X/user. Our quoted $Y/user seems misaligned. We need to get to at least a 20% discount to proceed."
* **Use your audit leverage.** If you've had an incident or downtime attributed to their service, that's a discount lever. If their security questionnaire was a nightmare, that's a discount lever. Post-mortems aren't just for blame; they're for credit.

If you don't ask, you're subsidizing the discounts for the people who do. It's not about being cheap; it's about not being a mark. The money you save here is budget you can allocate to actual security or monitoring tools.

- Nina


- Nina


   
Quote
(@davek)
Estimable Member
Joined: 3 weeks ago
Posts: 129
 

Strongly agree, especially on the vendor's built-in buffer. I've seen the same dynamic in cloud and SaaS negotiations.

Your point about needing a benchmark is crucial, but the hard part is finding the right comps for non-commodity services, like an observability platform's enterprise tier. Public list prices are often meaningless. I've had more success anchoring against the vendor's own pricing for a different deployment model, like comparing their cloud-hosted per-GB rate to what they charge for a bring-your-own-cloud annual commit. It's internal data they can't easily dismiss.

The one caveat I'd add is that for very small, tactical purchases, the time spent negotiating can outweigh the savings. But for any contract that's recurring or over, say, $10k annually, not asking is just subsidizing their other customers' discounts.


CPU cycles matter


   
ReplyQuote
(@contrarian_kevin)
Reputable Member
Joined: 3 weeks ago
Posts: 228
 

That bit about internal pricing is exactly how they trap you. You think you're clever comparing their cloud rate to their BYOC rate, but you're just playing in their rigged sandbox. The real move is to skip their pricing models entirely and get a competing bid with a totally different structure, even if you don't want it. Use that as the anchor. Their "internal data" is designed to make you feel like you've won while still paying their margin.


Just saying.


   
ReplyQuote
(@ci_cd_plumber)
Reputable Member
Joined: 3 months ago
Posts: 273
 

Getting a competing bid is the right idea, but it's often impractical for niche tools. If you're buying a specific CI runner fleet or a particular monitoring SaaS, there might not be a true competitor with a different structure.

Your time isn't free. The effort to run a full procurement for a fake bid can burn more cash than you'd save on a mid-sized tool. The move is to use the threat of building it in-house. Tell them their pricing forces you to consider a custom solution, even if you'd never do it. That attacks their margin without needing another vendor's quote.


Build once, deploy everywhere


   
ReplyQuote
(@auditlog)
Reputable Member
Joined: 3 months ago
Posts: 214
 

I agree with the principle, but as someone who reviews these contracts and their attached audit trails later, I see a missing step. You said to benchmark against *something*, even a public price. My addition is that you must document that benchmark and the ask.

If you just verbally ask for a better price, there's no record. When I'm auditing for SOX or compliance, a vendor discount with no supporting rationale is a red flag. It can look like a kickback or a relationship discount that wasn't available to all bidders.

So when you ask "What's the best you can do?" follow up with an email that states, "Per our call, you agreed to a 15% discount to align with the competitor list price of $X we discussed. Please confirm and reflect this in the updated quote." That creates the audit trail that justifies the price change from the original budget. The paper trail is what turns a negotiation from a conversation into a defensible business decision.


Logs don't lie.


   
ReplyQuote