Conga Contract Lifecycle Management (CLM) Reviews

One of our main uses for Conga Contract Lifecycle Management (CLM) is that we have integrated it with our Salesforce system.

One of the common use cases was managing sales contracts directly from Salesforce. When an opportunity reached a certain stage, the sales team would initiate a contract request from Salesforce. Conga Contract Lifecycle Management (CLM) automatically generated the contract using predefined templates and Salesforce data, such as customer information, pricing, and terms. The contract then went through an approval workflow, involving sales managers and legal teams. Once approved, it was sent for e-signature, and the signed document was automatically stored and linked back to the Salesforce record. This reduced manual effort, improved accuracy, and provided complete visibility into the contract status throughout the process.

In my day-to-day work, Conga Contract Lifecycle Management (CLM) helped streamline the contract process by keeping all the contract-related information in one place. My main involvement was tracking contract status, coordinating with stakeholders for approvals, ensuring required documents were attached, and following up on pending actions. Since it was integrated with Salesforce, I could easily access customer and contact information without switching between multiple systems. This improved efficiency, reduced manual working and manual tracking, and helped ensure contracts moved through the approval process on time.

The features that stand out most in Conga Contract Lifecycle Management (CLM) are contract automation, approval workflows, centralized contract repository, and Salesforce integration. Contract automation saves time by generating contracts from templates with pre-populated data. The approval workflow feature helps ensure contracts are reviewed by the right stakeholders before execution. The centralized repository makes it easy to search, track, and manage contracts throughout their lifecycle. I also find the Salesforce integration particularly valuable because it allows users to work within Salesforce and access contact information without switching systems. Together, these features improve efficiency, reduce manual errors, and provide better visibility into the contract management process.

Conga Contract Lifecycle Management (CLM) had a positive impact by streamlining the contract management process and reducing manual effort. It accelerated approvals and provided better visibility into contract status. It helped the organization manage contracts more accurately and complete the contract lifecycle faster.

Conga Contract Lifecycle Management (CLM) overall is a strong solution, but there are areas where it could be improved. The user interface can sometimes feel complex for new users and may require additional training. Some advanced configurations and workflow customizations can also be challenging and may require specialized expertise. In addition, improving system performance for large contract volumes and making reporting more intuitive would enhance the user experience. Despite these areas for improvement, the platform provides significant value through its automation and Salesforce integration.

I would appreciate seeing easier integrations with other enterprise systems, more powerful reporting and analytics, stronger AI-driven contract insights, and a simpler user interface. These enhancements would make the platform even more efficient and user-friendly.

Beyond what I have already mentioned, I would appreciate seeing easier implementation, faster onboarding, more pre-built templates, and self-service configuration options. These improvements would make the platform easier to adopt and manage.

I have been using Conga Contract Lifecycle Management (CLM) since one month ago.

Conga Contract Lifecycle Management (CLM) is stable. In my experience, day-to-day contract creation, approval workflows, document generation, and contract tracking operated reliably. As with any enterprise application, there were occasional issues or maintenance activities, but nothing that significantly disrupted business operations. Overall, I found it dependable for managing contract lifecycle processes and supporting business users.

Conga Contract Lifecycle Management (CLM) is highly scalable. It can support growing contract volumes, additional users, and more complex workflows. As an organization expands, since it integrates closely with Salesforce and is cloud-based, it can accommodate business growth without requiring any significant infrastructure changes. As our needs evolved, the platform was flexible enough to support additional approval processes, contract types, and reporting requirements.

The customer support was very responsive and has been positive. The team was generally knowledgeable when addressing issues or questions. For standard requests and troubleshooting, we received timely assistance and access to available documentation. Overall, the support experience was good and met our needs. I rate it ten out of ten.

Before Conga Contract Lifecycle Management (CLM), many contract-related activities were handled through emails, shared folders, and manual tracking. The move to Conga Contract Lifecycle Management (CLM) helped centralize contract management, automate approvals, improve visibility, and reduce manual effort. The Salesforce integration was also a major advantage.

I would recommend clearly defining processes, setting up proper workflows, focusing on user training, and using a phased implementation approach. Good planning and adoption are key to getting the best value from Conga Contract Lifecycle Management (CLM).

I do not have the exact metrics, but we have observed reduced contract turnaround times, fewer manual processes, and improved productivity. Since I was not involved in the financial analysis, I would not want to estimate specific cost savings or headcount impacts.

