Pega Platform Reviews

We primarily use the solution anywhere we have to manage processes. I have a large portfolio of clients in financial, health care, life sciences, etc., and I use the solution for all of them.

Pega is currently number one in BPM and case management solutions, according to Gartner and Forrester. I like that it’s mostly a no-code platform. It’s also more of an enterprise-level solution. It looks like a front end stack. There are dozens of applications that are just moored to each other. However, Pega feels like one solution.

The interface is quite simple and easy to use, even for beginners.

Pega currently is trying to add chatbots to their systems, and it's still quite immature. This part definitely needs to be improved. The RPA also needs improvement. Pega has its own RPA, via an acquisition a couple of years ago. They bought OpenSpan and tried to rewrite it to Pega's platform. It still has some gaps. For example, they have no machine learning. If they want to be more mature in the market, they probably need to consider working on improving that.

The solution is stable across all deployment models.

It's very simple to scale the solution, especially if it is on the cloud. It's your own environment. You can just make your own limitations as to how fast you want to create your own new environments. Right now, we are handling 20,000 users.

The initial setup is quite simple. How long deployment takes depends on what you want to implement. It can be as little as 50 minutes if it's something very easy. It's like moving bricks. You are not typing any code, rather you are creating processes. When you're developing it, the length of time needed depends on how many bricks or processes you have to move, or create, so to speak.

In terms of how many people you need to maintain the solution, It depends on what type of support was chosen. It can be your own maintenance, or it can be maintenance from other suppliers or the vendor. It also depends on the number of applications you have as well.

We are using both public and private cloud and on-premises deployment solutions. We're using product versions seven and eight and have previously used product version six.

We’re a Pega partner.

I would rate the solution ten out of ten.

We primarily use the solution for business process management.

The solution's most valuable feature is its quick setup. Nowhere else you can create a good-looking application this quick. It's a fairly robust system.

From an end-user perspective, you can build a really good user experience with the user interface they offer.

The solution could use more plugins.

The pricing model needs to be improved. Right now, it's too expensive.

The solution is very stable.

The solution is fairly scalable.

We haven't dealt with technical support very much. The solution has the usual community support, which is helpful. You can also raise the usual tickets if you're a partner and if you bought the licensing. They're quick to respond.

The licensing depends on each client, but largely they charge a yearly licensing fee.

There are extra costs, such as certification of developers that need to work on the solution. You need people with previous experience or they have to get the certification, which is basically an extra cost.

We use the on-premises deployment model.

I'd rate the solution ten out of ten. It's a robust system that makes it easy to create your basic applications. It is a premium platform, however, so it is costly.

We use the Pega BPM platform for helping companies establish, expand, or solidify their business process management and workflows.

We do the licensing of the product, and the capabilities of the platform have allowed us to flexible in the type of organizations we work for. Our strengths are in corrections and investigation into the organizational process. We also have our own IT and have existing models that we use for the insurance industry, inventions industry, and others. These models allow us to have a starting point and build out to fit a unique organization's needs. We do a bit of work for the government as well. For the clients, improvements should be an enhancement to business processes, workflow, and efficiency.

A lot of our customers are working with a digital confirmation. The enhanced features in Pega are appealing to our customers as they can use it on designs, digital agility, omnichannel or customer experience. The rapid renew structure allows better implementation over other solutions and aids clients in serving their customers. Because of the features available, we are filling a need we see for our customers. It works with team frameworks and allows them to take proactive decisions with their product lines, data integration, data crunching and some other features that are helpful for customer marketing.

In terms of improvement, we would see a benefit in Pega having better availability on the cloud side. Their presence on the cloud is not as strong as their competitors. Pega and the partners both have needs to enhance their cloud footprint compared to what it is now.

There is room for improvement with RPA as well (Robotic Process Automation) to automatically take action for users. 

The product is also extremely stable. It has a very strong case management base. This holds a lot of complex business to business information and that makes it so implementations and use can be simplified and promptly provided to the customer. The key is that the business department has to understand the product and its purpose in the right manner. I think Pega is one of the most stable applications in the environment of business technology, use, and implementation.

The product is extremely scalable. Scalability comes with two criteria: choosing the number of users and how it will be implemented in the businesses. Some organizations have 40-50 users on Pega and others have more than 1000 users. As far as the scale of use is concerned, there are absolutely no issues. 

The kind of variety and scale that Pega can handle — the different types of business, different types of application, the different types of integration — is absolutely amazing and don't think that any of its competitors come close.

The technical support is extremely good. By technical support, this refers to technical support that we as partners get from Pega. But the support comes in two parts. When we implement Pega, we take ownership of supporting our implementation on multiple levels.

We talk to Pega one-on-one for service requests and we have no reason to complain. That being said there are still some issues here and there, but they are infrequent.

