What advice do you have for others considering Pega BPM?

I would recommend Pega to organizations with good financial resources. For middle-layer industries, it may not be the best choice due to revenue considerations. I'd rate the solution ten out of ten.

The flexibility and comprehensive frameworks available with Pega make it a preferred choice for me. I'd rate the solution eight out of ten.

I'd rate the solution nine out of ten.

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.

When it comes to Pega, I haven't come across any particularly outstanding out-of-the-box functionalities. However, I appreciate their local, no-code approach, which makes it easy for users to quickly grasp how to create work solutions. Although case management is included, it doesn't seem as flashy compared to other VPNs. Pega was coming with lot of out of the box integration options with APIs and others but, we did not drive the AI part. Based on the specific use case, I would recommend it to companies prioritizing user functionality over scalability in their portfolio. However, it's crucial to collaborate with a skilled integrator to ensure smooth implementation. Overall, I rate the solution a seven out of ten.

We are using the solution's case management, many finance-related modules, and some frameworks. The solution's case management function has improved our daily operations. It was easy to customize Pega BPM for our industry. The solution handles some industry-leading tasks, like legal compliance. Pega BPM has a huge offering, which includes CLM (Contract Lifecycle Management) and many frameworks built into their packages to comply with industry standards. Pega BPM is deployed mostly on-premises in banks for data security. Other BPM services, such as Oracle BPM, IBM BPM, Appian BPM, and Camunda BPM, are available in the market. Small and medium enterprises have different needs and different costs. Pega BPM simplifies the modeling of a typical low-code workflow and data. There are other use cases where some other tool works better. Recommending Pega BPM depends on the business needs and journeys. Using the solution varies from case to case and depends on cost, complexity, infrastructure, and all other associated things that come with it. Overall, I rate the solution an eight out of ten.

Pega BPM and other solutions from the vendor are all low-code solutions. Especially in the Middle East and African markets, our company has noticed that they are more focused on front-end development; therefore, often, a customized UI is required, which cannot be implemented with Pega due to low code functionality and standard principles defined in the platform. But Pega BPM offers an integrated case flow and customer service, which contributes to the vendor becoming a world leader. There are AI-driven business process management features being incorporated in the solution. For instance, if you mention the vendor about your plan to develop a loan application, they build the entire case flow for you and make the application available within an extremely short span, after which the connectors and APIs need to be set up and integrated. Pega BPM is a highly advanced solution. At our company, we also evaluate if a customer actually needs Pega solutions before recommending it. For instance, if Pega is considered the Ferrari of the industry and the customer is willing to drive at a speed of 10 to 20 Km/h, then it's not worth the cost. For basic requirements, a customer can choose Comodo when only the BPM layer and custom UI are needed to build native mobile apps, while the workflow remains on Comodo. Pega is the leader in business process management solutions. Pega creates market trends across the globe. If you check Forrester or Gartner reports, Pega has always been rated as the top BPM solution provider. Other competitor companies learn from Pega and implement improvements in their products. Pega is not considered a front-end portal platform. The limitations of Pega are quite logical. The product owner of Pega mentioned that to build a low-code rapid development platform, it is mandatory to provide templates. For example, in MS Word, you can use the numerous templates or start from a blank template. The templates in Pega are pre-defined; they cannot be customized; when starting from scratch in a solution, it won't be considered as a low-code solution. Pega needs to find a way to implement low code even with a blank template. Pega is working on a new product line called Constellation in which the aforementioned issue will probably get resolved. I would overall rate Pega BPM an eight out of ten. There are still some challenges with the front-end aspect of the solution, but the product is best when it comes to business processes and customer service management. The European and American customers of our company are more keen on the process flow rather than the application appearance at the front-end. But for customers who are focused on the front-end more than what's underneath the Pega product, it becomes very difficult to make them understand the value of Pega. I expect the vendor to implement improvements on the front-end.

I recommend Pega BPM to others and rate it an eight out of ten.