While I was not responsible for purchasing decisions, my understanding is that enterprise contract management solutions like Conga Contract Lifecycle Management (CLM) require a significant investment in licensing and implementation. However, the efficiency gains from automated contract generation, approvals, and centralized contract management can help justify the cost for organizations with high contract volumes.

I was not part of the decision-making process, but common alternatives organizations often consider in this space are DocuSign CLM, Icertis Contract Intelligence, and Ironclad. However, I cannot confirm whether those were specifically evaluated or not, but we chose Conga Contract Lifecycle Management (CLM).

I would say the accuracy and reliability of Conga's AI capabilities are generally good, especially for tasks such as contract analysis, clause identification, data extraction, and workflow recommendations. However, as with any AI solution, the output should be reviewed by users, particularly for high-risk or legally sensitive contracts. I view the AI as a tool that helps improve efficiency and reduce manual effort, rather than a complete replacement for human review.

Conga Contract Lifecycle Management (CLM) is very strong on security. From my experience, the capabilities place a strong emphasis on governance and security, which is important when working with sensitive contract data. Features such as role-based access controls, audit trails, approval workflows, and centralized document management help ensure that only authorized users can access the contract information. The platform also supports compliance and accountability by maintaining a record of contract activities and approvals. As AI capabilities continue to evolve, maintaining transparency, data privacy, and proper oversight will remain critical. Conga appears to be moving in that direction.

Conga Contract Lifecycle Management (CLM) is a strong platform, especially with Salesforce integration. Its real value comes when it is properly implemented and adopted. It helps improve efficiency, visibility, and contract control across the organization. I would rate this review nine out of ten.

We primarily use Conga Contract Lifecycle Management (CLM) integrated with Salesforce. When an opportunity reaches the appropriate stage, we trigger document generation directly from the opportunity record. The system pulls in the relevant data, builds the contract from a template, and then we send it for e-signature without leaving Salesforce. I personally have not used every feature in-depth. I mostly interact with the document generation and e-signature workflow, but that part alone has made a real difference in how fast we can turn around contracts.

As I am not a front-end user, we configure Conga Contract Lifecycle Management (CLM) for the users. I can provide you with the use case from the opportunity stage. When we are at a particular stage, we have a generate document button available. We generate the agreement for certain record types. Once the agreement is generated, we perform approvals on that record. After obtaining the approvals, we send the documents for e-signatures.

The integration is smooth between Conga Contract Lifecycle Management (CLM) and Salesforce. The e-signature feature is built right in, which is convenient. We do not need a separate tool for that step.

The standout feature for me is the e-signature capability within Conga Contract Lifecycle Management (CLM). We have not explored the capabilities of Conga Grid and other services offered by Conga, but the e-signature feature is the most valuable one we use.

The valuable aspects are ease and speed. It has increased the agent's efficiency. Conga Contract Lifecycle Management (CLM) has impacted us positively because Salesforce does not have out-of-the-box document generation. Conga Contract Lifecycle Management (CLM) stepped in for that capability. In sales, we do not have to wait for manually signing documents as we did in Salesforce. This feature, built with the help of Conga Contract Lifecycle Management (CLM), allows us to send documents for review and signatures while using approval workflows. This increases our efficiency.

Template management could be more user-friendly. My colleague and I are using and configuring Conga Contract Lifecycle Management (CLM). The one who manages our templates finds the interface a bit clunky. It is not always intuitive to make changes, and it could be easier to navigate. The migration manager has more room for improvement. We would love to see more capabilities there, especially when it comes to moving or updating templates and configurations.

Sometimes document formatting can be inconsistent. We have noticed that generated documents occasionally come out with extra or unwanted spaces. As a developer, I find it concerning that I need to format the documents in Word, which should be handled by the system. This issue should be addressed.

While there are improvements we can make regarding the template management experience and some of the formatting quirks, the core functionality is reliable and has definitely sped up our contract process.

I have been using Conga Contract Lifecycle Management (CLM) since four to five months after I joined this company, S&P Global.

Conga Contract Lifecycle Management (CLM) is stable.

Conga Contract Lifecycle Management (CLM) is scalable. The core functionality is reliable and has definitely sped up our contract process. We can make changes as needed, though there are improvements that should be taken into consideration regarding the template management experience and some of the formatting quirks.

Customer support is very good.

I do not have a report available right now, but Conga Contract Lifecycle Management (CLM) has definitely improved our contract turnaround time.

I would definitely recommend this option to others considering it. I would rate this review as nine out of ten.

My main use case for Conga Contract Lifecycle Management (CLM) is that we are using Conga in Salesforce for the sales process, contract management, contract generation, and quote generation. We are also using Conga for document management, and if we want to sign any document from the client, we utilize Conga.

