Item: Nintex Process Platform
Rating: 9
Author: Rodrigo Amigorena

Use Cases and Deployment Scope

We are currently using Nintex in our 2 SharePoint 2010 farms in international, and there is another SharePoint 2013 farm in corporate also running Nintex.

Pros and Cons

Very intuitive user interface. Very simple and responsive
No Coding Required. Any power user with basic systems knowledge can configure advanced workflows.
Advanced features are supported like State Machine Workflows.

Our main problem today with Nintex is the licensing model. We are currently licensed for on-prem but we are actively moving to SharePoint Online. However the pricing model for Online makes it almost impossible for us to adopt the product and is forcing us to seek alternative products.

Return on Investment

Unfortunately we haven't been able to measure the true ROI of Nintex since we offer the solution as a shared service and we delegated to the business teams the usage of the tool since it is very user-friendly. This means that we don't have full visibility of the benefits it brings to the business.
The cost-benefit of our On-Prem instance is highly positive as it allowed us to automate hundreds of processes that would otherwise be done manually.
Due to the high cost of Nintex Online, it is next to impossible to justify the adoption of Nintex Online since most of our business processes are simple to medium complexity, and mostly driven by power users to automate their day to day activities. For enterprise business processes we tend to implement dedicated solutions and that is where finding the ROI for the online version gets very challenging.

We are currently using it in SharePoint 2010. The deployment process in our version is not optimal as we need to export each workflow definition manually from Dev to Prod and there is no CI/CD available. I am quite sure this has evolved in the latest versions but I am not fully familiar since we implemented Nintex 2010 almost 8 years ago.

Nintex Users

Nintex is PRIMARILY being used by NON IT staff and that is the main benefit of this tool. Any power user can build and maintain their workflows without any dependency on IT.

Alternatives Considered

ServiceNow and K2 Platform

The integration of Nintex with SharePoint was seamless and the affordable cost allowed us to deploy the service as a shared platform without the need for complex charge back models to each team. Developing in ServiceNow is significantly more complex and more expensive since it must be done by certified developers instead of power users.

Other Software Used

ServiceNow, JIRA Software, Microsoft Teams

Likelihood to Recommend

Nintex is one of the best solutions I have come across in the SharePoint space. It covers a gap that very few systems support which is empowering end users to automate their day to day activities, including approvals, reminders, and any simple business process. It integrates seamlessly with Infopath although Microsoft is retiring these forms and is only offering Powerapps and Flow as alternatives which is not really a like for like replacement. That is where Nintex Forms comes in play and is the perfect replacement.

In the past we tried to use Nintex to manage complex business processes for use cases that would may have been better suited for a dedicated and custom application instead. The main limitation is really Sharepoint as an application platform, not really Nintex. But our learning was that Nintex is great for use cases where you might not need future integrations or APIs.

Benefits of Nintex on Pre vs Nintex Online

Software Version

Overall Satisfaction with Nintex Process Platform