Pega BPM Reviews

If you search on Google, basically you will see a lot of use cases that you can implement. Wherever you have a kind of automation, a case management, a kind of logic, a kind of an exhaustive process flow where a particular task will flow from one group to another. In all those situations, Pega can be a very good fit. Nowadays, Pega provides machine learning, automation intelligence, DevOps, et cetera. Whatever is as per market standard, those are there in Pega.

Pega has lots of industry solutions as well which are targeted for specific industries such as financial, healthcare, or insurance. The product helps you to build faster. 

Pega is a niche product and any workflow management kind of use case, or maybe automation kind of use case can be implemented using Pega. The only thing that you need, is the right skillset. Pega is a very customizable product. You need to know the product very well to implement it to a proper standard. 

Pega has been on the market for quite a long time. I'm working with Pega for the last 15 years and they always have a lot of new features.

The way it is adapting to new changes is quite useful. The way it is changing itself to survive in the industry with other BPM tools and being competitive every time. 

With Pega you can deliver some things pretty quickly. You can deliver a prototype for what Pega calls a Minimum Viable Product or Minimum Lovable Project, MLP, very, very fast. 

The solution is stable.

You can scale the solution if you size it right at the outset.

It's very customizable.

You can use it for many industries.

There are lots of very useful features. They're constantly adding more items to the product.

There are lots of great automation and machine learning aspects.

The initial setup can take a while. You need to have the right people in place to handle it effectively. 

It can be pretty expensive and is better for larger enterprises. 

I've been working with Pega probably for the last 15 years.

It's a stable solution. 

The scalability is pretty good. Whenever we work in Pega, we propose this product to any customer based on their needs, how many tech resources they have, how many concurrent resources there will be, what their daily inbound volume is, et cetera. Based on that, we get the hardware sizing from Pega. If you do the right kind of estimation and start with the proper infrastructure, you will be able to basically ensure robustness, high availability, almost zero downtime, and everything can be shipped. 

Pega tech support is there technically and they do help us a lot. In the recent past, we have seen a little bit of trouble here and there, where tech support is taking a long time to fix some issues. Usually, if we route Pega with proper channels, then we can manage good support. 

They have a good tech support process and they also provide a good academy resource. Someone new to Pega can get a lot of documentation and material to learn the product.

I am from a Pega background and I do not know much about other competitive products in the market, so my feedback or whatever I'm giving, that is maybe a bit biased as I have been working with Pega only.

The initial setup takes time. You have to gather people with the right skills. If you have that then it won't take that much time at all. Basically, the main selling point of Pega is it can reduce your entire timeline drastically. The constraint is you need to have the right kind of people. 

Pega is a huge tool, and honestly speaking, nowadays, there are a lot of sections in Pega where there is no single user who knows the entire feature set. It's a big and complicated product. You need to have the right blend of team members to set up, to have an easy initial setup. In those instances, it might take six to eight weeks. After that, I have seen people delivering some base prototypes and a walking model in a few weeks.

We help our clients set up the solution.

Nowadays, standard open affairs configuration is there. If you ask me how much time it'll take to build it, it's maybe a few hours or maybe two to three days. When we talk about the entire project, we need to take care of a lot of things, not just the build part. Usually, there are integrations necessary and we have to have a lot of testing in place to manage different combinations, load testing, performance testing, and security testing. Most of the time clients ask for all these things. That adds to the setup timeline, however, the build is not included in that constantly changing time.

This is something every enterprise has to handle separately with Pega. As a vendor, we are not supposed to comment on pricing.

We use both cloud and on-premises deployments. In earlier days, Pega used to support only on-premises. Nowadays, it's supporting the cloud as well.

I definitely do recommend the product. Pega is a competitive product if it's not a small enterprise. Small companies usually avoid this product as there are a lot of open source products that are less costly there in the market. 

Based on the features I can recommend it. 

I'd rate the solution nine out of ten.

There is a feature to accelerate the development so that business analysts can directly create their user stories and assign the task to the developers. It's called DCO.

