Pega Platform Reviews

We use Pega BPM for backups, consumers, markets, payments, loans, etc.

The most valuable features of the solution are case management, routing, and low-code environment.

The solution's pricing model or licensing model could be a little better.

I have been using Pega BPM for 12 years.

I rate the solution’s stability an eight out of ten.

I rate the solution an eight out of ten for scalability.

The solution's technical support is good, but there are some things it needs to improve. Sometimes, the support takes longer because of the customer queries and the analysis it has to do.

Neutral

The solution’s initial setup could be made a bit easier.

We are using the solution's case management, many finance-related modules, and some frameworks. The solution's case management function has improved our daily operations. It was easy to customize Pega BPM for our industry. The solution handles some industry-leading tasks, like legal compliance.

Pega BPM has a huge offering, which includes CLM (Contract Lifecycle Management) and many frameworks built into their packages to comply with industry standards. Pega BPM is deployed mostly on-premises in banks for data security. Other BPM services, such as Oracle BPM, IBM BPM, Appian BPM, and Camunda BPM, are available in the market.

Small and medium enterprises have different needs and different costs. Pega BPM simplifies the modeling of a typical low-code workflow and data. There are other use cases where some other tool works better. Recommending Pega BPM depends on the business needs and journeys. Using the solution varies from case to case and depends on cost, complexity, infrastructure, and all other associated things that come with it.

Overall, I rate the solution an eight out of ten.

We primarily utilize it for automating a multitude of business operations, including finance, accounting, manufacturing, and product development. These processes play a crucial role in managing our day-to-day operations and we find that the automation provided by our use of this technology streamlines and simplifies these processes greatly.

The most valuable feature of Pega BPMI would be the academy courses, specifically the Product Development Network (PDN). Additionally, our organization has a dedicated Customer Engagement Team that we work closely with to achieve our goals.

The training aspect of Pega BPM requires significant enhancement. There should be more opportunities for third-party training and engaging events, such as hackathons where individuals can share their expertise. Additionally, the training structure itself should be more organized, as I have received feedback from my colleagues in the COE that the current training approach is overwhelming and requires excessive referencing to obtain accurate information. Another area for improvement would be the user experience with regard to RPA. Simplifying the IDA for citizen developers would make it easier for them to adopt the RPA tool.

I have been using Pega BPM for approximately five years.

I rate the stability of Pega BPM an eight out of ten.

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

The setup of Pega BPM is not complex.

I rate the initial setup of Pega BPM a six out of ten.

I rate Pega BPM a seven out of ten.

In conducting our evaluations and comparisons between UiPath and Pega BPM, we found that both systems hold a comparable standing. Although, it is evident that UiPath outperforms in certain aspects such as user experience and ease of use in the development process. On the other hand, Pega BPM excels in addressing complex customization needs and offers more cost-effective solutions. Ultimately, our assessment concluded that both systems score equally in terms of their capabilities and effectiveness.

UiPath is best suited for smaller-sized companies. Pega BPM is better suited for large-sized businesses. 

I would recommend this solution to others.

I rate Pega BPM a seven out of ten.

It's built on the base core product.

Pega provides a lot of out-of-the-box capabilities in terms of rules. You need not write anything. If there is anything that's specific to your company's need, then you'll go ahead and do a "save as" and work on those activities. That said, PegaRULES already provides most of the out-of-the-box activity for sending emails, sending correspondences, or most of the items that you do on general web applications.

Pega helps speed up and create rules around sending in correspondence as transmittal things, for example, PDFs, et cetera Pega gave us a lot of out-of-the-box rules we could just apply. It already converts from bytes to streams and PDFs to any other format, and it generates and gives reports to users. You need not worry about what Pega does inside, the back end. Everything is handled and you just benefit from the work it does behind the scenes. 

The rules Pega provides for almost all the areas are great. Pega provides a lot of flexibility or out-of-the-box rules. You do not need to write your own code. It's a low-code solution which makes it very easy to use. 

The setup process is pretty simple. 

It's not too expensive.

It is stable and reliable.

The solution can scale.

Technical support is helpful. 

The UI needs improvement. 

Some integrations can be a bit complex during implementation. 

Other than that, we have not come across any missing features. It's been very good across the board. 

I've been using the solution for nine years now. 

The stability is decent. It's reliable. I'd rate it eight out of ten overall. There are no bugs or glitches, and it doesn't crash or freeze. 

The scalability is good. I'd rate it eight out of ten overall. 

Technical support has been quite good overall. We are happy with the level of support we receive.

Positive

We previously used a VPN tool before. This solution is far better. 

The solution is fairly straightforward to set up. It's not overly complex. That said, some of the integration is a little complex. Apart from that, everything looks good.

It doesn't take too many people to deploy the solution. 

We have witnessed an ROI while using the product. 

The pricing is very reasonable. I'd rate it none out of ten in terms of affordability. It's not overly expensive. 

We have the solution deployed both on-premises and on the cloud. 

If anyone is checking out Pega or maybe trying to use the tool, I would say just go ahead and do it. It's a pretty good tool in the market, and users can easily deploy it to try it out.

I'd rate it nine out of ten overall. 

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.

Our customer base is varied, ranging from insurance to banking to government. In the insurance domain Pega is used for things like policy, as middleman management, policy administration and claims administration. In the banking realm, it's used across multiple areas from CRM systems, customer service, sales automation, and things like loan origination, payment investigations and payment arrangement management. In the government sector, it's used particularly as a case management software to manage processes.

