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 capabilities that can…
$35
per month per user
Coupa
Score 7.4 out of 10
N/A
Coupa’s cloud-native Business Spend Management
(BSM) platform provides end-to-end processes
that helps drive collaboration
across for every business leader from supply chain, procurement,
finance, treasury, compliance, and IT and supply chain
leaders to help their companies to get the visibility and control they need to
spend smarter, mitigate risk, and improve
resilience. A
unified platform approach frees up IT from complex integrations to help
leaders deliver on these goals.
I think the case when I would recommend Conga CPQ is in a legacy org. In that case, the older style and configuration might be more useful, and you are less likely to find yourself forced to upgrade to lightning. If you are already using lightning, or migrating to lightning, then I would only recommend Conga CPQ if the alternative does not support the features you need.
I am new to customer-supplier portals in my career. I use several different ones in my current role, including Ariba and Tipalti. To be honest, I don't really enjoy the user experience of any of them. I can see how larger companies may benefit from their services but for my current role submitting invoices on them and filling out vendor information requests seems somewhat clunky to me. When I'm in Coupa, the easiest, most non-clunky process for me is when I'm successfully connected with a customer who has successfully created their purchase order and I can easily upload my invoice to said PO. To me, emailing customer invoices directly to the customer from our invoicing system seems like the easier route of delivering an invoice. I suppose it is helpful and reassuring to know that an invoice has been successfully uploaded into a company's system rather than waiting to find out if your emailed invoice made it to the correct department for payment processing.
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.
Coupa is easy to use, however, we had to teach our end users about procurement. They are not used to conducting an RFP, onboarding a supplier, or preparing a PO. This is the change management that our employees had to be prepared to understand. The Shelby Group helped us with the implementation.
The hardest part was the integration between NetSuite and Coupa. We wanted to have a dynamic tight integration between the two solutions. If we adjusted the chart of accounts or added a new supplier we wanted it to be able to done in both systems and be available immediately in both systems. We used a partner called SuiteSkies to accomplish this dynamic integration.
We’ve been able to manage the implementation and maintenance with a very lean IT group.
Apttus has not completely transitioned from a product suite to a product platform vendor. Upgrades of certain products can have interoperability issues with other products in the Apttus stack. Our pain point here was attempting to use Apttus Xauthor for Excel to get around product line limitations in the Apttus CPQ shopping cart. The ultimate resolution was for us to upgrade and leverage the latest version of CPQ, where pricing callback limitations were addressed by client side processing, rather than the hybrid Xauthor process we tried to use.
Upgrades in general require significant testing to ensure no unanticipated issues occur. We have a complete Salesforce sandbox dedicated to providing an environment for testing any modifications or upgrades.
Apttus support model almost requires you to purchase premium support. Given the CPQ system is complex, the level of skilled support available through basic support require you to escalate several times before getting to a resource that can address your issue.
Support Team - A little slow in responding. I think the tool is so configurable that they struggle with figuring out what is causing certain issues that are being submitted on the portal.
I'd love for the Sourcing Module to be able to support larger events. There seems to be a limit on the number of lines each event can support and as a growing retailer, our store count dictates we have room to grow and that each store is represented in the bid process.
Would like to see the ability to issue multiple POs for a single item to multiple locations. The tool may do this but I know I can't and it may be due to how we interface with our ERP.
It is critical to our sales process. We are not satisfied with all aspects of the product and have gone through many tough experiences with their PS, support, and PD teams -- but we're not unhappy enough to re-build what we're already built
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.
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.
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
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.
Concur was a lot easier and more user friendly for employees doing expense reports on their phone. That is not the case with Coupa. You must use your laptop to do expenses and our managers don't always have enough time to do that while out in the field working. This has caused some issues.
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.
