We use Nintex to automate fundraising outreach at scale. It helps us send personalized emails to a large contact list, and we’d also like to automate follow-ups when there’s no reply. If you need highly customized solutions or clean, fully controllable code, I wouldn’t recommend Nintex. It has many features, but it’s not the same as building your own system from scratch. That said, it can save a lot of time for standard automation workflows.
A de minimis incentive was given to thank the reviewer for their time. The incentive was not used to bias or drive a particular response, nor was the incentive contingent on a positive endorsement. More Info
This software is very well-suited to companies who find themselves expanding their footprint, the number of their Sales representatives, their territories, and/or their products and services and need to maximize their ability to both keep up with those demands whilst streamlining their proposal resources. Further, this is a very powerful tool with a lot of features and functionality including CRM plug-in and reporting. Thus, it may be less appropriate for a very small organization with only one product and that is also blessed with lengthy cradle-to-grave turnaround windows. In addition, to better the odds for success an investment in upfront personnel training and either a dedicated periodic window of time and/or dedicated person(s) for content upkeep are prudent. Finally, working with the vendor is a delight as they make every effort to maintain and deliver a product that both meets your needs and on which you can rely.
Integrations with other services using various secure authentication methods, along with the seamless integration with SharePoint, are the icing on the cake. This makes it superior to other BPM tools available in the market.
Flexibility in application development - The diverse configurable properties offer multiple ways to utilise the controls and events, affording the flexibility to expand your scope and enabling the creation and use of processes in a myriad of ways.
The streamlined and efficient deployment process significantly accelerates release management, allowing for faster and smoother implementation of updates and new features.
The user interface of the pages offers a more refined and appealing look and feel compared to most other BPM tools.
A de minimis incentive was given to thank the reviewer for their time. The incentive was not used to bias or drive a particular response, nor was the incentive contingent on a positive endorsement. More Info
Using Qvidian as an RFP tool has made a difference in our RFP process, turn-around time, and content development. It's helped us streamline our RFP process so that we are able to produce the majority of the document before the kick-off meeting, which means we have more time to customize and refine the document before it goes to print.
Additionally, it took several hours before to gather all of the basic data we needed for an RFP, but now we can have the majority of the response ready in under 15 minutes in most cases. We are also able to start projects from our phones (iPhone thru Safari) or on an iPad. This has been extremely helpful while traveling.
Finally, our content is centrally located on a searchable database. Previously we had used several free tools to aid in content storage that would allow us access easily via search. It never seemed to do what we wanted, and when we did find something, we weren't sure if it was the most current or usable. The library functions in Qvidian have been a huge help, and has changes the way we collect data, and retrieve it.
If you are creating a process with parallel subprocesses, there's no way to see, in a single view in Nintex, all the steps for the subprocesses. You have to view each sub-process in its own view, so it's hard to see what's going on at a high level.
There isn't an easy way to filter the processes by another user (not yourself) in Nintex. There is a report that shows processes and objects by user, but that's not as convenient. This is something that I've seen in other tools (OpenPages by IBM) so I am surprised that it is missing.
Nintex doesn't really have a way to capture iterative processes (which we have a lot of). It's designed for linear processes.
A de minimis incentive was given to thank the reviewer for their time. The incentive was not used to bias or drive a particular response, nor was the incentive contingent on a positive endorsement. TR verified that a representative sample of customers was invited. More Info
One area where Qvidian occasionally struggles is feature regression. For instance, the editing option that puts multiple records into one document had always been present in Qvidian; however, when the multi-edit feature that only allows editing one record at a time was released in version 9.1, the original editing functionality was removed. This caused me a lot of frustration, as it severely slowed down my work flow since I could now only see and edit one record at a time. It wasn't until a year later when version 10 was released that the old editing functionality was added back. However, one bright spot of version 9.1 was an added feature that allowed organizing records by simply dragging and dropping them into different categories. This was much easier than having to right click on a record, select Move, then right click on a folder and select paste. However, with version 10, this feature was removed and I'm now back to having to right click on records instead of dragging and dropping. It seems that with each release, I never know if something I like will be taken away or if something I don't like will be added -- sometimes it's both.
A recent change that was added in version 10.1 that I personally view as a negative is that Qvidian now handles all requests server side instead of on the user's computer. This means that if a user wants to export or edit a large number of records, they have to wait for Qvidian's server to generate a report of those records. Depending on the number of records, this can be very quick (a few seconds) or very long (I've waited up to 20 minutes before) depending on how taxed Qvidian's servers currently are. I understand the reasoning behind the move, in that it takes the load off of a user's computer so that other applications they currently have open aren't affected by added memory usage, but in practice I find that it only slows down my workflow. Any somewhat modern PC shouldn't have any trouble handling a large report request from Qvidian.
Although Qvidian is certified for use in several different browsers (Internet Explorer, Firefox, and Chrome for Windows), it doesn't offer the same functionality in each one. For instance, in Explorer, when a record is selected for editing or export, it will automatically open in Word. In Firefox, a pop-up dialog appears and a user has to click Open in order for the record to appear in Word. And in Chrome, the file is added to the download bar and a user must click on the file there for it to open, unless they add an exception to .docx file types to automatically open in Word (which I had to do, since I prefer using Chrome). Other simple features such as right clicking on a folder or record to bring up Qvidian's context menu are hit or miss depending on the browser. In Explorer, everything is generally smooth, though the browser itself is slower than the other choice. In Firefox, right clicking generally works but sometimes has some hiccups, and in Chrome, more often than not right clicking brings up Chrome's context menu instead of Qvidian's, which often leads to having to first select a folder and then click the dedicated Actions button in Qvidian to perform the desired action. No matter which browser you use, there will be some sort of functionality that doesn't quite work as expected.
We are currently investigating which collaboration platform best suits our needs. Chances are that we move to SharePoint Online and then we're going to also consider the microsoft power platform (power automate and power apps) to develop forms and workflows. Aspecially the pricing model for the cloud is currently a blocking factor to go for the Nintex solution in the Cloud.
A de minimis incentive was given to thank the reviewer for their time. The incentive was not used to bias or drive a particular response, nor was the incentive contingent on a positive endorsement. TR verified that a representative sample of customers was invited. More Info
The tool provides us with the functionality we need to perform more efficiently and we have not identified another product that offers enough "nice to haves" in addition to the "must haves" to warrant a compelling reason for changing tools.
Based on the on-prem experience with this tool, I believe that they have a lot of potential to help the online version catch up to where the on-prem left off. Nintex developed their online version and it is not as fully formed or capable compared to the on-prem version, and the licensing model scales back what we would have liked to be an expansion or at least continuous improvement of existing flows. It is also not near as user friendly specifically to non-developers and has an uncanny similarity to Microsoft Flow in the online instance. Consistent with my reviews of the tool - I believe they have some good approaches to design thinking that, if translated well from on-prem to online, could make this a clear winner again.
A de minimis incentive was given to thank the reviewer for their time. The incentive was not used to bias or drive a particular response, nor was the incentive contingent on a positive endorsement. TR verified that a representative sample of customers was invited. More Info
The shift they made in architecting documents from content to outline, is now reversed allowing outline creation first, then content which is more natural. But, due to the fact that we went through a migration of content to get to the new version, it feels less optimized than if we would have re-implemented.
End users having to configure settings more often than desired
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.
A de minimis incentive was given to thank the reviewer for their time. The incentive was not used to bias or drive a particular response, nor was the incentive contingent on a positive endorsement. TR verified that a representative sample of customers was invited. More Info
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.
A de minimis incentive was given to thank the reviewer for their time. The incentive was not used to bias or drive a particular response, nor was the incentive contingent on a positive endorsement. TR verified that a representative sample of customers was invited. More Info
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.
A de minimis incentive was given to thank the reviewer for their time. The incentive was not used to bias or drive a particular response, nor was the incentive contingent on a positive endorsement. TR verified that a representative sample of customers was invited. More Info
They are very much in support of great customer service. They respond quickly with emails and in some cases phone calls to resolve any issues and often times user questions in the past when I could not figure something out.
A de minimis incentive was given to thank the reviewer for their time. The incentive was not used to bias or drive a particular response, nor was the incentive contingent on a positive endorsement. More Info
A de minimis incentive was given to thank the reviewer for their time. The incentive was not used to bias or drive a particular response, nor was the incentive contingent on a positive endorsement. TR verified that a representative sample of customers was invited. More Info
Live instructor training is expensive, though we have had instructors come to our offices for a ‘refresher’ before. The refresher was more of a “let us fix that for you” than a training on how to do it ourselves.
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.
A de minimis incentive was given to thank the reviewer for their time. The incentive was not used to bias or drive a particular response, nor was the incentive contingent on a positive endorsement. TR verified that a representative sample of customers was invited. More Info
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.
A de minimis incentive was given to thank the reviewer for their time. The incentive was not used to bias or drive a particular response, nor was the incentive contingent on a positive endorsement. TR verified that a representative sample of customers was invited. More Info
A de minimis incentive was given to thank the reviewer for their time. The incentive was not used to bias or drive a particular response, nor was the incentive contingent on a positive endorsement. More Info
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 lacks the development and robustness that Nintex provides. Nintex not only covers Microsoft environments but also Google and other important platforms.
A de minimis incentive was given to thank the reviewer for their time. The incentive was not used to bias or drive a particular response, nor was the incentive contingent on a positive endorsement. More Info
We have been using Qvidian for years, when Compass was introduced in our company. Having spent over a year using Compass, I would not recommend it for writing proposals. In all fairness, that is not Compass' strength. Compass is ok for general document sharing for informational purposes. It does have a Presentation Builder function for creating PowerPoint presentations, but it is cumbersome and not very flexible. Specifically, the linkage is awkward and files may have to be re-linked when they are updated. In addition, the architecture only allows you to create a couple of levels of content. The search function is very limited. Compass is a newer project and has not fully matured.
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.
A de minimis incentive was given to thank the reviewer for their time. The incentive was not used to bias or drive a particular response, nor was the incentive contingent on a positive endorsement. TR verified that a representative sample of customers was invited. More Info
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.
A de minimis incentive was given to thank the reviewer for their time. The incentive was not used to bias or drive a particular response, nor was the incentive contingent on a positive endorsement. TR verified that a representative sample of customers was invited. More Info
The positive impact has been to know we have a system that can house legally-approved responses to questionnaires. The good about this is that if we have a simple RFI that does not require a lot of response customization, we can draw upon previously-approved responses and create output MUCH quicker, without the need of laborious and time-consuming legal reviews of RFIs or DDQs we produce for prospective clients. Quicker, easier output with less internal review = efficient RFI process and quicker turnaround time to respond to our client/prospective client base.
The negative impact has only been the time it takes to orient oneself with the program, and REMAIN oriented. As we do not do RFIs on a daily basis, it is easy for us to become rusty, or to take short-cuts because we do not have time to re-train on the program. Those shortcuts and workarounds tend to cause us not to use the program to its full potential and lead to counter-productivity in some cases.