A specific scenario where Conga really made a difference in my workflow is that before Conga, we were using Visualforce and some tools in Salesforce which required more manpower to develop any functionality. After Conga, we are seamlessly developing functionalities where we can download or fetch a document and send it over email. We automated this process with Conga, and the main use case in our project is to generate a quote when the sales process has ended, starting with case creation and ending with the quote to be sent to the customer before signing the contract.

The approval workflow is a unique aspect that adds substantial value by automating approval routing based on business rules such as contract value, product type, and special terms. This reduces the dependency on manual follow-ups and improves approval turnaround times, with stakeholders receiving timely notifications and visibility of approval status within Salesforce. Additionally, one of the biggest advantages is the automation of Conga generation, allowing sales users to create contracts directly from Salesforce opportunities and contract records using predefined templates, which minimizes manual efforts, document errors, and ensures consistency in contract language and formatting.

Seamless document generation in Salesforce is one of the best features Conga Contract Lifecycle Management (CLM) offers, which is very helpful for our project and is crucial for the whole software. For us, the document generation process is vital within the sales process.

Conga Contract Lifecycle Management (CLM) has positively impacted my organization by significantly reducing time consumption compared to other tools, as we can quickly set up Conga per our requirements without needing extensive coding.

Specific outcomes and metrics since starting to use Conga Contract Lifecycle Management (CLM) include reduced time consumption and fewer errors, as we require less manpower to configure it. We only need one Conga specialist to handle the configurations, allowing us to meet timelines before expectations.

Improvements I wish to see in Conga Contract Lifecycle Management (CLM) include addressing occasional lags and glitches in the calculation and document generation, specifically when downloading newly created documents. Sometimes, we face issues with downloading earlier documents instead of the newly created ones, which is intermittent and requires resolution.

I rate Conga Contract Lifecycle Management (CLM) a seven due to issues I experience during document generation, specifically when newly generated quotes do not download correctly, causing replication of previous quotes, which can be frustrating and problematic in client interactions. We have raised tickets for this issue, but it remains intermittent and reproducibility is inconsistent.

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

Regarding Conga Contract Lifecycle Management (CLM)'s AI capabilities, I find its accuracy and reliability to be much reliable, which is why we have used Conga for the last two years. It is accurate in terms of calculations, and we have tested the document generation process, adding and removing multiple products while applying various discounts, and Conga consistently performs.

Regarding how it helps my team, a specific benefit is that before Conga, generating documents from Visualforce was a lengthy process requiring extensive coding. After implementing Conga, we can now seamlessly generate quotes in different timelines and for different products with just one click, ensuring that the quote structure and formatting remain unaffected when making adjustments such as removing a product or applying discounts, which has been a significant challenge for us as developers.

We are deploying Conga in Salesforce without any use of third-party apps for deployment. Our project utilizes internal resources such as Copado for deployment, and I am not directly aware of the deployment team details.

My advice for others looking into using Conga Contract Lifecycle Management (CLM) is to focus on the best configuration to achieve better results in the user interface.

I do not have any additional thoughts about Conga Contract Lifecycle Management (CLM) as I have already mentioned all feedback and use cases in our conversation. I rate this solution a seven overall.

My main use case for Conga Contract Lifecycle Management (CLM) is contract creation, tracking approvals, and managing the contract workflow from draft to signature. It is a very nice tool because it helps keep everything organized and in one place, instead of handling different documents manually.

A quick specific example of how I have used Conga Contract Lifecycle Management (CLM) for contract creation and tracking approvals in a recent project is on one workflow where a contract had to go through review and then approval from multiple people. Instead of just sending emails back and forth, I created the contract and sent it through the approval flow. I then tracked each stage in the system. It made it a lot easier for me to see who had approved and who had not, without chasing updates manually.

Regarding my main use case or how Conga Contract Lifecycle Management (CLM) fits into my workflow, it has actually helped me with keeping contract versions clean and very much organized. I have used it a whole lot. Instead of having multiple edited files floating around, everything stays in one place, structured in a structured flow. This makes it very much easier to manage and very much more possible to avoid mistakes.

The best features Conga Contract Lifecycle Management (CLM) offers, in my experience, are workflow automation, approval tracking, and version control. Workflow automation makes the whole contract process move without manual follow-ups. Approval tracking shows exactly where things are stuck. Version control is very helpful because it keeps everything in one place and then avoids confusion with having to deal with multiple document copies.

