Welcome to LinkSquares. We're going to be walking you through the entire platform today starting here within Finalize.

Finalize is LinkSquares workflow solution. This is where our customers can store not only their templates if they're initiating off of their paper, but also third party intake workflows, request forms, so that agreements can be initiated, funnel through the appropriate approval processes, and be reviewed before sending to signature.

Within finalize, users are brought to this main landing page. This is designed to give a user holistic visibility into their negotiations.

I can come into the system. I can filter down by counterparty.

I can track the agreement throughout the flight of the negotiation as well, and we can have visibility into what type of agreement is being negotiated, which agreement template it's sent from, but also things we track like the status, where the document currently sits. Is it with us? Is it with the counterparty? Has it been sent out for a signature? Is it fully signed, etcetera?

Users do have the ability to customize the viewing of this main page so that they're seeing the negotiations and they're seeing their queue in accordance with what's most important to their priorities.

In order to create a net new agreement, a user can come into LinkSquares and can select this new agreement button.

From here, the user will be presented with the different workflows or templates that they have access to draft off of. So for example, on the right hand side, if I have the ability to access various templates, I can come in, I can create an NDA and MSA or different types of agreements, but also for agreements that potentially are more complex or for customers who want request funneling through legal and legal actually creating the agreements, we do have request formability where end users can submit a request questionnaire. It can ping legal or other teams to initiate off that request.

We, of course, do also have intake workflows. So if you're receiving counterparty paper for review, this differs a little bit in the sense that we can drag and drop those agreements into these workflows to kick off that particular review process.

I will walk through an example agreement creation. So let's say I'm coming into the system to create an MSA. I can find the corresponding template. I can select the agreement to create off of, and you'll see it now brings the drafter to a question and answer format.

So the first page here are contextual questions.

All of these questions are customizable depending on the inputs and context different teams may want the drafter to fill out to provide additional information.

So think of this a little bit like a digital sticky note of information living alongside the agreement. Who is the counterparty? Where is the counterparty located? Total deal size, etcetera.

Not only do these provide context, but we can also trigger certain conditional processes off these questions. For example, a conditional approval process, bringing in finance potentially if the agreement is above a certain deal size, or even we can change language in the underlying template as well based on certain Canada. The next page brings us to the token. So these are the actual inputs going into the template.

I'm going to the token. So these are the actual inputs going into the template. I'm going to insert things like effective date, counterparty information. This, of course, would change depending on what our user is drafting and what changes in their templates.

Administrator users have the ability to set this up according to how much autonomy they wanna give the drafter. Do they have free text field input? Are they selecting from a pick list? Are they able to access Claude's library language? In certain instances, we can have pre approved language be accessible to the drafters so that they can view that, view notes on when to use, and then input that directly into the agreement.

I'll hit save here, and the agreement has been initiated. So we walked through the end user's perspective of creating the agreement, and it now brings us more so to this negotiation hub. So this is where we're going to track all versions surrounding the negotiation. We can track the internal communication and collaboration through this activity feed, but also the external back and forth with the counterparty via email.

So we just created this agreement. If we do want to send this directly to the counterparty, we can email right from the system.

Our email within LinkSquares allows the correspondence with the counterparty to not change. The counterparty is not required to come into our system and learn a CLM they're not familiar with. They still correspond with you via email. However, we attach to that email a unique identifier, which acts like a BCC. So in that sense, we're able to pull in any red lines or any correspondence sent back via email from the counterparty, and we can capture that version they send as a latest version within the system.

All versions will be time stamped, organized, and automated. So you can track full version history below. You can see who uploaded a version, whether it's internal or external from the counterparty, they will be numbered as well. So you do have that version allocation.

As we do go back and forth with the counterparty, we not only pull in their version, but we allow a seamless review process for the internal users.

We do have a Microsoft Word integration.