I would say the people who have realistic business process management kinds of use cases can go ahead and purchase Pega BPM blindfolded since it serves as a great case management tool, better than any other tool in the market. Pega BPM provides great visibility to its users, especially when you are involved in designing, where it will show you the number of stages, steps, processes, data, and even the people or parties who were involved, making it a great tool for case management. Presently, Pega BPM is heading towards the inclusion of more AI, owing to which it can be considered as one of the leaders in the market. The CRM part of the solution is one of its key selling features. Though the solution's UX is good for developers, when you have to deliver the product to the customer, you don't get too many options for customization that can help you create an appealing view. I rate the overall solution an eight and a half to nine out of ten.

I am using the latest version of Pega BPM. When we started, it was a team of 10, and now 23 employees are involved in the solution's deployment and maintenance. The solution has nine to ten developers and testers. Overall, I rate Pega BPM a seven out of ten.

This product is suitable for pretty much any size of organization. I rate this solution eight out of 10.

We have 30 people for the maintenance of the solution. I rate Pega BPM n eight out of ten.

As far as maintaining this solution goes, how extensive it is will depend on whether or not you will be maintaining just Pega. It allows you to delegate many of the business rules to business users where they themselves can actually go and configure their rules and modify them. A user can have their own dedicated set of rules that they can go and configure. Overall, I would rate this solution an eight, on a scale from one to 10, with one being the worst and 10 being the best.

I handle different projects that use Pega BPM. Some use version 8.5, while others use 8.7. I also have some using version 8.8 of Pega BPM. Pega BPM is deployed differently for different projects. Some on the public cloud and Pega Cloud on AWS. Some deployed Pega BPM on-premises, while others deployed the solution on a private cloud. All three versions of infrastructure can be used for Pega BPM. My organization is a pure Pega organization, so out of one thousand people, at least six hundred people within my organization work on Pega BPM, but my organization is a service organization with different clients. It's an elite partner of Pega, and only ten elite Pega partners exist worldwide. My rating for Pega BPM is eight out of ten.

I would rate Pega BPM an eight out of ten.

The business process management solution my team uses is Pega BPM, particularly the older version 7. My team is planning to onboard the new version of the solution, version 8, soon. Maintaining Pega BPM is sometimes expensive, but it's manageable. It takes money to maintain the solution, but it's a good product based on the service it provides to customers. Pricing doesn't matter because what matters to any client is that the solution should be very good and should provide accurate results. This is the main reason people go with Pega BPM. My company has a team dedicated to maintaining the solution. Five to six people currently use Pega BPM within the company. For now, I don't have any suggestions for people looking into implementing Pega BPM because for sure those people have research teams that do the research and implement the solution according to market research. They know exactly what type of solution is needed based on research. I would recommend Pega BPM to new users of BPM solutions or local platforms, but research is still required before implementing the solution. My rating for Pega BPM is nine out of ten. My company is a partner of Pega BPM with clients it provides services to. My company also provides implementation support to clients.

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

I would recommend that you work with one or two Pega developers in the initial stage. After that, it's quite straightforward. I would rate this solution as a nine out of ten. The Pega product is definitely good.

We use both cloud and on-premises deployments. In earlier days, Pega used to support only on-premises. Nowadays, it's supporting the cloud as well. I definitely do recommend the product. Pega is a competitive product if it's not a small enterprise. Small companies usually avoid this product as there are a lot of open source products that are less costly there in the market. Based on the features I can recommend it. I'd rate the solution nine out of ten.

I would recommend this solution to anyone considering implementing Pega BPM. It is a scalable, reliable platform that is suitable for many kinds of organizations. I would rate this solution a nine out of 10 overall.

Pega BPM is a very good tool if you have the budget to spend on it and you need to automate any business process wherein you get the data from multiple sources. I would rate Pega BPM as six out of ten.

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.

