Name: From Chaos to Clarity: Award-Winning Solutions for Smarter Contract Management
Uploaded: 2025-10-09T16:31:03.690Z
Duration: 58 min 8 s
Description: From Chaos to Clarity: Award-Winning Solutions for Smarter Contract Management

Transcript for "From Chaos to Clarity: Award-Winning Solutions for Smarter Contract Management": Good morning, afternoon, or evening, everyone. Thanks for being here today. We'll start momentarily to give everyone a few more minutes to get settled. Hi, guys. We're just good morning, evening or afternoon everyone. We're just gonna give just a couple of more minutes to get everyone settled, and we'll begin shortly. Thanks for your patience. Okay. Thank you for joining us today. So if you've ever felt overwhelmed having to deal with the chaos of contract management, then you're in the right place. That chaos that you know so well could range from having contracts scattered across multiple systems or having hundreds of thousands of contracts you need to review with limited resources or time or that feeling like you're looking for a needle in a haystack or maybe it's that knot you get in your stomach when you're worried about compliance risks. Well, we hope to take you from chaos to clarity today. Our expert panel will share strategies to help Rocket Software's legal team win an award for revolutionizing its contract management process to solve these chaos challenges. Before we begin, I have a few housekeeping items to go through. First, all attendee lines are muted. We will be recording the sessions and will provide the recording links to you within a few days. Feel free to ask questions at any time utilizing the Q and A feature. Questions will be addressed at the end of the webinar. If we are unable to get through all of them, we will follow-up offline to make sure we get to any outstanding questions. Lastly, as you leave the webinar today, please take a moment to complete the exit survey. Over the next sixty minutes, you'll get to meet and learn from our expert panelists about the strategies and tools they use to revolutionize the contract management process. Following this, you'll get a preview of some of the new product innovations coming down the pipe. And as mentioned, we'll finish off with some time for Q and A. So without further ado, let's meet today's speakers. My name is Daniel Lam. I'm the product marketer for Rocket Software's Content Services Solutions, and I will be your webinar host today. We are lucky enough to be joined by Theresa Parker, Alisa De Dominicis, and Randy Baiad. Theresa is the Director of Product Management for Rocket Software's Content Services Solutions focusing on Mobius. She brings more than thirty years of industry experience, including leading global presales and service delivery teams and holds a Master's of International Management from Thunderbird School of Global Management. We are extremely lucky to have Theresa with us today to moderate the fireside chat and provide a preview of new product innovations. Alisa is a seasoned legal operations executive and attorney with over two decades of experience driving strategic initiatives across global legal, compliance and technology functions. Currently serving as Senior Director of Legal Operations at Rocket Software, she partners with executive leadership to scale legal infrastructure and optimize operational efficiency. Alisa has held senior roles at WilmerHale, BCG, and the Massachusetts Child Corps, leading multimillion dollar transformation projects and cross functional teams. She holds a JD from Suffolk University Law School and an MBA from Northeastern University. Alisa will share her experience and insights leading the contract management transformation project for the legal team. Randy has worked at Rocket Software Software for nearly thirty years and was recently promoted to senior technical staff member. As a visionary architect, he has designed and developed multiple products, more consistently identifying creative solutions for customers. Randy will lend his perspective on how we partner with Alisa to maximize the tools and technologies to solve their contract management challenges. So with the affordability, I'll now hand it over to Alisa for the fireside chat. Thank you so much, Dan, and it's a pleasure to have everyone with us today. So to get things started, we wanted to frame why we're talking about this contracts management solution today, what the problem was, and how it was addressed. So I'll first start off with Alisa. So, Alisa, would like you to give us a little bit of insight into why you started down this path. What was the prompting factor that, spurred you to action? Well, I'm just gonna cut you really quickly. Alisa, we can't hear you. Sorry. Thank you. Thank you. So, Rocket Software was in the middle of a major acquisition, last year, and we were receiving millions of documents from the acquired company. These documents included everything from contracts and order forms and invoices and other critical information. We're under a significant time pressure to quickly analyze and understand the content of these documents and ensure the seamless continuity for the newly acquired business. So out of these millions of documents we received, about 20,000 were agreements that required legal review. However, our internal legal resources were insufficient to manage the volume. We could have went outside with, you know, outsourcing the work to a law firm or, using an alternative legal service provider or even a legal tech, vendor to sift through all of the documents, but that would have incurred significant costs. So beyond the financial impact, failing to understand our obligations and risks from what was included inside of these contracts and other documents would have exposed Rocket to serious legal and operational vulnerability. So the bottom line is is we needed to know what was in them. The remaining 1,000,000 plus documents included order forms and invoices and purchase orders along with a significant amount of, immaterial I'm sorry, insignificant material. So we needed to separate the junk, so to speak, along with the important documents that we needed to extract information from. Understood. So 20,000 documents that you had to review plus a million or more, that's that's huge. For those 20,000 that the that were specifically in the team, legal team's bucket, could you give us some insight as to how long it would take on average to review that? I I'd like to give folks an understanding of of the scope of the challenge that you guys were facing. Oh, that's a good question, actually. So we have a team a legal team of about 30 people. That's about it, and they're scattered all over the globe. And and let's please remember that they have a day job to keep Rocket Software going. So, if if you take a look at the 20,000 records or documents that need to be reviewed, at a minimum, it would have taken each legal person, ten minutes to find the agreement, retrieve it, review it, you know, extract mentally the key information, and maybe even store that key information in, like, an Excel file or a database. So that translates to about two hundred thousand minutes or four hundred and twenty workdays or about one point six years for one legal professional to get through it. Now I know we had more than one, but, again, we had a minimum of people that we needed just to keep the Rocket Software, operations going. So it would have been a major, major disruption for us to stop the Rocket Software Business to just look through these reviews. So for the rest of the million documents, let's just assume it was five minutes to to look at each document and and decide, okay. It's probably irrelevant or not. So using five minutes in the average, it would have taken a finance person or other resource about 10,500,000 workdays or forty years to look through all this stuff. So we're looking at cost to, you know, closing in on 42 years of of work. Holy moly. Labor. Yeah. Definitely. And and doing this in your quote, unquote, extra time. So with those agreements that the legal team was specifically looking at, what kinds of things were you looking for? For those folks who aren't familiar with with things that tend to fall into the the legal bucket, what were you looking for? Sure. So please give me a heads. It's not just legal. So other stakeholders have to have the need to look at the same information oftentimes as what legal is looking at. So we need to know the effective date of the agreement. So are they still billable? Can we still charge them for for cost? So the effective date of the agreement, termination, any limitations, like you can't increase the price of the products or, you know, over x percentage or can't do business in a certain jurisdiction. Other things that other stakeholders were were looking for is when is this up for renewal? When is the agreement up for renewal? Do they have exclusivity within this, you know, area, or can we have other clients with partnerships in that area? The amount, something as simple as the amount. How often are we supposed to bill? When can we collect? What are the payment terms? So very important legal information, but then also very important business information. Understood. And given that this is legal and I'm not a legal expert myself, I'm guessing that some of this information was privileged or had had information in it that just a very small subset of people could look at. Could you give us a little bit of insight into, you know, when when the you and your legal colleagues, this group of 30 that you were talking about, what types of considerations did you have from maybe, like, a risk mitigation perspective? And is that something that you personally were responsible for? Were there other folks within the Rocket Software organization that that needed to, you know, be a responsible party? Yeah. So first of all, our I report to the chief legal officer or the CLL of Rocket Software on a couple of things. One, that all of the mergers and acquisitions or M and A due diligence is done, has securities done privately. So legal and only those people that are disclosed within Rocket Software can be aware of what's in those documents and even knows about those documents. So for m and a work, security is is of the utmost. And then there's other agreements and other documents that can be sensitive too. Right? I can think of employment agreements or even just strategy or corporate agreements where you don't wanna give information out freely. So, ultimately, the security of all of this lands in legal. And before we even went down this road, it was, the number one question or requirement that we had, meaning that we needed the ability to keep certain documents secure, hands down. You know? There's no, loopholes of getting access to those documents. So that was the first thing. And then secondly, sometimes it's okay to see the document, but certain information on that document might be sensitive. So you wanna actually just kind of, you know, take a a whiteout for those of us old enough to remember. Take a whiteout and just put it on the PDF so people can't see it. And our one of our systems, have that capability. It's called, like, a redaction capability so that you can do that. So the business person that needs to look at the document can actually know the document exists, but cannot read certain sections or even the whole document if you wanna make that, sensitive. So two ways for the security, which worked out quite well for legal. Okay. And then one last question before we start, to chat a little bit about, you know, how you address this challenge because I'm I'm thinking back again to this forty one and a half years of of time to to do this manually. I'm sure you didn't have forty one and a half years. How much time did you actually have? What was the timeline given, to to finish processing this? What what what restrictions were you under? It so we had a an acquisition transition period of about six to eight months. So that meant we had to very quickly identify at a minimum the contracts and the invoices so that we could understand, you know, what the pay terms were and so that, again, we can keep the operations of the acquired company going. So it was about six to eight months, and, we met that timeline, but it also didn't stop there. So as renewals came up from the acquired company, you oftentimes have to go back to the original agreement to look up certain information in order to process that renewal. So it was great that we were able to do this for pure due diligence and to grab the information we needed to operationalize. But on an ongoing basis, we also needed the ability to be able to go back to these documents and refer to them to keep going. Right. So understanding that you had this, quantity of of 20,000 documents of a more legal orientation, you had this million plus other, which was involved, you know, on a day to day basis to keep the business going. You had forty one half and a half years that you had to magic down into six to eight months. What prompted your your, what what prompted your action to look for a solution, and how did how did you find a solution within Rocket Software? Can you walk us through that process a little bit, please? Sure. So if things were not crazy enough at Rocket Software during that time, it was around that time where Rocket Software launched its annual hackathon. So this is usually something the company does that, you know, creates innovation and encourages different use cases for existing products, which I'm a firm believer to use existing technology, just so you know. So, anyway, so in legal, obviously, we recognize that Rocket Software had an enterprise document content management system. So we thought maybe there's an opportunity there to leverage it to help us address this massive document review challenge that we were facing. So the idea, at least, was that if we could ingest all 1,000,000 plus documents, have the system review them systematically, and automatically extract the key information as metadata and store it, then the functional teams, including legal, can then easily search and, do what they need based on that key information and have all the documents available to them in a central location. Fantastic. So what was the ideal state that you hoped to achieve? You you've talked about, you know, having things in a centralized place and being able to extract information out. Was there anything else that you were hoping to achieve as as the overall ideal, out of this coupon? Yeah. So the other, the other goal that we had was we wanted the ability to, disarm bottlenecks within the company. So, again, we have a total of 30 people within legal, not all attorneys. And so it was it's really the attorneys become a bottleneck when they are processing certain agreements and renewals. So by using our existing existing systems, there's something we have called smart chat that enables natural language querying. It will it allowed us to push some of the work from the attorneys to other resources, more junior resources, to do some of that routine or administrative work. So often, we get the same question over and over and over. What is the renewal date? Is this contract still effective? Can you find me this contract? What are their payment terms? So very routine questions. And instead of having all of that go to an attorney using these systems, we're able to push that down to more junior resources. Nice. So it sounds like a combination of, one one source of information, the ability to maybe democratize information access, and be able to ask questions. So fantastic. And now I'm gonna delve a little bit into the technology. So, I understand, Alisa, that you worked with Randy Baiad, on this, and, Randy is with us here today to talk a little bit about, what the overall process was for bringing the information into the content technology. Randy, could you expand upon that just a little bit? Sure thing, Theresa. So the legal team needed a streamlined way to understand contract contents quickly. These contracts were stored in network folder. So our first challenge was to migrate them into our Mobius content repository where they could be properly governed, searched, and analyzed. We leveraged Rocket Software's orchestrator platform known as Enterprise Orchestrator to automate the file transfer process and to continuously monitor for any new files. Once ingested into our content repository, the textual content and metadata are indexed into a vector database for LLM process. Through the Mobius user interface, the team members can leverage our smart cap feature with proper authorization controls to query documents in natural language. The the configured LLM responds based on their access permission. Although some contracts may be viewable by staff outside of the legal department, access to the smart chat feature was granted to the legal team. Here's where we added efficiency. Since many of the same questions, like Alisa De Dominicis said earlier, were being asked across different documents, we built intelligence into the archiving process itself. Enterprise Orchestrator called a new service that uses AI to pre extract answers from incoming documents during ingestion, storing these as structured made metadata alongside the archived files. This capability, what we call smart extraction, leverages the same LOM technology as SmartPath. For Rocket Software, we partnered with OpenAI to ensure enterprise grade security with guarantees that customer content is never used for model training. We also support alternative elements with this approach, including on premise options for customers who prefer this. It is important to note that this pre extracting metadata differs from the metadata from the vector database. These are traditional indexes stored in our relational database. The result, anyone with the appropriate access can view these metadata fields in a tabular form, apply filters to it quickly, locate specific documents, and then use the smart chat feature for deeper ad hoc queries. That sounds absolutely incredibly amazing. So, Alisa, going back to something that you had mentioned, and with the the use of smart chat with, perhaps bringing that down, to, other individuals within the legal organization, you mentioned that of the 30, not all of them are attorneys. Were there any concerns about using that smart chat functionality to query the information? Was there any concern, about seeing things that people shouldn't? And I'm I'm going back to your comments about, you know, making sure that, things were kept at at the right level because there is is risk aversion, from our, chief legal officer I know. Was there any any concern that you had about just the overall security of the information that people were seeing? Oh, Alisa, I think you're on mute again. Oh, sorry. I don't know why that keeps happening. Sorry. Yes. There was a major concern. So we we at legal don't feel like we're at the point where lawyers have been completely replaced by AI. So the last thing we want is people using smart chat or chat GPT to, you know, to to just rely on that information as if you were relying on information by a lawyer. You know, while it's very good, AI definitely helps with routine tasks, answering routine questions, which again is a lot of the questions that we receive here at the legal department. It it doesn't appreciate the nuances of bringing together the totality sometimes of a bunch of different agreements that comprise the the overall agreement, nor does it appreciate the policies or the the future strategies of the business. So it's never gonna return an answer that includes those things. So you have to be really careful, particularly when you're you're giving out information related to contracts through some kind of AI chatbot or or or whatever it is. So we wanted to make smart chat available within legal for sure because there's some great efficiencies there. First of all, for, as I mentioned before, you can push the work down to a more junior resource, at least for that initial analysis. So, you know, finding the document, running it through the smart chat, asking it a question. For example, what is the termination date of this agreement? So the person asking the question doesn't need to know legal terminology to make sure it asks the right question. I I guess that's the beauty of it. Instead, you can just ask it in layman's terms, and it will go through the contract. And and, usually, it's it's pretty good. It's very good, actually. And so a junior resource can take that information and then kind of put a bow around it and send it to the attorney. So you've just saved the attorney a tremendous amount of time for all that lower level work. The other thing that's really good about the smart chat that's different than just extracting metadata is when you do ask a question through the smart chat, it not only gives you the answer, but it it gives you the reasoning. Like, how did it come up with that answer? Where did it find that answer? So we can have a junior resource just copy the results of a smart chat, put it into an email, and say to the attorney, you know, this is what I found. And it gives a good starting point for the attorney or whomever, the most senior person working on it, you know, to it versus starting with a bit blank slate. So it gives them a a great running start. Fantastic. And then going back then, you mentioned, in your initial comments about the million plus documents that weren't necessarily legal in nature, but, had applicability toward, you know, invoices and order forms and other things to do with, you know, potentially day to day sales activity. Is SmartChat, used currently by Rocket Software? Not at least with agreements. So there may be other documents that it can be helpful. So for example, if there's purchase orders and you just wanted to get a quick purchase order number or ask question, you know, questions related to that, shipping addresses, things like that for sure. But we, here at Rocket Software, don't make it available outside of legal just because, you know, when you when when I mentioned earlier, we had a million plus documents. Some of them are agreements. Not all of them are agreements. When you put them all together, you know, it's very difficult for a layperson to figure out which one is actually binding binding. So we only made that available to legal. And I should mention, when I talk about agreements, for us, that could mean anything from a sales agreement, which is like a master service agreement, could also mean a statement of work, could also be an order form, and it could also be a purchase order. So you have to be very careful when you make smart chat or any AI, available to to layperson because, again and you have to look at the whole situation. We also have vendor contracts that we use, as well. So very helpful. So, I guess the takeaway here is that AI isn't a magic button that replaces the the logic and the experience of people, but it's a tool that could be used to really help with streamlining overall work process and workflow. Would that be a a an accurate summary of what you just shared? Yes. Yes. So I think there's two ways to think about it. The way we have it the way it works here is that you have, AI using for some doing some smart extraction, looking through the document, pulling out some key information, storing it, and making that available. Most of the time, that is sufficient for your business stakeholders because most of the time, they just wanna know commercial terms very quickly. When did this you know, what contract when does this contract expire so that they know when to start reaching out to clients again? Then there's other, information that is really used by legal that's buried within the contract or more seasoned professionals. That's when Smart Chat really comes into handy. So it's not those day to day questions. It's more, you know, the nuanced questions that that you want use smart chat for, and that's where the AI really excels. I hope I understand. You sure did. Absolutely. So going back to Randy, I have two follow-up questions for you. One the first of them is, what what did you use? What APIs, what utilities did you use, for that metadata extraction? And it sounds like there was quite a bit of of, indexing slash processing that was going on. Randy, could you talk a little bit about that? Sure. So we built a Python based service that uses DS five from Stanford for reasoning driven reasoning driven metadata extraction. It takes document content along with defined field names and descriptions, then use l l then it uses the LLM chain of thought inference to determine the correct metadata values. Traditional NLP or regex based extraction relies on static rules or pattern matching. It worked if the data looks exactly the same every time. But our software, on the other hand, uses the reason driven extraction through large language model chains. It understands the content of the context rather of the field rather than just its format. For example, if you ask to find the effective date of or contract party, it can infer that even if the phrase even if it's phrase different or located in an unusual section in the doc, For a given any given document, they could define a set of metadata to extract and even fine tune how the how the data should be formed or even, provide instructions to help with the extraction. Fantastic. And then yep. If I could just add on to that. So, Randy, that's a that's a very good point. So I think what Randy's talking about might be called the smart extraction. I'm sorry. My Boston accent doesn't know about ours. So the smart extraction. So I was actually quite impressed. I I did not expect this to happen first going into it. So we loaded some documents that did not have an effective date. Some of them have the, terminology up in the beginning of the agreement that said, this agreement is effective of the first date of the signature or the last date of the signature signed. And then also in the agreement, it has something like this agreement is, lasts for thirty six months for an example. And then for the termination clause, it just said this terminates at the, you know, thirty six months after the effective date. So, really, there were no dates typed onto the piece of paper. So when we loaded the document with, if I remember correctly, very little work, the system Right. Read through the document and knew just based on this document is effective as the last date of the signature, went down to the signature block, pulled off the the date, which by the way was in handwriting, if I'm not mistaken. It was, like, just in ink. And it pulled that, and so it calculated the correct effective date. It knew the term, and it was smart enough to understand that the effective date plus the term equals the termination date and populated all three pieces. And it even included the notice period. So when an agreement is terminating, you generally have maybe ninety days, sixty days to tell the other party that you're you no longer wanna renew. That is a critical critical date, probably more important than the termination date. So, the system was able to identify that date as well. So that enables us to get some really good reportings in a nice runway so that we can get ahead of the fact when things are about to to terminate. That sounds really absolutely amazing. And, then I wanted to follow-up on one other question, and and this is from a couple of things, Alisa De Dominicis, that you have mentioned with regard to information security. You mentioned redaction, I think, close to your, the beginning of your opening comments, and understanding that not everybody should be able to see everything, especially when you're talking about contractual details and and things that should have a little bit more governance associated with that. I have a follow-up question for Randy Baiad of what what else we might have done other than just the the content technology itself. How else were we able to secure this information so that the right people were seeing what they needed to see and that, you know, someone like me, who, you know, shouldn't have access, doesn't have access. Could you expand upon that just a little bit? That's a great question. I love dealing with security. So security was a top priority from the start. So we implemented multiple on multiple layers of access control. First, we integrated with our Okta in, identity management solution using single sign on with a multiple with multiple factor authentication. This ensures robust authentication at entry point rather than managing access controls on a per user basis, which would be administratively challenging. We leverage active directory groups for authorization. This role based approach allows us to define access controls at scale. For example, the legal department has access to all legal documents while the sales department can only view customer contracts. This content level restriction is a of course through group membership. Beyond document access, we all we also implemented feature level controls. Like Alisa said, she doesn't want people to use the smart chat functionality. They they only wanna be able to do this, so we can restrict it that way as well. The other thing is this granular approach gives us flexibility, which we could wanna see whatever contract we wanna see and which feature they can use, all managed through existing directory group rather than individually used permissions. We also have like I said before, we have the capability to implement redaction for sensitive information, ensuring that even authorized users only see what they need to see. That sounds incredible. So I have two additional questions for Alisa, and they both, the they're they're, time based questions. So not time, and we only have thirty seconds to talk about them. But, the the time first time question is you had a lot of new going on. You you had this acquisition. You had these new documents. You had pressure. You were also working your day job, and then you had this new solution, which was providing huge benefits. But how long did it take you or your colleagues to learn to use smart chat and, you know, was it huge amount of training? Was it pretty intuitive? Was it you know, where did it fall into the spectrum of, you know, how much training it required for you? I think the most challenging part of using smart chat was just knowing where to find it. So it and that that's a joke, really. So we've all used smart chat. You know, we've all been on a website where it says need some help, and it works very much the same way. You just open up the box and then, I mean, I make it sound easy. Randy probably had to do maybe more work. I don't know. But I literally clicked on it, and, I could either do click on it and use it when I had one document on the screen because I really wanted to hone in on that one document. And, again, it's all natural language. So I would test it saying, is something as simple as is there a, you know, I don't know, is there a an indemnification clause in this agreement? I mean, I I might not know what an indemnification clause is, but maybe somebody's asking me that question. So you just type it in, and it it returns the results. Like I said, not just the results, but probably gives you more information than you wanted to know. You get a nice little concise summary of not only where it is, what it is, but then also why it thinks that it's good or bad. And then, also, if even and that's actually another point. I don't even need to know that much about the content that I'm looking up. We have an IP, an intellectual property practice here, within Rocket Legal, and I know very little about intellectual property. So when I'm looking at an agreement, I can just type in, you know, is there anything related to IP IP in this document or documents? And sure enough, smart chat is smart enough to know somehow that IP means intellectual property, and it will pick up all the inferences, I guess, is the word I should be using regarding IP. So it doesn't have to say intellectual property in the document. It has to be about intellectual property, and the smart child will bring it up. Oh, wow. That sounds really incredible. And and I know that would help me because I don't know intellectual property, what that means from from anything else. So going back then to something that you had shared with us at the beginning about these 20,000 documents, the million others, the forty one and a half years, what was the impact of using this content technology, the smart abstraction that you've talked about, the smart chat? What did that do for overall processing? Can you give us a little bit of insight into either time saved or effort saved or just, you know, the the term you hear a lot of, the total time to joy? Can you talk about that a little bit? Sure. I mean, all the way around, I think it was a game changer for us, and that's really putting it mildly. So we were able to let me back on a second. So about 70 of the legal work that comes in is routine questions or routine work. So immediately being able to take that 70% and push that down to more junior resources is is huge. Right? It it saves, it's a cost savings because you're using less expensive resources to do the same role that you were before. And then, for for me, more importantly, frees up more senior resources to do more value added work. So you don't have attorneys looking to see when the notice period is or the date that we have to, you know, terminate an agreement. You now have attorneys working on more value added work, on being more strategic in their work because they're not, you know, they're not working on that mundane stuff anymore. So so we shifted 70% of the work down to more junior resources. And then for the senior resources to do the same work, which I hope they're not actually doing the same work anymore, they're doing better work, they can retrieve documents faster. They can get they can get a collection of agreements a lot faster, things we couldn't do before. So if they wanted to see all of the agreements where, I don't know, maybe there's a a price cap limit because we're thinking of raising prices, which I I don't know if we are. Just a good probably a bad example. But if there's a price cap limit, then it will give us a list of clients that we can let you know, we can raise prices by x amount only and, you know, so it helps us with our bid operationalize our business as well, not just within legal. So I would say it probably saved us about 80% even just finding documents and getting to that key information. Wow. That's huge, especially when you're looking at that forty one and a half years. So I understand that, this has, been promoted not only within Rocket Software Software, but externally as well. And if memory serves, I believe that, Rocket Software Software Legal has won an award for this. And if memory serves correctly, could you talk about that a little bit? Sure. So Rocket Software Software Legal is a member of the ACC, which is the Association of Corporate Counsel and every year they have about six awards that they grant to both in house legal, as well as law firms for best use of innovation. And then they also have an award to an individual, and that award is very similar, the best use of innovation. So Rocket Software Software won three of the six awards for 2025, all related to this one project, this one initiative. And then, personally, I won the 2025 Monica Bay award, which is only given out to about three or four people, I can't remember, for the best use of innovation. And then when I went to the ACC meeting, the North America meeting in Chicago this year, we I demonstrated how the system worked. Randy helped me put together a little demo environment. And on the fly, I was able to take some documents and show them exactly what I'm explaining to you today, how it extracts the effective date and all all kinds of things. And then we also use the smart chat as well. It was it was very impressive. It was a proud moment. That's fabulous. Thank you so much for sharing that. So just a couple of of questions to wrap up this part of our webinar today. How else is this being used, internally? Are are we looking at this from, you know, further integration with sales, maybe with our CRM? What kind of other evolutions do you see, Alisa, in the future? Well, coincidentally, you mentioned, CRM. So Rocket Software is, extremely CRM centric. So everything revolves around our CRM, and our CRM system is the system where most of our stakeholders go to for some in for information, whether it be finance information, product information, even legal. Our contracts, while not stored in our CRM, are accessed to them through our CRM. So, what that means is, we need to be able to make sure that our CRM is as up to date as possible with key information as well as with the documents themselves. So what we did is from that acquisition, and we'll probably do this going forward, but from that acquisition, we loaded, when we loaded that milli those million documents into Mobius, we extracted some other key information that we needed because we took the documents and we went to load them into our CRM, but we didn't know which account they belong to, whether or not they were actually in agreement, or whether or not we needed to even bother loading them into the CRM. So we loaded all those million documents in, and at that time, we took out the counterparty name, which would be the account name in our CRM, as well as effective date and as well as a document type. And the document type was for us to identify if it's an agreement that needed to be loaded into the CI. So just to keep that into perspective, we had two people doing that, and it was taking them about fifteen minutes per document to do that work. So we were probably able to only do about 20 agreements per day because, you know, they were doing this in their magic time. They had a daytime job, and it needed to get done. Both needed to get done. Instead of do taking about 20 agreements per day, being able to do 20 agreements per day, with this automation effort, we got it down to processing thousands in just minutes. Right? That's absolutely amazing. So so just to emphasize so just to keep going on that. So we will go through this exercise every time we have an m and a due diligence. We will create an air a pure area within our systems. We'll take however many documents come in. We will load them through the system. We'll extract the key information, and then we can actually decide what to do next. So to answer your question, that's a future use case. Brilliant. Absolutely amazing. Well, I would really like to thank, Alisa Baiad and Randy Baiad as well for sharing such valuable experiences, into, you know, this this challenge, this huge problem, the innovation that came from the hackathon, your partnership for this. This has been absolutely spectacular. And one of the things that I'd like to mention as we wrap up this section just before we start our section on, what's coming down the pipeline for a product perspective, is that this isn't restricted to a legal use case. As Alisa has mentioned, there's mergers and acquisitions, and that kind of activity happens all the time. But maybe this is this is something that could apply to, you know, your merger, your acquisition, the stand up of a new line of business. It certainly applies to health care where you have lots and lots of patient information, some of which could be handwritten as has been talked about, some of which, might be being brought into a system for the very, very first time. And and how do you make sure that you process that correctly? How do you make sure that personal health information is secured so that the right people can see it at the right time? This type of technology applies to a lot of different scenarios. So keep that in mind as you're evaluating how this might help you in the future. So, again, Randy and Alisa, thank you so much for the valuable insights that you've shared, today. I know we've all learned a lot. You've given me and I'm sure everyone quite a few things to think about. So it's thank you so much. And, it's now my great pleasure to provide a few highlights of new features and functionality forthcoming in 2026. So if you're able to join us for our webinar in May, this first slide should look a little familiar. Back then, I discussed how Gen AI is a significant inspiration for our road map and how it's estimated that GenAI will influence 30% of task work by 2027. We also briefly discussed that IT execs are making significant commitments and investments in this technology, and I shared a short teaser about how Rocket Software Legal is benefiting from smart chat and how we are committed to the intelligent introduction of further AI enabled capabilities into Rocket Software Content Services. So as you've just heard, that potential has been realized, and I'm pleased to announce that this functionality will be available to Rocket Software's customers in 2026. By integrating this technology in your organization, you too could experience significant increases in productivity, as we've heard about from Alisa today, while remaining compliant with your information governance policies. So in addition to our emphasis on GenAI enabled functionality, we're remaining laser focused on improvements for both admins and end users, and loosely, we're calling this guidance experiences. We began working on this initiative with the introduction of search forms in 2023, expanded on this with our new UI experience, Rocket Software Content Explorer, in 2024, and this combination will culminate in a into a reimagined search forms experience in 2026. If you take a step back, in version twelve three, we introduced search forms. We wanted to provide Mobius admins with the ability to create interactive search templates using an easy to use form builder. With this form builder, admins were empowered to provide users with searches containing things like easily understood descriptions or questions, finite listings of possibilities for users to interact with, hints regarding the correct input to a question, and so on. Admins can also remove requirements for users to interact with search operators and also minimize or eliminate runaway searches caused by unoptimized logic. End users, on the other hand, simply answer a question and click search. But with version 12.6, we've expanded on this concept in several really important ways. First of all, the experience for Mobius Admins. There will be a new guided experience for creating the search form. Admins will see the evolving design with the ability for a full preview and testing before publishing the form for use. For those individuals who are more expert or who want to jump ahead, you will have the flexibility to create your forms outside of the guided experience. So clarification note here, the screenshot I'm showing today is still a work in progress, so the final result might look a little different, but I did want to show the overall direction that we're targeting. Now let's talk about the experience for end users. End users will enjoy a new progressive experience. Depending on how the forms are established by their admins, answers to one question might prompt another question to appear, or an answer may further restrict additional options. The objective here is to provide an improved facilitated experience, minimizing or eliminating the need for the vast majority of users to understand anything associated with search logic. Simply answer questions, obtain your results, and move on to your next task. Another guided experience we're adding in twenty twenty six is configuring single sign on. SSO isn't a new concept, and it's becoming standard practice for all mission critical applications. But even for the most experienced of admins, ensuring that SSO is established correctly can be a bit challenging. If you overlook a step, you might spend quite some time determining where something went wrong. That's where the SSO configuration experience comes in. This will guide you through all of the critical components required to quickly and easily establish SSO from Mobius. For those individuals less familiar with SSO, comprehensive tooltips will provide further insight and guidance. We're also introducing performance monitoring metrics to streamline the process of identifying bottlenecks and optimizing your performance. Once activated via the diagnostics panel in Mobius administrator, you'll be able to review key metrics such as the number of REST API calls or the time required for REST API calls during a specified period. And these metrics apply to document archiving, folder navigation, document retrieval, and search. With this, you'll be able to specify time and date ranges, view graphical results, and easily export this information to share with Rocket Software technical support. And finally, as we continue to keep pace with ever evolving technology, we're announcing support for Red Hat nine. This will be introduced in version twelve six targeted for February, and, therefore, version twelve five will be the final version to support Red Hat eight. So it was just a very, very short introduction into certain of the items that are coming in 2026. But with that, I'll conclude our brief highlights, and we'll now move to the q and a portion of today's session. So I'm going to go and and look at the chat here. I've got a few people who have been helping out with things in the the background, and I, did have a question. Let's see. I guess I'm going to surface this to Randy. So, Randy, with regards to the technology that you just discussed and Alisa De Dominicis discussed Beyond smart chat, could you give us a rundown of what Mobius tools or even other technologies were were used, for a comprehensive overview of of the process? Sure. So for our orchestration, we have to constantly call, like, monitor folders and call our smart cat or smart extraction service as well as Mobi service. We're using Rocket Software's product called Enterprise Orchestrator Mhmm. For a utility to orchestrate orchestrate, flows for IT for your IT staff, but we also use it internally for here. It's free. The other thing we're using is content automation. It provides the ability to quickly create applications that are governed, and we're using that for our, our administrative where we can where we can enter in questions. The legal team it's it was really cool when they were using this because we've created quickly created an application for them, and they could enter in any question they want by whatever metadata and quickly test this to see is this working, and they can find, you know, define or make better these questions or their definitions. And they can test and look. Yep. This is exactly how I want the data to extract and how it's formed. The other things we're doing within Mobius, we're using the stage search functionality with Mobius. So they can see really nice tabular form of all of their result, and they can quickly analyze that. So those are the features how we we're using that within some of the features within Mobius and external. Within lock it properly. Mhmm. So I'm just gonna run this down for folks. I've heard you mentioned, that just the repository itself, smart chat, content automation, enterprise orchestrator. You also mentioned, single sign on. I believe you said that was with Okta, and I had a follow-up question about that in just a moment. But have I outlined the technology, Randy, specifically that has been used with this this functionality? Yes. You do. Okay. And I I will have another question for you after this, but, let me let me go back to the security aspect. You mentioned single sign on and you mentioned Okta. Now was that something that was a one off for this solution, or is that something used more broadly within Rocket overall? It's definitely used more broadly. It's not only within Rocket, but used by a lot of our customers too. So what we're doing here for within Rocket, a lot of our product or applications are governed by Okta. So we just log in to our Okta. We try to access any of the websites we have internally. It prompts you for credentials. I have to go run and find my phone and do the multifactor, authentication, and then I'm in. And I can go I can go to any other application within Rocket Software too, so I'm not constantly this is something new. It's normal. And it's and it's great. And it's it's it's kind of it's something for single sign that's so valuable and so important that we don't have to deal with multiple passwords or dealing with anything like that. So just standard business procedures. Right, Alisa? If I could just jump in. So as I've mentioned over and over again, security is the utmost for legal, making sure that the, the correct people have the the right access to documents. So with Okta and whatever work that Randy did to integrate it to the systems, it allows us to rest at night because it it operationalizes the security for legal. So we no longer have to worry if Randy hits the lottery tomorrow and leaves. We know that the next person that gets access to Mobius and the products is going to get the right access to the right documents because it's all handled through Okta and the integration. So it's not only just the access to Mobius and the products, but it's also they get the right through Okta integration, get the access to the correct documents as well. Brilliant. Thank you for that additional context. That's super helpful. And I did wanna come back to Randy for one additional question. You mentioned, OpenAI. And so for the solution discussed today, we're using OpenAI, but is it possible to use something else or an on prem LLM? Or, you know, I I think that AI and LLM are a little bit unfamiliar to folks. So if you could expand upon that just a little bit, please? Sure. You can use any of the LOMs that are out. I mean, we can use on prem Mhmm. Which would be great if some customers wanted that. They could tie into another LOM such as, like I said, OpenAI or Quad or other ones they want. But that's what that's what we do. So it makes it it makes it flexible so you can you can use any of those those LLM. And the LLM being it's a it's a large language model. Right? This LLM, and it's an advanced form of artificial intelligence designed to understand and generate an interactive and integrate with human language. Right? It's gonna interact with the mind. Gotcha. Thank you much. Well, it looks like that was the last question that I had, that had been posed. So for those of you who did pose the question, thank you so very much. And with this, sadly, our time is is running short, so I'm going to hand this back to Daniel, to wrap things up for today's webinar. Daniel, over to you, please. Great. Well, thank you so much, Theresa, for sharing those, product innovations coming up, and thank you for all our speakers. You've definitely shared a lot with us today. We've learned a lot, and we've gotten a lot of good insights into, you know, how you've transformed and and really made a success out of your contract management process. So thanks again for speakers and the wonderful insights that they shared. So we'll wrap it up here. If you could as you're leaving the webinar, if you could please fill out the post webinar survey, that would be greatly appreciated. And, again, thanks for everyone for attending. We look forward to seeing you at the next webinar. Thank you.