Nintex offers a platform that helps companies discover, automate, and optimize business processes.
$480
Minimum 1,000 users per user
Windward Core
Score 9.1 out of 10
Enterprise companies (1,001+ employees)
Windward’s low-code document generation solution embeds into any application, enabling users to populate data-smart documents within the familiar landscape of Microsoft Office. It's a solution from PDFTron since the April 2021 acquisition.
$19
Per User, Per Month (10 user minimum)*
Pricing
Nintex
Windward Core
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
Windward Hub Standard
$19.00
Per User, Per Month (10 user minimum)*
Windward Hub Premium
$49.00
Per User, Per Month (10 user minimum)*
Windward Core Pro
$547.00
per month*
Windward Core Flex
$605.00
per month*
Windward Hub Enterprise
Custom Pricing
Offerings
Pricing Offerings
Nintex
Windward Core
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
—
*Pay annually: 15% discount
10% discount for quarterly payment of Windward Core.
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
SharePoint is a nice tool, however, it requires a lot of effort to create the forms and code for pulling in data if it's not within SharePoint itself. Maintenance of reports will require SharePoint knowledge as well. Windward removes many obstacles in traditional report …
Unfortunately, I was not involved in the research process when selecting Windward, so I can't speak to the alternatives. However, it has worked out very well for us.
Prior to Windward, we were using an HTML to PDF conversion for our reporting solution. It required substantial development to create and modify our reports and the styling was never up to our standards. Windward has certainly helped decrease our time in developing and …
We evaluated several other products to integrate with our new software, but Windward Studios was an obvious standout above the majority. Other applications required some level of software development knowledge and experience to create templates and a much steeper learning …
Again, it's been so long since I've used another reporting tool it would be hard for me to say. I just know we used a couple of components, and their report designers never offered the simplicity of designing a report directly in an MS Office document.
A weak point of WindWard is its antiquity compared to other tools already positioned within the globe of software developers. However, a critical success factor is the ease and speed to get results, and in that WindWard has a good advantage. For this reason and to be able to …
I have never used a alternative but i have peers who have used Dundas. The speed and flexability of Java Reporting Engine is much greater that that of Dundas. This had a big part to play with the Java Reporting Engine syncing with out backend much easier.
Each tool in our kit has its strengths and weaknesses. When we need to build complex reports and native Microsoft Office output is a secondary (or less) consideration, we turn to tools from Jaspersoft or InetSoft, which are great for building complex reports but are frankly …
Truthfully when I came to AmWINS this was the only product that they had as an add on to Excel. I did not do any research before coming here. I also did not know what AutoTag Template Designer was before coming here but I enjoy working with it in Excel and Word.
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.
AutoTag is a brilliant solution for less complex reports where native Microsoft Office output is required. This is where AutoTag really shines. It's also appropriate in situations where our customers want to develop and maintain their own reports but don't necessarily want to commit an experienced data person or report developer to do the work. For complex report requirements that need JavaScript or considerable data manipulation inside the report templates, we will continue to look at other tools in our kit.
AutoTag can easily be connected to virtually any data source. The wizard walks you through all the needed steps. This is very helpful in getting reports from multiple sources or departments.
WindWard has put together a Wiki based user guide and has the best tech support I have ever worked with. For the rare occasions that we get stuck trying to convert a report the help is plentiful.
AutoTag is built within the Office suite and is therefore able to leverage all the familiar features. This is very useful when you need to make reports useful and appealing.
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.
It would be very helpful if it was possible for tag logic to handle an array of data. Without it, the syntax can become very verbose when there are multiple logical conditions to check.
Most tags are only built to handle a single piece of data so it can be a little confusing when a query only appears to return 1 record.
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.
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.
For the most part, the Windward report designer is intuitive for our users; but there are a few areas where it is less intuitive. In these cases, our users need to search Windwards support wiki site, or even contact their support technicians. This can also be due to the short time we've had Windward and our lack of knowledge.
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.
Support is something they take pride in. Once an issue is raised, they are quick to respond and provide details on a fix. No complaints on support here.
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.)
Prior to Windward, we were using an HTML to PDF conversion for our reporting solution. It required substantial development to create and modify our reports and the styling was never up to our standards. Windward has certainly helped decrease our time in developing and modifying reports and has also helped us greatly improve the styling of them as well.
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.