Agiloft Contract Lifecycle Management Platform
Centralized contract approvals have streamlined lab operations and support faster purchasing
What is our primary use case?
My main use case for Agiloft Contract Lifecycle Managment (CLM) involves managing all vendor contracts, material transfer agreements, and creating vendor contracts, reviewing them, updating them, and maintaining the lifecycle of the contracts, as well as getting contract approvals. During this process, I work with different teams including legal teams, scientists, managers, and different vendors until we receive approvals on all material transfer agreements and vendor contracts so that we can purchase the items.
The main processes I manage with Agiloft Contract Lifecycle Managment (CLM) include all quote approvals, non-disclosure agreements approval, vendor contracts, material transfer agreements, and purchasing orders.
What is most valuable?
I appreciate working with Agiloft Contract Lifecycle Managment (CLM) because it offers user-friendly features. Uploading a draft of any contracts, material transfer agreements, NDAs, or quotes is easy, and it is also easy to work with multiple team members for them to review. I can request other team members to review and approve, and we can manage who is currently reviewing and who has approved it. Once the approval process is completed, we maintain all documents in one place, making them audit-ready. If we want to pull any documents from Agiloft Contract Lifecycle Managment (CLM), it is easy to do so. This provides central communication for managing all contracts.
During Agiloft Contract Lifecycle Managment (CLM) and approval processes, I find it user-friendly because I can assign approvals to primary approvers, secondary approvers, and final approvers. I can also track the exact status when I assign it to the primary approver. Once that is done, I can also send them reminders. If the team has not approved, I send them email reminders to speed up the approval process for the contracts or at least get back to me with any comments when I work with different teams.
Agiloft Contract Lifecycle Managment (CLM) has a positive impact on my organization because it is time-saving. As I mentioned before, it centralizes communication for all vendor contracts. We maintain all contracts, POs, quotes, different MTAs, and everything in one location. This process avoids going back and forth, and there is a place where other team members can look up what their tasks are, whether they need to review any contract, and whether they can approve the contract. For everyone, it is a place where we can all work to speed up the contract management approval process. This helps save considerable time for everyone. I work with different team members, and that was one aspect where we can communicate with different team members on one platform. Furthermore, we could speed up the vendor contract management process. This helps us to have smoother lab operations regarding sample procurement, any orders we want to do, any equipment we want to obtain, and vendor communications as well. Overall, we achieve improved efficiency in lab operations.
What needs improvement?
I feel there are always opportunities to improve Agiloft Contract Lifecycle Managment (CLM). For example, the process can be improved by standardizing contract intake, approval workflows, naming conventions, required fields, and renewal notifications.
It would be great if Agiloft Contract Lifecycle Managment (CLM) could integrate with NetSuite, an ERP purchasing system. That way, I would not need to upload all the approved contracts, quotes, and purchase orders to NetSuite. Additionally, during the approval process, this could have automated routing based on contract type, dollar value, and department.
For how long have I used the solution?
I have been using Agiloft Contract Lifecycle Managment (CLM) for two years when I was working at Thales Biomedical Corporation.
What do I think about the stability of the solution?
Agiloft Contract Lifecycle Managment (CLM) is stable.
What do I think about the scalability of the solution?
Agiloft Contract Lifecycle Managment (CLM) is definitely designed to be scalable as the number of contracts, users, departments, workflows, and integrations increases.
How are customer service and support?
My experience with customer support for Agiloft Contract Lifecycle Managment (CLM) was good.
Which solution did I use previously and why did I switch?
We did not use any different solution; we only used Agiloft Contract Lifecycle Managment (CLM).
What was our ROI?
With Agiloft Contract Lifecycle Managment (CLM), we could save money and also reduce the number of employees needed. Only a few important people from the executive team, the legal team, and the necessary scientific team, such as team leads and the lab operations, were required, as I was the one managing the contracts in Agiloft Contract Lifecycle Managment (CLM). For that purpose, it definitely worked well with Agiloft Contract Lifecycle Managment (CLM) managing it.
What's my experience with pricing, setup cost, and licensing?
My experience with the pricing, setup cost, and licensing for Agiloft Contract Lifecycle Managment (CLM) was good. The pricing and licensing were satisfactory because we used it. I was at that company for two years, and we were satisfied with Agiloft Contract Lifecycle Managment (CLM) pricing and working on Agiloft Contract Lifecycle Managment (CLM); we never considered switching to another solution.
Which other solutions did I evaluate?
Before I joined the company, Agiloft Contract Lifecycle Managment (CLM) was already in place, so I did not evaluate other options.
What other advice do I have?
I experienced a specific outcome with Agiloft Contract Lifecycle Managment (CLM) when I worked on the Bio-Rad equipment purchase, the DDPCR. During that time, we had to go through the terms and conditions on the quote. Given the urgency of acquiring this equipment as soon as possible, I uploaded and initiated the approval process. I could interact with different teams and also sent them reminders. One by one, I received all three approvals from different team members within two days, allowing me to purchase the equipment on time.
I rate Agiloft Contract Lifecycle Managment (CLM) an 8.5 out of 10 because it can improve with better integration into other ERP procurement platforms such as NetSuite, Ariba, Oracle, and Coupa. A better dashboard control would also enhance the experience.
I have never faced any security issues with Agiloft Contract Lifecycle Managment (CLM). I believe all vendor contracts, vendor information, and company information are well-protected in Agiloft Contract Lifecycle Managment (CLM.
Regarding Agiloft Contract Lifecycle Managment (CLM) and AI, I am fully satisfied with its accuracy and reliability of output.
I had a great experience working with Agiloft Contract Lifecycle Managment (CLM), and I definitely recommend it to any company or customers exploring options for vendor contract management systems because I had a great learning experience and very good experience working on Agiloft Contract Lifecycle Managment (CLM). Agiloft Contract Lifecycle Managment (CLM) is very organized, user-friendly, and serves as a single source to maintain all different contracts and all data related to workflows, renewals of contracts, and maintaining accurate contract records. It also helps to understand the roles of different teams and gives the necessary permissions. I definitely recommend it to others.
I have no additional thoughts about Agiloft Contract Lifecycle Managment (CLM); I just want to know how you are planning to improve the current Agiloft system in the future.
Automation has transformed contract workflows and now saves hours on reviews and renewals
What is our primary use case?
My main use case for Agiloft Contract Lifecycle Managment (CLM) is contracts management and execution. I use Agiloft Contract Lifecycle Managment (CLM) for receiving contracts, sending drafts to different teams, and then sending them to attorneys for review, creating DocuSign documents, and then creating a repository for the contracts.
I also manage renewal and expiration management, and obligation management, where I track contractual obligations such as deliverables, payment terms, insurance requirements, and terminations or indemnity clauses. I keep a tab on these clauses. I also manage vendor and supplier contracts, and conduct compliance audits for my contracts.
What is most valuable?
The best feature Agiloft Contract Lifecycle Managment (CLM) offers for me is contract lifecycle management, which manages contracts from initiation to end, including drafting, review, approval, and signatures. I love the workflow automation. It automatically routes the contract to legal, compliance, and finance people, so I don't have to go to everyone individually. It allows different approval paths based on the contract type. It also has an automated alert feature that helps me track renewals or notice periods, or if something is coming to an end, or if there are any fees related to that.
The automated alerts and approval paths save a lot of time so that I don't have to check a spreadsheet for renewal dates or expiration dates. I receive an alert as the contracts manager or contract lifecycle manager, and then the teams who are actually the owners of the contract also get a notification. Even if I sometimes forget or ignore the notifications, they have the notices and notifications, and they come to us indicating that a contract is expiring in X days, so that we can work on renewals, terminations, or stopping any auto-renewal. This is very helpful.
I really love the reporting dashboard of Agiloft Contract Lifecycle Managment (CLM), and when I can download all contracts in an Excel sheet format and correct any names or dates, at least I have something to see where I can find small mistakes. I also love the template management and e-signature integration. These are very exciting features.
Agiloft Contract Lifecycle Managment (CLM) has positively impacted my organization. The automation process has helped me to have better contact with my attorneys. They have their own alerts about the contract, so I don't have to remind them. That is the best feature; it helps me with a lot of manual follow-ups that are now automated. It acts as a centralized repository so that we don't have to go to everyone's desk or email to ask for documentation. It gives me real-time visibility of the status of a contract. It also has an automated approval workflow, which helps me a lot and saves a lot of time. If I was spending 10 hours on a contract, now I just spend four hours.
What needs improvement?
I feel Agiloft is a little bit less user-friendly than Conga. I used Conga in my previous experience, which was much more user-friendly than Agiloft. There are too many fields and steps that can discourage business users from submitting requests. It would be great if we could reduce the steps, such as making user intake forms more user-friendly. Automating more routine decisions, such as contract type, approval level, or risk category, or integrating Agiloft with ERP, CRM, or HR systems would also be great. Improving the dashboard a little bit would be beneficial; if it were more visually pleasing, that would be an improvement. Integrating some AI features, automating extraction, flagging unusual clauses, identifying contracts approaching renewal, or getting a summarized version of a contract would also be beneficial.
For how long have I used the solution?
I have been using Agiloft Contract Lifecycle Managment (CLM) for two years.
What do I think about the stability of the solution?
Agiloft Contract Lifecycle Managment (CLM) is stable.
What do I think about the scalability of the solution?
Agiloft Contract Lifecycle Managment (CLM) is highly scalable because it can accommodate increasing contract volumes, user departments, workflows, and integration. Its no-code architecture allows us to modify the workflow as business requirements evolve. The strong governance and standardization are important to prevent excessive customization from making the system difficult to maintain, so workflow scalability is great.
How are customer service and support?
The customer support for Agiloft Contract Lifecycle Managment (CLM) is great.
Which solution did I use previously and why did I switch?
We previously used Intelagree, which is a contract management system, and spreadsheets, which are not very useful. With Intelagree, their AI features were just coming up, and they were not great. Tracking the contract was also a little difficult, which is why we tried to use Agiloft.
How was the initial setup?
We are still trying to deploy Agiloft Contract Lifecycle Managment (CLM); we have not done it completely.
What was our ROI?
I certainly observe a return on investment with time saved and fewer employees needed, so ROI is good.
What's my experience with pricing, setup cost, and licensing?
I was not authorized to discuss pricing, setup cost, and licensing of Agiloft Contract Lifecycle Managment (CLM), but I think it was great; that's why we are having it.
Which other solutions did I evaluate?
Before choosing Agiloft Contract Lifecycle Managment (CLM), I evaluated Conga, Intelagree, and Smartsheet.
What other advice do I have?
I am trying to put together how much I have spent on a contract, how much other teams have spent, and how they remind me about any contract or how I remind them. Everything together, such as follow-up with procurement, finance, and attorney, shows a significant improvement.
My advice for others looking into using Agiloft Contract Lifecycle Managment (CLM) is to focus on business outcomes and process design, not just technology. Agiloft is highly configurable, so it's important to clearly define contracts, processes, approval requirements, roles, reporting needs, and other things. I would also recommend prioritizing integration, user adoption, and data quality.
Overall, I think Agiloft Contract Lifecycle Managment (CLM) is a strong contract management platform, particularly for organizations with great volume, many customers, and numerous suppliers. I would recommend starting with a clear contracting process rather than trying to automate every exception from day one. Another important consideration is long-term administration. I would rate this platform an 8 out of 10.
Customizable and Intuitive
Flexible Screen Integration, but Actions and Rules Feel Too Complex
Contract automation has accelerated deal cycles and uncovered insights but support still needs improvement
What is our primary use case?
My main use case and interaction with Agiloft Contract Lifecycle Managment (CLM) involves implementing and helping clients implement it.
We worked with a company that provided travel recommendations for their customers, and they used contracts. They automated their contracting process with supplier agreements using Agiloft Contract Lifecycle Managment (CLM).
When I helped implement Agiloft Contract Lifecycle Managment (CLM) for this travel recommendations company, I was managing the connector alignment between Agiloft, us as an implementation partner, and the customer.
What is most valuable?
From my experience with these implementations, the best features Agiloft Contract Lifecycle Managment (CLM) offers include drafting contracts, creating templates, and using AI to help redline contracts and connect them back to customer playbooks. The ingestion of third-party documents using Agiloft's AI helps customers who are predominantly using third-party papers through their contracting process. Customers have the ability to review the terms in those contracts using AI and against their own playbooks and rules. Creating workflows for specific contract types, whether it be an NDA, MSA, or a supplier agreement, allows for bespoke workflows so that those contracts are routed to their correct individuals, which massively shortens the time from beginning to end for a contract.
Out of those features, the insights that clients derive from post-signature have had the biggest impact. These insights enable clients to use the data within their contracts to initiate billing cycles, know when it is time to renew that contract automatically rather than having to do this manually, and review which suppliers they are using based on information in the contract. For example, if some of their policies or the laws have changed and some of their supplier agreements do not potentially comply with new laws, they can use a review of that process, potentially saving their company thousands if not millions in potential lawsuits for using suppliers that have policies or unethical trading and are not covered within that contracting process.
Agiloft Contract Lifecycle Managment (CLM) has positively impacted my client organizations by massively reducing contract authoring. Some contracts used to take three months to execute, and we have seen contract execution time reduced from months down to hours.
The reduction in contract execution time has improved client satisfaction, increased deal velocity, and allowed their legal teams to focus on other tasks outside of contracting, thereby freeing up time for the legal departments.
What needs improvement?
Agiloft Contract Lifecycle Managment (CLM) could be improved in several ways. The training is not good, and they do not offer very good training at all. They lack great support for partners looking to implement or customers, tending to charge for what they call expert services to support partners, but they really do not provide support at all. They just shadow projects. The overall support from Agiloft, customer service, and training and enablement could be massively improved.
How are customer service and support?
The majority of the support Agiloft offers customers is based in the US. They could improve their European footprint to support customers based outside of the US.
What other advice do I have?
I would rate Agiloft Contract Lifecycle Managment (CLM) a seven out of ten.
I chose seven out of ten because I think there are others in the market that are doing things a lot better than Agiloft and are far more advanced with their AI. Agiloft seems quite far behind when it relates to AI, specifically generative AI and agentic AI.
Regarding Agiloft Contract Lifecycle Managment (CLM)'s AI capabilities, the governance and security are good. They can offer on-premise solutions for their customers and have been used by some government, security, and financial organizations because they have high clearance for those.
Regarding Agiloft Contract Lifecycle Managment (CLM)'s AI capabilities, the accuracy and reliability of output are okay. Based on prior testing, accuracy was around eighty percent to eighty-four percent.
My advice for others looking into using Agiloft Contract Lifecycle Managment (CLM) is to do your due diligence, make sure that you are fully ready and have all of your requirements up front to avoid surprises down the line, and insist on a good level of support post go-live from Agiloft to ensure continuous support once your partner is off the project. I gave this product a rating of seven out of ten.
Review at a glance
Works Well, But an Upgrade Is Long Overdue
Centralized contract repository has improved visibility and supports detailed spend analysis
What is our primary use case?
My main use case for Agiloft Contract Lifecycle Management (CLM) is uploading all contracts and creating the contract repository. I also create spend reports based on the orders that have been placed. I use Agiloft Contract Lifecycle Management (CLM) for all of the sourcing documentation that I do for RFP, RFX, and auctions. I use it more as a centralized contract repository because it is easier for me to share the links within the teams. I am obviously exploring various modules within the CLM side of Agiloft Contract Lifecycle Management (CLM) to cater to our requirements, which I have been discussing with them.
Agiloft Contract Lifecycle Management (CLM) makes it easier to share links within our teams by providing a centralized contract repository, which I need in the global procurement area where I work on various contracts: mid-size contracts, lower-hanging fruit contracts, and the big-ticket contracts. I essentially need to have a contract repository similar to a Coupa, an Ariba, an SAP workspace, a OneDrive, or a SharePoint. Agiloft Contract Lifecycle Management (CLM) gives me that end-to-end CLM functionality, and it really helps me upload all of the contracts for various projects that I do. I plugged it with Teams. So, for example, if one of my VPs or one of my business unit leaders needs to access a specific contract, I have the admin access, so I can put the permissions in place. Depending on the role and the specification of the requirement in terms of the use case from the business side, I am able to share those links based on what use case and what requirements they have so that they can easily access the contract and understand what they have agreed to. I also use it more in terms of doing the contract redlining and contract review, which is the initial step before I sign off and agree on the contract.
I have summarized my main use case for Agiloft Contract Lifecycle Management (CLM) and how I use it day-to-day, as well as how it is helping us from a day-to-day procurement and stakeholder management perspective.
What is most valuable?
The best features Agiloft Contract Lifecycle Management (CLM) offers include the ease of working. The platform is very easily accessible. It is very easy to comprehend and easy to work with from a day-to-day perspective. It is also very useful for stakeholders to access the specific contracts because you have the option to download the signed contract. They know when the contract was signed, and it has a very good treatment of how the contracts are stored. For example, I have done an overarching MSA, and within that, I have done a SOW, an order form, and probably a change request. So I am able to drill down right up to L3 or L4 in terms of taxonomy of spend. At the same time, I am able to drill down based on the overarching contract and what the sub-work orders or sub-SOWs are within those contracts, plus the change order notifications. This gives me the entire length and breadth of visibility. At the same time, it has all the orders as well because our order management system, the PO, is also enabled within the CLM database.
The taxonomy and the ability to drill down into different contract levels help my team significantly. For example, if a new person in procurement joins and wants to understand which taxonomies and subcategories they are supporting, and they want to have a spend overview based on the orders that are being placed, Agiloft Contract Lifecycle Management (CLM) gives that particular view. I have Tableau plugged in with Agiloft Contract Lifecycle Management (CLM) as a front-end system that provides the order management view of the entire spend taxonomy. It also provides a drill-down in terms of which suppliers I have been working with for the specific categories. At the same time, it provides the spend and details on the contracts that I have with them, whether it is a specific SOW, a bespoke agreement, or an MSA. It has the links and the orders that have been placed. It gives a complete view from a taxonomy perspective where I can drill down based on the type of spend. For example, within IT, I have hardware, software, and services. Within services, I have IT professional services, SaaS, fixed-price services, time and material, IT staff, and IT security services. I am able to drill down based on L3, L4 taxonomy.
What needs improvement?
Agiloft Contract Lifecycle Management (CLM) could be improved in the area of catering more from a CLM perspective. Unlike vendors in this area like Ariba, Coupa, Icertis, and Ivalua, which also provide the sourcing side—RFX, RFP, RFI, auction—through the tool, that area within Agiloft Contract Lifecycle Management (CLM) is lacking. I would be happy to see those modules well-placed and well-balanced based on how other competitors are catering to that requirement. I would also like to see various enhancements within the dashboard and customization based on client and customer requirements. That is something that I would like to see more within the dashboard and the tool.
If I had to pick one area where Agiloft Contract Lifecycle Management (CLM) could be improved, it would be better slice-and-dice options within the dashboard. That is something that is very important and critical for me.
I chose 8 out of 10 because there are certain areas where Agiloft Contract Lifecycle Management (CLM) would need to look at what their competitors are doing. CLM is a very hot area for procurement because it is used by direct and indirect procurement folks. Based on those requirements, use cases, and especially based on what clients need and how their competitors are performing, I think there is room for improvement on the enhancement side, improving the overall customer experience on the dashboard, having more layouts, and having the option to slice and dice the spend and the orders. It would also be good to have different charts and infographics based on the contracts that have been uploaded, which provides a picture to the procurement person. For example, when they are doing a renewal or want to work with the same vendor, it provides some sort of ammunition to make an informed decision and ensure that the data coming out of the tool represents factual insights. This will help drive savings, better outcomes with the supplier, and better stakeholder engagement. It is all linked to how the tool can be more efficient and effective.
For how long have I used the solution?
I have been using Agiloft Contract Lifecycle Management (CLM) for more than six years in different capacities.
What do I think about the stability of the solution?
Agiloft Contract Lifecycle Management (CLM) is stable.
What do I think about the scalability of the solution?
Agiloft Contract Lifecycle Management (CLM)'s scalability is good because I can add users, and I have user and license provisioning as well. I do have that option within the contract.
How are customer service and support?
Customer support for Agiloft Contract Lifecycle Management (CLM) is good because they provide 24/7 customer support. Overall, my experience has been good.
I would rate the customer support 10 out of 10. Whenever there is a query, they always provide feedback. A ticket is created, and they address the ticket in less than 24 hours.
Which solution did I use previously and why did I switch?
I have been using this solution without previously using a different one.
What was our ROI?
I definitely saw a return on investment in terms of time saved, cost reductions, and improvements in compliance. At the same time, I also saw ease of working on the tool. Their technical help is 24/7, and they have an AI bot plugged into the system. For example, if the dashboard freezes or if a specific group is not able to get access to the tool, all of that is handled through their bot. They have multiple questions within that, and based on their FAQs, I can decide which one I want to know and drill down. If there is a specific question that is not captured within the FAQs, I can run it through their bot, which provides responses in real-time. That is a great advantage, especially for stakeholders who take time to understand the platform and the tool.
I do not generally let employees go, so it is more about how I can improve the experience of the tool. But overall, I have definitely seen a 5% to 10% savings in terms of how contracts are managed and how they can be done in a more systematic way.
What's my experience with pricing, setup cost, and licensing?
My experience with pricing, setup cost, and licensing has been overall good. I generally do multi-year agreements with them. Based on the total contract value, I decide savings and user licensing, and look for an optimized cost flexibility model with better payment terms. Overall, they have been pretty good.
Which other solutions did I evaluate?
Before choosing Agiloft Contract Lifecycle Management (CLM), I evaluated other options including SAP Ariba, Tableau, Cognos, Ivalua, Icertis, and the GE solution from different vendors.
What other advice do I have?
I would definitely say that Agiloft Contract Lifecycle Management (CLM) tool is quite good, but I would give the caveat that I should also have discussions with their product team about customization, dashboard creation, and infographics. If I am looking for specific real-time insights and data, I should discuss how that can be funneled. Those are the things that I would call out. But apart from that, the tool does serve its purpose. I have provided everything in a very articulate and lucid manner, and that is what I would like to convey. I give this review an overall rating of 8 out of 10.
Manual contract work has remained challenging while automation has improved internal signing visibility
What is our primary use case?
My main use case for Agiloft Contract Lifecycle Management (CLM) is to help our colleagues in Siemens digitize the contract lifecycle management and automate the contract signing process.
How has it helped my organization?
Agiloft Contract Lifecycle Management (CLM) has positively impacted my organization by eliminating manual contractual signing within the company, although we still have some manual signing or manual contract processes with vendors outside the company. Within the company, you can see the status of the contract, whether it is in signing or who is left to sign, and you have a single platform to manage it all. Previously, we were using a different tool that was slow and not very user-friendly, leading to many problems getting users onto the platform. Many were still trying to sign contracts through email, resulting in lost contracts since our policy requires keeping contracts in our systems for ten years. With Agiloft, everything is organized in one place, with data in tables and our own archival elsewhere in our cloud. Everything is in Agiloft cloud, making data management more streamlined.
What is most valuable?
Agiloft automation is a good feature that stands out to me, and I also appreciate the tables that they provide and the connection from one table to another, as well as the integrations between Adobe for the signing process to Snowflake for the data archival. Additionally, they sometimes provide experts to support you along the way and do the initial setup for your company needs while giving you a period of time where you can approach them for any doubts or any changes that you may need to do. Even after that period expires, you can still reach out to them for additional support, though there is a monetary cost involved. Overall, the experts that they assign you really help you, and the initial setup they do is comprehensive.
The connection between the tables, for example, which we call Rules and Actions, is the most valuable feature for my team because it helps you move the process from one table to another, bringing together contracts and services within a contract, which is another table. This feature also helps you to connect to and talk to different systems, and there are thousands of connectors available that you can use on your platform. I have not tried their AI capabilities yet, but I attended a workshop from them that offered valuable insights.
What needs improvement?
You can build automation workflows similar to robotic process automation with Agiloft Contract Lifecycle Management (CLM), which is an improvement point since you can create those processes or automations to avoid doing things manually. An area for enhancement that I feel could be improved is the user interface, and if I have to suggest something to add to Agiloft platform, it is the presence of logs or history. Currently, when changes are made, it is very difficult for someone else to find what has been changed, so we have faced issues where employees who did those developments left the team and the handover was not complete. If we had a common place where we can find logs or history of what was changed, by whom or when, it would really enhance the platform in my opinion.
There are many improvement points for Agiloft Contract Lifecycle Management (CLM). For example, better logging can greatly help users navigate the complex system with numerous connectors, rules, and actions. Finding where mistakes occur can be time-consuming; thus, improving the search functionality is essential. Furthermore, enhancing workflow processes, similar to robotic process automation, can yield better results. The user interface and development platform need improvement as well since there is currently no provision for writing code, which is essential in a low-code environment. While Agiloft allows for small code scripting with Ruby and others, having an easier way to execute something such as Python would be beneficial, and the current complexity in executing codes is unnecessary and requires streamlining.
For how long have I used the solution?
I have been using Agiloft Contract Lifecycle Management (CLM) for approximately seven months.
What do I think about the stability of the solution?
Agiloft Contract Lifecycle Management (CLM) is quite stable.
How are customer service and support?
The customer support for Agiloft is represented by a couple of experienced individuals who assist us, though their support tool for raising queries or tickets for addressing problems could use improvement. It is neither great nor bad, but there is room for growth.
Which solution did I use previously and why did I switch?
Previously, we were using a different tool that was slow and not very user-friendly, leading to many problems getting users onto the platform. Many were still trying to sign contracts through email, resulting in lost contracts since our policy requires keeping contracts in our systems for ten years. With Agiloft, everything is organized in one place, with data in tables and our own archival elsewhere in our cloud. Everything is in Agiloft cloud, making data management more streamlined.
How was the initial setup?
Expecting a lot of work and being involved in the setup when Agiloft sets the system for you is my advice to others looking into using Agiloft Contract Lifecycle Management (CLM). Engaging in the beginning helps you understand the platform, and it is important not to focus too much on the basic training offered, as it may not meet your organizational needs. My advice is to be engaged throughout the setup process of your organizational platform from Agiloft.
What was our ROI?
As a developer, I do not possess metrics regarding return on investment, but as a small team with many customers, we have noticed a decrease in the number of tickets related to various issues every month, indicating that things are working as expected. Since finance and pricing mistakes are not tolerated, it is encouraging to see a decline in ticket numbers over the last year, although I cannot provide exact metrics.
What's my experience with pricing, setup cost, and licensing?
I did not manage the pricing, setup cost, or licensing since when I joined the team, the setup was already done by Agiloft when purchasing the service. Siemens developers need only provide a specification of what they need for the setup to be handled.
What other advice do I have?
I would rate this review overall as a three out of five.
Improved contract reviews and standardized playbooks but still needs stronger financial integrations
What is our primary use case?
My main use case for Agiloft Contract Lifecycle Management (CLM) includes contract review, submissions, editing the contracts, ensuring that our legal team has a complete repository of all the contracts with terms and conditions, making sure that there are playbooks and templates defined for typical contracts, and finding out anomalies.
A specific contract process where Agiloft Contract Lifecycle Management (CLM) helped me was when it easily picked up payment terms. For instance, if we had a standard payment term of Net 45, and the contract signed with a vendor did not use that, it finds that out. There are many different terms it automatically detects and identifies, notifying the contract administrators. If our policy is to avoid three-year contracts, it flags those and notifies us as the IT leaders. Another example is when the contract language differed from our standard templates, it compares and contrasts and identifies challenges with insurance terms and coverage.
What is most valuable?
The best features of Agiloft Contract Lifecycle Management (CLM) include creating a playbook and integrations with the Microsoft tech stack.
The integration with the Microsoft tech stack helped my workflow by ensuring that Microsoft single sign-on is working, along with integration with SharePoint and other Microsoft toolkits such as Microsoft go-to-market solutions and Microsoft Business Online. The playbook creation feature provided a good, easy way to create playbooks for standard agreements, subscription agreements, rental agreements, and contracts.
Agiloft Contract Lifecycle Management (CLM) has positively impacted my organization by improving the lifecycle of contract reviews and approvals, which may have saved some time for the legal team to do other work.
It is hard to estimate time saved for my legal team because when you start using a new tool, the time it takes to learn it and get settled in varies. After everything settled, the review time reduced from three hours to about two hours for contract reviews.
What needs improvement?
Every software can improve, so better integration with the Oracle financial system and out-of-the-box integrations would certainly add a lot more value, particularly for procurement and sales contracts.
For how long have I used the solution?
I used Agiloft Lifecycle Management twice in my prior companies, each one for about nine months to a year.
What do I think about the stability of the solution?
Agiloft Contract Lifecycle Management (CLM) is stable.
What do I think about the scalability of the solution?
It is hard to say much about Agiloft Contract Lifecycle Management (CLM)'s scalability as we did not have to expand or scale beyond our initial need.
How are customer service and support?
We had engaged the professional services of Agiloft Contract Lifecycle Management (CLM) for our project and hypercare post-go-live, so customer support engagement was minimal to none during that period. Post-go-live, we did not have to contact customer support much, as it was all through professional services.
Which solution did I use previously and why did I switch?
We did not switch to a different solution before using Agiloft Contract Lifecycle Management (CLM); when I joined, it was already in place, although I have been familiar with other contract lifecycle tools such as Salesforce's Contract Lifecycle Management, Oracle's CLM tool, and Ironclad CLM tool.
What was our ROI?
I have seen a return on investment with Agiloft Contract Lifecycle Management (CLM); since the contract was renewed after a year, it certainly showed value. Regarding time saved, it amounts to about one hour for a legal contract review person, and there are about three people in the company, totaling three hours a day saved.
Which other solutions did I evaluate?
I believe my organization evaluated other options, including Ironclad, although I wasn't there to confirm this.
What other advice do I have?
My advice to others looking into using Agiloft Contract Lifecycle Management (CLM) is to focus on integrations, focus on outcomes, and not just the template. Focusing solely on the legal aspect will not yield the desired results; it is important to look at a complete end-to-end process. I have rated this review seven out of ten.