So if we receive red lines from the counterparty, we can get a notification that we've received a version from the counterparty, and we can open the document up within Microsoft Word.

We do have other aspects of editing, which we can discuss as well, but we do have a lot of our customers who leverage the Word integration as they typically use Word when they are reviewing these documents.

So here is the Microsoft Word document itself. This is just the desktop version of Word. We can access all the same functionality that Microsoft Word provides while connecting directly to LinkSquares.

So the right hand side provides additional LinkSquares functionality.

That includes some aspects to assist with collaboration. The activity feed or that audit log you saw within the platform exists within LinkSquares’ Word application.

You can view a full audit history of what's occurred throughout the negotiation up to this point, and you can even use this as an internal chat and collaboration mechanism.

If you need to tag in colleagues or even highlight certain language to assign to a different department to review, you can do so directly within the Word integration.

We have other aspects as well, like a clause library. You can view a clause library or playbook that you set up within the system. You can have it accessible when you're in the document. I can review certain provisions, insert my standards into the document, access my fallback language, or even compare to what the counterparty sent when I am reviewing the document and editing.

Finally, alongside that point, we have brought different aspects of generative AI to our word integration to streamline review and the redlining process.

So some of that includes, first and foremost, an agreement summarization.

Let's say this is third party paper or something that is negotiated. We can use the AI We can use the AI to do a summary first pass of the agreement. What is this agreement? Who is it between?

You'll see in this abstract, and then a summary of key points as well throughout the contract. This allows me to see, you know, what are those key points before I actually dive into the agreement to start my edits. Now on that point as well, we have a more traditional AI chatbot. So this essentially is the ability to type in a chat to the AI and for it to do an analysis across the agreement.

A lot of our customers use this not only for typing in ad hoc prompts and questions as to whether or not certain language exists in the document, but you can even ask it to suggest language as well. And it can suggest those drafted languages, and then essentially, you can insert that into the document as well as you do review the document and make your edits.

Fairly simple prompt here, does this agreement auto renew? You'll see the AI automatically tells us whether that's the case. And if it is the case, it brings us to where that auto renewal language is in the document, so we can review further.

Finally, we do have playbooks. So this essentially is a way to narrow down the scope of the AI on a more granular level. So we can have certain rule sets here, which our AI can run across according to our certain nonnegotiables or standards for certain types of agreement.

For this particular example, for my MSAs, I have rules that the AI must review the agreement for payment terms and make it net thirty. Price increase must be, you know, six percent. Governing law must be Massachusetts.

The AI will run across the document as it's doing. It'll flag if that language exists in the agreement. So for payment terms, you can see it brings me directly to where payment terms was pulled from, and we can see it's ninety. Now not only does it flag that that deviates from our standard and needs review, but it also suggests edits to make it adherent to my standards.

I can accept this here, and that goes directly into the document to make it thirty. Of course, if I have track changes on, it would be the smart edit as well. So it's not the entire strike of the entire paragraph itself. It's simply that Smart Edit.

Once I have made all my edits, I can save a version right back to the system. All versions, again, are tracked, automated, and organized so that you never wonder what the latest version is. All different collaborators have visibility into that versioning.

If I come back to LinkSquares, you can see down below we have that version history.

As we do go back and forth with the counterparty, we can not only see version history, but we can also do things like document comparisons.

This allows us to highlight any and all versions within the system and run a comparison across them.

Maybe as we go back and forth with the counterparty, we want to run a comparison and see if there are any changes they made to the document without track changes. We're able to do this compare, and you'll see here it'll show me any changes to the document. You can see the deletion of ninety to make net payment terms thirty in this case.

Now documents can also funnel through an approval process. So on the right hand side, you'll see this task tab. This is housing the approval process for this particular agreement. We can have a standard approval process where certain types of agreements or agreements initiated off a certain templates funnel through a particular approval matrix before signature, and that can be an ordered process, unordered.

