Pega Platform Reviews

Our use case for Pega BPM is BFS process management. Earlier, we were facing some challenges such as using the end numbers of applications, but now we are careful. Decision-making took too much time in the past, but now that can be done within a few hours or a few days. For example, when managing a claim, that used to take almost five days to a week. Now, that would only take two to three hours in terms of resolving issues. The processes are much faster now in Pega BPM, in particular, almost ten times faster.

The most important features of Pega BPM are case management and claims management, and soon they'll also be offering claims processing.

I also love Pega BPM in terms of performance. It's also one of the very few user-friendly solutions in the market. It may take some time to learn Pega BPM, but once you get a proper handle on it, tracking and managing processes become very easy anytime, anywhere.

Pega BPM also has very good documentation you can use to learn the solution. Pega has a community portal that has complete information and explanations, and if you're facing a challenge, you can post your challenge on the community portal and get a resolution at the same time.

Currently, there isn't any feature I want to be added in the next release of Pega BPM because Pega always adds new features that my team welcomes and looks forward to learning.

One area for improvement in the solution is the long learning curve, but after that, you'll find Pega BPM easy to use.

I've been using Pega BPM for almost four years now.

Pega BPM is a stable solution.

Pega BPM is a solution that's easy to scale.

I haven't contacted the Pega BPM technical support team yet, but when an issue arises, and I would need to contact the team, hopefully, there would be a good response and availability from them.

Pega BPM is my first BPM solution, so I have no experience with other similar solutions.

Setting up Pega BPM was very easy for the team. Deploying the solution is so much faster and takes up a lesser amount of time than other solutions. For example, if a competitor takes a month to completely deploy, Pega BPM deployment will be completed within two weeks, or almost half a month.

I would rate the setup for Pega BPM four out of five.

We implemented Pega BPM in-house through our BPM team.

In terms of the pricing for Pega BPM, other solutions may be cheaper, but it doesn't matter if Pega BPM has a higher price tag because what's important is that it's the best solution, and that is what people look for.

If I would rate the pricing for the solution, I'd give it three out of five.

You have to pay extra for additional features in Pega BPM.

The business process management solution my team uses is Pega BPM, particularly the older version 7. My team is planning to onboard the new version of the solution, version 8, soon.

Maintaining Pega BPM is sometimes expensive, but it's manageable. It takes money to maintain the solution, but it's a good product based on the service it provides to customers. Pricing doesn't matter because what matters to any client is that the solution should be very good and should provide accurate results. This is the main reason people go with Pega BPM.

My company has a team dedicated to maintaining the solution.

Five to six people currently use Pega BPM within the company.

For now, I don't have any suggestions for people looking into implementing Pega BPM because for sure those people have research teams that do the research and implement the solution according to market research. They know exactly what type of solution is needed based on research.

I would recommend Pega BPM to new users of BPM solutions or local platforms, but research is still required before implementing the solution.

My rating for Pega BPM is nine out of ten.

My company is a partner of Pega BPM with clients it provides services to. My company also provides implementation support to clients.

This solution is useful for business process management if you have any banking solutions or need to manage a process. Maybe a very simple example could be a loan approval process where you need to upload your documents and have them be verified by users. In other words, you have a methodical process in place that encompasses reviews. It can be anything, it might be an order that you have placed on Amazon which needs to go through another. Anything that involves a methodical process is a good fit for Pega as a product.

What I found the most valuable is the case management and the UI design capabilities. We have the ability to do any kind of integration on Pega, which is really beneficial. 

I think there is room for improvement in the low code/ no code environment that they're promoting now. That needs to be aligned a little bit more. I still feel that it is not that friendly for a person who has no experience with Pega to just go in and try to create something. It is a little bit difficult to comprehend, which can be a challenge for the developers who manage the solution because they will have a hard time getting people to use it. For example, if several business users start developing an application at the same time, bottlenecks can happen and the developer will have to go in and kill the conflict in the rules that they have created. That could be better streamlined, which means there is room for improvement there.

I have been using this solution since 2010.

I would rate the stability of this solution a nine, on a scale from one to 10, with one being the worst and 10 being the best.

I would rate the scalability of this solution a seven, on a scale from one to 10, with one being the worst and 10 being the best.

I would rate their support a five, on a scale from one to 10, with one being the worst and 10 being the best. There are lags in their responses.

Neutral

My impression is that the initial setup process has to be followed via documentation. It's becoming a little bit less complicated, but it is still not easy for an inexperienced user to kickstart and deploy. The deployment an hour and a half at most. It can be deployed by one person. 

