Pega Platform Reviews

The primary use case for this solution is business process management within a local bank. The environment involves handling various banking operations and customer interactions, where the solution aids in streamlining and automating processes.

The platform has significantly improved organizational efficiency by automating complex processes and enhancing operational flexibility. It has facilitated smoother workflow management and integration with existing systems, improving overall productivity.

The product's most valuable features include its adaptability and flexibility, attributed to its Java-based architecture. It allows for easy updates and incorporation of new features, ensuring the solution remains relevant and effective in meeting changing business needs.

The product's artificial intelligence capabilities could be improved. More advanced AI features could further optimize process automation and decision-making.

I have been using Pega BPM for approximately three years.

The solution generally maintains good stability. It is designed with dual balances to ensure continuous operation even if one server fails.

The platform is highly scalable, accommodating the growth of organizations and adapting to increased demands effectively.

We previously used a different business process management tool but switched to Pega BPM due to its superior flexibility and adaptability to our specific needs.

The initial setup was straightforward and self-explanatory, taking approximately one day to complete.

The implementation was conducted in-house, and no vendor team was involved. Our internal team handled the process efficiently.

The return on investment is substantial, ranging from 3o% to 80%, with visible improvements and benefits typically realized within a short period.

The product pricing is considered reasonable compared to other solutions in the market.

We evaluated several options, including IBM BPM and Oracle BPM. 

Overall, the solution is highly effective for business process management. However, to fully leverage its capabilities, you must stay updated with the latest features and improvements.

I rate it an eight out of ten. 

PegaRULES is used more for business process management. Perhaps in a bank or any other organization. If you want to automate anything, you may require a tool, which is, simply building the same thing in Java. 

People choose Pega because it's a flow-oriented tool that is already predefined and you can plug and play.

I can say that less development effort is required for developers, allowing them to focus on business problems rather than technical issues. It corresponds to every BPM, so it serves the same function.

Pega also sells the same so that you can integrate with legacy applications or with different applications that may or may not have AP capability. You can use UiPath in between with PegaRULES integration.

There are a lot of features, which most people prefer.

Case Management is the most valuable feature of PegaRULES, which is not found in other BPM tools.

Containerization should be improved in relation to Pega because Camunda is deployable in the containerization deployment process. Pega is trying to move in that direction, but that will have to improve slightly.

I have been using PegaRULES for 15 years.

Pega has multiple models, and I believe a few teams are cloud-based. Our organization is mostly moving to the cloud, but not entirely. However, we use on-premises deployment.

PegaRULES is extremely stable. It is still dependent on developers. 

Initially, I believe we will require the services of architects to set up the cloud structure and design. Everything must be thoroughly reviewed. Developers will need to follow suit. In terms of stability, I would say it's a solid application. How you use it is determined by how you built it. You must exercise caution when developing the application. If teams attempt to build the Pega without the necessary experience, performance issues and other issues may arise. That design must be correct, and it must be reviewed and monitored. I believe it will be able to stabilize this application.

It can also be scaled up. It is determined by the scope of the data, but it can be scaled up to meet the requirements of the application. It's in hardware and adding hardware to an extra. It will follow the data availability features. Pega will support the ability of Java applications to scale up based on stability. I don't know much about that particular hardware side, but I can say that it can scale up to meet the needs of the user. It is dependent on the application or how large these applications are. It can be scaled to any size.

The number of users is dependent on the project. There are large projects that may involve 10,000 or more users. In a few applications, you may see only 1,000 or 500 users or something along those lines. It is dependent on the application and who is using it.

I have contacted technical support, and they are very good.

The technical support for Pega is excellent. They were able to assist us and even guide us if we had any issues. If you contact Pega technical support, we'll find a solution right away.

I would rate them a five out of five.

Positive

We mostly use Pega products.

Pega provides documentation. The same documentation can be followed during their own deployment process.

In my opinion, it's not complicated in terms of deployment; but it depends on how your applications will be deployed. It's the same method. 

Pega will also assist you in this regard. It simplifies the deployment process and makes it easier to set up others.

I would rate the initial setup a five out of five.

