Pega Platform Reviews

It is a multi-tenant offering for developing applications. We have its latest version.

Generically, at the moment, it can take things that were non-functioning processes and crossing stovepipes and make them function.

I have found a lot of features valuable. The ability to define processes, build reports, and get insights or analytics on data is most valuable. It is a powerful platform.

The way the IDE works with the chatbox and the taxonomy imports could be a little smoother.

There should be quicker approvals for CDH. It is a bureaucratic approval process to be able to get those particular licenses.

I have been using this solution for two and a half years.

It is stable. Like everything, it depends on the quality of the knowledge of the people who are using it.

I like it. It allows for a lot of multi-tenancy.

In terms of usage, it is in its initial use areas, but it is rapidly being adopted.

I have interacted with them. Our overall experience is positive. They have some good folks there. Occasionally, their system doesn't realize the urgency of a problem if the problem isn't in production. If your problem isn't currently causing production failures, the turnaround time can be slower than expected.

We don't use Pega exclusively. We've got other stuff in there. There are some things for which one solution is good, and for another set of things, another one fits very well.  It just depends on the application, the tendency, and the purpose.

We brought in experts. Our experience with them was positive.

The advice that I would give is that when spinning, think about if you're setting up a private one. You should also think about your tenant or your organizational control structure for multi-tenancy so that you can have a mix of licenses for tenants while not overly complicating and having to maintain tons of different work control layers. 

Before you start up an app, take a look, run the wizards, and see what you can reuse from the structure. Its wizards are very good to use when starting up. There are a lot of powerful data models and workflows that you can use as starting points. You can also simply reuse and rename them. 

Whenever you're building things, work with your team regularly on the data model supporting it so that you have a lot of reusable capability. So, you enhance it. It is worth the time to meet weekly with your team over your data architecture.

I would rate Pega BPM an eight out of 10. There is a bit of a learning curve, but it is extremely powerful. When you get into it, then you realize that it is far more powerful.

We are developing campaigns and business solutions on top of Pega. It is a part of the campaign management solution that we have. We are also using it for the core business. We are offering personalized content, personalized product, and personalized information for each of our customers. Pega is one of the main products for us for pricing, catalog, and content. It is being used for everything.

I have a lot of experience in this kind of industry, and Pega is one of the best solutions in terms of performance, capabilities, and the way we develop. 

It should have integration with non-relational databases. A lot of databases are non-relational, and as a company, we are planning to move to NoSQL or open-source databases. It would be good if we are able to install and use Pega on a NoSQL database. 

They can also try to tailor or organize the company a bit differently and go more towards the microservice concept.

I would like Pega to develop machine learning and intelligent AI algorithms. They have a good foundation in terms of the model and the stuff that we are using for some customers, and it will be good to onboard as many machine learning algorithms as possible.

I have been using this solution for a couple of years.

It is one of the most stable solutions, but you need professional expertise. If you are working in a professional way, you won't have issues. If you install it on top of any provider as a database and you are not able to tune the database, you will have issues. Every product has bugs, but it is a more stable one.

We have 25 to 30 customers who use this solution.

Their technical support is fine. There is always room for improvement, but overall, it is fine.

I have used different products and shifted to Pega. In the past ten years, I developed an in-house solution, and I also hired a company to develop it for me, but that was not enough. Now I am relying on Pega in Google Cloud, and it is running my business strategy and everything else. It is one of the best solutions in this category. I can't even compare it with other products. Based on Gartner's ratings, Pega is one of the top ones.

Its installation is straightforward. I don't see any big issue. We are using it on Google Cloud VMs. We are not using Pega container, but I know another company that is using it fully in a container.

For its deployment and maintenance, you need highly skilled people.

We mostly have a yearly license. 

I would recommend this solution. I have been recommending it to different customers across Europe. It is a professional product, but you should know what you are doing. If you don't know what you are doing, you might think it does nothing, but if you are mature enough to understand the power and potential of Pega, you can do magic with it. You should have the know-how, and you should know a customer's expectations. 