Out of those features, the one that has made the biggest difference for me is the workflow automation. It removes the manual chasing and keeps everything going automatically. Once a contract is created, the system guides it through each step. I do not have to constantly push it forward. It just makes the whole process smoother and then helps me save a whole lot of time.

Conga Contract Lifecycle Management (CLM) has positively impacted my organization or my work by making the whole contract process much faster and much more organized. Before, a lot of time was spent actually following up on approvals and then checking document versions. Now, everything is just tracked in one place and it is very much easier to see progress and keep things moving smoothly without delays.

Regarding a good summary of the features, what I can say is that it is actually a good summary. One extra thing I can be able to add is that it really helps reduce errors a whole lot, because everything flows through a set process instead of just being handled manually. I love using Conga Contract Lifecycle Management (CLM).

To improve Conga Contract Lifecycle Management (CLM), there are just a couple of things that need to be fixed. First, the setup can feel a little bit complex at the start, especially for new users. A simpler onboarding flow can actually go a long way in helping. Also, more built-in templates for common contract workflows would make it way faster to get started with without building everything from scratch.

Regarding the needed improvements, I think I would also add a better built-in in-app guidance while building workflows. Small tips or step-by-step instructions inside the system would make it much easier for new users and also reduce a whole lot of mistakes.

I have been using Conga Contract Lifecycle Management (CLM) for two-plus years now. It was one of the tools that I started using when I delved deeper into workflow automation. I mainly use it for contract flow and the document management side of Conga Contract Lifecycle Management (CLM).

My advice to others looking into using Conga Contract Lifecycle Management (CLM) is that they should start small and begin with simple contract workflows first. You can scale up to build as soon as you get more comfortable because you have to master the system and how it looks and what works and what does not work. Also make sure your contract templates are well-prepared very early. This makes everything much more smoother later on.

Conga Contract Lifecycle Management (CLM) is a very good, solid tool for managing contracts end-to-end. Once you get used to it and once you master it, it actually works a whole lot. It can really help to reduce manual work and then keep everything organized in one flow. I would rate this review an eight out of ten.

My main use case for Conga Contract Lifecycle Management (CLM) is that my client is using it to generate documents from the opportunity object based on requirements and to track when users sign contracts and their status. We manage these activities through Conga Contract Lifecycle Management (CLM).

The best feature Conga Contract Lifecycle Management (CLM) offers is its reliability, which is more dependable compared to Conga Composer. This main feature allows us to arrange things with more conditions.

Conga Contract Lifecycle Management (CLM) has positively impacted my organization since this is the package provided by the company, and we use it based on the client's requirements. This is a paid feature that we configure with Salesforce because it has a good integration process and works closely with Salesforce CRM.

Conga Contract Lifecycle Management (CLM) can be improved because implementation can be complex, and the loading process could be enhanced. Additionally, I would appreciate a new version of the UI since I have been using Conga Contract Lifecycle Management (CLM) for two years and am still seeing the same interface, while everything else has been modified. I think Conga Contract Lifecycle Management (CLM) should be updated and provide all documentation in a simple way so any new user can work easily.

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

Conga Contract Lifecycle Management (CLM) is stable.

The customer support for Conga Contract Lifecycle Management (CLM) is good. When we raise an issue, we receive feedback or answers from the customer support team.

Before using Conga Contract Lifecycle Management (CLM), we initially used S-Docs for document generation, but since S-Docs has limited features, we switched to Conga Composer.

I have seen a return on investment. I have worked on Salesforce CPQ in which we manage things and save money to set up the product based on pricing.

My experience with pricing, setup cost, and licensing for Conga Contract Lifecycle Management (CLM) is good.

Before choosing Conga Contract Lifecycle Management (CLM), I evaluated Conga Composer because Conga Contract Lifecycle Management (CLM) has more features and options compared to Conga Composer.

Regarding Conga Contract Lifecycle Management (CLM)'s AI capabilities, I think there should be conditions so that client information should not be shared with someone else. The model cannot train with our client information, so there should be some guidance or security whenever we start to use that AI feature. All conditions should be mentioned in a simple way so everyone can understand and change their settings according to our requirements.

Currently, Conga Contract Lifecycle Management (CLM) is good regarding its AI capabilities according to the requirements based on Conga.

My advice to others looking into using Conga Contract Lifecycle Management (CLM) is that if they want to manage documents in large volumes, Conga Composer will be the best option for them, and I have suggested the same for our clients. Some clients had not used Conga Contract Lifecycle Management (CLM) because it is a paid package, but after we provided all the documentation and advantages, they are now using Conga Composer.