If everything works and is ready, the initial setup can be deployed in half a day.

In terms of the price, if I were to compare Pega to other tools, it would be more expensive, but it would also provide you with the same features.

If there are applications that scale up to the enterprise level, we would go with Pega, and if it's a smaller application with a smaller workflow, or if they can't afford to invest that much money, they'll go with less expensive tools such as Appian. Camunda is open source, we have people working on it.

The licensing fees are not that much.

I would rate PegaRULES an eight out of ten.

I work in the automobile industry, and I generally use Pega for automating regulations and warranty applications.

Currently, we are in a project where the return on investment is less than six months, which is quite noticeable. Time savings are about three hundred percent when building an application in Pega compared to building in Java.

It's an end-to-end solution and a digital transformation tool. It has a range of modern technologies and proven designs built into it, making it a one-stop solution for many industries, including banking, insurance, automobile, and government. It includes AI, has decision-making capability, and is a rich case management tool.

The UI layer is a concern since it is native to them and embedded into the code. I cannot have my own UI layer at the moment. Also, finding a person with the right knowledge for Pega, since it has fewer resources available, is a challenge.

I have been using it for 18 years now.

When you say stable, it all depends on how you have approached the application or the design. If you choose it and design it correctly, it is 100% sustainable.

There is no need to be concerned about scalability. It is scalable across regions and divisions.

The support is okay. I would rate it as six or seven. They have a process-driven approach that can delay problem-solving.

Neutral

I have used WorkFusion and Kofax in one of the solutions. However, Pega clearly outperforms them in all aspects.

As a cloud-based solution, it's a click away. If you are talking about on-premises, it hardly takes an hour, and one person is enough for installation.

Currently, we are working on a project where our return on investment is less than six months.

Pega is at the higher side of medium pricing, but with the cloud, it should be manageable.

I have used WorkFusion and Kofax before. However, Pega clearly outperforms them.

I'd rate the solution nine out of ten.

Our customers range from banking to insurance to telco. In banking, customers use Pega for marketing, sales management, and onboarding processes as in loan onboarding or customer onboarding. They also use it for customer service, for example, when a customer calls up the bank to handle a payment inquiry or a problem. Pega also handles collections. We also deal with many of the operational processes inside the banks. 

In insurance, we work with Pega on property, casualty, and health. In insurance, we have built underwriting systems, and systems to manage attack claims, as well as the sales and customer management service part.

When it comes to telcos, it's primarily in the marketing area. Besides that, we have customers in the government sector. So, in government sectors, it is primarily to automate many of the citizen services, as well as to automate many other online operations.

Pega has traditionally been very good in inclusion automation, which primarily deals with case management, and following the automation along any other processes.

Pega has a capability called the Pega series, which is a customer lesson hub. With it, you can offer or create a business conversation with the customer. For example, if a customer comes onto a bank's website and they're searching for a loan, we have to present the right offer to the customer in milliseconds. With Pega, you can quickly understand the customer and therefore be able to present the right, most personalized offer to them.

Many customers use Pega for customer service also. It's quite useful for that.

It is stable.

We find the product to be scalable. 

Customers expect more out-of-the-box solutions. Right now, Pega is a platform on which you can build anything; as a platform, it's very powerful. However, what customers also expect is a quick turnaround. That is one area where they can improve. If they could create more business-friendly, customer-friendly solutions in the areas where customers traditionally use Pega, that would be helpful. That way, the same solution can solve similar problems for other customers, and it is more plug-and-play.

They are building in process mining. They acquired a technology company in Brazil, so they're bringing process mining over into the product. Process mining will help the customers to do continuous business implementations since they will find challenges to help adjust processes. That is one thing that we're looking forward to. 

We've been a Pega partner for seven years. 

From a stability point of view, Pega is increasingly used in markets like Southeast Asia, where the volumes are very high. From that perspective, it's able to handle large volumes. Also, as a modern SaaS technology, it is compliant with all the standards which are required. It is very compliant and very stable.

