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, or Enterprise Resource Planning, integrates essential business processes into one unified system. It provides the tools necessary for comprehensive management of core operations, improving efficiency and decision-making.ERP systems bring together various business functions under a central framework, facilitating seamless data flow and communication across departments. This harmonization allows for real-time visibility into business operations and strategic resource planning. Designed to...
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.