We can also base approvals on conditions. So think of those contextual questions. If the deal size is above a certain threshold, finance is automatically brought in. We're able to fully customize those so the proper review of these contracts occurs before signature is possible.

The entire approval process has occurred, the status of the agreement updates to ready for signature.

So you'll see here at this point, all collaborators have insight into the fact that the agreement has been approved, and now it is ready to be sent out.

At this point, we connect to our e signature solutions.

LinkSquares has a native signature solution, LinkSquares Sign, where we can facilitate the signature process. We also do have native integrations with DocuSign and Adobe Sign for signature. So customers can connect to their accounts, facilitate the signature process through those systems. But with that, we are tracking the document.

So you would get updates when it's out for signature, partially signed, fully signed, and we take the fully signed version. We pull it back into LinkSquares and automatically can store it in analyze when the agreement is fully executed.

LinkSquares Sign is LinkSquares native signature solution.

If customers have finalized our pre signature workflow solution, we connect natively to that. So for example, once an agreement is fully approved and ready to be sent to Signature, we can connect directly to LinkSquares Sign from this workflow.

So this takes the approved fully, the fully approved version and can send directly to LinkSquares sign from here. LinkSquares also offers a sign hub.

So if I toggle over to our sign hub, this allows for customers to manage all their signature requests or initiate a net new request.

So let's say we are initiating a net new signature request. I can grab an agreement from my desktop to upload to start the signing process.

I can start this here, and you'll see here it allows me to either request signatures in bulk or just this particular agreement, which I can rename as as well. Links were assigned will pull up the PDF of the agreement that is being sent to signature.

So you'll see here, we pull up the PDF and we allow the sender to actually input the recipients here.

So this is an example agreement that I'm going to sign. You'll see here on the right hand side, I can add those recipients. So I'll add myself. You can add the counterparty signatory. You can have them be optional signatories or required.

And then of course you can add an additional message that will be sent to them as well.

If we do have multiple signatories, which I can show here just to showcase, we can make it an ordered process. So if the counterparty signs before internal signatory up to your process, you can have that be ordered.

We also can set the fields that the signatory will receive. So again, for our internal signatory, we can have the signature block, initials, name, title, date, field, etcetera, but we also have the ability to set that for the counterparty so that when they are tasked with signing the agreement, they have their fields to fill out as well.

Once I send that request, that email is sent out. So the signatories receive an email from LinkSquares Sign saying, please sign this agreement. They're able to click that link, access LinkSquares Sign, and then sign the agreement.

All the while within LinkSquares for internal users, you have visibility and tracking of the status of the agreement. So you can see that it has been sent out for signature. You can see that zero of two has signed, and we actually audit and track when that signature process has occurred. So, again, even when the agreement is fully signed, we track that. We pull in that version back into the system so you can see the actual executed agreement. And if our customers use analyze as well, we have a way to automatically push that signed agreement into the repository to store it when it is fully executed.

Transitioning into Analyze.

Analyze is LinkSquares cloud based repository.

This is where our customers can segment out and store all their executed agreements. And this is where our proprietary AI runs across the contracts for data extraction.

Our AI can extract around a hundred and fifteen different data points from their contracts, things like full clauses, key dates from the agreement, key numerics, and milestones. So customers can not only search and report on those contract obligations, but we actually use those data points we extract from your contract but we actually use those data points we extract from your contracts to assist you with automating the organization of the contracts. As you can see here in my repository, every contract has been renamed automatically to a standard naming convention.

Users can customize their naming preference so that every agreement, both legacy, but also contract signed moving forward are renamed automatically to that convention.

The type classification occurs as well by our AI. Our AI reviews the documents and determines what broad category of agreement they are. This allows for an automated data filter. If I come into the system, I want to see only my NDAs or certain type of agreement. I can refine down by type.

The right hand side is our tagging structure.

