Name: Scale It: Put Contract Intelligence to Work
Uploaded: 2026-09-24T17:46:12.534Z
Duration: 25 min 32 s
Description: Scale It: Put Contract Intelligence to Work

Transcript for "Scale It: Put Contract Intelligence to Work": Hello, everyone. Give everyone another minute or so to join in here. A little timer, so we'll give another fifteen seconds. Alright. Let's jump into things. This will be recorded, so it'll be sent to folks. If you join a little late, you can, kinda go back and and look at what you missed there. But thank you for joining. This is the final of the three part webinar series for Find It, Fix It, Scale It. The past ones, July 22 was the first one. We went through Find It. We'll go through a recap in a little bit and fix as well. But today, we're here for scale. How do we bring this all together and make sure that you're getting everything out of Astra to make everything run-in scale with your growing contracting needs? So with this, I wanna bring us back just for a second of kind of how we ended up here, what we're trying to bring together here. And in part, it's a recognition of, hey. Your contracts have two moments that really matter. Right? It's it's pre signature. Of course, you want, your team to kind of really understand what your standards are, be able to look at questions and, or look at the terms, sorry, and say, hey. Does this actually align to what our standards are? And that can become slow and inconsistent if you don't have some process or tools in place to help to streamline that. And then thinking post signature. After it's already been signed, there's things that have to be executed on. There's obligations you have to understand, but there's also things you can learn from those contracts. How do you make new decisions without understanding exactly what's in every contract, and then how do you use those decisions and those new understandings to change things in the future? And that's where ASHRA comes in. ASHRA is about bringing those two moments together in one platform. So looking presignature, hey, how do I apply those standards consistently? How do I redline and review, in a standard way that my standards or fallbacks, my different positions are always followed, whenever we're negotiating different contracts? And then how do I also after it's been signed and executed, how do I then go back and understand what's in those contracts and how I can learn from that? So that way I can go back to my standards in the first part, update them, and be able to run a consistent review on those contracts as well. So then what have we been doing in this series? The first one, find it. We looked at two different use cases, auto renewals. Say you're in a position where, hey. Someone just got a little slap on the hand because a contract auto renewed, and no one knew it was gonna be auto renewed. We're like, hey. How did this happen? And you wanna know, okay. Time out. What are all the potential vendor contracts that might come up for auto renewal? And let's reveal those. That way we know, is this a common thing that's coming up in our contracts? And then another hot topic right now, your AI terms. Are your, potential contracts looking at, hey. The data that is yours, are they using their AI models to train on it? This is a hot topic, and so how do you make sure you're going back and able to review all of your contracts at scale to say, are we in alignment? This is a newer, thing for us to worry about. How are we making sure that we're being compliant and aligning to the standards of our company? And so that was finding it. So I will drop this in a link. If you missed this one, this is a great way to understand how to use assistant to quickly go through your contracts, get some insights, and be able to use that to inform some of your next steps. And then we did just that in fix it. Tanya brought us through how to build screens and standards, specifically carrying that example through of, hey. There were some auto renewals, and how do we go update our service agreements to take out auto renewals, or if there is an auto renewal, some type of alert, requirement sometime before then. And then also thinking about those AI terms. How do we update those playbooks and our different standards to make sure they're taking into account, that potential to be in the contract and make sure we're negotiating that in a way that aligns to our standards. And then today, we have the honor of Cal joining us. He will be bringing us through how to scale it. How do we actually bring that through and make sure you're catching it every time, something potentially a contract's going through and it's potentially misaligning with something we had? Or, also, how do we actually carry through at scale that red line in review and making sure people are staying aligned to those standards? So now I will pass it off to Cal. In one second. Let me just try to get Cal, I think you're backstage if you wanna hit the go on stage. There we go. There we go. Cool. Ready to go. Yep. Alright. Let me start sharing my screen here. Okay. Yeah. So as Marissa said, previous two sessions, we're learning how to prompt using, ask ask AI or asking those questions and building those screens. Today, we wanna put that into practice and then, showcase what that looks like from pre and post signature perspective. So from pre signature perspective, how do you enforce those standards? But, when we scale it, really, that means, being able to add this and use this across not only single contract, but multiple contracts at once as well. So when we're scaling our contract operations, we're trying to optimize and streamline, actions that we have to take, including reviewing a contract. So in this, we're gonna showcase how leveraging a screen can do the heavy lifting and flagging, identifying, and tagging all those risky items, while also helping you redline to enforce those standards. From a posting tour perspective, we have those important milestones and deadlines and obligations. Streams will apply there as well. I'm gonna show those two consecutively so you can get the full idea of the contract life cycle. Before we do that too, I think there's a couple other items that are are pretty new exciting ads to the Astra platform that were released, a week and a half, maybe two weeks ago, all working in tandem to help you scale your contract, operations. And so I'm gonna showcase a couple of those before we dive in. Number one, we've added something called elements. Right? So in Tanya's, demo, I'm not sure that this was actually in there yet. And so what elements are are if you remember when you build screens, what goes into a screen is creating different standards and different questions. So you'll see we have 42 standards and 10 questions. Elements are just a standard or a question. So you might be wondering, how's that different from before? Well, if we think about reusable elements, let's say we come in, we look at, this one standard. Right? Disputed payment withholdings. This is something that could be potentially relevant for not only this screen or this playbook, but other playbooks as well. Now instead of having to create it, again from scratch, every time you create a new screen or a new playbook, you can just search for it in the elements library and add it to your screen. So this helps streamline. This helps you scale your contract obligations and, create better processes as well. One more thing that helps in this manner is, hey. If you want to update a particular standard, let's say this AI training question or standard, now you don't have to go through and update it in every single screen or playbook. You just do it one time, and now it applies to all of the different playbooks that's using this standard or this question. So that's, feature number one. Feature number two, let's come back and look at this playbook. I wanna showcase, let's take a look at this one, for example. If you look on the left hand side here, we're gonna see we now have preferred positions. What we heard, a lot of our customers are asking for were fallbacks, so that's something that's now in the system. Instead of just defaulting to one position, now you can have multiple fallbacks. You can have your preferred position, obviously, fallback one, fallback two, fallback three. That becomes especially helpful, again, when we're doing that first pass. It also goes back into the cumulative contract score when running a playbook. So show what that looks like in practice now. Let's navigate over to an agreement record. I'm gonna open up this file, and now I'll pull it over to the screen. And so you'll notice I've just opened up a Word document. Now I can access that Ashwaft Astra plug in. Once I sign in, I'll be able to come in and and start to leverage these playbooks and run them against these this agreement. Alright. So I'm all signed in here, and let me just expand this a bit. What you'll see up top is my screens, my playbooks, and community playbooks. So this is probably something Tanya talked about in the previous session, but these are prebuilt playbooks or screens developed by trusted industry professionals vetted by Agloft. But for today, I have created this procurement and risk playbook that we're gonna run. Once I click run screen, what's happening is we're going through and we're evaluating and indexing this agreement against all of our positions, preferred positions, and generating some of those red lines for things that have been identified as high, medium, or low risk. And, of course, some of these standards are gonna pass as well. All of that's gonna factor back into the overall score. What we're gonna see in this one is there might be a fallback that gets triggered. And if it actually passes that fallback, it won't be a hit to the overall score. Additionally, when you run these playbooks as well, you'll have all the options that that you see here. You can query for answers. So this is kind of like a chatbot. You could ask it questions about the document. Is there force majeure? Is there termination? But, also, we'll go through some of the other features as well. But here are the results. We can see, we're getting let's go to the scorecard first. We're getting a score of 50 out of a 100. So how are we getting that score? We're looking at past preferred, past fallback, and, standards that were just complete fails regardless, of whether fallbacks were present or not. And so if we wanna come in here and understand these results, I can click on any one of these standards, and it will give us not only the AI reasoning, show us where it sourced that information, but also offer up a change or a red line as well. So if I were to take it up on that red line, I could apply that change. We can automatically add that comment as well. So thinking about this, how we could save time in a first pass. Typically, users would be going in, control f ing, reading through the entire document, then coming in here and manually typing in or making some of these edits and red lines. Right? Again, this is helpful for first pass, especially if this is a fifty, hundred page document. It allows you to run the screen, identify all these important components, and and really go from there. Right? And this assistant, if we need to come in here and start to ask additional questions, we can. And then the boost feature down here, really just for anything that might not have been captured within those findings. So if I wanna come in and say, hey. Make this more mutual. We're short and we're clarify this. Right? All leveraging generative AI features to help you complete some of those more menial tasks. From a holistic perspective, we could also quickly come in here and generate, a risk summary. Once we have this generated, we can do, many things with it. Right? We could copy it. We could paste it into an email. We could share it out with other team members or stakeholders. Again, this just takes daily tasks that might take a little bit more time and helps you streamline that process. Okay. Great. So from here, let's go back into Agiloft. I'm gonna give this a refresh. And it's helpful to be able to see that when you're negotiating in a Word document. Right? But being able to tie that full circle and structure that data and centralize it is what makes it especially helpful when we wanna get the full picture, get insights, reference this, later when when we're contracting with the same vendor entity again. Right? So if I come over to extracted data, I could scroll down, and now I can see here's the playbook that I was able to run, and here are some of the results. Now that we have this in AgileSoft in a structured format, we can take action off this. If things are identified as a fail or a high risk and it falls under, certain sections or categories, we can now decide to create rules and actions, that notify users that may need to come in and review these items. So this is what things look like from a presignature perspective. I wanna showcase what things look like from a post signature perspective now. So let's come over here. We are on an active contract agreement, meaning, after this is executed, now there are important deadlines, milestones, obligations. Right? We were able to run a screen from a Word document, but we could also run gauge these screens directly from within Azure auth too. So in this case, I want to extract some of those obligations. I can select what screen I wanna run, and or what document I wanna run. When I click extract obligations, I'll be able to come in here and select my obligation screen and screen that document. So once that document screens, we'll be able to go back and take a look at it. I'll wait for those results to load for a minute. But while we're waiting for that, I wanna come back here and showcase how do we use this in practice across not just one document, but multiple documents as well, and how do we immediately start to extract value from that. So if I come to my documents tab, I can see I've uploaded, a few documents here ahead of time so we'd have something to use, and I've added labels to all of them. So here are five documents I've simply uploaded into the system, and now I wanna create a project off it. So over here, I can click new projects. Oh, sign in again. Okay. You reselect these, and we'll create a new project. And let's go ahead and just start from scratch here. So we'll create a project. You can see we have the projects tab over here. And what is a project? It's just creating, again, a table with structured data. And we don't have any right now, but we could come over here to columns. I'm gonna select all of these columns. And once I select them, we'll start to see those values, populate. And, what we can also do is select all of these documents and run screens on them as well. Actually, I'm gonna do it from this tab. So the same screen that we just ran, I'm also gonna use on these. And with these documents, there's actually something pretty important that I've added that relates back to the previous two sessions. So we had looked at renewals, auto renewals, and we had also looked at, AI data training. So once these finish running, we'll be able to see answers to those questions. Again, we're moving from a single document to multiple documents, doing that all concurrently and immediately getting some of those results. So while that's loading, let's come back to our contracts table. Let's look at this agreement, and let's go back to our obligations. So we can see our obligations have been extracted. Now we can take action off these obligations. Right? So if I can see, hey. This one is a reoccurring payment. This is something that occurs more than one time. Maybe I wanna come in here and be able to create an obligation task. So if I run that action, now that's been completed, I can go ahead, save, give this a refresh. And right down below, we can now see we've created an obligation task. Now this can be assigned to the proper individual or team depending, again, on classification on that obligation type. Okay. Let's go back to our projects. We were able to run those items, and we can see all of the pass fail standards. But more interestingly, I wanna come over here and look at some of these results. Auto renew, I set this to have answers come out as true or false. So if I wanna come here and just sort by false, or true, I can also click on that true value to to help identify where we're able to source that answer. So this is showing in the contract exactly where we're able to find that information. Now this is also important because, a lot of people ask us how do we deal with hallucinations. Right? When we run our AI models, it's just against the four corners of the contract. So we're not introducing any kind of external sources. So that keeps it true to exactly what resides within the four corners of the contract and, prevents any of those types of hallucinations. What about AI training? What if I sort this by results here? If this one says yes, I wanna understand exactly where it comes from and what that means. Right? AI training customer data supplier may use de identified and aggregated. So if it's PII, how do we randomize and de identify that in a manner where it's just randomized IDs and then train off of that. And if that's something that's unacceptable, of course, now you have a new data point, which you can create a standard around, and create preferred and fallback positions as well. Now looking at this, I wanna take it one step further. Great. We've got this project. We've got this structured data. Maybe there's something else that comes up that I just wanna be able to have an answer to, and I want it in this table format as well. So I'll come over here, and I'll add a column. And I'll call this auto renew notice dates notice period. And I could put in a prompt here. So this is gonna be my question. If there is auto renew contracts, how many days notice do I have to give, before? And then over here, select this. I want the output to be, free text or, actually, in this case, number. If there is a number of days, I want that to be the answer that's populated in the actual column. So when I click click create column, we're gonna go through again scan. It looks like, auto renewal is true across these three contracts. So we're gonna get, an NA for the false. But for these ones, we can see oh, great. Now within just typing in that question, again, we're structuring this in a table format, and we can immediately identify where it's sourcing some of those answers. So that's a quick and easy way, especially if you're looking at a a bulk set of agreements. You have a screen. You wanna run that screen. You get some answers. You wanna follow-up. Now you have this in an exportable manner as well. You could download. You could share. You could send it out, to any stakeholders. Again, that that might assume this is valuable information. And so the last part here, I I wanna be able to tie everything back together. We looked at what it's like in practice to use a screen presignature. Post signature, how do we extract those obligations? And then across bulk agreements, how do we get some of these results? But, all of it's gonna be important to be able to centralize. Right? It's good to get those data points, but now how can we view this on something like a dashboard? So if I come over here, I'm looking at a dashboard that showcases, insights and risks. So we could see these are pass rates based off screens that we have run-in the past. We can look at the number of high risk contracts. We could look at, results by contract type or agreement type as well. What if we were looking at things from a post winter perspective? If I were to come over here and look at some of those obligations, where is it drawing this obligation data from? Well, when we ran that obligation screen, we're able to extract and map that data back into the contract record. Now that's in there, we can use it to power these dashboards so that users can come in and understand, important things like, active contracts with obligations, that are maybe past due or have a financial, penalty if they are missed. So with that, we've kinda gone full circle, end to end contract life cycle, pre to post signature, looked at what it looks like to use screens, against contracts, but also centralized that data once we found it. So I don't see any questions. With that, I'll I'll pass it back to you, Marissa. No questions in there. What I am gonna do, I'm gonna drop the link or at least try to if this lets me. Maybe we'll just have to send it out in an email after. I was trying to just drop a link for the other ones on demand in case you've missed it. Yeah. It's not letting me do that. Let's try this far. Okay. No? Yep. There we go. Okay. So that is the find it webinar, and the fix it one as well, I will drop in there. And so thank you for coming along on this three part series. If you missed the first two, this is the first one you're tuning in, I highly recommend going back and just looking at how all these pieces come together, and you can use Astra to really carry your contracts pre through post signature and get value on both sides, and drive meaningful contracting within your org. And thank you so much for joining, and this recording will be sent over to you. Thanks so much.