Conga CPQ has some drawbacks. If you have a larger number of products that should be added to the cart, the cart is taking so much time to load. In that case, sales users should wait for some time. However, it is not comparable to the manual process; it is much better. If the number of products being added to the cart is more than 5,000, in that case, the cart is a little slow, which is a drawback I identified. The loading of bulk products is the one thing I have identified so far. Conga CPQ can increase the cart loading functionalities, which are not loading at all if you have a large number of products. I think that solution has also come into the picture now that RLP has been implemented. That is also being taken care of.
Conga CPQ Developer at a tech vendor with 10,001+ employees
Real User
Top 10
Jun 27, 2026
Conga CPQ could be improved as it has recently launched Conga RLP, a Revenue Lifecycle Platform, to enhance performance. However, I am currently facing many difficulties with data synchronization, and it has several loopholes not working as expected in Turbo, such as validation callbacks working fine in Turbo but failing in RLP. I have encountered many issues recently and have raised these to the product team. Regarding the needed improvements for RLP, data sync is the first issue, especially incremental sync and full sync. When I create a new field, I must perform a full sync, which takes a lot of time. The initial org setup also consumes time, and tracing failed syncs for related records is difficult. Furthermore, these validation messages, error messages, and warning messages that compare old and new JSON values, along with cascading from parent to child, even when blank, have a lot of issues. There are also many discrepancies in approvals, with backend queries returning one value and displaying a different value in the UI. Currently, Conga CPQ is performing well. If Conga RLP can expedite its processes and resolve all open related bugs, as well as increase the product and engineering team size, it will benefit many clients, allowing them to switch from Turbo to RLP with fewer issues. In RLP, increasing the team solving product bugs would lead to faster pricing and overall improvements.
Salesforce Technical Lead at a outsourcing company with 501-1,000 employees
Real User
Top 20
Jun 11, 2026
There are a few manual steps we need to take, such as handling a complex approval process in Conga CPQ. Deploying data from lower organizations to higher environments can be challenging, so Conga should consider improving the deployment of approvals. Additionally, there are maintenance tasks, such as product rule or price rule maintenance, that need automation to prevent errors. Performance issues exist since Conga CPQ cannot load 200 or 250 products on the cart page.
Conga CPQ Developer at a computer software company with 501-1,000 employees
Real User
Top 20
Jun 5, 2026
After converting to Conga LP revenue life cycle platform, we identified several areas for improvement. We run into more sync issues and data synchronization problems. After moving to the revenue life cycle platform, changing all the logic from Turbo to the platform has created many issues. While setting up the organization, it takes considerable time to sync all the data.
Conga CPQ streamlines the sales process by automating custom pricing and quoting, providing a configurable platform to optimize product selection and price accuracy. It enhances workflow efficiency, making CPQ processes faster and more reliable.Conga CPQ offers an intuitive approach to managing complex sales configurations. It efficiently handles intricate pricing rules, seamlessly integrates with CRM systems, and promotes accuracy in sales workflows. Businesses find it valuable for its...
Conga CPQ has some drawbacks. If you have a larger number of products that should be added to the cart, the cart is taking so much time to load. In that case, sales users should wait for some time. However, it is not comparable to the manual process; it is much better. If the number of products being added to the cart is more than 5,000, in that case, the cart is a little slow, which is a drawback I identified. The loading of bulk products is the one thing I have identified so far. Conga CPQ can increase the cart loading functionalities, which are not loading at all if you have a large number of products. I think that solution has also come into the picture now that RLP has been implemented. That is also being taken care of.
Conga CPQ could be improved as it has recently launched Conga RLP, a Revenue Lifecycle Platform, to enhance performance. However, I am currently facing many difficulties with data synchronization, and it has several loopholes not working as expected in Turbo, such as validation callbacks working fine in Turbo but failing in RLP. I have encountered many issues recently and have raised these to the product team. Regarding the needed improvements for RLP, data sync is the first issue, especially incremental sync and full sync. When I create a new field, I must perform a full sync, which takes a lot of time. The initial org setup also consumes time, and tracing failed syncs for related records is difficult. Furthermore, these validation messages, error messages, and warning messages that compare old and new JSON values, along with cascading from parent to child, even when blank, have a lot of issues. There are also many discrepancies in approvals, with backend queries returning one value and displaying a different value in the UI. Currently, Conga CPQ is performing well. If Conga RLP can expedite its processes and resolve all open related bugs, as well as increase the product and engineering team size, it will benefit many clients, allowing them to switch from Turbo to RLP with fewer issues. In RLP, increasing the team solving product bugs would lead to faster pricing and overall improvements.
There are a few manual steps we need to take, such as handling a complex approval process in Conga CPQ. Deploying data from lower organizations to higher environments can be challenging, so Conga should consider improving the deployment of approvals. Additionally, there are maintenance tasks, such as product rule or price rule maintenance, that need automation to prevent errors. Performance issues exist since Conga CPQ cannot load 200 or 250 products on the cart page.
After converting to Conga LP revenue life cycle platform, we identified several areas for improvement. We run into more sync issues and data synchronization problems. After moving to the revenue life cycle platform, changing all the logic from Turbo to the platform has created many issues. While setting up the organization, it takes considerable time to sync all the data.