One of the reasons why some customers are getting a lot of success is because we have Pega and Data Lake or big data platforms close to each other. Data Science runs the algorithm on the Data Lake, and we propagate the data and the segment to Pega. This way the customer gets a high value. They are doing a great business because they have the potential data, and they can combine and build campaigns and segment customers on an individual basis. After that, your big data is in real-time, and you have real-time notifications. You are doing everything in real-time.

I would rate Pega BPM a nine out of ten.

We use this solution for HR automation or HR service delivery.

It is quite configurable, which is the most exciting feature. We can easily configure it as per our needs. 

Reporting is not so clear and not so great. We really struggle to get the right reporting. When we need reporting based on the content of the tickets, we are not able to get it. The MIS reporting is not great. That's one of the reasons why we are switching to ServiceNow.

Its compatibility with the higher versions of Internet Explorer should be improved. It really works well in Mozilla Firefox or any other browser, but when it comes to Microsoft Edge or Internet Explorer, sometimes, the layout gets disturbed. The positioning of the buttons changes, and there is some distortion in the layout. I am not sure whether it is our configuration problem or Pega's, but when it is working in Mozilla Firefox, it should also work in Microsoft Edge or Internet Explorer.

I have been using this solution for almost three years now. We started using it in late 2017.

It is stable. We haven't faced any downtime or any other issues.

It is quite scalable.

My team would know about it, and I personally don't really get into those details. After the implementation, our teams are on their own. I don't think they are reaching out to Pega support frequently because I don't see any product issues as such. Everything is configurable, and it is running daily.

It is not so complex, but it needs an intermediate level of skill set. It is not so complex, but it is also not so easy.

It is cost-effective for medium enterprises. It is cheaper than ServiceNow.

I would definitely recommend this solution. It is more cost-effective as compared to other products. It is the right product for medium enterprises rather than a highly-expensive solution such as ServiceNow, to which we are switching. When you're implementing it, you should configure it in the right way with all categories, subcategories, and other things.

I would rate Pega BPM a seven out of ten.

The most valuable feature is the ease of deployment.

We would like to have a better ability to customize PegaRULES.

In Pega, it is very important to have good overall system performance. As such, the performance should be improved.

Better automation would be helpful because I would like to see all of the manual intervention removed.

I have about five years of experience giving applications support for PegaRULES.

We cannot say that any application is fully stable, as it depends on the particular requirements. For example, if we have application automation then we need to make it scalable, but nothing is 100% perfect.

This is a scalable product. We have perhaps 50,000 users across our clients who use it.

I do not generally contact technical support. Instead, our core idea is to determine the issues and resolve them ourselves.

It is easy to install PegaRULES. There are no major issues because we have the proper guidelines for release and configuration. The length of time needed for deployment depends on the requirements for each client.

We have a complete in-house team that performs the implementation and deployment for our customers. This includes creating new rules and definitions, determining which policies are required, managing the system, giving support, and release management. 

We are planning to move our system to the cloud within the next six months, so this is something that we are preparing for.

The suitability of this solution depends on the organization, but in general, I definitely recommend PegaRULES. When assessing the appropriateness of this product for a client, I would first study their requirements.

I would rate this solution an eight out of ten.

We are using Pega for developing our workflow applications.

It's a good tool for workflow automation.

It's stable and secure.

In regards to the integration, more APIs may be required.

It needs more integration with other platforms.

I have been using Pega BPM for six months.

It is stable, and it is a distributed architecture.

We have approximately 1,000 users, but it can scale up to approximately 15,000.

It's a scalable product.

We have not contacted technical support.

Previously, we did not use another solution. It was all manually done.

The initial setup is straightforward, nothing complex.

It took two or three days to deploy. We are still new to the system.

We completed the implementation ourselves.

We have a complete team of administrators and application administrators who maintain this solution.

It's a user-based license where, as you scale the numbers of users, the price increases.

They also price base on the number of cases you have. 

They have varieties of pricing models.

Currently, we are working on the deployment models. 

We have not yet started on how to do automation of deployment. I think it's there, but we have not explored it yet.

We have in-house applications that we want to implement automation for. We will be using this software to automate those products.

I would recommend Pega BPM.

I would rate this solution a nine out of ten.

