Pega Platform Reviews

The solution is basically a quoting application. When insurance brokers or internal users have to call or do insurance quotes for commercial insurance, we use Pega. The insurance we cover is for outdoor coverage and for a casualty to property, as well as casualty insurance.

The solution's case management is its most valuable aspect. 

It's basically an open architecture based software, which means the main aim of the software is to provide a low-code application development environment. It has several authoring tools on the UI flow and makes sure that you can put in a lot of gadgets and create the screen very quickly using those gadgets.

Right now, it has a pretty good feature set. It has case management and BPM workflow as well as robotic automation. It has decisioning. It has chat and virtual assistant support, and we just implement it on the cloud, therefore it's a pretty robust feature set.

They use something called a unique model-based architecture. During development, where the database and the UI, everything comes from one single piece of architecture. Due to that sometimes the enterprise architecture teams do not like it due to the fact that it forces them to use just one piece of architecture. If these could be more modularized, then it can be easily deployable in different kinds of scenarios in organizations, it would be much better.

However, they are kind of tightly coupled and it's difficult to separate everything out. Still, I would say it is an improvement to consider for the future. Id they could decouple the various components so that it gives flexibility to enterprise architects to deploy what is most needed as part of their enterprise architecture strategy, rather than getting kind of, looking at the only way the product handles, it would be a stronger product.

They are currently spending some time on improving the product with respect to machine learning, especially related to robotic automation. They probably could be a little more adept on that area would help.

It's very difficult to change many things unless somebody puts in the time to figure everything out. However, Pega could learn from all the customer service calls they get and categorize them in order to do an automatic form-based or customer service based response. If they could set it up to everything automatically, then that would save a lot of time and headaches for companies and help them troubleshoot and work through issues faster.

We've been using the solution for almost ten years. We haven't used in the last 12 months too much, however.

We have found a few issues on the solution and we work closely with technical support to help fix them. While it is largely stable, we do find we need to keep up with problems and work closely with Pega directly to address and fix them when they arise.

In terms of scalability, provided you throw hardware at it and you do a proper production implementation approach and alignment strategy, it's scalable. 

You can go up to 2000 to 3000 users pretty easily. It's just that you need to throw a lot of hardware at it and make sure that you manage and create the web servers required. You need to create various pieces such as database servers and things like that, to make sure that you get the performance you need for those 2000, 3000 users.

The solution is being used continuously. I'm not sure about the increase in the usage, but at least it's serving the purpose as needed for the brokers.

It's a complex piece of software. For that reason, we did find some issues and I was kind of instrumental in working with Pega on their global support model. We had weekly calls to review. They have a process to track issues that are unique. Sometimes it's handled by their support network, and sometimes the issue is taken up to be dealt with by working on the next version. For us, triage calls are made every week.

The initial setup is never straightforward. It's always complex. Organizations deploying the solution will need a Pega admin and experts. It's not like anybody can just walk in and install it onto a PC. It needs a lot more performance concentrations and much more integration considerations. Therefore, it's a little complex.

In terms of deployment times, on-premise, it takes a little more time, and I would say it would take maybe about a month. However, now, cloud implementations are pretty quick and go much faster.

In terms of maintenance, we do need someone from the company to help us manage the solution.

We did solicit outside assistance for the implementation. We actually used both the Pega professional services in the beginning for a short time and then a subsequent implementation was done by an integrator.

There are multiple models. They have enterprise licenses for each server, for the product version. If you're doing it on-premise they also have per user basis on their cloud. 

It depends on what your specific need is. Those vary from customer to customer, depending on the number of users and the volume of business and things like that. There's no, set price, or a specific quote and everybody just follows it. It's more they work out the enterprise licensing agreements or per user basis with respect to each client.

I joined the company when those decisions were already made. I wasn't part of that decision. However, in a lot of places where I've consulted as a digital transformation consultant, we did definitely compare Pega with competition such as Appian and other BPM, and even Salesforce and other workflow systems as well.

We're just customers. We don't have a business relationship with Pega.

