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.