Pega Platform Reviews

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.

We use the solution as a low-code development tool. The tool has pre-built rules. Hence, they can be reused and configured as per client requirements.

We can use the rules as per the class.

PegaRULES need to improve its JVM. It needs to enhance the operation speed and memory size.

I have been working with the solution for four years.

I would rate the tool's stability a nine out of ten.

I would rate PegaRULES' scalability a nine out of ten.

The tool's support will take time to resolve issues if it's a product enhancement issue. Application-related issues will be resolved immediately.

Positive

PegaRULES' setup is easy.

I would rate the product's pricing a six out of ten.

PegaRULES is mainly for enterprise companies and I would rate it a nine out of ten.

The company has a strategic partnership with Pega. I was the general sales manager. 

This is a customizable product. It's low code and can be restored quickly if needed. 

The solution is expensive and it put many of our customers off. After a while, the company was no longer prepared to work directly with customers which created problems. 

I recently stopped using this solution because I changed jobs but I had used it for 18 months. 

The product is stable. 

The technical support is very good. 

Positive

We helped our customers implement this solution because the company had its own in-house dedicated team. 

This product is quite expensive. 

This product is suitable for pretty much any size of organization. I rate this solution eight out of 10. 

The solution offers business process modeling when it comes to processing your models or maybe your workflows. 

Every company will have a process where it goes from case initiation to different stages based on the business need or business requirement. Pega helps get processes routed to different or next stages depending on the business rules and based on where it needs to be routed. 

Out of the box, Pega provides processes where the assignment will be picked based on some criteria or many other attributes. It's purely based on your business needs. It ensures the process is routed through the correct criteria from start to end and helps manage the entire flow, the process, and everything.

The solution offers many use cases. 

The case management is great. 

Pega provides a lot of advanced smart shapes wherein you can just create a case for using the smart case itself. You can integrate or maybe add any integration points you need there. 

A lot of Pega is out-of-the-box. You can use it as is or configure it in just one click.

The UI part needs improvement. 

Some integrations can make it unstable. They need to strengthen the integration aspect and make the process more seamless. 

It would be nice if Pega provided suggestions while users were on it. It already gives you some warnings, however, in relation to specific rules, it would be ideal if Pega could provide suggestions to help users make improvements here or there.

I've used the solution in almost every project I've worked on. 

We have hundreds of people using the solution in our company. 

The scalability is good in general. I would rate the ability to scale eight out of ten. 

Technical support has been good overall. 

Positive

I worked on a Vis ID tool and a BPM tool. It was for a short span of time. Pega was far better than that.

While it is not too complex to set up, you do need to understand the solution and know the rules. 

We have people in place just to set up the pipeline and everything. The Pega team has to work with the system team to set up everything and maybe one or two people are involved over there. From the core setup perspective, it's the role of a developer who has to do it. There's typically a lead and two or three developers that handle the setup and validate things once deployed. 

We did have some help from Pega during the initial implementation. Mostly, we handled the setup in-house. 

We have witnessed an ROI while using the solution. 

The pricing is quite good in general. I'd rate it nine out of ten in terms of affordability.

We've deployed the solution both on-premises and on the cloud.

It's a pretty good tool. If you're using it as an adjusted rules engine, Pega gives you the flexibility to integrate with different applications seamlessly. You can give the responses back as well. It has scalability. It makes it easy to maintain rules and you can delegate things seamlessly from Pega when you're doing that. 

I'd rate it nine out of ten 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. 

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.

Pega is an Intelligent Automation Platform that has evolved from a BPM perspective. This allows teams using this solution to address complexities without having deep knowledge in a specific development area.

One of the areas of this solution that could be improved would be to improve the low code features of the application itself. We would also like to use the same platform to build any application, even if it is not necessarily defined as a functionality needed by a BPM.

The RPA tool within this solution needs further enhancement to compete with other RPA tools in the market. They are focusing more on the overall platform rather than working on the RPA. Document AI tools could be an added functionality, for example. Alternatively, customers will need to purchase another RPA tool to complement the whole solution if they have very advanced RPA needs across their business.

I have used this solution for one year. 

This is a stable solution. 

This is a scalable solution. 

The technical support is good.

The initial setup was not that complex but also was not that simple.

We often recommend this solution to our customers. It is a wonderful solution. There are not many professionals working with this tool which is important to note.

If the core need of a customer is for BPM and automation, this is a suitable solution. If their needs exceed a BPM solution, such as modernizing different kinds of applications, there may be other suitable solutions. 

This is a good solution from a technical perspective and is based on a very reliable and scalable platform.

I would rate this solution a nine out of ten. 

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.