I have mentioned everything needed for Conga Contract Lifecycle Management (CLM). I would rate this product 8.5 out of 10.

I have been using Conga Contract Lifecycle Management (CLM) for about a year.

My main use case for Conga Contract Lifecycle Management (CLM) is for contract management, and I also use it for e-signatures.

A specific example of how I used Conga Contract Lifecycle Management (CLM) for contract management or e-signatures in my daily workflow is that I failed to implement it in a meaningful way after one year; however, the e-signature I used on a daily basis for both internal and external contracts made a difference.

The best features that Conga Contract Lifecycle Management (CLM) offers in my experience include the tight integration with Salesforce as the CRM of choice that attracted us to it, and the e-signature feature was very useful as it used the backbone of Adobe to support us.

The integration with Salesforce and the Adobe-backed e-signature impacted my workflow positively because it was used on the backbone of Adobe, which gave a lot of people confidence that it was good. When we sent it to a customer, many of them were slow to accept it, but when they saw that it was Adobe, they accepted it much more readily. However, in terms of the contract management application, it required what seemed like endless amounts of tweaking and modifications in Salesforce to get anything meaningful out of it.

Conga Contract Lifecycle Management (CLM) did not impact my organization at all because after about a year, we canceled the contract as we just could not get it to work.

The decision to cancel was led by specific challenges or issues that made it unworkable for my team, such as Conga Contract Lifecycle Management (CLM)'s reliance on Salesforce, which uses a lot of Salesforce in-built capabilities, with most user requirements satisfied through Salesforce modifications rather than Conga Contract Lifecycle Management (CLM). I had looked at Spring at the time, and that was much more of an independent application, but it was more expensive.

In my opinion, Conga Contract Lifecycle Management (CLM) could improve by reducing its reliance on Salesforce. In our case where other comanies in the group used different CRM systems this reliances caused a lot of problems as it could not be considered as a possible solution for any of these companies. The implementation created confusion among the user community as everything seemed possible, yet nothing was possible.

I found the user experience challenging, as it was hard to know when I was actually in Conga Contract Lifecycle Management (CLM) contracts; my legal team struggled to understand the workflow, as everything indicating contracts had to be done in Salesforce, leading to them typically getting lost in the application or the modifications. Therefore, Conga Contract Lifecycle Management (CLM) needs to build more of a bolt-on to Salesforce rather than being completely integrated.

In my experience, Conga Contract Lifecycle Management (CLM) was stable.

I never got to test the scalability of Conga Contract Lifecycle Management (CLM) since I only had a limited number of users, but I was assured it would scale appropriately if rolled out.

Customer support for Conga Contract Lifecycle Management (CLM) seemed to be very good.

I did not previously use a different solution before Conga Contract Lifecycle Management (CLM).

I have not seen a return on investment from Conga Contract Lifecycle Management (CLM), as it was a waste of time; I spent a long time trying to get it to work, and it was not adopted by the users, ultimately failing to live up to what I had promised to the business.

My experience with the pricing, setup cost, and licensing for Conga Contract Lifecycle Management (CLM) is that it was significantly cheaper compared to other options I evaluated.

Before choosing Conga Contract Lifecycle Management (CLM), I evaluated Spring CRM and the Spring contract management.

The e-signature was the most traction; as I mentioned, the main product proved unworkable.

I found the fact that it was so tightly integrated with Salesforce very good; however, it did mean that I was stuck with problems when looking at changing CRM to Microsoft Dynamics, and I had a problem with Conga Contract Lifecycle Management (CLM) because the implementation was not transportable to Microsoft Dynamics.

My advice to others looking into using Conga Contract Lifecycle Management (CLM) is to really understand and spend a lot of time defining what you want from a contract management system, engage with all potential users, and have them involved in reviewing the products for user buy-in. One of the problems I ran into was the lack of user buy-in at the end, especially since the legal team tends to prefer using what they know, which led us to struggle.

The main thing about Conga Contract Lifecycle Management (CLM) is that the implementation different that say a typlical app implementaion, being very integrated into Salesforce. It is difficult to understand what is Salesforce and what is Conga Contract Lifecycle Management (CLM),much of the value was actually coming from core Salesforce. This needs to be defined by Conga Contract Lifecycle Management (CLM), and the ingrained nature of the implementation left us with a problem when asked to move to a different application on the CRM side.

