Conga CPQ vs. PROS Smart CPQ

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.

Incentivized

Is my IT team ready to handle the challenges with data integration ? Are all the features offered by my current quoting tool being offered by Cameleon? Do I need a SaaS based quoting tool? Would it be easy and intuitive for my sales team (who,quite frankly, worship MS Excel) to use Cameleon ? Do I need a real-time/near-real-time quoting tool or would delays in data refreshes be acceptable

• 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.

Incentivized

• Salesforce.com integration via a plugin that lets end users access Cameleon CPQ systems.
• Quoting made easier with complex business rules.
• Good support from the Cameleon team with fixes and enhancements.

• 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.

Incentivized

• Integration with other onsite systems such as Oracle databases require the expertise of knowledgeable developers. Manual upload of flat files are always an option , but not necessarily the cleanest.
• Better Cameleon CPQ Designer UI would go a long way. Currently UI is a stark contrast to the intuitive UI of SalesForce.com or similar SaaS based tools. Not too much to ask for , considering the fact that we work in the era of Facebook and Twitter.
• Real time data availability is a long way to go for Cameleon CPQ. Updates to data pushed over as batches to Cameleon are reflected at Salesforce.com only after a 'versioning' process is launched. Current recommended frequency for this process is once a day (an upgrade to make it twice a day is in the works).

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

Incentivized

There are a few features that we expected from the tool but Cameleon's CPQ has fallen short on these. Possible enhancements and product fixes should be made as soon as possible to change the perspective. Unexpected bugs in the tool have come up during the roll-out that has caught the implementation team off-guard

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.

Incentivized

I have not heard of any issue

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.

We attended 5 hours worth of webinars early on.

We had to understand how objects worked to figure out how to structure our data.

I would have liked more in-depth training but it would have been an additional cost

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

Incentivized

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.

SaaS based tool. Better quoting rules.

• 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.

• A salesforce.com -esque approach to CRM has a whole gamut of advantages. Cameleon CPQ complements this approach.
• Expect down times , feature problems or general disagreement about Cameleon's capabilities initially. This is true for adopting any new tool or technology. Hold on and it will tide over.
• As a person who has used Cameleon purely as a developer standpoint , I do not have anything more to add-on.