When it comes to using software in a low-volume market and a few of the other smaller markets, scalability is not much of a factor. When it comes to implementation in countries in Southeast Asia like Vietnam or Indonesia, then the volumes are very high, and we have seen Pega stand up to those challenges. It is scalable.

Technical support on Pega has improved in recent days with the advent of the cloud. If there is any kind of improvements that are required, Pega manages that.

For anything where any of the customers require advanced support from Pega, the support team is always available. They have specialized teams now to basically provide the exact support that is needed. Earlier, it used to be one team. Now, most specialized teams are available on Pega to provide the required support based on the need.

The initial setup is very straightforward, although if it is a customer who is new, they might find it challenging. If they involve the right system integrator, then along with the right system integrator, I don't see a challenge there.

Pega is also available on the cloud as well as on-prem. It is one of the few types of software which is available both on-prem and on the cloud. With the cloud solution, starting up is pretty easy. A successful setup is basically a combination of using the right partner and going onto the cloud to reduce the initial friction to onboard Pega.

From a staff point of view, for a standard application, it requires 10 to 12 resources, and they would involve people who are lead architects and developers.

It would require business analysts or someone who can work with the business to understand and visualize the solution.

It requires one engagement lead to work with the customer and manage the entire project and one or two clusters. With a team of 10 people, we have seen we can deliver end-to-end applications on Pega quite easily.

When it comes to maintenance on production, it requires a team of either two or three based on the size of the application.

We have witnessed an ROI. 

It varies based on the business case of the customer. For traditional operational processes where either the operation process is not automated - or even if is - it can create time-saving scenarios. 

In the scenarios where Pega is used in the market capabilities where it's more for offer generation or to upsell and cross-sell to the customers, we have seen an uptick in the revenue as Pega did show a conversion-based increase in outcomes.

When it comes to other scenarios, like based on the business context, if it is a customer's service application, that's where we have seen Pega help improve the average call handling. It has the capability of RPA. Therefore, during the call with the customer, if you have to fit information from other systems and quickly provide all the information in a very short time in front of the call center representative. It has helped reduce the average call handling time and the number of FTS required to manage customer service.

Therefore, it has had an impact on customer satisfaction, as well as reducing the overall cost related to servicing customers.

We are one of the largest Pega partners.

They have a primary product: case management, clean automation, and customer engagement. Various customers will be in various versions of Pega, and we deal with all versions.

If customers require an enterprise-wide implementation, they should be aware that there are requirements that are specific to the various lines of business. If they require such complexity to be addressed in a very specialized way, Pega can work well.

I'd rate the solution nine out of ten.

The rule engines work well.

It is a stable product.

The solution could be more scalable. 

It has some DevOps limitations.

The product could be more robust and faster compared to what they have right now.

Pega is also stable. It is also an old product. They have DevOps limitations if we compare it with Appian. That said, from the tool perspective, Pega is stable and reliable.

It is not as scalable, as, for example, Appian. However, I don't have extensive knowledge and therefore can't speak widely on the scaling process. 

I've never contacted technical support. I'm not sure if they are helpful and responsive. I've never talked directly with them. 

I've also used Appian.

I have limited experience with Pega. I don't have extensive knowledge about the Pega, however, there are a few things, which may be the reason to prefer Appian over the Pega. The engines, the rule engines, internally, on Appian or Pega work. However, in terms of how they process your request Appian is more scalable and more robust.

The setup is also good. It also provides the cloud, so it's not an issue from that perspective. I did not use it very extensively, however, they do have a cloud, so it's fine in terms of implementation.

I can't speak about the exact costs. I don't deal with that aspect of the solution. 

I don't have that much experience on the Pega, however, from what I have experienced, there's a little bit more that can be offered. I'd rate it a six out of ten.

The solution is used in banking, telecoms, and in insurance.

In certain circumstances, it can be fairly straightforward to execute and deploy new modifications.

The usability of the solution for developers is sometimes difficult to work with because instead of fixing the existing bugs in the previous version, there is always a rush to push out a new version leaving the bugs in the old versions unresolved. I would like the bugs to be fixed before moving on to a new version.

