Conga CPQ empowers sales, partners, and customers to efficiently configure complex products and services offerings, and provide personalized prices and quotes, utilizing codified product and pricing information - to drive higher win rates and a more pleasurable buying experience. Conga CPQ also helps to maintain a single price book, discounting structure, and quoting structure across all channels. With an API-first approach, configuration, pricing, or quoting…
$35
per month per user
Nintex
Score 8.0 out of 10
N/A
Nintex offers a platform that helps companies discover, automate, and optimize business processes.
It is well suited to providing quick pricing recommendations, allowing those who are quoting to get our agreements out efficiently. Where I find there may be some limitations is around the details that it uses to establish recommendations and the overrides. For example it would be nice to have a way to set overrides for those criteria like length of agreement, etc. and have it apply across the board
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.
The perceived power strength is that it is supposed to contain CPQ, Contract Management, Document generation and template manipulation, and cash/invoice process all in one wrapped package.
It was developed on the Force.com platform.
They provide multiple releases of their product per year.
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.
Our number one complaint with Conga CPQ has been speed. In my experience, Conga CPQ is extremely slow, especially for large orders.
In my opinion, the configuration methods of Conga CPQ are outdated and error-prone. One literally puts configurations into string-based custom settings, including the API field names. This often leads to deployment issues and run-time configuration errors.
In my experience, Conga CPQ is everything but simple to develop. You need things like a 12-step pricing callback to support custom pricing.
In my experience, Conga CPQ support is not responsive.
When it comes time to lock in a renewal contract for Conga CPQ, in my experience, they delay engagement, so you are truly behind the 8 ball when it comes time to decide if you are going to continue with Conga CPQ.
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.
The rating is based on several things: 1) Ongoing support requirements being able to be addressed by cross training existing Salesforce administrators 2) Apttus superior corporate vision for the quote to cash space 3) Apttus execution of the corporate vision with automated agents (Max), and Artificial Intelligence/Machine Learning offerings to leverage the investment in Configure Price Quote 4) Apttus corporate health and investment in the product line
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.
Conga CPQ is a great tool but lacks good support and [a] very limited knowledge base which doesn't include day to day errors which users face, thus leading us to support and take more time in turn. Also cart performance can be improved drastically which will enhance the user experience as the user doesn't have to wait for the pricing.
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.
Tier1/tier 2 support can only handle native functionality. Customizations have to be escalated to developers which aren’t included in the support program.
I go ahead and copy the people I directly worked with on implementation for assistance. I would rate them an 8 for support assistance.
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.
Be iterative. Take the opportunity to build a catalog based on how Apttus works well. Learn the tool yourself or use an SI. Take the time to build a configuration / pricing migration tool with X-Author for Excel or roll your own. Stick with OOTB Apttus as any customization will cost you every time a new version is released
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 selected Apttus CPQ over SteelBrick due to the simplicity of SteelBrick's out of the box pricing and ability to customize quoted products. As a global organization with selling a highly configurable products, we felt the ability of Apttus to handle our requirements as standard functionalty rather than a customization was a material difference between the platforms.
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.
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.
The ability to generate engineered configurations that is right by construction has reduced the cycle time of the customer engagement. The fact that we are able to guide the process and end up with a validated bill of material reduces the iterations with the customers.
As long as the validations rules are correct the generated bill of material is accurate. We are now looking at using Apttus to perform quality checks in our product rules since the tool is able to test different configurations quickly and efficiently.
Configuration that use to take weeks and consumed valuable engineering resources has been transformed to become a customer facing application that is simple enough for customer to self-service.
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.