The main reason I rate Conga Contract Lifecycle Management (CLM) a three out of ten is that most of Conga Contract Lifecycle Management (CLM)'s functionality is derived from Salesforce; a significant amount of contract management could be done within Salesforce without the actual need for Conga Contract Lifecycle Management (CLM). When I compared it to Spring, there was a lot of clever functionality within Spring that would have met my needs better; however, Conga Contract Lifecycle Management (CLM) was cheaper, which is why I chose it. I would rate Conga Contract Lifecycle Management (CLM) a three out of ten overall.

Conga Contract Lifecycle Management (CLM) is used for managing the complete contract lifecycle within Salesforce. On a day-to-day basis, it is used for contract creation, document generation, approval workflows, contract reviews, tracking contract status, and maintaining a centralized repository for contract documents. It helps streamline the process from contract request through approval, execution, and renewal while ensuring compliance and visibility across teams.

The best features of Conga Contract Lifecycle Management (CLM) are its contract lifecycle automation, approval workflow and management, document generation capabilities, and seamless integration with Salesforce. It provides a centralized repository for contracts, which improves visibility and tracking. It helps to standardize contract processes, reduce manual effort, and ensure compliance through automated workflows and audit trails. Another valuable feature is the ability to manage a contract from creation through approval, execution, and renewal within a single platform, making the entire process more efficient and easier to monitor.

It has had a positive impact on the organization by streamlining the entire contract management process. It has reduced manual effort, improved the speed of contract creation and approvals, and provided better visibility into contract status and key milestones. It has also helped standardize the contract process across teams, reducing errors and ensuring compliance with company policies. Since all contract-related information is stored in a centralized system integrated with Salesforce, users can easily access and track contracts, which improves collaboration and decision-making. Overall, Conga Contract Lifecycle Management (CLM) has increased operational efficiency, improved contract turnaround times, and provided greater control over the contract lifecycle.

Lifecycle automation has helped the team by reducing the amount of manual follow-up required during the contract process. Instead of users manually routing contracts to different stakeholders, the system automatically moves contracts through review and approval stages based on predefined business rules. This has improved consistency and reduced processing time. Document generation has also had a significant impact. Rather than creating contracts manually, users can generate standardized contract documents directly from Salesforce using predefined templates. This reduces errors, ensures the correct language and clauses are used, and saves a considerable amount of time for business users. Overall, these features have improved efficiency, increased process visibility, and helped the team manage a higher volume of contracts with less manual effort.

Conga Contract Lifecycle Management (CLM) is a robust solution, but there are a few areas where it could be improved. The first is ease of configuration. Some advanced workflows and business rules can be complex to set up and maintain, especially for organizations with unique contract processes. Another area is reporting and analytics. While the platform provides reporting capabilities, more out-of-the-box dashboards and insights would help business users monitor contract performance, renewals, and bottlenecks more effectively. The user interface could be further simplified in certain areas to make navigation and adoption easier for new users. These enhancements would improve the overall user experience while reducing administrative effort.

From an integration perspective, while Conga Contract Lifecycle Management (CLM) integrates well with Salesforce, more pre-built connectors and simplified integration options for third-party systems could reduce implementation effort. In terms of support, faster resolution times for complex technical issues and more detailed implementation documentation would be helpful, especially during large-scale deployments. Regarding scalability, Conga Contract Lifecycle Management (CLM) generally handles enterprise use cases well, but performance optimization for organizations managing very large contract volumes and complex workflows would further enhance the user experience. Overall, these are enhancement opportunities rather than major concerns, and they would make an already strong platform even more effective.

Conga Contract Lifecycle Management (CLM) has been used for approximately one year as part of a Salesforce project.

I have not worked extensively with the AI-specific capabilities of Conga Contract Lifecycle Management (CLM), so a detailed assessment of its accuracy cannot be provided. However, from the limited exposure that has been had, the outputs have generally been consistent and useful for supporting contract-related processes. In my experience, AI-generated solutions and insights should still be reviewed by business or legal users, especially for important contract decisions. Overall, no major reliability issues have been encountered, but human review remains an important part of the process.

Conga Contract Lifecycle Management (CLM) is deployed in the organization as a public cloud solution. Since it is integrated with Salesforce, users access the application and contract data through the cloud environment. This provides scalability, accessibility, and easier maintenance compared to on-premises deployments.

The recommendation would be to clearly define your contract management process and requirements before implementing Conga Contract Lifecycle Management (CLM). The platform is very powerful, but organizations get the most value when they have well-defined workflows, approval processes, templates, and governance policies in place. I would also recommend investing time in the initial configuration and user training to ensure strong adoption. Since Conga Contract Lifecycle Management (CLM) integrates well with Salesforce, organizations already using Salesforce can benefit significantly from having contract management and customer data in a single ecosystem.

