Nintex offers a platform that helps companies discover, automate, and optimize business processes.
$480
Minimum 1,000 users per user
SAP Build
Score 8.7 out of 10
N/A
SAP Build is a business application development and automation solution with a comprehensive suite of low-code, pro-code, and generative AI tools. SAP Build is for developers, IT professionals, and business users/citizen developers who want to create and customize business applications.
$1.82
per month per user
Pricing
Nintex
SAP Build
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
SAP Build Process Automation - Standard User
$1.82
per month per user
SAP Build Process Automation - Advanced User
$15
per month per user
SAP Build Process Automation - Attended Automation
$534
per month
SAP Build Process Automation - Unattended Automation
Nintex is constantly releasing new updates to the process platform. We are partially mapping out our current processes and have already seen areas where we can reduce the overlapping work of various staff members. Process mapping and the platform take time, no matter how easy the tool makes it (it's easy). If you don't have the time or resources to commit to process or experience improvement, you may need to look internally to see if your business C-level is ready to 'improve' things. We learned this the hard way until we were able to show results.
The SAP Build Process product is best suited for managing pipelines and scrum boards without limitations. Implementation of the software is also simple, and unlimited users can connect the software with third-party systems to push codes. The software integrates well with other products, making it easy to build and deploy pipelines. The only issue with the SAP Build Process is the cost of implementation, which is far higher than that of other similar products.
Adding Machine learning features like the "Image and Text Automation" component, which allows bots to extract data from unstructured sources like scanned documents or PDFs.
Natural language processing (NLP) features to understand and interpret human language, which can be useful for tasks like customer service or data entry. mostly for middle east countries where Arabic language is used.
Integration with external systems where many industries uses their own legacy systems and they need RPA bot to interact with their systems as well.
Adding More OCR tools for Document data extraction and dynamic content.
The only one I can think of that has made me not continuously use SAP Build is the cost of this tool. I see it a bit higher compared to other tools that provide the same functionality for cheaper or free plans.
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.
SAP Build is not necessarily easy to implement, especially for non-IT-skilled people. Most of the software features require some amount of basic training and experience to get the best outcome. The only user-friendly features that do not require skills to navigate are the user dashboard and the product interface.
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.
There are, for example, great blog writings about automation cases and examples. The studio version is updated often. There are also useful OpenSAP online courses.
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.
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.
Compared to Mendix, we decided not to go for low code application building and in the other parts of Build, Build is stronger and better integrated with SAP. On the hand of Coding, using Build Code, gives us Joule, which understands SAP better and also have a tighter and more secure coupling with SAP services.
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.
We have saved our company thousands of dollars by creating our own customer support system rather than using a 3rd party tool.
The ability to generate documents/PDFs in workflows has solved a great number of process issues for us and groups who had previously been using paper documents.
Automating many permissions updates through workflows has been a huge time saver for repetitive processes.