We have been using Pega BPM since our inception based on capabilities. Our expertise has helped us carve out a nice niche with the marketplace.

The Pega BPM is designed in a manner which allows for the product to be implemented by experts and then for control to be handed over to the business users. If the business users are not prepared, the flexibility and ease of use for the business users can't be guaranteed. If the Pega platform is implemented in the right manner, the organization needs to integrate the right skills, the right implementation, and best business practices. 

Unlike other software solutions, Pega is not about having a whole army of developers working to put a solution together. Once the core platform is set, the application can be taken further with even junior developers implementing more controls.

The resources involved in the implementation actually support the organization and the product when implemented well.

As we do the implementations we do not rely on outside teams. We are the outside team with a high level of experience with the product.

Of the business tool available on the market, as of right now, Pega is not the cheapest. But when you choose Pega, it is possible to realize a greater return on investment. The return on your investment is more important. The implementation is a big investment as is the commitment of the organization, but the return is greater.

I would place Pega BPM at around an 8.5 out of 10 because of the cloud and RPA issues. However, Pega is an excellent choice. It is efficient and does what it is supposed to do. It is extremely important to choose the right product and implementation partner. What the customer should be looking for in terms of an implementation partner is the quality of resources that they have, it is not the quantity. 

The Pega resources are classified into solution updates, frequent solution updates and new solution updates. An implementation partner needs to have a core team that brings the solution together. The emphasis is on the people who take the implementation forward.

It is very important to see if the implementation partner has the right interface and the right experience. Organizations themselves need to look at developing a certain amount of internal Pega support. This means choosing a partner or provider willing and able to impart their skills and knowledge. The client has a lot of control on their side. Its good to be able to rely on a strong business implementation partner.

The most valuable features of Pega are the integrations that come out of the box. You have extra force in doing some common tasks like OLS, solving situations, or reporting.

What I found useful is irrelevant when our customers often could not afford a full Pega solution. I'd like to see them introduce some cheaper or more affordable solutions.

Some of our clients are still waiting to upgrade from Pega 6 to Pega 7. Only a variety will upgrade from 7 to 8. Overall, Pega 8 is a good platform with improvement.

What should be included is some UI features and maybe some integrations. This includes documentation on how the UI works. For example, some way for the Pega out of the box tools to support UGS. That would be very wise.

My issue is that the UI is hard to see in some small details. You can't do fast work with it all the time. Sometimes a customer has some requirements that you go outside of this box. It gives you the Pegs UI tool which has some limitations about styling and customizing the UI.

For some customers, it meets their requirements and for some, it doesn't. That's my view for organizational use. Maybe they could provide better technical support. 

When you are trying to do some minor attachments, you shouldn't be required to use the UI. However, you can just use the solutions that are already in there.

I like Pega BPM and the way that Pega is in harmony with all of these solutions.

Scalability is a good part of Pega. Big applications are slow. They always have something in a test-mode or something to be improved. Some other Pega features are not too good in my experience.

We are not using Pega in my organization. We are providing solutions to our customers based on the number of users. One of the issues around Pega I've had experience with are applications that confuse the users.

While Pega technical support is okay, it also depends on the issues you need help with and who your contact is with Pega. When you have a solution license, you don't get the support.

You need to go to some other sites, ask questions and hope that somebody will answer them. Pega has a solution where they provide support if you have some issues. You can find a solution with a person who has some experience at Pega for support.

We managed to resolve all of our issues and the overall experience was quite nice.

Setup is the flexibility of Pega from my point of view. There have to be some complex things that make issues on any project. Pega needs some additional features here.

I worked as an integrator and consultant. I did the setup on my own.

My main advice is to look over the solutions for each customer base to understand the main features in Pega and what should be done or shouldn't be done.

In my experience, I've met some people who say that Pega is quite expensive and hadn't even the slightest idea of how to use it and these features.

My main advice is just to get acquainted with Pega as a solution. I will give it a score of eight out of ten. It's quite good.

Our primary use case for this solution is for case management systems.

This product makes it easier to connect to multiple applications because integration through API or web services is very easy. That is one thing that has helped. The development time is very quick.

The most valuable features are case management and integration services.

The unit testing needs to improve, as well as the user interface.

In coming releases, I would like to see something in Artificial Intelligence (AI) and Machine Learning (ML).

This solution is quite stable. We deploy applications every month, generally to production, so we see that the product is quite stable, with no complexities. Overall, we're happy with the stability.

The scalability is good. In some areas, we had some trouble, but I think it was the way it was designed and not the product itself. So, we feel that it is good.

The technical support is quite good. They come back very soon, so we're happy with the support.

We did not use another solution prior to this one, so we started with Pega.

The initial setup for this solution is straightforward and not very complex.