Pega BPM is definitely one of the topmost BPM packages out there. It hits all the right notes for a containerized implementation. The only thing you need to be careful is that you definitely need experts to help you along the way, in both the design and the requirements capture. They have an excellent requirements capture tool as well. However, if somebody needs to be trained on that, you need the help of experts, both on the software architecture as well as business architecture as well as the Pega admin. Eventually, these kinds of positions will either require a company to staff up or they will need to work with a system integrator. 

Most of the companies work with system integrators due to the fact that Pega professional services are definitely very expensive. Organizations will work with a company life Cognizant or Accenture or others to really help them out along the way.

I'd rate the solution nine out of ten.

We are using Pega for content management and as a ticket management system.

The most valuable feature is flexibility, as we can configure it to best suit our requirements.

The reporting does not work well for us. If we have somebody working on a ticket or request, we are not able to track the end-to-end time. Also, the assignment is not happening correctly. Ideally, they should have panel management reporting.

The end-user notifications need to be improved because there is a delay.

It is not fully compatible with all versions of Internet Explorer, so sometimes, it does not work. There are technical glitches because of this.

I have been using Pega BPM for about three and a half years.

We have experienced technical glitches with the use of Internet Explorer and with reporting.

I don't feel that there are any issues with scalability. That said, until our concerns with reporting are satisfied, we don't want to scale.

The technical support is good.

The initial setup is not complex, although I would not say that it is simple, either. You need to know the technology to implement it.

Our in-house technical team was responsible for the deployment, and we had a consultant working with us.

The pricing is pretty good, compared to other similar products.

We are changing systems because we are trying to bring total service delivery into a common platform, and Pega is not able to handle the requirements. We are interested in a user-friendly solution without reporting glitches and difficulties.

The suitability of Pega BPM depends on the requirements. For smaller companies, where one or two products are being serviced, I would recommend it. However, I suggest that larger enterprises consider other tools.

For what they are providing, I think the pricing is fair.

I would rate this solution a six out of ten.

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.

Pega BPM can be deployed on-premise and in the cloud.

All the scalability issues are addressed with Pega BPM because you can create enterprise-grade solutions with the architecture it has.

Pega BPM has a use case in every sector and area, such as manufacturing, insurance, vendor suppliers, and vendor collaboration hubs.

The most valuable feature of Pega BPM is its architecture.

Pega BPM could improve the UI, it is poorly designed to have a good UX experience.

I have been using Pega BPM for approximately six years.

Pega BPM is stable.

Pega BPM is enterprise-grade and scalable.

The support from Pega BPM is very good.

Using Pega BPM on the cloud is simple. Within five minutes you can have your own Pega BPM instance.

The licensing model from Pega BPM is too complex and is more expensive than other solutions, such as SAP. The overall price of the solution depends on the use case.

My advice to those before purchasing is the UI capability is not good and the cost of the implementation generally is higher in the implementation.

I rate Pega BPM

They use it for marketing and case management. It is also used for workflow process automation and market intelligence, using the solution’s AI capabilities.

The case management functionality of this solution has been most valuable.

There is a scarcity of resources who have worked with this solution before.

I have been using this solution for eight years.

This is a stable solution.

This is a scalable solution.

I would rate the customer service for this solution a four out of five.

Positive

The initial setup for this solution is not that complex.

The enterprise product has the best features as a cloud product. It is the market leader in the BPM space.

I would rate this solution a nine out of ten.

We are a strategy consultancy for someone who is looking for a Low-code No-code platform for the utilization of digitized service processes. We can determine if Pega BPM is the right fit for them because it can be deployed on the Cloud,on-premise, Kubernetes, and Dockers. We are in discussions with customers with many other solutions, such as OutSystems and Mendix. From a strategic point of view. We're not going to implement only one service tomorrow.

We mostly use European providers. We do not use hyper scalers because of privacy concerns, such as Google, Microsoft, and Amazon.

We use Pega BPM for simple service management processes. We are a consultancy that works for the government. We look at public services and how public services can be supported. These new types of workflow technologies where you to have end-to-end case management. They can be used for public services processes that are created on these platforms.

Pega BPM could improve the artificial intelligence capabilities because they are always valuable and case management for all types of industries is important. Additionally, the reporting performance management capabilities could be better because you want to have insights into how your processes are working, such as Cloud protection. The whole range can be better. However, the platforms are improving every year, they are on the right track.

