In our current project, we use Conga Contract Lifecycle Management (CLM) as a pricing model, and it is quite effective. It is helpful for us, similar to CPQ, as it redirects pricing to the CPQ from CLM. We first make an agreement, and then we link those agreements for different accounts. If this is going to affect the pricing for the CPQ to that account member, then we use those accounts as members. After that, we can consider it as a product. If we are selling that product to that account, it will apply discounts such as tier one, tier two, or tier three. We are using it as a pricing platform, not the contract we made for a customer. The main benefits I have seen from using Conga Contract Lifecycle Management (CLM) are that we use it as a discount platform in a huge project for different customers or accounts across the world. It helps us manage discounts directly set in the system, picking those prices from a contract price list and not the country price list. CPQ and CLM are interlinked. As per making contracts, we are not currently using Conga, but the Conga team proposed to use the contract, and we are planning to move fully forward with Conga.
My main use case for Conga Contract Lifecycle Management (CLM) starts from contract creation and approval workflow. In the past, I have used Conga Contract Lifecycle Management (CLM) to generate contracts from pre-approved templates. When a sales deal is finalized, I create the contract using standardized clauses, which reduces manual drafting. Then I route through automated approval workflows, which includes legal, finance, and management, so everything moves quickly without back and forth emails. This helps us cut down contract turnaround time significantly.
My main use case for Conga Contract Lifecycle Management (CLM) involves a customer who has around 10 different record types. We work on getting the contract through the end-to-end contract lifecycle management on Conga, and we also do different kinds of automations. For example, we have a use case where they have a source system from which information is pushed into Conga using a middleware, and then contracts are created on Conga automatically and are automatically generated. After customer review, we can bulk send them to the customers for signature. I will take the example of one which I already shared. For a particular record type, such as MSA, the contracts that go out to the customer were around more than 1,000 per month, and it is very difficult for the customer to come into Conga and create those contracts manually. We created a process where we pick the contracts from the source system. We have created some custom APIs on our end to fetch that information from the source system. Based on the different APIs we have created, we have created the contracts on Conga and then generated them. Once the customer reviews those contracts, we have created some utilities using which we can send it out to the customer using Adobe Sign automatically. Because of these processes, the customer can send out thousands of contracts in one go instead of creating them and having a lot of people appointed to do this job. It is a one-person job now. Other examples include that we have done a legacy upload of around 10,000 contracts at a time. We have used Conga Contract Lifecycle Management (CLM) to send amendments out to the customer using Conga's processes. Within Conga, we have used wizards to give users a questionnaire where they can put information and then create contracts for them and generate. We have also done some auto-generation within Conga.
Learn what your peers think about Conga Contract Lifecycle Management (CLM). Get advice and tips from experienced pros sharing their opinions. Updated: May 2026.
Apttus enhances sales and contract management by automating quote generation, pricing, and product configuration. Valued for its robust contract lifecycle management, it integrates seamlessly with ERP and CRM systems. Users report streamlined workflows, improved collaboration, and increased accuracy, boosting operational efficiency.
In our current project, we use Conga Contract Lifecycle Management (CLM) as a pricing model, and it is quite effective. It is helpful for us, similar to CPQ, as it redirects pricing to the CPQ from CLM. We first make an agreement, and then we link those agreements for different accounts. If this is going to affect the pricing for the CPQ to that account member, then we use those accounts as members. After that, we can consider it as a product. If we are selling that product to that account, it will apply discounts such as tier one, tier two, or tier three. We are using it as a pricing platform, not the contract we made for a customer. The main benefits I have seen from using Conga Contract Lifecycle Management (CLM) are that we use it as a discount platform in a huge project for different customers or accounts across the world. It helps us manage discounts directly set in the system, picking those prices from a contract price list and not the country price list. CPQ and CLM are interlinked. As per making contracts, we are not currently using Conga, but the Conga team proposed to use the contract, and we are planning to move fully forward with Conga.
My main use case for Conga Contract Lifecycle Management (CLM) starts from contract creation and approval workflow. In the past, I have used Conga Contract Lifecycle Management (CLM) to generate contracts from pre-approved templates. When a sales deal is finalized, I create the contract using standardized clauses, which reduces manual drafting. Then I route through automated approval workflows, which includes legal, finance, and management, so everything moves quickly without back and forth emails. This helps us cut down contract turnaround time significantly.
My main use case for Conga Contract Lifecycle Management (CLM) involves a customer who has around 10 different record types. We work on getting the contract through the end-to-end contract lifecycle management on Conga, and we also do different kinds of automations. For example, we have a use case where they have a source system from which information is pushed into Conga using a middleware, and then contracts are created on Conga automatically and are automatically generated. After customer review, we can bulk send them to the customers for signature. I will take the example of one which I already shared. For a particular record type, such as MSA, the contracts that go out to the customer were around more than 1,000 per month, and it is very difficult for the customer to come into Conga and create those contracts manually. We created a process where we pick the contracts from the source system. We have created some custom APIs on our end to fetch that information from the source system. Based on the different APIs we have created, we have created the contracts on Conga and then generated them. Once the customer reviews those contracts, we have created some utilities using which we can send it out to the customer using Adobe Sign automatically. Because of these processes, the customer can send out thousands of contracts in one go instead of creating them and having a lot of people appointed to do this job. It is a one-person job now. Other examples include that we have done a legacy upload of around 10,000 contracts at a time. We have used Conga Contract Lifecycle Management (CLM) to send amendments out to the customer using Conga's processes. Within Conga, we have used wizards to give users a questionnaire where they can put information and then create contracts for them and generate. We have also done some auto-generation within Conga.