My perspective is primarily based on Conga Contract Lifecycle Management (CLM)'s overall governance and security framework rather than the AI-specific features. From my experience, Conga Contract Lifecycle Management (CLM) provides strong security through the Salesforce security model, including role-based access controls, permissions, audit trails, and data access management.

My experience with Conga Contract Lifecycle Management (CLM) has been positive. It has helped streamline the contract management process through automation, document generation, workflow management, and Salesforce integration. The platform has improved visibility and efficiency across the contract lifecycle. I would rate this product an eight out of ten.

Conga Contract Lifecycle Management (CLM) is primarily used for contract management and the workflow related to contracts for companies. It can be used to make modifications in contracts while maintaining versioning, approving contracts, and sharing them between departments.

The best feature of Conga Contract Lifecycle Management (CLM) is the versioning capability because you can see the updates and everybody can see the changes. It helps with collaboration, reduces the time required for keeping updates, and shows the updates in a more transparent way.

Conga Contract Lifecycle Management (CLM) had a mode called Kira that was related to artificial intelligence, and it was quite difficult to work with. The artificial intelligence was not working properly, and a lot of improvement has to be done. The AI issues included inaccuracy and unreliability. We were using Kira and had to do a lot of tests, and still, it was not working perfectly.

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

I did not have any issues while deploying Conga Contract Lifecycle Management (CLM) as it was stable for me.

I did not experience any scalability issues.

The employees were quite helpful.

I did not have any issues while deploying Conga Contract Lifecycle Management (CLM) as it was stable for me.

I cannot answer this question because I was doing the deployment of Conga Contract Lifecycle Management (CLM), I was not giving the price and cost, and I did not negotiate licensing.

I cannot answer this question because I was doing the deployment of Conga Contract Lifecycle Management (CLM), I was not giving the price and cost, and I did not negotiate licensing.

Conga Contract Lifecycle Management (CLM) governance was quite good because it is related to Salesforce, so it is quite intuitive. Regarding security, I did not have any problems. I was doing the deployment, so I did not know what the result was on the organization because it was visible after I left the project.

I believe that the organization has to be ready for Conga Contract Lifecycle Management (CLM), so not all companies are ready to have CLM. A lot of them do not have the documents in digital version, so first, they have to be prepared before applying CLM. I would rate this review eight out of ten.

My main use case for Conga Contract Lifecycle Management (CLM) is generating documents, so once we click on a button, the document should be generated in the back end and that should sit in the notes and attachment, and that document will be used for signing purposes using DocuSign.

We are using Conga Contract Lifecycle Management (CLM) to generate different types of documents, including DocX, CSV, Excel, and PDF.

Conga Contract Lifecycle Management (CLM) has positively impacted my organization by reducing errors that we encountered when we were using a third-party tool for document generation. Since we started using Conga Contract Lifecycle Management (CLM), we do not find such types of errors, and it is helping the company to boost the economy.

In my experience, the best features offered by Conga Contract Lifecycle Management (CLM) is that data can be collected from multiple objects like accounts and contacts, and I can use Conga Contract Lifecycle Management (CLM) queries to fetch any multiple objects.

I find that the ability to collect data from multiple objects and use Conga Contract Lifecycle Management (CLM) queries in my day-to-day work makes things easier. If we do not have a Conga Contract Lifecycle Management (CLM) document, we have to rely on manual typing, and having a Conga Contract Lifecycle Management (CLM) document generated in the back end is very useful, reducing a lot of time.

Conga Contract Lifecycle Management (CLM) could be improved as sometimes when we click on the document, it indicates success without generating a document, requiring us to check the logs. Having a clear error message for failures like invalid Conga Contract Lifecycle Management (CLM) queries or configuration issues would be much better because it would be impractical to check every record in real-time.

Regarding necessary improvements, better error handling is needed for invalid Conga Contract Lifecycle Management (CLM) query IDs, and when document or attachment names contain invalid characters, it would be helpful if the system communicated these issues instead of just indicating failure without explanation.

I have been using this solution for about six years.

In my experience, Conga Contract Lifecycle Management (CLM) is stable and there has been no downtime for us. I did not hit any type of limit in my career.

Conga Contract Lifecycle Management (CLM) handles growth and increased workloads very well.

Customer support for Conga Contract Lifecycle Management (CLM) has been good. When we purchased the Conga Contract Lifecycle Management (CLM) license, we received a manager's email ID, and they resolve our issues promptly when we reach out.

I would rate the customer support a nine out of ten.

