We performed a comparison between IBM BPM and Pega BPM based on our users’ reviews in four categories. After reading the collected data, you can find our conclusion below.
Comparison Results: Pega BPM finishes slightly ahead of IBM BPM. Pega BPM is low-code and very user-friendly. It provides next-generation processes that will convert problem statements into different diagrams and then implement the process, saving time and keeping organizations running efficiently. IBM BPM has a big learning curve and lacks many basic features that other BPM solutions provide.
"It is a stale solution."
"It continues to keep up with the changing needs of the business. That is the strong value proposition of BPM. It's not a one-time automation."
"The most valuable feature for the organization is the Document Store."
"We use it for automating certain processes which previously took a lot of time for agents to set up different products for customers. They would have to enter a lot of different systems. This has now mostly been automated."
"It helps maintain, and in many instances, lower costs, as well as to maintain those costs, keeping them stable."
"It's a solid product. It covers most of the pain points for clients."
"Technical support is good. They are very responsive. It is usually me who takes more time to get back to them than they take to get back to me, which is good."
"IBM BPM is stable."
"The most valuable feature is flexibility, as we can configure it to best suit our requirements."
"The stability has been good. We haven't had any issues."
"The solution offers excellent workflows."
"Fast prototyping."
"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."
"The initial setup is pretty straightforward."
"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."
"Pega BPM offers a lot of out-of-the-box functionalities."
"We care about technology and support because support is very important and a BPM is not easy to implement."
"I have an interest around the robotic piece, and integrating that with the processes. I think that is certainly a good direction to be going."
"The price and the overall installation process could be improved."
"All our clients are changing to microservice and cloud service. However, BPM does not have a solution for microservice and cloud service."
"IBM BPM lacks openness, that is, the ability to become open for new options in terms of APIs, front-end development, and ecosystem. IBM BPM has been quite closed. One of the main improvements would be to somehow embed the rules engine into IBM BPM. Merging IBM BRMS and the rules engine with IBM BPM would be helpful. If there was some simpler way to define rules without having to put IBM BRMS on top of it, it would be good. It's something that we can get out of Camunda but not out of IBM BPM."
"This is technology, and there's always room for improvement. It would be better to have a single solution. Trying to have an overview in terms of this solution brings together the concepts of BPM processes, customer journeys, and an automation part for KPIs. All of this working together and coming up with a single solution with privacy is more commercial than anything else."
"One of the things that we are looking at is cognitive learning. IBM has another product called IBM RPA, I think, which is doing some of that stuff. We would like to see more of that with respect to cognitive learning and AI put back into the process engine to help."
"The solution can improve integration with SAP, CRM, and Salesforce, which is not capital-intensive."
"I believe that Pega's strategy when it comes to the UX part is not that great currently as compared to the other emerging BPM tools in the market."
"It needs more integration with other platforms."
"The unit testing needs to improve, as well as the user interface."
"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."
"The cost of licensing could be improved."
"Pega BPM could be improved by including token-based authentication and extending its integration options."
"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."
"The workflow automation can be slow, so there is room for improvement there."
IBM BPM is ranked 5th in Business Process Management (BPM) with 105 reviews while Pega BPM is ranked 3rd in Business Process Management (BPM) with 57 reviews. IBM BPM is rated 7.8, while Pega BPM is rated 8.2. The top reviewer of IBM BPM writes "Offers good case management and its integration with process design but there's a learning curve". On the other hand, the top reviewer of Pega BPM writes "Provides built-in frameworks that can be reused and reduces time and cost". IBM BPM is most compared with Camunda, Appian, IBM Business Automation Workflow, Apache Airflow and ServiceNow Orchestration, whereas Pega BPM is most compared with ServiceNow, Camunda, Appian, Microsoft Power Apps and OutSystems. See our IBM BPM vs. Pega BPM report.
See our list of best Business Process Management (BPM) vendors and best Process Automation vendors.
We monitor all Business Process Management (BPM) reviews to prevent fraudulent reviews and keep review quality high. We do not post reviews by company employees or direct competitors. We validate each review for authenticity via cross-reference with LinkedIn, and personal follow-up with the reviewer when necessary.