Nintex offers a platform that helps companies discover, automate, and optimize business processes.
$480
Minimum 1,000 users per user
S-Docs
Score 8.7 out of 10
Small Businesses (1-50 employees)
S-Docs headquartered in New York offers what they present as a secure document generator and E-signature solution built on the Salesforce Platform. It aims to help users to create and e-sign sophisticated documents that improve efficiency, reduce errors and eliminate tedious work.
$65
per month per user
Pricing
Nintex
S-Docs
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
S-Docs for Salesforce
$25
per month (billed annually) per user
S-Docs for Salesforce with e-Signature
$40
per month (billed annually) per user
S-Docs & S-Sign Bundle
$40
per month per user (Minimum contract of $8,400)
S-Docs for HubSpot Team Edition
$65
per month per installation
S-Docs for HubSpot Professional Edition
$275
per month per installation
Offerings
Pricing Offerings
Nintex
S-Docs
Free Trial
Yes
Yes
Free/Freemium Version
No
Yes
Premium Consulting/Integration Services
Yes
No
Entry-level Setup Fee
Optional
Optional
Additional Details
—
S-Docs for Salesforce is priced by seat. Organizations that are interested in the enterprise edition - including per-document pricing and Experience Cloud plans, can reach out to sales. S-Docs for HubSpot is priced by usage. S-Docs for HubSpot Team Edition comes with 500 documents and 250 e-Signature requests per year. S-Docs for HubSpot Professional Edition comes with 2,500 documents and 800 e-Signature requests per year.
Nonprofit discounts are available.
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.
S-Docs would be great for anyone looking to make the process of getting signatures more seamless and less time intensive. You can get a signature in minutes no matter where the signee is located. No more having to worry about printing, scanning, and emailing over important and time-sensitive documents.
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.
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.
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.
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.