Before using Conga Contract Lifecycle Management (CLM), we were using a manual process and did not have an automatic process.

Conga Contract Lifecycle Management (CLM) is deployed in my organization through a package, which we installed, making it available for all users.

We did not evaluate other options before choosing Conga Contract Lifecycle Management (CLM) as we were recommended to use it at Deloitte, where they are using Conga Contract Lifecycle Management (CLM) for other portfolios as well.

I have seen a return on investment since using Conga Contract Lifecycle Management (CLM), particularly in terms of time saving.

I estimate that my team saves about one or two hours for each employee on a daily basis compared to before using Conga Contract Lifecycle Management (CLM).

Regarding pricing, it is a little bit higher, but when we go for bulk purchase, we do receive some discounts.

We purchased Conga Contract Lifecycle Management (CLM) through the Salesforce AppExchange.

The types of errors we used to see before switching to Conga Contract Lifecycle Management (CLM) were due to a lack of a proper error mechanism. The UI would say the document is generated, but there would be no document in the back end, showing us that there were many errors happening in the background, whereas Conga Contract Lifecycle Management (CLM) query is user-friendly and shows a clear error message.

My advice to others considering Conga Contract Lifecycle Management (CLM) is that it can handle all types of documents, including password-protected PDFs, and it allows for gathering multiple object data into a single document using Conga Contract Lifecycle Management (CLM) queries.

I rate Conga Contract Lifecycle Management (CLM) an eight out of ten. I choose eight out of ten because two points are for error handling and better improvements, one point is for better handling of the Conga Contract Lifecycle Management (CLM) Composer URL request, and the second point is for better error response for REST API requests.

I believe I have covered everything regarding Conga Contract Lifecycle Management (CLM), including error handling and what went well.

My main use case for Conga Contract Lifecycle Management (CLM) is managing employment contracts and SLA contracts.

Conga Contract Lifecycle Management (CLM) offers smooth integration with our existing systems like Salesforce, as well as tracking and using Conga queries in the back end to fetch the data.

The tracking feature helps me in my day-to-day work by automating the system completely with our Salesforce, which saves me time and helps avoid mistakes.

We have created Conga templates and added Conga queries at the back end that dynamically fetch the data, render it on the template, and forward it to the end-user, making it a seamless transaction that saves a lot of time with no manual intervention needed.

Conga Contract Lifecycle Management (CLM) has positively impacted my organization, and I have noticed improvements in productivity, accuracy, and turnaround times.

I see one blind spot for Conga Contract Lifecycle Management (CLM) in that additional logic features depending upon user types and customer types would be helpful.

Improvements in reporting, integrations, and user experience are areas that need addressing.

I have been using the solution for nearly three years.

Conga Contract Lifecycle Management (CLM) is stable in my experience, showing no downtime or issues.

Conga Contract Lifecycle Management (CLM) has excellent scalability and can handle growth and more users easily, as we have nearly 10 lakhs of records.

The customer support for Conga Contract Lifecycle Management (CLM) is good, and I have reached out to them and faced no challenges, with very good response times.

I would rate customer support a 10 out of 10, as it has been excellent throughout.

Initially, we were using Conga as well as DocuSign, but we are now only using Conga Contract Lifecycle Management (CLM).

Conga Contract Lifecycle Management (CLM) is deployed in my organization as a private cloud. We have installed managed packages of Conga Contract Lifecycle Management (CLM) and then completed our integration while using our Conga Admin Console in Salesforce to configure all the settings, templates, and queries.

We are not resellers; we are a service-based company and partners with the vendor.

I have seen a return on investment with Conga Contract Lifecycle Management (CLM), as fewer employees are needed to draft processes because it is now automated.

My experience with pricing, setup cost, and licensing for Conga Contract Lifecycle Management (CLM) indicates that whenever we use it with Salesforce, it is at an enterprise level, making the pricing a bit high. If the pricing were lower, it would be more useful for other SMEs.

We have evaluated similar applications, but the use cases are completely different. We have another provider called G-Proper, which is a faxing application, but Conga Contract Lifecycle Management (CLM) is a completely email application, marking the main difference.

Everything we use regarding AI capabilities is from Salesforce, like Agent Force, and I have not used the AI capabilities in Conga Contract Lifecycle Management (CLM), so I cannot comment on its governance and security.

The accuracy and reliability of Conga Contract Lifecycle Management (CLM)'s AI output have met my expectations, and we have faced challenges setting it up for the agent we built in Salesforce, but it is working as expected.

I rate this review a 10 overall.