The time for deployment depends on the complexity of the application.

We handled the implementation in-house and have people with experience in Pega.

I cannot share the financial details, but what I can see is that the users are happy because they get the solutions faster. That, for me, is a big benefit because I can show my product to the customer quicker than with any other solution. It makes me more efficient.

The licensing fees are based on the number of users.

I don't think that we evaluated other solutions. We were happy with what the tool was offering and chose it.

This product is pretty easy to work with. Sometimes you need experts, and it can be difficult to find Pega experts. Otherwise, it's a good tool to work with.

I would rate this solution an eight out of ten.

We worked with different frameworks and components that Pega offers to build a complex process management solution for a large scale financial institution.

It helped streamline process management, but was difficult to implement due to the quality of vendors available.

getNext, because it removes some of the management overheads, as well as some of the inbuilt reporting capability.

The UI needs improvement. The product itself does not have too many issues, but implementing Pega solutions is a bit of a challenge due to the way code is handled, and in general the quality of partners available with Pega specialisation could be improved.

I help clients do digital transformations, so I've been consulting with CIOs, C-level executives, to implement solutions around Pega BPM. One example is for a commercial insurance company, it is a quoting system for their brokers. For a retail management company, it could be something like their human resources onboarding system.

It cuts down the time taken for coding. Earlier it used take for us four hours to do a particular code. Now this can be done in less than 30 minutes. That's the kind of productivity gains you can get.

I think it is the user interface and the ease of developing the workflow for an application. It has a lot of gadgets to just plug and play, and that cuts down your development time quite a bit.

The biggest thing I have seen is when going from one version to another and upgrading to the latest version, it takes a pretty long time for an organization to go through an upgrade process. I think that's an area where they can make it a little smoother.

Also they need to come up with licensing options. Right now they do have a cloud-based option, but the cloud prices I've seen are much more expensive compared to competing products.

Yes, we did in the sense there have been some performance scalability issues. Suppose you want to add more users. You go from, say, 800 users to 1,500 users, and sometimes that creates issues for which there is no clear explanation. To fix it you have to escalate it with customer service and sometimes the response is not up to the mark in resolving those issues.

It is scalable, but it also interacts with a lot of other systems. I think they thought that the interface to other systems, legacy systems, was its strength, but when problems do occur, quickly diagnosing those problems has been a challenge.

On a scale of one to 10 I would give them a seven. They're fairly knowledgeable and if they've seen a problem somewhere else, they have a knowledge base and they send out solutions. But if they haven't encountered a problem, if it's unique for a particular customer's situation, sometimes it's very hard for them to provide a solution. They say, "Hey, we will take care of this in our next version upgrade." For that you have to wait for a long time.

I was working with various other products like Savvion BPM and IBM VPN. Because some of the customer situations, we switched them from those applications to Pega, and I think customers have been happy with it.

There are two options. If you are doing on-premise, it's a little complicated because you need an admin-type person who can help with the installation. But if it is cloud-based, then it is easy. It's all done in the Pega cloud and you just have to get the user ID and password and you are in business.

It depends on which option the customer goes for. It is definitely complicated if it's on-premise.

They have both on-premise and cloud licensing. If you are a small to medium company, go for the cloud option because that eliminates a lot of the setting up of your DevTest and performance environments, multiple environments, because you can buy that from Pega with the cloud option. So your setup time really goes down.

If you're a large company, then you're better off putting it within your company. You have other skill resources within your company to create environments. Large companies have an option of either going for cloud or for on-premise.

We evaluated IBM BPM and Appian.

You really need to know how you are going to use this product. Is it for customer service? Is it for marketing? Is it for robotic automation? Is it for other things? You also need to work with your business partners to clearly define the processes a user goes through to achieve the desired end result. So you have to do some "pre-work" before you buy this product or before you install this product. Licenses are expensive. You cannot start the process after you buy because then you are wasting the license dollars. If you are using this product for business process management be aware that organizations a long time to make changes to those processes. You have to initiate those changes early so that you can take full advantage of this product.

I rate it nine out of 10 overall. I feel that they should consider making the licensing more flexible and more economical. The second issue is upgrades. They have to work on them to make them smoother.

Real-time operational case management and live reporting of key arrival and departure information, including live operational data feeds from both internal and external data sources on web and mobile devices.

Decreased time for plane departures and landing, supported analytical insight for planning of three to six month forecasting, and helped with operational decision planning and support.

Pega Cloud and Pega BPM, because they allowed us to develop and quickly release with confidence using cloud technologies. We limited disruption on core operational systems while proving the business and technology requirements.

Pega Cloud early adoption and use for cross enterprise capability was new to many. The early adoption meant version 2.0 of their cloud service may require refactoring and redesign of some services.