So this is how we categorize and organize the contracts on a more granular level within the system. We do have automated tags. You'll see here in green. The AI pulls out the parties in the contract in effective year. So that baseline customers have that organization set. If you wanted to come into the system and see all your contracts with this vendor or customer or counterparty, you can click that counterparty name, and it brings you to those contracts you have with them.

Now we can also add additional tags according to your preference. So this is a way to segment out contracts further by department it belongs to or by type of agreement it is or project or region. This would be fully customized depending on your organizational preference. We do have ways as well to input these tags during the pre signature process. So if users are utilizing our finalized pre signature solution, we can apply tags there. And once the agreement is fully executed, those tags in that organization for that contract will flow in to the repository alongside with the agreement.

Now focusing on an individual document. We can touch on the different processes that occur when we ingest the contracts into the repository.

The first process is to ensure that the contract is accurately digitized and searchable for our users.

So oftentimes, we have customers who have older documents that look like this or things that are wet signed or scan locked. And so we can ingest these types of agreements into the system. These would funnel through our OCR process.

So we do have an internal OCR process where we run the initial OCR to transcribe a document like this. However, that could pull some errors, especially with an older agreement like this. An m transcribes as two n's or the incorrect date here January one could pull as January l. Just causing a lot of errors and causing a lot of issues if you are trying to full text search across your agreements.

So we layer a proprietary script on top of the transcription that's gonna flag all those different error points. And we do have a human QA team based here that can go into those error points and fix them so that you do have an accurately searchable agreement for full text searching.

After that point, we layer on our AI.

Again, for agreements that are digitized, our AI will automatically run and pull out different data points. But if we do have that scanned agreement, we do need the digitized text to run the AI across.

Once the agreement is in the system, the process is on our team to not only have it digitized, but also have the AI run. So the left hand side is showing the output of the around a hundred and fifteen different data points that can be automatically surfaced from the contracts.

That includes things like full text clause extraction.

Our AI can extract key provisions from the contract so that you can search and report on those obligations.

Things like what are the assignment provisions in my contracts? What are the change of control clauses, limitation liability, indemnification language, the term clause?

We also have algorithms that are true false data points. This checkbox here. So this will flag if the agreement auto renews or if there's termination for convenience language or if change of control consent is required.

In that way, you can pull those reports in aggregate. I can pull a report of my contracts that auto renew or quickly see if we have agreed to any contracts with termination for convenience language in our agreements.

A big point for a lot of teams is tracking key dates. That's something we automatically pull as well. We extract the effective date, the commencement date, the renewal date, the termination date. And even if a date is not explicitly stated in the contracts, we'd be able to do a calculation.

For example, not only pulling the renewal date itself, but actually taking into account the required opt out period. If you have to give notice sixty days before the renewal, we backtrack and calculate the automatic renewal opt out date. That way, prior to any renewals or prior to any decisions regarding next steps with that particular engagement, you'd be able to get adequate notice and have information as to whether or not you do want it to auto renew.

All these data points are out of the box, but customers can also customize data points. If there's something more bespoke you'd like to track, there are different ways to do that. One of those ways is what we call user generated data points. So oftentimes, this encapsulates tracking things not within the four corners of the contract, like a point of contact, an agreement owner. You can see at the bottom here, I have a couple examples, these blue pencils.

Users can create as many additional data points as they'd like to track. And again, you can search and report on these alongside the automated data extraction as well.

There's quite a few things we do with the data now that we extract. So we can showcase holistic reports. We pull all those dates we extract from your contracts, and we present them automatically into an events calendar. This showcases what's up coming for termination, renewal, what's the auto renewal opt out date. So you can see this month, this quarter. We can also present this in a list view as well.

All of these dates as well, we can set up automated notifications to go out prior to these dates.

These reminders can be customized in terms of who's receiving those reminders. If there's a certain team managing these dates and these milestones, you can set it up so they receive that reminder. You can also customize when they receive that reminder. Thirty, sixty, ninety days before, we can set that up so that those proactively go out to those individuals prior to these dates.