In the next release of Pega BPM, they should add more ways to do the customer interaction fields in the portals.

I have been using Pega BPM for more than one year.

Pega BPM is scalable. If you have larger data models, for example, thousands and millions of transactions, they have their limits. Larger data models need to be improved. It's not only technically scalable, for instance, if one organization develops a solution built on ServiceNow or Pega BPM, how can you transfer the solution to the next organization that has the same platform. They have a marketplace on most of the platforms where third-party vendors can show their services. For a public organization, if you develop a small application, the next town could use it the same way. How to transfer easily from one to another one. It might not be a relevant case for private companies because you are in competition. There's no need to give away knowledge. However, in the public domain, it's a different case but it's very special, nothing in general.

The technical support of Pega BPM is very good.

If you work with any of those platforms such as Pega BPM, Mendix, OutSystems, or ServiceNow, they have different sweet spots. You should always think about what you really want to accomplish. What do you want to do with those platforms, you have to choose between Pega BPM or ServiceNow. You have to decide what is the right provider, and it is not one-fits-all. 

The platforms are used to be faster. You have citizen developers who can build faster solutions but in the end, if you have no governance, no strict rules on how to use it there can be problems. For example, to put out a fire somewhere, you can do it in 10,000 different ways. If you don't have strict rules, how to do it, you might end up with a crazy solution that you can't manage over time, such as the maintainability of those solutions or of the platform ecosystem in general.  You need strict governance or rules of what to do and how to do it. Otherwise, it will be like a crazy zoo of different solutions and you don't know what it is, how they work, or why they work. If everyone is able to use a solution but they are not using it in the same way it can be improper and this is why governance and rules need to be applied.

I rate Pega BPM a seven out of ten.

Pega BPM is good, it is not the worst solution you can find on the market. However, it depends on what you're looking for. It has to meet the use case that you are looking to solve. Other solutions, such as OutSystems and Mendix, they're more open-minded, you can do whatever you want to do, but they don't have strong case management. In my industry, it's more or less, very simple service processes.

I've been using Pega BPM for insurance underwriting, claims management, and pricing.

What we like about Pega BPM is their case management feature which we find powerful. We also like its workflow capability.

The licensing model of Pega BPM is tricky, especially for first-time customers, so it's something that they could improve.

The technical support team for this solution could be faster in resolving tickets.

I've been using Pega BPM for five years.

We are satisfied with the stability of this solution.

We have been able to use Pega BPM in different lines of businesses for the past few years, so we find it scalable.

We faced some issues so we had to contact technical support. We raised the ticket and it was resolved. It took a week, but it was resolved.

We implemented Pega BPM with the help of a consultant.

This solution's licensing model needs to be improved.

It's a yearly subscription, but there are no extra costs apart from the standard licensing fee.

I'm using one of the latest versions of Pega BPM: version 8.

It was the IT side, with the help of a consultant, who handled the installation of this solution, so I didn't have much visibility into whether it was easy or complex. It was done over a period of seven to 15 days.

The number of end users using Pega BPM in our organization is 35 to 40.

Deployment of this solution did not take many people: just two people, but for maintenance, we have three people, so deployment and maintenance requires a total of five people. All of them are engineers.

We use Pega BPM almost on a daily basis. We currently don't have any plans of increasing its usage.

I'm recommending this solution to other people, particularly if it is a good use case for them.

Pega BPM is the first business process management software we were able to try. We had an old tool we were using, but it was not a BPM software. 

My rating for Pega BPM is eight out of ten.

Pega BPM is a business process management tool that can be used to build enterprise applications.

The solution is operating well overall.

I have been using Pega BPM for approximately two years.

They need to support the solution better, at this time the company does not have enough support.

The implementation is not complex.

I need people who understand this tool and they can implement it. I cannot rely on someone that implements it and leaves. They do not have enough people qualified in the market. If you are not able to operate it, improve it, or do enhancements changes yourself, it will be an issue.

The price is a bit expensive.

I rate Pega BPM a seven out of ten.