My advice would be to know what a product is offering and align your requirements. You should have a clear vision of how you want to use a product and make sure that you are getting what you are looking for. Many times, the salespeople sell something, but the end client or the company doesn't get what they were looking for. So, first of all, the company needs to have a clear vision of the product and requirements. I've been working mostly with Pega throughout my career. I find it very good in terms of how easily a process can be developed around a customer's thinking. I've not seen any other tool that can be used in such a manner. So, from my perspective, as a developer, I would always recommend Pega, and I would always go for it. Overall, I would rate it a seven out of ten.
We are one of the largest Pega partners. They have a primary product: case management, clean automation, and customer engagement. Various customers will be in various versions of Pega, and we deal with all versions. If customers require an enterprise-wide implementation, they should be aware that there are requirements that are specific to the various lines of business. If they require such complexity to be addressed in a very specialized way, Pega can work well. I'd rate the solution nine out of ten.
Architect at a financial services firm with 10,001+ employees
Real User
Top 20
2022-08-15T16:47:05Z
Aug 15, 2022
Pega can be effective, but it is not trivial to get it set up, get it deployed, and get people to know it. That's not unlike some of the other big enterprise solutions. Even for Salesforce, as an example, you're going to need to staff appropriately. Pega isn't one of those solutions that you can basically put in an ecosystem and expect three or four people to roll out successfully. I just don't think that's the case. You're going to have a challenge finding people who already know it. When we were doing the RFQ, there were some other organizations we talked to, and they were very successful, but now, they had quite a large installation base. I know at one of the organizations when they installed Pega, and this was circa 2018, they had a lot of road bumps. They had to get Pega consultants in. Maybe they had SI in because I was indirectly working with it with consumer lending, and it was one of the many factors that they were late and over budget for delivery. That's the challenge with these big platforms. For a simple point-click solution, they can be quick to get going, but most organizations, especially banks, don't have something simple. You've to integrate with a bunch of APIs. You have to do testing, and you got to do the deployment, etc. So, you need to create a center of excellence, and I hate that term, at least to get started until you get some organizational-wide talent. In terms of maintenance, if you've got it on-premise, you're going to need two or three admins to work with your infrastructure team to stay on top, but it isn't something they're going to do full-time all the time. SaaS offering has a lot of advantages because it gets you out of that whole deployment perspective. To most companies, I would recommend seriously looking at the SaaS version and not getting involved with on-premise. I'd rate it a seven out of ten.
Technical Lead at a tech services company with 10,001+ employees
Real User
2020-06-08T06:11:07Z
Jun 8, 2020
We are planning to move our system to the cloud within the next six months, so this is something that we are preparing for. The suitability of this solution depends on the organization, but in general, I definitely recommend PegaRULES. When assessing the appropriateness of this product for a client, I would first study their requirements. I would rate this solution an eight out of ten.
PegaRules is a very powerful rule engine. It's a very powerful platform to build any sort of solution onto. Where a customer makes mistakes is when they underestimate the business expertise of a partner, so they really need to ensure that initial implementation is right. It is very important to understand who is implementing it on the ground. If they don't understand the business requirements and the required business outcome of management, it can be awkward, and not in line with expectations. The main thing I have realized is that understanding the business problem and understanding the required outcome for the customer is very important. One of the biggest business areas is to focus on understanding problems and the kind of business outcome the customer requires. It's really about understanding the big picture. I would rate this product a nine out of 10. There is always room for improvement, but I've seen many customers getting very good value out of this solution.
Principal Business Analyst at a tech services company with 201-500 employees
Real User
2020-03-25T07:03:00Z
Mar 25, 2020
My advice is to suggest people focus on the main purpose for the BPM platform. Are they really looking for a BPM platform, something that gathers all the business processes throughout the company, or is it just for reporting processes like a customer process and connecting it to some SAP processes or some CRM, or whatever. If you decide to use Pega as the main platform, then it's a really good choice. On the other hand, if you have a different software in your company like micro services or other big platforms like SAP, then you really should think carefully whether adding Pega as another large solid piece of software is really a good idea, or whether you can find other ways to integrate the other pieces of software for the purpose. I would rate this product an eight out of 10.
Team Leader at a tech services company with 10,001+ employees
Real User
2019-10-28T06:33:00Z
Oct 28, 2019
We're a Pega partner. I'd suggest those considering implementing the solution start small and maybe do a POC. That will give you a sense of what the solution would look like in production. I'd rate the solution eight out of ten,
PegaRULES Process Commander is the latest generation of Pegasystems' industry leading, rules-based business process management (BPM) solution and
provides a complete suite of BPM lifecycle tools to build, execute, simulate, and analyze business processes. Delivering a unique blend of process and practice rules, Process Commander provides a BPM lifecycle architecture that includes a patented enterprise business rules engine, process engine, simulation engine, and robust business activity...
Overall, I rate PegaRULES a nine out of ten.
This is one of the best solutions in its category. I rate PegaRULES a nine out of ten.
My advice would be to know what a product is offering and align your requirements. You should have a clear vision of how you want to use a product and make sure that you are getting what you are looking for. Many times, the salespeople sell something, but the end client or the company doesn't get what they were looking for. So, first of all, the company needs to have a clear vision of the product and requirements. I've been working mostly with Pega throughout my career. I find it very good in terms of how easily a process can be developed around a customer's thinking. I've not seen any other tool that can be used in such a manner. So, from my perspective, as a developer, I would always recommend Pega, and I would always go for it. Overall, I would rate it a seven out of ten.
We are one of the largest Pega partners. They have a primary product: case management, clean automation, and customer engagement. Various customers will be in various versions of Pega, and we deal with all versions. If customers require an enterprise-wide implementation, they should be aware that there are requirements that are specific to the various lines of business. If they require such complexity to be addressed in a very specialized way, Pega can work well. I'd rate the solution nine out of ten.
Pega can be effective, but it is not trivial to get it set up, get it deployed, and get people to know it. That's not unlike some of the other big enterprise solutions. Even for Salesforce, as an example, you're going to need to staff appropriately. Pega isn't one of those solutions that you can basically put in an ecosystem and expect three or four people to roll out successfully. I just don't think that's the case. You're going to have a challenge finding people who already know it. When we were doing the RFQ, there were some other organizations we talked to, and they were very successful, but now, they had quite a large installation base. I know at one of the organizations when they installed Pega, and this was circa 2018, they had a lot of road bumps. They had to get Pega consultants in. Maybe they had SI in because I was indirectly working with it with consumer lending, and it was one of the many factors that they were late and over budget for delivery. That's the challenge with these big platforms. For a simple point-click solution, they can be quick to get going, but most organizations, especially banks, don't have something simple. You've to integrate with a bunch of APIs. You have to do testing, and you got to do the deployment, etc. So, you need to create a center of excellence, and I hate that term, at least to get started until you get some organizational-wide talent. In terms of maintenance, if you've got it on-premise, you're going to need two or three admins to work with your infrastructure team to stay on top, but it isn't something they're going to do full-time all the time. SaaS offering has a lot of advantages because it gets you out of that whole deployment perspective. To most companies, I would recommend seriously looking at the SaaS version and not getting involved with on-premise. I'd rate it a seven out of ten.
I would rate PegaRULES an eight out of ten.
We are planning to move our system to the cloud within the next six months, so this is something that we are preparing for. The suitability of this solution depends on the organization, but in general, I definitely recommend PegaRULES. When assessing the appropriateness of this product for a client, I would first study their requirements. I would rate this solution an eight out of ten.
PegaRules is a very powerful rule engine. It's a very powerful platform to build any sort of solution onto. Where a customer makes mistakes is when they underestimate the business expertise of a partner, so they really need to ensure that initial implementation is right. It is very important to understand who is implementing it on the ground. If they don't understand the business requirements and the required business outcome of management, it can be awkward, and not in line with expectations. The main thing I have realized is that understanding the business problem and understanding the required outcome for the customer is very important. One of the biggest business areas is to focus on understanding problems and the kind of business outcome the customer requires. It's really about understanding the big picture. I would rate this product a nine out of 10. There is always room for improvement, but I've seen many customers getting very good value out of this solution.
My advice is to suggest people focus on the main purpose for the BPM platform. Are they really looking for a BPM platform, something that gathers all the business processes throughout the company, or is it just for reporting processes like a customer process and connecting it to some SAP processes or some CRM, or whatever. If you decide to use Pega as the main platform, then it's a really good choice. On the other hand, if you have a different software in your company like micro services or other big platforms like SAP, then you really should think carefully whether adding Pega as another large solid piece of software is really a good idea, or whether you can find other ways to integrate the other pieces of software for the purpose. I would rate this product an eight out of 10.
We're a Pega partner. I'd suggest those considering implementing the solution start small and maybe do a POC. That will give you a sense of what the solution would look like in production. I'd rate the solution eight out of ten,