What needs improvement with Conga Contract Lifecycle Management (CLM)?

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.

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.

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

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

Conga Contract Lifecycle Management (CLM) is easy to use for me, though one area for improvement could be Conga Composer, as it would be beneficial to simplify how I open it and add my queries quickly during the automated process. I chose a nine because sometimes I feel that opening Conga Composer feels a bit heavy, and occasionally I need to refer to additional documents to complete specific tasks, which is the only reason preventing a perfect score.

Sometimes I feel that the generation of templates in Conga Contract Lifecycle Management (CLM) is slow or it breaks somewhere. This is a rare case, but it is something I have heard from my colleagues, though I have not personally experienced it.

Conga Contract Lifecycle Management (CLM) can be further improved in a few areas to enhance user experience and efficiency. The user interface could be made more intuitive and faster to navigate, especially for new users learning the system. Performance optimization during large contract searches or bulk processing could also improve speed. Additionally, enhancing the AI-powered search with more contextual understanding and smarter close recommendations would make it even more powerful. Integration flexibility with non-sales systems and more advanced real-time collaboration features during negotiation could also be strengthened. Overall, these improvements would make the platform even more seamless, intelligent, and user-friendly. It can sometimes feel slow, so I think additional strong real-time collaboration tools during negotiation and smoother integration with non-sales systems would also be helpful.

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.

Regarding what I would improve in Conga Contract Lifecycle Management (CLM), from my technical understanding, there is improvement criteria everywhere, but currently, we can achieve whatever we want. They are implementing other things and improving as well, and I do not recall any issue we have faced right now. Conga Contract Lifecycle Management (CLM) can be improved in every system or ERP. While we are not facing any issues currently, there might be some sticking points at some stages, but that is primarily due to user awareness. Waiting for the time to complete transactions helps it run fine. In terms of specific features missing in Conga Contract Lifecycle Management (CLM), the standard process is fine. However, we can enhance more customization, implement signature steps, or allow direct signing within the CLM tool. Negotiation can also be improved. However, it is working fine currently. The complexity of customization in Conga Contract Lifecycle Management (CLM) alongside the mentioned sync issues could be improved. However, the syncing issue primarily stems from different integrations such as SAP. While using SAP as an order or contract tool or integrating other tools for signing, there may be some slowness, but the templates and overall customizability are fine. Conga's customization is greater than many other CLM tools, so my assessment remains a nine.

Conga Contract Lifecycle Management (CLM) is a powerful tool, but there are a few areas where it could be improved. One challenge is the initial setup and configuration, especially for complex workflows and approval hierarchies. It can require significant time and expertise to get everything aligned with the business process. Another area is the user interface, which can feel a bit complex for new users. We also find that reporting and customization could be more flexible. While standard reports are used, creating highly tailored reports sometimes requires additional effort or technical support. The main areas for improvement would be the initial setup complexity, a steeper learning curve for new users, and more flexible reporting. But overall, it is a strong platform once configured properly. Integration is also complex, whether we need to integrate other ERP tools or middleware tools, so integration and mobile access are two areas where there is room for improvement. Setting up and maintaining these integrations can be complex.

The only drawback of Conga Contract Lifecycle Management (CLM) is that it does not work for small-scale business areas because I have implemented it for one customer with four or five pages of templates and three to four record types. For that small business, Conga Contract Lifecycle Management (CLM) does not work well because it is a bit complicated. Sometimes all customers need is a click of a button to go in and do things, and Conga Contract Lifecycle Management (CLM) is a bit complicated for such kinds of businesses. There are definitely areas where Conga Contract Lifecycle Management (CLM) could be easier to use for smaller businesses, particularly making processes more streamlined and user-friendly.