I would rate the product pricing seven. The licensing costs were reasonable, with the last amount being around $17,000 annually for 80 users, equating to about $200 per user per year.
If the value proposition is clear for the customer, they won't see it as an expensive solution. A solution becomes expensive when it doesn't do what it promises. I generally don't blame the products for that, but the people who do the business and data architecture. So, the business architecture can become complicated. If a product can't accommodate that complexity, the customer will feel it's not good. But then, another product might not work either because your complicated business process might not be well-suited to it. So, you need to know the limits of all products and the ecosystem. With a good enterprise architect, you shouldn't fall into this complexity trap. It still happens, though, maybe because the business decides on a specific route, and IT isn't involved or lacks knowledge. There's inherent complexity in any ecosystem, for sure.
Enterprise Resource Planning (ERP) is the cohesive management of various central business practices engaged in a myriad of data management categories, such as finance, product and production planning, marketing and sales, manufacturing and materials and inventory management. A company depends on its data through IT and DevOps who are tasked with vital IT capital expenditure investments. IT key opinion leaders rely on ERPs to collect, store and interpret business data. Of course, security is...
I would rate the product pricing seven. The licensing costs were reasonable, with the last amount being around $17,000 annually for 80 users, equating to about $200 per user per year.
If the value proposition is clear for the customer, they won't see it as an expensive solution. A solution becomes expensive when it doesn't do what it promises. I generally don't blame the products for that, but the people who do the business and data architecture. So, the business architecture can become complicated. If a product can't accommodate that complexity, the customer will feel it's not good. But then, another product might not work either because your complicated business process might not be well-suited to it. So, you need to know the limits of all products and the ecosystem. With a good enterprise architect, you shouldn't fall into this complexity trap. It still happens, though, maybe because the business decides on a specific route, and IT isn't involved or lacks knowledge. There's inherent complexity in any ecosystem, for sure.