Nintex offers a platform that helps companies discover, automate, and optimize business processes.
$480
Minimum 1,000 users per user
Pega Platform
Score 5.7 out of 10
N/A
Pega Platform is a combined business process management and robotic process automation (RPA) platform with advanced workforce analytics from Pegasystems.
$35
per month per user* (or $0.45 per case**)
Pricing
Nintex
Pega Platform
Editions & Modules
Enterprise - Process Platform
$480
Minimum 1,000 users per user
Professional - Process Platform
150,000
per year
Expert - Process Platform
185,000
per year
Custom
Personalized Quote
Low-code Factory Edition
$35
per month per user* (or $0.45 per case**)
Standard Edition
$90
per month per user* (or $0.80 per case**)
Enterprise Edition
Custom Quote
Offerings
Pricing Offerings
Nintex
Pega Platform
Free Trial
Yes
Yes
Free/Freemium Version
No
No
Premium Consulting/Integration Services
No
No
Entry-level Setup Fee
Optional
No setup fee
Additional Details
—
*500 named user minimum. Additional users available in blocks of 100. Billed annually. Based on a 3-year term.
**350,000 cases / year minimum. Additional cases available in blocks of 150,000.
We selected Nintex because Process Manager is a purpose designed platform for knowledge management. However, what we discovered is that there are significant limitations, which has lead us to now explore developing a knowledge management platoform in sharepoint. this is a much …
Microsoft environment does not have the scalability of Nintex; it is perfect for small and medium-sized companies, especially in environments where Microsoft environment is almost entirely used. Although Microsoft offers options to connect to other applications, its platform …
Nintex Process Platform is a great tool for automatic tasks and creating forms in SharePoint Online. For automating using other applications, including third party, Power Automate has more usage.
Xmind was great for mind mapping, but when I tried to use it as a process mapper, I found it was rather lacking. It has its uses, but process mapping (at least for us in our stage and phase of mapping) was not up to the task, unfortunately. We didn't have any other software we …
We use Outsystems for other processes in our operation but we see that this platform is not able to indentify processes when drawed. Besides that OutSystems requires some basic development knowledge to use it. This makes it not really useable for business units.
Nintex workflows has much complex process management tools and better integration tools than Microsoft Power Platform. Being able to host it on premises is also an important feature for companies that are not cloud fans.
Nintex was selected because it was somewhat unique in its capabilities and depth/breadth of ability 7+ years ago. However, the competition has now caught up and pricing is a significant factor in whether we continue to use Nintex going forward.
Nintex Process Platform was and still is by far the most flexible and easy-to-use than any of the other form creation and workflow designer apps we looked at.
It's much more reasonably priced and we were able to actually experience the platform for a bit before we made a decision. And by the time our demo was finished we had already started depending on it for some of our processes so it would've been very hard to separate from it.
We use Microsoft Power Automate as well in our organization but used Nintex Automation Cloud workflows for most of the automation workflows because NWC is low code solution to develop automation workflows for SharePoint, integrate well with Microsoft teams, better designer tool …
We are using Nintex for SharePoint 2016 forms and workflows only for all kinds of automation. It has the following benefits over others. It is faster than working with the old SharePoint Designer and its
textual design or Visual Studio with coding. Less complex workflow can
Pega Platform has more functionality that is relevant for our business such as templates, categories and an audit trail that helps us better manage our knowledge base. Ultimately these added features and the ability to also manage workflow within the same tool made it a no …
Salesforce is much faster, but you can’t complete the same things in it. Pega does work well with Salesforce though and can track cases. Pega requires a lot more setup and training than Salesforce, at least at my company. I don’t even know if Salesforce offers the same thing as …
Pega was by far the best one on leveraging AI and BPM to drive 1-1 personalization. Pega Next-Best-Action capabilities were definitely what made us choose them among the competition. Moreover, Pega has a robust community of users that made us feel we were making the right …
Pega RPA and UIPath both are tools for Robotic process automation. In our projects we were dealing with Pega applications which are easily coupled with Pega RPA. It is better in a multi-threading environment as separate features are provided in Pega RPA. In UIPath, one needs to …
Our business needs have a lot of dealing wherein case management is of utmost importance. We had to have a concrete structure of cases, child cases, and their binding cases. Also, data appropriation and its synchronization in these particular cases also play a very important …
Pega is a browser portal verses with Oracle you get an installed console and BUI Pega is Java base. If you need software you can manage with not coding, Pega is a good option however you can still do so much with the OSC without any coding. JIRA would be better for service desk …
Pega Platform provided me the many OOTB features like SLA, Workflow, Reports, which are very much needed for my application development with very minimal or no changes. Even customization is very simple and robust. Business rule management is very much needed in my application, …
Pega was who we first chose, but due to the high learning curve and really needing developers who knew CODE, we were forced to look at other solutions like UiPath.
I can only compare it to our legacy ticketing system we were using previously (based in Remedy) and Pega far outfunctions that system. It provides us the ability to customize intake forms, business rules, and reporting that far outperforms Remedy. We can also intergrate Pega …
We used Salesforce.com and Orcle CRM. Later, after creating a couple of mock applications, we found Pega was best suited to our customer business process.
Pega Platform is the best BPM tool with more modularity, scalability and the best case management features. Very suitable for Banking, health insurance, and finance projects. The platform is used by analysts, developers and a number of other roles within a single Pega …
We did evaluate multiple products offerings with Pega Platform capabilities and observed that Pega PRPC rules engine and case management capabilities are better over so many BPM Tools. We also conducted a detailed study with developers to identify the best products out of Suite …
Pega offers a business-friendly toolkit for defining applications. Unlike traditional BPM tools, there is much fewer complications, the technical syntax to handle in modeling processes and hardly any hard-coded programming. A well-trained business user can be trusted to create …
Cheaper than TIBCO and has a better front-end as compared to TIBCO. Cheaper than Salesforce when the target audience is the internal customers like call center agents and claim specialists.
The Nintex K2 platform is not only efficient and developer-friendly, but the support provided by the vendor is also highly commendable. The platform's ease of use and robust functionality make it a preferred choice for developers, while the vendor's exceptional support ensures smooth implementation and ongoing assistance, enhancing overall user satisfaction.
Pega [RPA] is good to address a specific business function requirement with not too many bots or automation processes. It takes time and effort to set it up. Though once done, it is very easy to configure and use. One should also run a POC to verify if this product meets the scalability requirements.
Pega’s Situational layer cake architecture is capable of organizing application to suit enterprise needs. An enterprise can have a complex organization structure located around the globe. Because of Situational layer cake architecture reusing common policies and procedures is easy while allowing for differences between products, regions, channels and customer segments.Whereas with some application development platforms, separate copies of the application should be created to suite different business context.
Faster application delivery
With Pega developers can reuse common policies and procedures, replicate functions and industry specific frameworks and utilize pega UI elements to develop applications. IT is easy to deploy.Therefore developers are capable of delivering application earlier compared to some application development platforms. Pega reduces time taken to deliver an outcome.
Pega upgrades
Pega platform is upddated to adapt and work with latest technologies.
Proprietary users support and maintain Pega platform continuously. Pega customer support is always willing to enhance product support.
Difficult to fix flows that are in process (such as re-assigning a task for someone that is OOO or has left the company).
Nintex support team does not have resolution SLAs (only acknowledgment SLAs). Occasionally this has led to key issues taking weeks to resolve.
The number of integrations available is impressive, however, sometimes key methods are not available within an integration. This has been improving significantly in the past 2 years as the platform has matured.
Reporting is not extensive in Pega. Because of this higher management is not able to get the reports which will give them insights into a different area. So Reporting functionality can be improved in Pega.
Organizations that want to fully use all the features of the Pega 7 platform must follow Pega’s solution development methodology which may not be aligned fully with the organization objectives.
During upgrades, some of the rules which are deprecated have to be changed to new available rules. This becomes a problem as one has to understand all the functionality and then change a lot of things.
Renewal is mainly on the fact that Nintex is so widely used and it would be impossible to migrate all of these existing workflows to another engine. Third-party lock-in within SharePoint is pretty strong, which makes it difficult to move to something else. Our Nintex database is well-over 100 GBs. Nintex email support is very good, and I've been impressed. The Community however is non-existent and filled with unanswered questions.
Pegasystems has continued to demonstrate a strong partnership with our organization and investment in their product that aligns with our overall vision and need. Pegasystems has engaged us at every level, with the assistance of minor defects to the overall roadmap planning and alignment of our goals
Nintex Workflow does exactly what it is advertised to do: make workflow development fast and easy. It doesn't provide very much new functionality, but it isn't really supposed to. When I am working with a client on a SharePoint project, I am always happy if I hear that they use Nintex Workflow, as it makes workflows much easier.
Pega Platform is enhancing its product and launching new features day by day which help to achieve customers needs. If I talk about the earlier version of Pega Platform (i.e. pega v5 and 6.3) there were many numbers of limitations in Pega Platform and if we need to do some customization then needed to write custom java and jave scripts to achieve the functionally. Now I can say Pega Platform is running with market trends and demand. Pega Platform is giving all the options which support the current technologies like decisioning capabilities, real time processing, mashup, process fabrics etc..
The Nintex Process Platform has never crashed or had any availability issues during my usage. However there was an issue that was of my own making that caused a slowdown of the system. I had set up a process to run once a day and check for employees on a list that had certain parameters selected, and for some reason that I had to troubleshoot, the process instead ran constantly, which filled the cache quickly. I ended up having to dismantle that process so the system didn't crash.
Unlike any other process automation product out there. Not only is it a low-code, easy to use tool for building processes in environments like SharePoint or Salesforce, they have really started to expand their tool-set by offering tools to manage other things like process mapping, RPA, mobile,etc.
The support team works as fast as they can and they are usually fast to solver the issues. Sometimes they need more time to solve one of them because our workflows and so on are more complex than usual clients.
It’s very slow sometimes, but that may be our servers. Also the Knowledge Library needs some work - again, not sure if it’s our setup or what- but I’m unable to search the body of an article for content, so I have to be very intentional with tagging, but it’s not ideal.
I used the Nintex training software, it was easy to watch and follow along. It didn't go too fast and was descriptive enough to understand what the steps needed were in order to produce efficient workflows and user friendly forms.
1.Start with Simple Workflows: Begin with basic workflows to gain user confidence before tackling complex processes. 2.Involve Stakeholders Early: Engage business users and IT early to align workflows with real business needs. 3.Comprehensive Training: Invest in user training to ensure smooth adoption and reduce resistance. 4.Leverage Prebuilt Templates: Use Nintex’s templates to speed up implementation and maintain consistency. 5.Iterate and Optimize: Continuously improve workflows based on user feedback and performance metrics.
I was not part of selecting Nintex, but I think Nintex does a better job of generating linear flowcharts vs. Microsoft Visio because it automates the majority of the process of creating process maps. (Microsoft Visio is better for creating flowcharts that are not linear. because it is less automated and more flexible.)
We did evaluate multiple products offerings with Pega Platform capabilities and observed that Pega PRPC rules engine and case management capabilities are better over so many BPM Tools. We also conducted a detailed study with developers to identify the best products out of Suite of BPM products. It's observed that Rules engines integration is very streamlined with forms in Pega whereas other tools multiple have powerful data model capabilities but lacks the ease of creating business rules.
The scalability is really bottlenecked by the imagination of the user. I was able to make processes for my own personal usage, making my daily tasks easier. I was also able to make processes that affected hundreds of employees, making large standardization and efficiency gains. So either way, the system is used the same way, and I was the limiting factor.
People have woken up to the amount of overlap after mapping their processes.
People can be resistant to process changes. You need to have the support from above or support from the 'business' that you are process changing to be able to see the positive impacts.
Numbers talk. if you can get a general salary figure from your HR dept to show savings for 'employee bands', then when you present reports, they will be all the richer in data.