Nintex offers a platform that helps companies discover, automate, and optimize business processes.
$480
Minimum 1,000 users per user
Pipefy
Score 7.5 out of 10
N/A
Pipefy headquartered in San Francisco offers their process management and workflow software providing processes for customer success, service desk, sales operations, and other processes.
$22
per month
Process Street
Score 8.3 out of 10
N/A
Process Street in San Francisco offers their application which allows teams to create simple recurring checklists, collaborate around them and track as they’re completed.
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.
Pipefy is very well suited if you have a team doing any sort of process... for real! It simplified everything from our sales and marketing objectives/processes, to our onboarding and accounting side of things. Since you can share different pipes with others, it's easy to see where others are at in the process and move the card along while keeping others informed. It makes sure you don't miss any information or steps along the way, which is great if your process is detail-oriented. It is a little less appropriate for marketing efforts, but we still try to use it to keep track of things in a central space. Definitely best suited for sales, technical things, and accounting.
if you have standard processes that are often executed, it's worth to use. If you are a small company it is generally not worth to implement because you will need somebody who permanently works with it and maintains the processes.
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.
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.
If you had the ability to drag tasks around in a nonlinear way, it could be a cool creative feature. An example is to have a subtask next to another that says N/A if the task wasn't executed because it wasn't applicable.
Inbox tab can be overwhelming but that may just be the style in which I built my checklists.
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.
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.
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.
Pipefy support is pretty good. There were a few instances where the agent didn't really understand what I was trying to get help with, but that was only once. Every other time it has been pretty fast and efficient. They are also very kind and understanding. I don't think they need much help in that dept
Since my last login into the platform, the latest update made the app much easier to use and learn. It's incredibly clean, and everything is exactly where it should be location-wise. You can tell they listen to their user base for features.
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.
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.
We started using software we already had (such as Slack and Sheets) but this software is not actually ideal to manage processes, which led to errors, miscommunication, and execution problems. Trello is good for managing demand but offers no process customization or approval and Jira is too focused on development for our needs, and also hard to customize.
I've tried other checklist tools like Google Keep, but it was too simple. I've tried Flowster, which is very similar to Process Street, but I like Process Street better. The interface is a lot more balanced and pleasant to look at. I found Flowster to be a less appealing interface even though the features were similar. I also briefly tried systemHUB but it is very expensive for what it offers compared to Process Street.
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.
Our processes are more organized and we are not missing any steps.
We are able to touch base with customers easier since we have all potential/missed clients in one pipe, with automated alerts (i.e. it has been 60 days since contact with this customer).
We are able to keep track of customer billing changes easier.
Because of Process Street I am no longer losing money when having to redo things
It helps me eliminate those nasty "egg on the face" situations with clients because now nothing slips through the cracks. The team is able to be on top of it!