Pega is claiming they're into low code but as per Gartner Magic Quadrant, Pega is not there now. Appian, OutSystems, Mendix, Salesforce, and Microsoft Power Platform are the major leaders in the market as low-code platforms as per Gartner Magic Quadrant. Pega has to improve if they would like to gain their position in the low-code space. They would have to improve major functionalities that these low-code vendors and low-code platforms have like their mobile compatibility. A citizen developer can easily make B2C mobile apps.

Pega has to come up with a lot of improvements in these low-code areas for the citizen developers who can easily create mobile apps with minimal coding or no coding. With other competitors like Appian, OutSystems, and Mendix, you can do it using visual modeling.

The price could also be improved.

I have been working with Pega for about six years as a solution architect.

Pega is a stable product. If you're solving a business problem for case management, Pega is the best for case management solution, but the product architecture is entirely different. It's rule based. It's not popular for UI or UX management.

Pega's technical support is not as friendly as Appian. 

I would rate Appian higher than Pega. The price of Pega is a bit higher than Appian and the software isn't as friendly.

The price could be lower.

I would rate this solution 8 out of 10.

We have two different projects right now using Pega BPM. In one we are doing a migration of applications regarding claims, and the process requires orchestration between different providers that this company needs to organize the work. When you have a claim and you need a repair for something, we need to organize the work that we send to the provider. One, for example, is doing water claims. Another one could be about car claims. These are our main processes right now for Pega BPM. 

The other project is regarding onboarding customers in a bank. We use Pega to orchestrate the different aspects we need to complete the onboarding for our customer.

One project is on-premise and another one is on cloud, but we started using the Pega cloud and right now we are migrating to Azure Cloud,

Yes it has improved the KPIs. For example, in the insurance project, the time required to complete the project with Appian was around a month and now with Pega it is around two weeks. We still have a lot that is manual, but we reduced the time of the process.

The best part of Pega, for me, is that they let you reuse a lot of the aspects in the product.

The main problem with Pega is that it is quite complex, so it is very difficult for the developer to learn. Sometimes it is like a black box where you can't develop other things. When you try to modify something on the product it is quite difficult. Also, when new people try to learn how to develop in Pega, it is quite difficult to learn, and it's a big product. I think that is the problem.

Maybe they could try to make an easier implementation. I don't know how. Maybe with more information on the Pega platform, in the Pega academy, or modifying the application to make it easier to implement. 

I started using Pega BPM 11 years ago.

Pega BPM is stable.

Pega BPM is more scalable than Appian. We can have more processes running, more data in the server, and the performance is better.

Both of our projects are in production right now, but in one of them the customer will require around 3,000 users. With the other project it will be around 300 people.

Right now, there are two or three people running this kind of project, so we will need more people for that.

The plan for Pega in both projects is to continue for around five years more - so we have a lot of work there.

We don't have too many problems. It's true that we have more ticket service requests with Pega, but they answer quickly, so I think that is good.

In one of our projects, we previously used an application called .NET by Microsoft and the solution was so slow. Well, I think it was created 20 years ago so the modification on that application was too slow because the code is much longer and you have to read more lines of code so it was not easy to modify the processes on that application. It was for that reason that we tended towards Pega, looking for more agility on the modifications and giving control to the business people to modify different business rules for themselves.

The initial setup is complex.

When you are doing a project in Pega, it is more complex than the processes that you are normally going to implement. When the product is complex to learn it's more complex to develop.

The deployment time is not too much. It is about the same as with Appian when you have the configuration down, no more than one or two hours.

Normally when we use Pega we are thinking about a more global application that you can use in different countries or for different areas.

It requires a Pega architect from the company.

The pricing with Pega BPM is a huge problem because it is quite expensive for the Spanish customers. It is higher than other BPMs.

