Pega Platform Reviews

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

We primarily use the solution for customer experience. We also use it to create some workflows.

The solution provides us with a very good dashboard.

From a technical point of view, it would be helpful to have some advanced analytics to help with configuration. We have a lot of unwanted features and it would be good to configure it more appropriately so that we are using just exactly what we need.

I've been using the solution for five years.

In terms of stability, occasionally there are a few glitches to contend with. It's fine. It's to be expected. It doesn't affect our work too much.

The solution is scalable. If a person needs to expand the solution for their organization, they can easily do so.

Currently, we have more than 20 people using the solution.

We've never been in touch with technical support, so I can't speak to how they are or what the process is.

We previously used Appian. At the time, there was some product integration and it made sense for us to switch to Pega.

In terms of implementation, the solution's initial setup is a little bit complex. It's not exactly straightforward. The software implementation and deployment, for example, is very complex. In comparison to the on-premises model, the cloud is very quick to deploy. The configuration on the cloud is much more straightforward.

If a person is using an on-premises solution, they will need one person to manage it, but if the cloud is deployed, there's no need for anyone.

We're still in the process of evaluating other solutions. We're comparing other offerings to Pega.

We're partners with Pega.

I'm not sure of the exact release number, but we are using the latest version of the solution.

It's a good idea to get clarity in terms of what future upgrades the solution plans to implement. Then, compare it to the competition. It will give you a good idea of what is possible and what will be possible.

I'd rate the solution eight out of ten overall. It's been quite good and we've been quite satisfied with it.

We are primarily using the solution for or our authorization workflow.

The most valuable aspect of the solution is the various workflows.

I haven't been using the solution for that long, so I don't know if there are any features that are lacking.

We need more light retail BPM tools within the Pega system. However, Pega is mostly for big companies.

As our group is pretty small, we may need to look for a different solution that's more geared to smaller sized organizations.

I've only recently begun to use the solution. I've been using it only for the last three or four months.

So far, over the few months we've used it, the solution has proven to be quite scalable.

So far, we've found the solution to be quite scalable.

We haven't reached out to technical support yet. We've been only using the solution for a short time.

The initial setup is straightforward, The installation is not that complicated. One of our team members has deployed it onto the storage.

Our own teams handle maintenance. We have several teams on different projects.

We're constantly evaluating other products. We're looking at others on the market right now.

Most of our use cases are related workflow kinds of tasks like data workflow, user onboarding workflows, etc.

Although the solution might be too big for our purposes, as of now we are continuing with Pega because we don't know of any such tools which have the scalability, as well as the ease of use that this solution provides. That's why we are continuing with it right now.

Although I personally haven't used the solution for very long, I would rate it eight out of ten.

We do not use this solution in my organization. We are consultants and we act as a third-party for our clients.

This solution is used to orchestrate processes across different parts of the infrastructure. All of the activities are coordinated and controlled, managed by a unique platform where they can keep track of everything. 

The most valuable feature is the situational layer cake. It's a feature of the tool that allows us to specialize a process according to different countries, products, or other dimensions. This means that we can create complex processes that are differentiated according to geography, product, or other characteristics. The result is that it makes it much easier for us to maintain the solution.

In terms of functionality, Pega is probably the number one solution in this field.

Compared to other BPM products, the interface is somewhat complex, so the usability could be improved.

We have been using this solution since 2014.

Pega BPM is very stable and our customers use it on a daily basis.

This is a very scalable solution. Our customers are large enterprises.

The technical support is okay.

One of our clients was using a BPM solution by TIBCO before switching to Pega. TIBCO is more technical, whereas Pega is more business-oriented.

The initial setup is quite complex. It requires a lot of time and its not something that you can just do quickly. Pega is a very complete and structured product that needs to be configured according to the organizational structure.

Considerations have to be made with respect to managing data and integrating with their tools. In many ways, it is a Plug and Play tool, but it will require some time.

We have had cases where we have done the deployment for our customers, although in other instances, the client does everything. We prefer not to do the installation, if possible.

The price of this solution, including installation and configuration, is comparable to competing vendors.

My advice to anybody who is implementing this solution is to make sure that they understand it. For example, we are certified in the usage of Pega BPM. It's a very complete product but it is not a simple one. They need to use the right, structured approach to implement it properly. Pega is not a product for a client with small needs. If anything, when setting up Pega you should think bigger and put things in place for what will be needed to lead the team in the right direction in the future.

I would rate this solution an eight out of ten.

The marketing automation is very good. The solution is very convenient to use.

The solution would benefit from more integration capabilities.

There are some tools within the solution that are difficult to use.

I've been using the solution for 1.5 years.

The stability has been good. We haven't had any issues.

The scalability of the solution is very good.

We've never contacted technical support.

I've previously worked with Bizagi, and I find this solution has more features in comparison.

The initial setup is straightforward. Deployment typically takes a few days.

We handled the implementation ourselves.

We use the cloud deployment model.

We've been using the solution for a long time and it's been very good.

I'd rate the solution eight out of ten. There are some technical tools that are hard to use.

We primarily use the solution in claims for our clients in the insurance industry.

The visualization of the business process and the collaboration aspects of the solution are its most valuable features.

The solution is more user-friendly than its competition, and more visual. Its level of inference is much lower as well.

The solution needs to invest more in its technology. For public and private clouds, for example, the development environment is slow. Saving events should take one to two seconds, max, and because you are making changes often, the slowness cuts down on productivity because we have to wait for things to save before continuing. 

The UI could be slightly improved.

The solution is stable.

The solution is scalable.

The technical support has been very good. They answer our questions in a straightforward manner.

The initial setup can be a bit complex because you don't just deploy the solution out of the box. It has many possibilities and when you are implementing the solution you are setting specific features to align with the requirements of the business. In POCs and real production environments as well you need to think about all of the different aspects and this makes the setup complex.

We handled the implementation ourselves.

We're a Pega partner.

I'd suggest those considering implementing the solution start small and maybe do a POC. That will give you a sense of what the solution would look like in production.

I'd rate the solution eight out of ten,