We use it for some insurance companies for underwriting.

The workflow designing and integration are the most valuable features. Also, the UI design was pretty easy. 

All the features that are related to case management are pretty outstanding.

It's called a local platform but on the other hand, it needs a lot of experience. It's not all that easy to click and plug and play. If you really want to use all the features out of this platform, you definitely need a lot of experience and a lot of training to get there.

Because the platform offers a lot of different features, it's rather complex and makes it very valuable for many different use cases, but what I would improve is that you can't tell all the people that it's a local platform, which suggests that it's for everybody, even for those people that do not have any clue about IT. They are using a lot of functionalities that try to help those developers and usually they make good jobs, but there are some situations where this automation will cause a lot of stress and trouble. This is something that creates more work at the end than if you just started from scratch. 

It depends on the use case but in general, it's stable. We have two use cases where we use a lot of different tasks and if you have more than 1,000 use cases then there seems to be some problems with the stability. It may depend on other features like load balancing and those kinds of things. 

It is definitely scalable.

Technical support is quite good if you don't have very special requests or defects. It depends mostly on your own code. But if it's on the general code that is provided by Pega, it's quite easy to set up a question to the Pega team and it's usually answered within a couple of hours, sometimes even faster. 

There's a lot of information that can be found in the Pega community which is quite helpful.

The initial setup is quite easy. If you use the cloud options, you get the full stack delivered and you do not have any hassle with setting up certain features or certain information. If you just install it on your local machine, it is also going to work pretty well. 

It's more complex if you set it up in a local environment on the local server, then you have to check a lot of different things and especially all the things that are related to securities.

I think the pricing reasonable. On the other hand, Pega has a clear focus on future companies. So, they say, "Okay, this is for our main customer focus," and this is, in my eyes, a bit of a pity because I think the technique and the software are really mature and could be very helpful for other companies as well that are not a main focus of them. 

My advice would be to have a focus on what the main purpose of the VPN platform is. Are you really looking for a VPN platform, something that is gathering all the VPN processes in the whole company, or is it just for reporting some processes like a customer process and connecting it to an SAP process? 

If you are planning to use Pega as your main platform, then it's a really good choice. On the other hand, if you have different software in your company like microservices or other big platforms like SAP, then you really should think if adding Pega as another big solid piece of software is really a good idea or if you just look if you can find other ways to integrate the other pieces of software for the purpose.

I would rate Pega BPM a nine out of ten.

I would like to have a lightweight version of it; something like Appian. In the very beginning, you just had Word and Excel, and you were fine with that. Now, you have a complete suite starting from SharePoint and Teams, etc, but you don't need all the features because you have a specific purpose and for this purpose, you need the best software. But nevertheless, you don't need, for example, all these RPA stuff, which is heavily promoted. These are all things that you just buy-in and are reflected in the price. It would be helpful if they offered a lighter version. 

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.

We developed an an underwriting platform for an insurance company. In this project I mainly worked as a senior developer. I have more than four years of PEGA experience in both technical and business consulting. My company is an official PEGA partner.  

The new PEGA underwriting platform replaced the former underwriting system and helped to integrate other legacy systems and functionalities in one application. It also helped to save licence costs for other legacy systems.

PEGA provides many OOTB functionalities which can be configured for your purpose.
What I really recommend are the following features:

* Case Management (incl. extensive Audit Trails)
* User Interface (based on HTML5 and constantly improving)
* Integration (pre-configured functionalities like REST, SOAP, API)
* GetNextWork (configurable algorithm to route the most critical task to users)
* Multi-Channel-Ability (start your case from whichever device and continue on other channels)

PEGA claims that they provide a LOW-CODE-PLATFORM which is easy to use - even for "citizen developers" (i.e. business employees).  bla bla. If you really want to use all the features out of this platform, you definitely need a lot of experience and a lot of training. In all of my projects there were many obstacles to solve which weren't simple and which could not be solved by "citizen developers" but only by Lead System Architects with 5+ years of PEGA experience. You can compare PEGA with SAP - if you really know how to use both of them, it can make the difference. If you are only interested in developing automated micro services / processes, than there are far better options.  