I would rate this process a six, on a scale from one to 10, with one being the worst and 10 being the best.

The pricing is a bit costly. Although it is a little bit costlier than all other tools on the market, it is more consistent. It also shortens the time to go live by quite a bit.

As far as maintaining this solution goes, how extensive it is will depend on whether or not you will be maintaining just Pega. It allows you to delegate many of the business rules to business users where they themselves can actually go and configure their rules and modify them. A user can have their own dedicated set of rules that they can go and configure. 

Overall, I would rate this solution an eight, on a scale from one to 10, with one being the worst and 10 being the best.

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 are using Pega BPM for all the major domains, insurance, banking, FMCG, and telecom.

The most valuable features of Pega BPM are low code, no code, functionality, and easy development.

Pega BPM can improve product management, case management, omnichannel, CDH, and the customer data hub. All the major domains can improve. Additionally, more AI functionality and proper integrations with Pega RPA would be helpful.

I have been using Pega BPM for approximately four years.

I rate the stability of Pega BPM a nine out of ten.

We have approximately 2,000 users using this solution.

I rate the scalability of Pega BPM a nine out of ten.

I have contacted the support from Pega BPM.

I rate Pega BPM an eight out of ten.

Positive

I have previously used OutSystems.

Both OutSystems and Pega BPM are Java-based applications with similar implementation methods. However, Pega BPM has a more integrated digital transformation solution and includes tools for RPA, while OutSystems does not have a specific focus on RPA. Pega BPM has more solutions geared toward digital transformations.

The initial setup of Pega BPM can be complex if the implementer does not have Java knowledge.

The price of Pega BPM is in the middle range compared to other solutions.

I rate the price of Pega BPM a five out of ten.

We have 30 people for the maintenance of the solution.

I rate Pega BPM n eight out of ten.

It is just for business rules. An example would be that you want to apply for a credit card limit, and if the credit limit amount is less than a certain value, we won't necessarily do a real-time check. We do basically auto adjudication. So, the rules can be used as part of the flow.

They're pretty easy to create, and they're pretty easy to deploy. 

In theory, business rules tend to be something that business users can use. What I mean by that is that I don't know whether it always works out that well because the problem in banking specifically is that you need auditing and you need some kind of control. So, even if you're doing rules, there has to be an approval process. You can do all that in Pega, but it is not exactly everything that the vendor says it is. I've spent some hands-on time with the platform, and you can do those things, and it is all low code, but is it as easy as they make it sound? No. That's my two cents. For example, if I want to do something, there is no way to switch from low code. I just want to do a simple If-Then-Else rule, but I have to go through their low-code tool and do dragging and dropping. I'm a development person, and in my opinion, even some business users could do this easier. There is no way to go back and forth to an editor where I can just type in an If-Then-Else rule, which would be much faster than drawing in their low-code editor. They don't support that. They lead you too much. It depends on your level of expertise, but in some cases, it is just not that easy to use.

I don't like their whole deployment pipeline. It is very closed in nature. You have to use their pipeline to push things out to production. It is a turnkey solution, and I'm not a big fan of that. That was one of the things that we liked better about Salesforce. With Salesforce, we could use our own deployment tools or we could use a third-party deployment tool. Pega is a pretty closed system. It is closed in the sense that the deployment pipeline and some of the things that you do go through their tool. They don't integrate with GitHub, Azure DevOps, and so forth, which are really effective for versioning. I just don't like that.

It works, and it is effective.

At a previous organization, there were a couple of thousand users executing PegaRULES, and there were 30 to 50 users creating and modifying rules.

They're decent. A big organization or a big bank is going to want to pay for the premium tech support. If you don't, then you got to be willing to wait. They're no different than any other enterprise solution. Their support, as an example, is better than MuleSoft because we had rather big challenges with MuleSoft support, but Pega was better.

We also have an IBM rules management solution, and we also have Appian, but the situation is that we're having challenges getting the productivity out of them.

I've also used FICO Blaze rules, but that was not here. It was at a previous job.

It took a while to onboard.

They're very cagey in giving out prices, and it is very difficult to find out the real price any organization is going to get. It is almost never their list price, if you can find it, and there are a lot of factors that go into the whole pricing. 

Their SaaS deployment model, which was the way we were going at a previous organization, had some benefits over Salesforce, but the concern was the price they were going to charge depending on the number of rules or something like that. We were afraid that the cost was going to blow us out of the water. We didn't choose it. We went with Salesforce.

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 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.