Conga Contract Lifecycle Management (CLM) Reviews

My main use case for Conga Contract Lifecycle Management (CLM) is to create contracts after placing the quote or proposal in Conga CPQ. As a developer, I develop contracts using Conga Contract Lifecycle Management (CLM).

The best features Conga Contract Lifecycle Management (CLM) offers include optimizing contracts, managing them, and generating contracts according to our use cases, which is the main thing that helps us. Conga Contract Lifecycle Management (CLM) has positively impacted my organization by making the contract lifecycle easier for customers when quotes get created. All the details of the quotes and pricing will be on the contracts, making it easy for customers as well as business people and sales users.

Particularly, I don't have any metrics regarding that, but Conga Contract Lifecycle Management (CLM) has improved accuracy and increased customer satisfaction as it is very quick to complete. Generating contracts is very easy with Conga Contract Lifecycle Management (CLM).

I don't think I am in a position to help improve Conga Contract Lifecycle Management (CLM), but you need to change the UI so it would be easy for customers or sales users to have a very good user interface.

Regarding Conga Contract Lifecycle Management (CLM)'s AI capabilities, I think its accuracy and reliability of output are good.

I have been using Conga Contract Lifecycle Management (CLM) for two years.

I would tell others looking into using Conga Contract Lifecycle Management (CLM) that it is useful, but the licenses are a bit expensive compared to the other contract lifecycle managements in the market. I would rate Conga Contract Lifecycle Management (CLM) a nine out of ten because it's easy to process and has very good features, but there are other contract lifecycle managements in the market. Recently, Icertis has onboarded their own CLM.

My overall review rating for Conga Contract Lifecycle Management (CLM) is nine.

In my previous projects, my main use case for Conga Contract Lifecycle Management (CLM) was that soon after accepting a proposal, we had a requirement to generate a document or create an agreement. That is where CLM entered the process. An agreement was created completely in CLM. The agreement was sent for review and approvals. After approvals and review, the agreement was accepted, and then orders were created. Once the orders were created, assets were automatically created and attached to the particular account.

The agreement generation process in Conga Contract Lifecycle Management (CLM) involved creating a proposal from the opportunity and then configuring some of the products. After configuring products, if they required any approval, we could send them for approval. After approvals, the cart was automatically finalized. Once the cart was finalized, we had a process to create an agreement from the proposal. When the user clicked on create agreement, an agreement record was created, copying the information from the proposal, and the agreement line items were created, copying all the information from the proposal line items. This was fully automated in our previous project.

Regarding the automation process in Conga Contract Lifecycle Management (CLM), once the user clicked on create agreement, it asked for different kinds of record types, and the user needed to select a particular record type. Once the record type was selected, we had written a flow on the agreement object to copy the information from the proposal. Some of the basic details were automatically printed on the agreement, copying from the proposal. We had written some flow and trigger on agreement line items as well to copy the information from proposal line items.

The best features Conga Contract Lifecycle Management (CLM) offers include document generation, which is part of CLM. We can go for X-Author or Conga Composer for document generation. I have previously worked on Conga Composer as well, and I appreciated that feature.

What I valued most about using Conga Composer for document generation within CLM was the template automation. Whenever the user clicked on generate document on the agreement record, it was a Conga Composer process. We created a Word document and uploaded it into Salesforce. Once the user clicked on create or generate document, we showcased some of the information on the template, such as the proposal name, agreement name, and all the agreement line items. That is what we accomplished.

I would add that we can use X-Author to generate the document within Conga Contract Lifecycle Management (CLM).

Conga Contract Lifecycle Management (CLM) has positively impacted my organization as it mostly handles the agreement object and asset management can also be done in CLM.

The automation and document generation in Conga Contract Lifecycle Management (CLM) have made things easier for my team, saving time and reducing errors. The best part of CLM is that it is a complete quote-to-cash solution. When the user chooses products and the cart is finalized, the entire process is automatic. The agreement is created, and then the document is created. The document includes all the details related to account, contact, billing address, shipping address, and the products that the user has added. CLM has automated everything that makes our life easier.