My organization is a service provider for Pega. We're implementation partners. If we use it completely depends on what the client wants and needs. If you are using it for the first time, you probably should have a consulted implementation partner as well. That said, it is easy to use. It shouldn't be a problem. It's very flexible. I'd rate the solution eight out of ten. We generally don't encounter any issues as far as Pega is concerned. Whenever there's an issue, there's a quick resolution.

It's important to check all options and ascertain that this is the appropriate solution for you. There are other features that products like Camunda provide, but as you need to scale and get more sophisticated in your process management, Pega becomes a better option. I rate this solution eight out of 10.

For an enterprise-level requirement where there are multiple implementation business cases, Pega BPM provides the platform that is most encompassing. 

Effectively it depends on the business case/s. 

There are some very good solutions and platforms available in the market and Pega scores very high with respect to a lot of dimensions needed in the platform for implementation.

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.

We often recommend this solution to our customers. It is a wonderful solution. There are not many professionals working with this tool which is important to note. If the core need of a customer is for BPM and automation, this is a suitable solution. If their needs exceed a BPM solution, such as modernizing different kinds of applications, there may be other suitable solutions. This is a good solution from a technical perspective and is based on a very reliable and scalable platform. I would rate this solution a nine out of ten.

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.

They should have a solid foundation of business processes in place before embarking on this journey. If the case is small or the process is not complex, they should use a smaller and simpler BPMS. The primary reason is the cost. However, if they are considering it at the enterprise level or for a more complicated process, Pega is, in my opinion, the best option. I would rate Pega BPM an eight out of ten.

The platform as a whole is very rich - you can do a lot of things with it with minimum time and cost. I would recommend Pega as a BPM solution but make sure that your contract states you will receive support, otherwise you may not get any. I would rate this solution as seven out of ten.

We are a customer and an end-user. We have been using Pega for more than six years, and at this point, we also want to just explore the other BPM tools. It's kind of for considering cost efficiency also. We are looking at the cost of the development effort or the scalability of the tool. While I like Pega, I'm just exploring the other BPM tools with respect to Pega. While it depends on the application you are using, if you're planning for an enterprise application that can interact with different applications, Pega would be a good option. Sometimes if you have a smaller workflow, for example, if you're just introducing a smaller workflow in an existing application and you just want to leverage only that workflow-related feature, you don't need Pega. You can just have any workflow tool, like Camunda or Appian. Cost-wise, Pega may cost you more. If you're planning to leverage all the features in Pega, like case management and low-code, no-code and RPA, robotic process automation, and other high level or case management, if you are planning to leverage all these different kinds of features that are available in Pega, just go with Pega. And if you're just planning to leverage only a kind of workflow, you don't need to go with Pega. You can just go with other BP flows or BPM process models like Camunda. There are a lot of features that you can explore in fault tolerance and error handling, exception handling, et cetera. There are other items as well if you're in the development stage, and something like Page will likely be helpful. I don't know of other tools that will support anything to that extent. There are still some limitations in the solution. I'd rate it at an eight out of ten, as there are still some improvements that can be made.

I rate Pega BPM a seven out of ten.

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.

This solution is one of the best tools on the market right now. I would recommend it to others. I rate Pega BPM a ten out of ten.

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

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

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.

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

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.

I would definitely let people know about it. Let me give you a scenario. Let's say there is a banking system. Generally, people come to the bank, fill out the form, and submit it. Then a record will be created in the system. So what happens by using the Pega BPM is that we can clearly identify the flow - how you do it by using the different user input tasks. This is appealing to the user, to the customers, to everyone. Definitely I would like to get a return on that and let them know that if they use this BPM tool, more than any other technology tool, it has the most complete set of tools for the system. On a scale of one to ten, I'd rate it an eight. This is because it is easier to use than any other product and it is more secure. All of our software was developed in Java and as we know Java is a secure language. There are many more features. It is easy to use, easy to understand, easy to implement and easy to enhance and we can do it as a Cloud. Also, it is very user-friendly. Nowadays, it's on Cloud so we can access it from anywhere. There is no location per se or any system requirement.

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

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.

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.

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.