My advice to anyone considering Pega BPM is that they have to think about that they want to do on it because not everything is possible. It is similar to Appian, so really think what you want do you in Pega. If you are thinking about moving an application towards innovation on Pega, it's not a big solution to do it. If you're thinking about something more, it's a good product. Don't spend money on that because Pega is more expensive than other products.

The main lessons regarding Pega are that you need people who know how to use it because it is a complex product. If you create the application from the beginning, you are going to need a lead system architect to do it, because if you don't do it correctly, the use and the good points that Pega has could be an issue for you. The main point here is that you need people who know Pega really well in your team.

As a product I have to say that I think Pega BPM is the best right now, and the only problem that we have with Pega is the people. So if I focus only on the product, on a scale of one to ten, I have to say Pega is a nine.

The product is so good. The only problem is that the people who work on it need more knowledge.

I help clients do digital transformations, so I've been consulting with CIOs, C-level executives, to implement solutions around Pega BPM. One example is for a commercial insurance company, it is a quoting system for their brokers. For a retail management company, it could be something like their human resources onboarding system.

It cuts down the time taken for coding. Earlier it used take for us four hours to do a particular code. Now this can be done in less than 30 minutes. That's the kind of productivity gains you can get.

I think it is the user interface and the ease of developing the workflow for an application. It has a lot of gadgets to just plug and play, and that cuts down your development time quite a bit.

The biggest thing I have seen is when going from one version to another and upgrading to the latest version, it takes a pretty long time for an organization to go through an upgrade process. I think that's an area where they can make it a little smoother.

Also they need to come up with licensing options. Right now they do have a cloud-based option, but the cloud prices I've seen are much more expensive compared to competing products.

Yes, we did in the sense there have been some performance scalability issues. Suppose you want to add more users. You go from, say, 800 users to 1,500 users, and sometimes that creates issues for which there is no clear explanation. To fix it you have to escalate it with customer service and sometimes the response is not up to the mark in resolving those issues.

It is scalable, but it also interacts with a lot of other systems. I think they thought that the interface to other systems, legacy systems, was its strength, but when problems do occur, quickly diagnosing those problems has been a challenge.

On a scale of one to 10 I would give them a seven. They're fairly knowledgeable and if they've seen a problem somewhere else, they have a knowledge base and they send out solutions. But if they haven't encountered a problem, if it's unique for a particular customer's situation, sometimes it's very hard for them to provide a solution. They say, "Hey, we will take care of this in our next version upgrade." For that you have to wait for a long time.

I was working with various other products like Savvion BPM and IBM VPN. Because some of the customer situations, we switched them from those applications to Pega, and I think customers have been happy with it.

There are two options. If you are doing on-premise, it's a little complicated because you need an admin-type person who can help with the installation. But if it is cloud-based, then it is easy. It's all done in the Pega cloud and you just have to get the user ID and password and you are in business.

It depends on which option the customer goes for. It is definitely complicated if it's on-premise.

They have both on-premise and cloud licensing. If you are a small to medium company, go for the cloud option because that eliminates a lot of the setting up of your DevTest and performance environments, multiple environments, because you can buy that from Pega with the cloud option. So your setup time really goes down.

If you're a large company, then you're better off putting it within your company. You have other skill resources within your company to create environments. Large companies have an option of either going for cloud or for on-premise.

We evaluated IBM BPM and Appian.

You really need to know how you are going to use this product. Is it for customer service? Is it for marketing? Is it for robotic automation? Is it for other things? You also need to work with your business partners to clearly define the processes a user goes through to achieve the desired end result. So you have to do some "pre-work" before you buy this product or before you install this product. Licenses are expensive. You cannot start the process after you buy because then you are wasting the license dollars. If you are using this product for business process management be aware that organizations a long time to make changes to those processes. You have to initiate those changes early so that you can take full advantage of this product.

I rate it nine out of 10 overall. I feel that they should consider making the licensing more flexible and more economical. The second issue is upgrades. They have to work on them to make them smoother.

I am the Head of Digital Transformation at my organization. Currently, I am implementing Pega for my customers. All of our customers want payment and collection solutions implemented.