I have not used Conga Contract Lifecycle Management (CLM) deeply, but I know that document generation still has some improvements that need to be implemented. If those improvements are made, we can have better results.

I am a beginner using Conga Contract Lifecycle Management (CLM).

Based on my experience, Conga Contract Lifecycle Management (CLM) is stable, but improvements are still needed. I can say it is acceptable.

The scalability of Conga Contract Lifecycle Management (CLM), based on what I have seen or heard, is an eight out of ten.

I have not used a different solution before Conga Contract Lifecycle Management (CLM).

Regarding my experience with pricing, setup cost, and licensing for Conga Contract Lifecycle Management (CLM), it comes under Conga CPQ, and I have one to two years of experience with it.

I evaluated other options before choosing Conga Contract Lifecycle Management (CLM). For example, Conga Composer is part of Conga CPQ where documents are generated on the proposal record itself instead of the agreement. I have used that feature in Conga CPQ apart from CLM.

In estimating how much time my team saves with CLM automation compared to manual processes, if it were manual, the sales representative would have to pass each and every piece of information about the products, the proposal, billing address, shipping address, and if the customer needs a different shipping address, that would take some additional days. Additionally, negotiations, document generation, and review processes take considerable time. Sending the document for review can lead to redlining and checking different versions to see whether the customer agrees with that agreement. Without automation, that would require significant manual effort, possibly taking one to two weeks just for reviews. Creating a single order manually could take two to three weeks, but using CLM, we can save that time and effort.

Regarding Conga Contract Lifecycle Management (CLM) AI capabilities, I think its accuracy and reliability of output are good. We can rely on the CLM part as most organizations have started using it because of document generation and the automation of the orders and acceptance process.

My advice to others looking into using Conga Contract Lifecycle Management (CLM) is to automate the document generation process, automate the creation of orders, automate accepting the order, and automate this complete amendment process. I would advise my customers to choose CLM because if it is not CLM, that would require manual effort and is a time-consuming process. I gave Conga Contract Lifecycle Management (CLM) a rating of three because I have not worked extensively on CLM, which is the reason for my score.

My main use case for Conga Contract Lifecycle Management (CLM) involves red-lining features, clauses, dynamic clauses, contracting, legal team involvement, and approvals from the legal team. Everyone has their own sets of approvals, and something is getting changed.

Whenever the agreement gets generated, it goes to Conga Contract Lifecycle Management (CLM), and the legal teams get notified along with the customer. If customers are looking for any change in the agreement, they can discuss it with the legal team, and the legal team can go back and forth on the agreement. If any clause or statement gets changed dynamically and requires certain approval, the system generates automated approval workflows in Conga Contract Lifecycle Management (CLM) itself. On approval, the agreement gets signed from both parties, customers first, and then from the legal team and the leadership team.

In my experience, the best features of Conga Contract Lifecycle Management (CLM) include the way they handle dynamically changing agreements and manage the approvals within the system, which is great.

Conga Contract Lifecycle Management (CLM) positively impacts my organization by reducing the CLM life cycle by days. Initially, my client's company used to have a CLM life cycle of around a week or more for one contract. Sometimes emails would sit in the email boxes of the legal team, and they would occasionally miss or delay the process. However, with Conga Contract Lifecycle Management (CLM) in place, everything is centralized, and there is a Service Level Agreement (SLA) as well, so the legal team and other teams are on top of that. Plus, the approval process does not sit idle; it stays in the system.

Conga Contract Lifecycle Management (CLM) can be improved by making the configuration of approvals a little simpler.

I have used Conga Contract Lifecycle Management (CLM) for a year.

I would rate Conga Contract Lifecycle Management (CLM) an eight or eight and a half on a scale of one to ten.