Upgrading versions is a challenge and expensive. PegaRULES should try to spend more time on developing the newest versions in such a way the upgrade could be easier, or in a way that clients don't need to upgrade every year to a new version or every couple of years in order to plan expenses and complicated upgrades.

The UI needs reworking. PegaRULES has added new features to the UI, but I'm not sure it's the right direction.

I have been using the solution for over ten years.                                                                                        

I give the stability a five out of ten. The solution is not the most stable solution available.

I rate the scalability of the solution a five out of ten, taking into account the requirements, user base, licensing, and hardware constraints that could potentially limit scalability.

The technical support is responsive, but sometimes negotiation is necessary to get the materials needed to address simple bugs. When working on a complex project sometimes patches can be found and the response is usually helpful. Often they'll come back with a fix and point to where the problem lies, however, there have been occasions where upgrading to the next version is the only solution, regardless of whether it is feasible for the client or even possible.

Neutral

The initial setup is challenging. I give the initial setup a three out of ten.

Some clients work with older versions and eventually choose to upgrade, which can take anywhere from five to ten years. This upgrade process is very expensive; although I haven't been on the sales team responsible for the pricing, I know it costs millions of dollars.

I give the price a five out of ten.

I give the solution a five out of ten.

We have around 20 people using the solution in our organization.

PegaRULES approach is unique; its own hierarchy and structure of applications are distinct from most other similar tools; which are more object-oriented and adhere to traditional methods.

The solution offers business process modeling when it comes to processing your models or maybe your workflows. 

Every company will have a process where it goes from case initiation to different stages based on the business need or business requirement. Pega helps get processes routed to different or next stages depending on the business rules and based on where it needs to be routed. 

Out of the box, Pega provides processes where the assignment will be picked based on some criteria or many other attributes. It's purely based on your business needs. It ensures the process is routed through the correct criteria from start to end and helps manage the entire flow, the process, and everything.

The solution offers many use cases. 

The case management is great. 

Pega provides a lot of advanced smart shapes wherein you can just create a case for using the smart case itself. You can integrate or maybe add any integration points you need there. 

A lot of Pega is out-of-the-box. You can use it as is or configure it in just one click.

The UI part needs improvement. 

Some integrations can make it unstable. They need to strengthen the integration aspect and make the process more seamless. 

It would be nice if Pega provided suggestions while users were on it. It already gives you some warnings, however, in relation to specific rules, it would be ideal if Pega could provide suggestions to help users make improvements here or there.

I've used the solution in almost every project I've worked on. 

We have hundreds of people using the solution in our company. 

The scalability is good in general. I would rate the ability to scale eight out of ten. 

Technical support has been good overall. 

Positive

I worked on a Vis ID tool and a BPM tool. It was for a short span of time. Pega was far better than that.

While it is not too complex to set up, you do need to understand the solution and know the rules. 

We have people in place just to set up the pipeline and everything. The Pega team has to work with the system team to set up everything and maybe one or two people are involved over there. From the core setup perspective, it's the role of a developer who has to do it. There's typically a lead and two or three developers that handle the setup and validate things once deployed. 

We did have some help from Pega during the initial implementation. Mostly, we handled the setup in-house. 

We have witnessed an ROI while using the solution. 

The pricing is quite good in general. I'd rate it nine out of ten in terms of affordability.

We've deployed the solution both on-premises and on the cloud.

It's a pretty good tool. If you're using it as an adjusted rules engine, Pega gives you the flexibility to integrate with different applications seamlessly. You can give the responses back as well. It has scalability. It makes it easy to maintain rules and you can delegate things seamlessly from Pega when you're doing that. 

I'd rate it nine out of ten overall. 

The primary use case includes working with Pega Platform, but the organization is planning to switch to another solution soon.

While there may be stability issues, they are minimal.

The technical support is very low, rated at a one or two out of ten. There is a lack of support and community presence in the country, leading to challenges in finding developers.

There have been some stability issues, however, they are not significant.

The technical support from Pega is very low, rating a one or two out of ten.

Negative

The pricing is expensive, and this is an issue.

The organization is in the process of selecting a new solution.

I'd rate the solution seven out of ten.