We have multiple projects that have many use cases for Pega. For example, one client is in the insurance industry that uses insurance data. Another customer is in banking where we implemented a customer service system.

Pega can implement an automation system that catches incoming emails and can automatically triage and route them. 

Pega BPM has a full suite for any enterprise. It is a process orchestration platform. It has detailed features for case management and workflows. 

I value Pega's decision control, which can take care of your next transaction with all the decisions taken care of. 

The solution also has very strong customer service where all your issues will be taken care of across multiple channels like calls, email, and chat. It has a really powerful UI. It is a single platform for customer service automation for any enterprise.

I would like to see Pega BPM improve the user experience. The platform has a lot of restrictions. 

I have been using Pega BPM for 18 years.

Pega BPM is stable compared to other solutions on the market, even for high usage.

The solution is scalable. There are constraints when it comes to the terms of design and when you want to expand. When considering infrastructure scalability, there is nothing to worry about, it is scalable.

If you choose Pega BPM on the cloud, the initial setup will take care of the infrastructure. You will need to spend some time to identify the suitable infrastructure. Even after implementation, there is a certain amount of upfront work required in terms of design and foundation. Once this is complete, everything else is smooth. 

Deployment can take a few days to get on board with your foundation as it is very tedious.

Licensing varies across geographical regions for us. 

I would recommend this solution to anyone considering implementing Pega BPM. It is a scalable, reliable platform that is suitable for many kinds of organizations. 

I would rate this solution a nine out of 10 overall.

When our clients automate the KYC and onboarding processes, they can reduce their manual force and then deploy them in much better tasks rather than the mundane activities of selecting forms and gathering information.

There is definitely an advantage to digitization, so we recommend Pega to our clients for the KYC digitization. Pega's strength is in KYC onboarding.

The workflow automation can be slow, so there is room for improvement there.

Personally, I have been using the solution for the past three years, but my company has been using it for about seven or eight years. 

The solution is stable.

The solution is quite scalable. 

The customer service team is very responsive and helpful. We haven't had any complaints or issues with them. I would rate the customer service as a nine out of ten.

Positive

The initial setup was easy. On a scale of one to five, I would give it a four. 

The deployment was handled by Pega and was quite easy, not very complex, and the customer was satisfied. 

The pricing is a bit on the high side, but you're paying for a quality product.

I would recommend that you work with one or two Pega developers in the initial stage. After that, it's quite straightforward.

I would rate this solution as a nine out of ten. The Pega product is definitely good. 

I use the product for process orchestration purposes.

There are a lot of frameworks in the product. I use Pega PRPC the most.

There are no job opportunities for users who have expertise in Pega. They are learning the certification program but need work. Pega should work on redefining their model and creating a demand for their skills. They need to reach a large number of business organizations.

I have been using Pega BPM for five years.

I rate the platform's stability a seven out of ten.

We have more than 500 Pega BPM users in our organization. We plan to increase the usage.

The initial setup process is straightforward.

We do not have to purchase any licenses for the product.

I recommend Pega BPM to others and rate it an eight out of ten.

Our use case of this solution is for clinical case management. I'm the senior vice president of the company and we are customers and end users of Pega BPM. 

The solution has assisted us by automating our workflow. It supports the process management of medication therapy engagements with patients. 

We appreciate that this solution supports the size and scale that we need.

This is a very expensive product and there is a lack of availability of the Pega skill sets, the resources. 

I've been using this solution for 10 years. 

The solution is stable. 

The solution is scalable, we have around 1,000 users and don't have any plans to increase that number. 

We deployed ourselves and I don't recall any issues. The solution is not maintenance heavy and we have a few people responsible for upkeep. 

Licensing costs are very high. 

It's important to check all options and ascertain that this is the appropriate solution for you. There are other features that products like Camunda provide,   but as you need to scale and get more sophisticated in your process management, Pega becomes a better option.

I rate this solution eight out of 10.