Appian vs Nintex Platform

• Repeatable process. Once implemented in Appian, you have an automated process that will always work in the same way. No more dependencies on people remembering what needs to be done or how to do it.
• Great integration with other applications. Appian allows you to integrate with many other applications to provide a seamless process flow.
• Reporting capability. Appian has the ability to report on information from any connected system to provide real-time data. Very nice graphical and textual reports can be created.
• Sites. The ability to create a place for a user to be able to perform their required job without having to see all of the other applications, reports and records. This allows a very focused approach for a user to interact with the system.
• With every release Appian adds more functionality

Read full review

• On-prem Nintex did workflow design and authoring great - it was easy to automate workflows as a non-developer
• It did a great job of approvals and reviews (a primary business need for us)
• It helped us manage business processes that were global and kept information flowing rather than keeping it stuck on an Excel file on someone's desk. It just worked very well with SharePoint.
• It was a great notification / communication tool for us; automating messaging for state-changes in Sharepoint and giving us artifacts of activity that we could use in an audit.

Read full review

• Even if Appian is working a lot on it, it should improve the low-coding features.
• Improvement of the form design not using sail.
• Foster the connection for different customers, all of them using Appian. Having a process across companies and not only offices could be great.

Read full review

• Nintex needs to hit voice of customer hard. Workflow means automation of some function. Those transactions have key components like communication, approval, review, etc. When Nintex moved to Office365, much of what was basic and easy to author in the on-prem version became very obscured or non-existent.
• Nintex servers have a tendency to bog down and get SLOOOOOOOOOOW when stressed at volume. That's true of most any system, but load balancing just didn't happen and by EOL on some of our flows, it could take 20 minutes or more for single workflows to start, to switch states, or execute an action.
• The licensing model for only allowing a fixed collection of simple workflows is not a customer requirement. If you survey voice of customer, I'm relatively certain there were no customers who said, "you know, if I could only be allowed 100 workflows of low complexity, that would really help me get my org empowered to exercise this tool to its fullest..."
• I could only edit Nintex workflow in Internet Explorer. I use a Mac as my workstation. To edit a flow, I had to fire up a VM and open IE. Making it editable in most modern browsers would be might nice.

Read full review

• Appian has reduced average call handling times in every company we have implemented it in
• Appian has allowed us to create a consistent experience for our customers and simplified our internal processes saving time and money
• Appian enables heavy re-use through out allowing us to cut development costs

Read full review

• Nintex offers process automation that simplifies business solutions. Learning how to use all of the actions is not as time consuming as other WorkFlows I have configured before.
• The learning curve on creating, maintaining and troubleshooting Nintex WorkFlows heightens productivity. Plus, I can appreciate the online courses offered on their Nintex community site along with live support assistance if and when the occasion rises.
• I have noticed less WorkFlow bottlenecks; This improves efficiency, controls expenditure of time, money, resources and drives process improvements.

Read full review