I chose that score of eight or eight and a half because of the features that I have used and the flexibility. I have not used Conga Contract Lifecycle Management (CLM)'s AI capabilities regarding governance and security. I have not used Conga Contract Lifecycle Management (CLM)'s AI capabilities regarding accuracy and reliability of output either.

My client made the decision on whether to purchase Conga Contract Lifecycle Management (CLM) through Amazon Web Services (AWS) Marketplace, and I am not in the decision-making process. If you are looking for a CLM agreement and the entire transformation of CLM, Conga Contract Lifecycle Management (CLM) can be used effectively. My overall rating for this product is eight out of ten.

My main use case for Conga Contract Lifecycle Management (CLM) is that we are using it as a CPQ project. In our organization, we are using Conga CPQ as well as Conga Contract Lifecycle Management (CLM). Conga Contract Lifecycle Management (CLM) is used for the agreement life cycle and for generating the contracts and creating agreements and asset line items.

The best features Conga Contract Lifecycle Management (CLM) offers include template generation and contract creation. In this contract, the agreement line items are created which can be captured for generating revenue. The templates which we design for the contract life cycle are very helpful, and you can customize those to a very large extent.

Conga Contract Lifecycle Management (CLM) has positively impacted my organization by automating contract generation. The legal process is very much optimized because of Conga Contract Lifecycle Management (CLM). The whole process is completed, and because of this, revenue is generated as a sales cycle; without CPQ and without Conga Contract Lifecycle Management (CLM), it is not possible.

When I say the legal process is optimized, the timing is reduced for the legal process. For example, if someone is trying to manually create those processes, it will take several days. However, because of introducing Conga Contract Lifecycle Management (CLM) and creating the agreement generation with templates, the whole life cycle can be done in less than one day.

Regarding the features, I think that in Conga Contract Lifecycle Management (CLM) features, we get less content online as it is a managed package. If the content and customization feature-wise are available more extensively, that would be beneficial.

Conga Contract Lifecycle Management (CLM) can be improved because, as it is a managed package, it has certain restrictions. As a result, sometimes you cannot use the out-of-box features and have to create and customize them. That slows me down, and if we face any issue in the managed package, we have to contact Conga for raising cases, so all things take time.

I have been using Conga Contract Lifecycle Management (CLM) for around five years.

In my experience, Conga Contract Lifecycle Management (CLM) is stable, and there are no downtime issues reported.

Conga Contract Lifecycle Management (CLM)'s scalability is effective. As I have already mentioned, it optimizes the process of the contract and the contract structure. It contributes to the growth of the company.

The customer support for Conga Contract Lifecycle Management (CLM) is responsive and helpful, but as with all support teams, it takes some time to debug issues and reach a resolution.

I have not used a different solution before Conga Contract Lifecycle Management (CLM). For the CLM processes for two projects, we have used Conga Contract Lifecycle Management (CLM) only.

Before choosing Conga Contract Lifecycle Management (CLM), we checked Salesforce process, but it is not that optimized. It does not cover many scenarios, and for revenue generation while contracts are offered, there are certain limitations that cannot compete with Conga Contract Lifecycle Management (CLM).

I rate Conga Contract Lifecycle Management (CLM) an eight out of ten.

I choose an eight out of ten because it still has scope. As we are covering some scenarios, those scenarios can be done by Conga as well. I give it an eight because we are able to automate our whole life cycle of legal contracts through Conga Contract Lifecycle Management (CLM).

When it comes to customizing those templates, the challenges are always there. For example, when there is an issue in creating those merge fields, it becomes difficult to debug. However, once the template is created and generated, it is very helpful for the salespeople.

Regarding Conga Contract Lifecycle Management (CLM)'s AI capabilities, I have not used any AI capability for Conga Contract Lifecycle Management (CLM), so I do not have many pointers on that part.

My advice for others looking into using Conga Contract Lifecycle Management (CLM) is to go through their release documents first before implementing, and then you can evaluate the pros and cons. Also, because the product is expensive, you have to compare that with other contract CLM products such as Salesforce CLM and other solutions.