I would like to have a lightweight version of the solution, something like Appian or Outsystems that is much more focussed on process core features. If you set up your first projects and you see that you need more functionalities, than it would be great to upgrade to the PEGA platform.  

For me PEGA is sometimes like the MS Office package. In the past you had the core functionalities like Word and Excel, and you were fine with that. Now you have a complete suite starting from SharePoint and Teams and whatever, but in most cases you don't need all the features because you just have a certain purpose where you need the best software. 

CONCLUSION: The PEGA platform is an outstanding product for those companies that are really willing to use it as a BPM PLATFORM throughout the whole company. The many features and OOTB functionalities makes it very valuable for many different use cases. Those companies that are willing to setup a BPM program for a couple of years will definitely benefit from PEGA.

More than four years.

The stability really depends on the use case. We have two use cases where we use a lot of different tasks. If you have more than 1,000 tasks then there seem to be some problems with the stability. But it may depend on other features like the load balancing and those kinds of things. This isn't my core business but I've heard from others.

Technical support is quite good if you don't have very special requests requirements or defects. It depends mostly on your own code, but if it's on the general code provided by Pega, it's quite easy to set up a question to the Pega team and it's usually answered within a couple of hours, sometimes even faster. There's also a lot of information that can be found in the Pega community which is quite helpful.

The initial setup is quite easy. If you use the cloud option, you get the full stack delivered and there's no hassle with setting up certain features or certain information. If you install it on your local machine, it also works fine although it's more complex. If you set it up in a local environment on the local server, then you have to check a lot of different things and especially all the things related to security and that can add some hassle.

Compared to what you get - the costs are reasonable. However the question is, if you really need all features? Pegasystems has a clear focus on big companies. Although the software is really mature and thus could be very helpful for SME companies, the high licence fee will be an issue for most SMEs.

My advice is to suggest people focus on the main purpose for the BPM platform. Are they really looking for a BPM platform, something that gathers all the business processes throughout the company, or is it just for reporting processes like a customer process and connecting it to some SAP processes or some CRM, or whatever. 

If you decide to use Pega as the main platform, then it's a really good choice. On the other hand, if you have a different software in your company like micro services or other big platforms like SAP, then you really should think carefully whether adding Pega as another large solid piece of software is really a good idea, or whether you can find other ways to integrate the other pieces of software for the purpose.

I would rate this product an eight out of 10. 

The use cases vary. The solution is useful for various types of processes such as client onboarding, opening and processing accounts, policies and quotes, claim registration and reimbursement, underwriting, etc.

The solution offers excellent workflows. 

The amount of processes a user can access is very broad.

The integrations within the solution are excellent.

The solution has the ability to manage different versions of rules.

Overall, there isn't a feature on the solution that isn't useful. The solution is excellent.

There are some UX shortcomings within the solution. However, it's my understanding that they have addressed them and in the next three months they will come out with a new updated version. They will be moving away from HTML5.

I've been working with the solution for fourteen or more years.

We have some clients that have up to 2,000 active users at any given time.

The solution is meant for large-scale enterprises.

It has been used in the insurance and finance industries as well as manufacturing, healthcare, and government. Many governments have started using it as well, so it is being used all over.

We've been in touch with technical support many times. They are quite good, overall. 

The only thing is sometimes responses get delayed because they need to go to the logs, they need to go through all the steps, what someone was trying to do, and what was not working. It's quite intensive. It takes time. Otherwise, it is simply good. Great.

I've previously had some experience with Appian. They are actually quite different solutions. It's hard to compare them.

The implementation is not the quickest. An organization needs to get a good partner from Pega who will be doing the implementation. If a partner's doing the setup the correct way then it all goes well.

We are a Pega partner and assist clients with the implementation.

We have a business relationship with Pega.

We handle both on cloud or on-premises deployments according to the client's needs. Many financial institutions prefer on-premises, because of the data security. However, even some of the banks have opted for cloud as well.

I'd advise other organizations to get a good partner and take time to compare other options and to do a roadmap. Not every product is suitable for every scenario, so it's important to do a bit of research first.

I'd rate the solution eight out of ten.