LinkSquares also has a dashboard. So within the repository, our dashboard is focused on analyzing your executed agreements. Now that everything is centralized and stored and organized in the system, you can really get this bird's eye view. I can see of the fourteen hundred agreements I have, what's a breakdown of contracts by type. I can see agreements renewing or terminating each quarter. You can click into these present spreadsheets of these data points, export anything to Excel.

But it also provides for a deeper analysis into all the clause analysis allows me to view and compare certain clause provisions. If I wanna see the change of control clauses, I can pull that report. If I'd like to see price increase language, I can zero in on that data point. Similarly, with those true language, I can zero in on that data point.

Similarly, with those true false data points, you get holistic visibility into whether that language exists in your contracts. I can see ninety five contracts I have have termination for convenience language in them, and quickly access those agreements as well. Now the dashboard is really focused on overarching reporting. We can also get really granular and specific with reporting back here on this main page.

There's many different ways to search and filter across your repository.

First and foremost, now that we have helped you organize the contracts, you can filter by name of the contract, by type of contract, or by organizational tag. But we also can advance filters and search within the contracts themselves.

There's many different searching options. I'll showcase a couple here today. We do have an agreement content search.

So this acts as a keyword search across your entire contract database.

I can type in a term. I can advance it to multiple terms. We have and or searching abilities.

But essentially, this runs off of fuzzy or inexact logic where it's pulling me not just to regulate in my contracts, it's pulling me to regulations, regulatory as you can see down here, and allows me to toggle within the contract to see where that was extracted from as well.

This gives you the broadest search possible, but you can also narrow this down to just an exact search to just pull the term regulate.

With our full text searching, again, this allows you to have all your contracts in the system. Maybe most things are digitized, but even if you have older contracts that are, again, presented like this and are not currently searchable, those would have gone through our OCR process, are digitized, and are now full text searchable for you.

Similar to the full text search, we do have proximity searching abilities. So you can even narrow down the scope of the full text search to look for language within a certain word count of a certain term. The word data, for example, within twenty words of the word delete deletion.

This allows me to go within a paragraph or a sentence in my contract to do do that proximity hook.

In addition to the full text searching, we also have reporting based on our AI data points. So global term searching allows us to report on our AI data points, any custom terms we're tracking as well. And essentially, we can get really granular with our searching and reporting.

Let's say we wanna pull a report of my contracts coming up for renewal within the next quarter or within the next year. You can specify the period, but, essentially, depending on the time frame you input, so here the next year, it'll refine me down to the forty two contracts I have renewing within that period.

This is where tags come to play as well because I can use tags, the organization, as additional hooks in reporting. Let's say I just wanna run this renewal date search for a certain department's contracts or my vendor customer contracts or contracts from a certain region. You can get And customize the report with data from the contract. So we can treat this page a little bit like an Excel.

I can build out this spreadsheet with any data I want to view and compare. So maybe the renewal date here, the notice clause, you'll see those will present on this page so I can compare that. We also can export. So if we needed to send this to any stakeholders or anyone external, we can push this to Excel to access as well.

As you can see here.

Finally, our system also allows customers to leverage a clause library. This is a great hook between the repository, the executed agreements, and the pre signature aspect.

So a lot of times our customers come across language they like in terms of language they've agreed to in the past. You can see here this assignment clause and this one contract, and they wanna use that in the future when drafting. You can simply highlight a clause from here and add it right to the library. You can name it, categorize it, have notes on when to use, and submit that as a clause version.

Within the system, you can track all those clauses and your library and playbook, so you can see different iterations of clauses, different fallbacks, and really have notes on when to use. And, again, all these clauses can be pulled seamlessly into the pre signature side. So when you're creating new agreements, you can access certain clause iterations. Even when you're negotiating and directly within Microsoft Word, you'd be able to access as well.