Most of our customers are enterprise businesses, we are partners of Pega and our company functions as a system integrator. I am co-founder and Chief Technology Officer. 

One of the valuable things in the solution is that Pega offers a unique environment where its entire architecture is very unified, meaning it's used free across multiple areas. In other products, say IBM, and other solutions, the products range across several solutions and include separate components for analytics, separate components for the UI and a separate component for business roles. Pega, on the other hand, is one unified architecture and that is very valuable. The second thing is that Pega is model driven architecture so building something up on it from models is very quick. 

From a room for improvement point of view, what I've seen is that many customers want solutions that directly meet their requirements so while Pega has somewhat vertical solutions on Pega customer service and sales automation, industry and customer experts expect more out-of-box solutions to be readily available on Pega.

It is the same for additional features - the customer expects more business solutions to be directly available on Pega. For example, when I say business solutions, Pega could have a business solution on customer service, a business solution on sales automation. Pega may not have a proper business solution for LOS, or Loan Origination System. These are common business solutions which could be made available in the solution, it would be very good if they could focus on the direct business solutions which customers expect over here.

I've been using this solution since 2003, so 17 or 18 years. 

As enterprise customers are using it, you can tell it's stable. It's one solution which we've basically used and worked both on-prem as well as on cloud and it's one of the other unique value aspects of Pega, that the same solution can work on cloud as well as on-prem. 

From a scalability perspective, it's scalable. In terms of high volume, we have some applications based out of Vietnam which have millions of cases, so in terms of the number of cases, it's highly scalable. We have other customers who also have a high volume of users. 

Because I've been working with Pega since 2003, I can see the improvements that have been made in terms of how they go about establishing contact with customers. These days, it's pretty easy and accessible.

Initial setup is quite straightforward. Deployment time is based on the actual size of the project. On average, it can take anywhere from three to five months to build. Usually, the team servicing from our side is around five to seven people and from the client side it's usually a project manager and a couple of others. 

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.

In terms of features that I have found most valuable, there are lots of new things in Appian BPM, maybe six in this newer version. Earlier, what we needed to do if we wanted to deploy some code into the other environment was to upload it into the environment, take a patch from the other environment, patch it, and import it. Nowadays it is easier. There is a new feature in the Admin Console where I just need to click on that environment, pick a patch, and just select the environment. Then I see whether it is queuing in the scheduled environment or going for production. I select the environment and I can directly deploy that patch. This is a very good feature of the current version.

There is a very well implemented UI side - the front-end visibility. There is a new progress bar that allows you to see your progress. There is a very impressive UI design that they've embedded into the BPM tool.

In terms of areas that need to be improved, I would say the timeout. This is because sometimes when we are patching some data from the database, we are getting added as a timeout. I would like to build a solution for that or to improve that feature, because by doing so the process will be trimmed. Sometimes it gets stuck just due to taking so much time for the user in the back-end data from the database. I think all the other features are very good.

Additionally, I'd like to select the availabilities. I'm using the earlier version now because it is on-premise implementation. If I go on the newer PGi for a couple of days, the latest version, then I will able to see what other additional features we need to have in the BPM tool.

I've been working on Appian BPM tools for about three years.

I do not have an issue with stability. I'm completely fine with that.

It is definitely scalable and I know that is a very good feature of the Pega BPM and Appian BPM.

I have never contacted support. 

But we have one help ticket raised, so technically I do support the production.

I like Appian BPM. In Appian BPM I need to code for the components. If it's a bigger program, depending on the sizing, I read about using Pega BPM for that. But I'm working as an Appian Lead and working on Appian BPM tools for about three years.

About a year ago, I was working as a DOS developer and then I moved to Appian BPM and Pega BPM. I get feedback from the users. Based on the data from the POC, I present that to the user and if there is any implement I'll do it on the same day and avail it to the user. If they're okay with it, then I can go ahead and create the application and develop it for the solution.

Working as a DOS developer I'm coming from a different place. I came to know about this BPM tool from the website and learned that it has very good features. So that's the main attraction to BPM tools.

The initial setup is not complex, it is easy. For the first time user, we do have the trial version of it. Nowadays, as you are aware, we have data in the Cloud where it is like MySQL. It will take under 30 minutes. Not more than that.

We are working in Agile. So there is a sprint of two weeks. After each and every sprint we have to be looking forward to the after-sprint plans. So the solution has been deployed after each and every sprint to the queue and on the decided date, to the production.

I used a number of integrators for my current project that was as a re-seller. I don't have experience with implementing. On my current project, I do integrate with the re-seller that does business with Appian. We are just consulting for the solution at our end with an integrator at Appian by using the data authentication.

I would definitely let people know about it. Let me give you a scenario. Let's say there is a banking system. Generally, people come to the bank, fill out the form, and submit it. Then a record will be created in the system. So what happens by using the Pega BPM is that we can clearly identify the flow - how you do it by using the different user input tasks. This is appealing to the user, to the customers, to everyone. Definitely I would like to get a return on that and let them know that if they use this BPM tool, more than any other technology tool, it has the most complete set of tools for the system.

On a scale of one to ten, I'd rate it an eight. This is because it is easier to use than any other product and it is more secure. All of our software was developed in Java and as we know Java is a secure language. 

There are many more features. It is easy to use, easy to understand, easy to implement and easy to enhance and we can do it as a Cloud. Also, it is very user-friendly. Nowadays, it's on Cloud so we can access it from anywhere. There is no location per se or any system requirement.

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.