![](/static/253f0d9/assets/icons/icon-96x96.png)
![](https://fry.gs/pictrs/image/c6832070-8625-4688-b9e5-5d519541e092.png)
This company may be dogshit, but seat count is the standard licensing structure for most employee facing business software, including on-prem.
Most business software licensing/CRM tools requires that information to generate a quote, as price will be dependent upon several factors, including volume licensing tiers i.e. volume discounts.
Sometimes, licensing structures are simple enough that an employee or rep might be able to give you a quick ballpark without that information, but that would be the exception, not the rule.
And all of that is assuming that pricing is only based on seats, when there could be a whole lot of other variables that would be required even for their system just to generate single quote e.g. core count, support terms, etc.
To be clear, none of that means anyone should trust, or switch back to, elasticsearch. It’s just a minor peak into the mundane horrors of business software licensing.
Generally the elastic or usage/volumetric type billing structures are used on SaaS/cloud products, not on-prem.
Although it’s entirely possible that elasticsearch, and other vendors in the space use that pricing model for their on-prem customers.
Regardless, that’s even more of a reason why it would be very difficult to give a quote without being first having a presales meeting with a solution architect or knowledgeable rep.