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.
ERP systems streamline various business processes by integrating data and functions into a unified system. This integration helps organizations improve efficiency, make informed decisions, and optimize resource management.Many ERP solutions offer tailored functionality to suit different industries, including manufacturing, retail, and healthcare. By centralizing data and automating processes, ERP systems reduce redundancy and facilitate scalability, serving as a single source of truth for...
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.