I used BizFlow. Nintex is more of a no-code or low-code solution. If you are thinking about a more custom solution, you will never choose Nintex. But, for a small organization and project, you can definitely go with Nintex. 

On the other hand, BizFlow can work in every scenario, in every work. It’s a little bit difficult to go with the custom things. But, you can achieve whatever you want.

We opted for K2 because K2 is very easy to use, and it gives you room to customize the way you want your forms to look and the way you want the data to be presented, whether as PDF or SysTrack. It's very easy to use. And we can assign tasks to certain users of our products to review what has been initiated and then approved. So all those things remove the paperwork within the organization. That's the reason why we opted for K2. We don't want the files to be passed around from one person to another. We are just removing that hassle and trying to automate the process using the K2 application.

We still want to use K2. We will likely be upgrading. We're hoping that the migration will be easy.

If we change solutions, we might consider Nintex Workflow, however, we're not sure if that would be too much work and we would be starting from scratch. If we have to start from scratch with K2 as well, we might switch over and try something else. 

Nintex may also offer RPA, which would make it a bit more robust.

We had previously evaluated other workflow engines, a Russian product. We also used SharePoint Nintex. We switched to K2 since we use Visual Studio for the automation process and to develop our own portal using ASP.NET. So, we don't want more than the required license for forms and other components that we don't need or don't use.

We have worked with Nintex and SharePoint.

Previously, we used Lotus Notes for workflows and approvals. 

While I have used other solutions in the past, I'm not really an expert in others. 

SharePoint Designer and Visual Studio are alternatives, as are K2 and a few newer players in the visual workflow and forms design arena. These tools tend to be far more technical to use, harder to support, and also have limitations not inherent to Nintex. While Nintex is an expensive solution, the value can be returned very quickly, with the quick development and go-live cycle, as compared to traditional or competitor tools. This is a key value for Nintex.

Nintex was chosen as the first option.

I used previously K2, then after Nintex bought K2, we are now using them both. 

The main difference is K2 is used for complex and deep processes. While this solution is used for simple to moderately complicated processes.

I worked with Nintex for a few years. Recently, after I ran a comparison between K2 and Nintex, I've been working for six months on the K2 platform. I've found it very useful, and very easy in comparison. However, I still use both. Nintex acquired K2 recently.

I have used Pega and I feel that it offers more than the K2 solution, in terms of the latest technology. For example, I like their implementation of the AI and the robotics inside of their system.

K2 is my first and only one solution that I recommend.

We actually don't need this solution in our own company. We have a demo platform that we implement because we are developing software, so we don't need this solution. We use alternative management stuff.

Previously, we did not use another solution, it was our first test workflow system.

We have used a number of products, and we are very happy with Nintex.