Too expensive for typical needs
Software Version
Nintex Workflow for Office365
Overall Satisfaction with Nintex Platform
As a consultant I've used Nintex for SharePoint, Nintex for Office365, Nintex Workflow Cloud, and other BPA tools (Microsoft Power Platform and SPARK). I've used it for a variety of industries, but for the purpose of this survey I'm answering based on a Nintex for Office365 project with a pet food manufacturer's export requirements to a number of countries. The business problem is coordinating approval of product to countries with widely differing content policies.
- It is not difficult to put together a simple workflow.
- The user interface for both workflow and forms is intuitive.
- The worst thing about Nintex is that it is way too expensive for the value it provides. This has resulted in a number of lost opportunities.
- For Nintex for Office365 in particular, the use of collections and dictionaries is too complicated for most users.
- The designer performs very slow for medium- to larger-sized workflows.
- Too often a project is doomed to failure due to the complexity of the workflow. This results in lost business.
For this survey, I'm considering a particular project in Nintex for Office 365. The Office 365 deployment is easy, and this is helpful to clients that want a cloud solution fully integrated into SharePoint.
I have found that my Nintex customers are almost always a department outside of IT. If it were an IT project, a programmer can develop a code-based solution that is more manageable for larger and complex applications.
ITLAQ's SPARK/SPARKnit is not in your list of products. SPARK provides all of the basic functionality of Nintex forms and workflow at a much smaller price. The Microsoft Power Platform is inexpensive, but slightly more difficult to use.