[version_five]

I'll just ask, flag if this is out of place, I see lots of complaining about pricing - how many of those people are in a position where they would actually be buying this? Isn't it an enterprise product targeted to executive level buyers, and customized to the business? Just because some users or hands-on folks at smaller companies are angry they can't get a price doesn't mean there is a problem. It's probably a feature from a business perspective. Not every business model can just give a $x/user/month price.

[julienlafond]

I'm im position of buying this kind of product (CTO of 50eng), I could be interested by this kind of tool (we're alerting a lot through slack, and I'm searching a way to better track my incidents), but i'll never take 1 hour to "present my company" and "discuss a pricing" for a such "little" product.

For a product that costs tens of thousands of $ I understand, for a product that would cost hundreds, red flag, I don't have time for that. Incidentally, there is nothing worse than non-transparent prices, which can change dramatically every year

If AWS manages to have public pricing (with customers ranging at $100/m, $1000000/m), why not you?

[statictype]

Consider the possibility that the team hasn't yet figured out what the correct pricing model should be. Being able to talk to teams and understand how they use it and what they value in the product will help them shape a pricing model that works.

[synicalx]

> Isn't it an enterprise product targeted to executive level buyers, and customized to the business?

Maybe, and maybe not. Execs aren't or at least shouldn't be making these kinds of decisions in a vacuum, they should be asking their engineering/technical people for input. And in a lot of places stuff like this might be purchased at the business unit or even team level.

I work at a large enterprise (as in >100k employees) but our business unit/division's execs would consult with teams like mine before buying into a product like this, and for some tooling we may actually be tasked with investigating it and talking to sale creatures ourselves. For example we're looking for new ways to implement and manage SLO's that would shape development work for ~9k people, and even the junior engineers on our team attended meetings and demo's with multiple vendors related to this goal.