Skip to content
Notifications
Clear all

My results after sharing our pricing data with the community

4 Posts
4 Users
0 Reactions
25 Views
(@devops_rookie_22)
Honorable Member
Joined: 7 months ago
Posts: 311
Topic starter   [#18184]

Hey everyone, I wanted to share a quick update since I posted here a few weeks ago asking for advice on our first Kubernetes monitoring tool quote. I was pretty lost on what was reasonable.

After sharing the anonymized numbers I got, the feedback here was a game-changer. Turns out our initial quote was about 40% higher than what others were paying for a similar scale. Armed with that, I went back to the vendor.

I managed to negotiate a much better deal that’s almost in line with the benchmarks you all shared. Just wanted to say a huge thank you! This community saved us a big chunk of our learning budget. 🙏 It’s amazing what sharing data can do.



   
Quote
(@amandap)
Estimable Member
Joined: 2 months ago
Posts: 173
 

That's really encouraging to hear. I'm new here and looking at CRM pricing for our team, and it's so hard to know what's fair.

So you just shared the anonymized quote you got, and people told you it was high? Did you have to show your user count or any other specifics, or was the price alone enough?



   
ReplyQuote
(@cloud_cost_analyst_pro)
Honorable Member
Joined: 6 months ago
Posts: 469
 

> amazing what sharing data can do

It is. That 40% is typical for first quotes when there's no price transparency. Good you caught it.

The next challenge is keeping those savings year-over-year. I've seen many get the initial discount, then get hit with 20-30% renewal increases because they didn't anchor the baseline. Get your negotiated rate in a master agreement, not just the initial quote.


cost per transaction is the only metric


   
ReplyQuote
(@alexh3)
Reputable Member
Joined: 2 months ago
Posts: 254
 

You've hit on the critical next step. The master agreement advice is correct, but its effectiveness hinges on the specific terms within it. The renewal increase cap is the most important clause, but it's often missing or vague.

A negotiated rate means nothing if the agreement defines pricing based on a "then-current price list." You need explicit language that sets the annual increase ceiling, typically tied to CPI or a fixed single-digit percentage. I've seen teams get a 30% year-one discount, only to have their renewal price jump to 120% of the standard list price because they only locked in the discount, not the pricing mechanism.

Beyond the cap, ensure the agreement defines what "scale" means. Is your per-unit cost tied to nodes, metrics, or users? If it's users, get the exact definition of an active user baked in. Ambiguity there is a common lever for inflation.


Data is the source of truth.


   
ReplyQuote