LinkSquares
Contract lifecycle management platform for in house legal teams, covering the full lifecycle across pre signature drafting, review and approval through Finalize and post signature repository, extraction and analytics through Analyze, with workflow automation and reporting connecting contracts to business data. The AI layer is LinkAI, rebuilt in May 2026 on an AI native agentic architecture rather than added as a chat layer over the existing product. Extraction is the historic strength and is targeted at the terms in house teams track most: payment deadlines, governing law provisions, liability clauses, renewal language and commercial obligations, with batch analysis across large volumes of legacy agreements for due diligence and repository audit, clause libraries and playbooks available inside the drafting environment, and extracted contract data turned into reporting and business intelligence. The vendor states that customer contract data is never shared with or used to train any third party LLM providers and that data stays private within the platform. Integrations named are Microsoft Word, Google Docs, Microsoft 365, Salesforce, Slack, DocuSign and HubSpot. Security is published on a dedicated page stating SOC 2 Type II, ISO 27001 and GDPR compliance with encryption. Stated adoption is more than 1,200 customers, with DraftKings, TIME, ProPharma and Asurion named. Recognised as a G2 Leader in contract lifecycle management for five consecutive years, including the Winter 2026 Grid Report. Raised a $100m Series C in April 2022 led by G Squared at a stated $800m valuation, bringing total funding to $161.4m. Pricing is not published. The vendor also publishes extensive buyer guidance on evaluating AI contract management, including advice that buyers should demand precision and recall benchmarks on their own documents.
Capability grades
All 15 axes, graded from public sources on the date shown. Hover a grade to see what the letter means on that axis.
AI Centrality
How much of the product is actually AI. Whether the machine learning is the mechanism the buyer is paying for or a feature layered onto conventional software, and whether the vendor is specific about which is which.
A platform that chose to rebuild rather than bolt on, which is the distinction this axis exists to catch. LinkAI launched 5 May 2026 as an AI native agentic architecture replacing the prior approach, and independent review material credits that specifically as rebuilding on an AI native architecture rather than attaching a chat sidebar to the existing product, noting most incumbent CLM vendors took the bolt on path. Extraction has been the core of the product since the beginning: identifying and pulling payment deadlines, governing law, liability, renewal and commercial obligation terms out of executed agreements is a model task, and the analytics layer that made the company's name is built on that extracted output, so the models generate the data the rest of the product reasons over. Held at B rather than A because the repository, workflow, approval routing and reporting infrastructure still stands without the model layer, and because the rebuild is four months old at the date of this record, so the AI native claim describes a recent architectural decision rather than a long established one. Revisit on the next pull.
Citation Accuracy and Hallucination Disclosure
Whether the vendor publishes measured accuracy on citations and assertions, grounds output to primary sources, and says plainly what its system does when it does not know. Legal has a documented public record of fabricated citations reaching filed briefs, so an untested claim of accuracy is not evidence.
The vendor tells buyers to demand the exact measurement it does not publish, which is the sharpest instance of that pattern in the pull. Its own published buyer guidance on evaluating AI contract management states that buyers should demand precision and recall benchmarks on their own documents and maintain review workflows for exceptions. That is correct advice and it is the right metric for extraction work. LinkSquares publishes no precision or recall figure of its own, for any clause type, on any corpus. Extraction accuracy is claimed as a differentiator in comparison content and quantified nowhere. Also absent: no error rate by clause type, no statement of behaviour on non standard or ambiguous language, no confidence indication on extracted values, and no evaluation methodology. The gap is consequential because extraction failures in this product are silent: a missed renewal date or auto renewal clause does not announce itself, it simply never appears in the report the legal team relies on. Checked the LinkAI page, the security page, the comparison and buyer guide material and the home page on 29 Aug 2026.
Autonomy and Oversight Model
What the system decides on its own, what a lawyer must approve, and whether the vendor documents where the review point sits. A tool that drafts under review and a tool that files without one are different products and different risks.
The product is marketed as agentic and the oversight model is not described. LinkSquares positions itself as agentic CLM and states that the platform handles the bulk of standard contracts automatically, which is an autonomy claim with commercial substance behind it. Its own buyer guidance recommends maintaining review workflows for exceptions, so the vendor knows where the human belongs. What is not published for its own product: which contract types or value thresholds can complete without human review, what makes a contract standard enough to be handled automatically, whether an agent can send or approve a contract unattended, what confidence threshold routes an exception to a person, and what the audit record shows when an agent rather than a lawyer made the call. Marketing an agent and describing its limits are different acts and only the first has happened. Checked the home page, the LinkAI page, the comparison material and the buyer guide material on 29 Aug 2026.
Operational and Outcome Evidence
Named, dated evidence that the product works in production at real firms or legal departments. Case studies with figures and identified customers count. Unattributed testimonials and launch announcements do not.
Customers are named, a case study carries figures, and one of those figures does not survive arithmetic. Named customers: DraftKings, TIME, ProPharma and Asurion, with more than 1,200 customers stated. Independent placement is dated and repeated: G2 Leader in contract lifecycle management for five consecutive years including the Winter 2026 Grid Report, with a stated 98 percent of users reporting the product moving in the right direction. A named case study, Softonic, reports outside counsel costs reduced by 40 percent, which is a coherent and checkable claim from a named company. Held at B rather than A on the quality of the other figures. The same case study reports NDA processing time cut by nearly 400 percent, and a reduction of more than 100 percent is not a possible quantity, so the claim is either a throughput multiple described as a reduction or an error, and either way it cannot be read as stated. A separately published 360 percent ROI over three years carries no methodology, sample or baseline. A vendor that names its customers and publishes an impossible percentage is being open and imprecise at the same time, and the record should say both.
Privilege and Confidentiality Posture
How client confidences are handled: attorney client privilege and work product treatment, segregation of one client matter from another, whether client data trains any model, and what the vendor commits to in writing rather than in marketing.
Confidentiality is well evidenced at platform level and privilege is not addressed. Published: SOC 2 Type II, ISO 27001 and GDPR compliance on a dedicated security page, encryption of all contracts and data, and a stated commitment that customer data stays private within the platform. Independent review material describes data residency and retention controls as mature enough that a public company legal operations lead does not need to negotiate addenda, which is a practitioner assessment rather than vendor material and is treated as supporting. What is absent: any treatment of legal professional privilege or attorney work product, and any statement about the confidentiality of proprietary negotiation playbooks and clause libraries, which are the closest thing in this product to work product and which the vendor elsewhere states are isolated. The platform is used by legal, sales, procurement, finance and HR in the same instance, so the boundary between legal's own analysis and the wider business is a live question and is not described. Checked the security page, the LinkAI page, the data privacy solution page and the home page on 29 Aug 2026.
UPL and Professional Responsibility Posture
Whether the vendor is clear that it supplies a tool rather than legal advice, who its audience is, and how it addresses unauthorized practice of law, competence and supervision duties, and jurisdiction limits. ABA Formal Opinion 512 is the reference point.
Not located. The product drafts, reviews and approves contracts and is explicitly sold for use by sales, procurement, HR, marketing and finance alongside legal, so non lawyers act on machine generated contract analysis by design and the vendor describes that as a feature. Nothing published addresses the professional dimension: no statement that output is not legal advice, no guidance on when a contract should reach a lawyer, no positioning on the in house counsel's supervisory role over self service authoring by business users, and no engagement with any bar guidance. Checked the home page, the LinkAI page, the solution pages and the buyer guide material on 29 Aug 2026.
AI Governance and Bias Disclosure
Published governance over model behaviour: who owns it inside the vendor, what is tested before release, and what is disclosed about disparate output across matter types, parties, or populations.
The vendor publishes governance guidance for its customers and nothing about its own models. Its buyer guide recommends implementing quarterly AI governance reviews to monitor bias, validate accuracy and enforce compliance, and lists model governance covering audit trails, PII handling and zero retention options as things a buyer should expect from a vendor. Every one of those is advice pointed outward. For LinkAI itself the located material amounts to a claim that it is designed with enterprise grade data security and governance built in. No AI policy, no model card, no bias or fairness testing, no evaluation methodology or result, no accuracy monitoring, no drift statement, no named governance body and no ISO 42001 despite holding ISO 27001. Same shape as FinregE, which analyses regulatory obligations for customers in structured detail and turns none of that rigour on itself, and graded the same way for consistency. Checked the LinkAI page, the security page, the buyer guide material and the comparison content on 29 Aug 2026.
AI Safety and Data Stewardship
Retention, deletion, access control, and what happens to prompts and documents after they are processed. Whether the vendor states its subprocessors and its incident practice, or leaves the buyer to assume.
A real and repeated training commitment, with a carve out that has to be read carefully. The vendor states that contract data is never shared with or used to train any third party LLM providers, that contract data and proprietary playbooks are completely isolated and never used to train public AI models, and that data stays completely private within the LinkSquares platform. That answers the dominant risk for a CLM, which is customer contract text reaching an external model provider, and it answers it in plain words rather than by implication. Held at B rather than A because of what the wording leaves open. Both formulations are scoped to third party and public models. Neither states that LinkSquares does not use customer contract data to train or tune its own models inside its own platform, and stays completely private within the LinkSquares platform is consistent with internal training rather than exclusive of it. No retention position for AI processed content is published either, and the vendor's own buyer guide lists zero retention options as something a buyer should demand without stating whether this product offers one. A well drafted sentence that stops precisely where the harder commitment would begin.
AI Liability and Recourse
What the vendor stands behind contractually when its output is wrong. Indemnities, caps, carve outs, insurance, and whether any of it is published or only reachable through a negotiated agreement.
No published position located. Nothing was found on liability for AI output, warranty, service levels or remedy where an extraction is wrong, a clause is missed, or an agentic action progresses a contract that should have been escalated. The exposure is concrete: the platform is stated to handle the bulk of standard contracts automatically, and a missed auto renewal or liability cap in an executed agreement is a loss the customer discovers later with no published vendor position on it. Checked the home page, the LinkAI page, the security page and the site navigation on 29 Aug 2026. Enterprise agreements govern this and are not public, and no public terms page was located in this pass.
Practice Systems Integration Depth
How deeply the product reaches into the systems legal work already lives in: document management such as iManage and NetDocuments, Word and Outlook, contract lifecycle management, matter management, e-billing, and court filing systems.
Integrations are named, numerous and aimed at where contract work actually happens. Named: Microsoft Word, Google Docs, Microsoft 365, Salesforce, Slack, DocuSign and HubSpot, with the vendor stating that clause libraries and playbooks are accessible from inside the drafting environment so users do not switch tabs or upload files. Word and Google Docs native drafting is the integration that matters most for this product class and it is present, and the CRM and e-signature connections cover the pre signature path end to end. Held at B rather than A on a gap identified in independent review material and not contradicted by anything located: no generally available developer facing API, which limits a customer's ability to move contract data into systems the vendor has not built a connector for. No document management system such as iManage or NetDocuments is named either. Checked the LinkAI page, the comparison material, the home page and independent review material on 29 Aug 2026.
Deployment Model and Data Residency
Where the software runs and where the data sits. Multi tenant cloud, single tenant, private deployment, on premises, and whether region of residence is a published option or an enterprise conversation.
Residency is described in third party assessment and not in vendor material located here. Independent review material states that data residency and retention controls are mature enough that a public company legal operations lead does not have to negotiate addenda, which is a specific practitioner claim about the existence and quality of residency controls. No vendor page located in this pass names a hosting provider, enumerates regions, states a residency commitment, or describes single tenant or private deployment options. Source basis recorded as Third Party Estimated on that footing rather than credited as vendor disclosure. Correction candidate: the dedicated security page carries certification statements and may carry residency detail below the summary content read here.
Security Certifications and Trust Center
Independent attestation a buyer can pull without a sales call: SOC 2, ISO 27001, penetration test summaries, a trust center with current reports and named scope rather than a badge image.
Two named certifications on a dedicated security page, published openly rather than gated. SOC 2 Type II and ISO 27001 are both stated, alongside GDPR compliance and encryption of all contracts and data, on a page whose purpose is security rather than as a line in marketing copy. Both certifications are corroborated across independent review material, which describes them as the two certifications that clear most enterprise procurement gates. Publishing the status openly with no login is better than the request flow tier and is the reason this sits at the top of B. Held below A on three absences: no auditing firm is named for either certification, no certificate date, examination period or expiry is published so currency cannot be established, and no trust centre or documentation request route was located, so a reviewer wanting the report itself has no stated path. Consistent with Regology and Onspring at B, and below Lexis+ AI and Exterro at A, which add currency, scope detail and a verifiable route.
Model Supply Chain Disclosure
Which models sit underneath, whose they are, where they run, and whether the vendor commits to telling customers when that changes. A legal buyer inherits every dependency it cannot see.
The category is acknowledged and no party is named, and the acknowledgement is inadvertent. By committing that contract data is never shared with third party LLM providers, the vendor confirms that such providers exist in the architecture, since a commitment not to share with them is only meaningful if they are there. Nothing names any of them: no provider, model family or version, no subprocessor list, and no statement of what runs where between the vendor's own infrastructure and any external model. For a product now rebuilt on an agentic architecture, the identity of the underlying models is a question an enterprise security review asks directly. Compare Onspring at B, the only record on this index naming its provider outright. Checked the LinkAI page, the security page, the comparison material and the home page on 29 Aug 2026.
Commercial Transparency
Whether a buyer can learn what this costs without entering a sales process: published rates, the unit being charged, what sits behind an enterprise tier, and what implementation adds.
No pricing published at any level. No price, no range, no tier structure and no unit of charge, and the vendor's own buyer guidance tells readers to compare user based, usage based and record based pricing models without disclosing which of those it uses itself. Third party reconstruction places the median around $31,000 per year with a starter tier near $10,000 and enterprise above $75,000, which is independent estimation rather than disclosure and is recorded as context rather than credited. That estimated range is material to a buyer because it places the product outside the reach of small teams, which is exactly the kind of fit judgement published pricing would let a reader make for themselves. Checked the home page, the LinkAI page, the pricing navigation and independent review material on 29 Aug 2026.
Firm and Practice Coverage
Who the product is actually built for. AmLaw, midlaw, small firm and solo, in house departments, government and courts, and which practice areas are supported rather than merely claimed.
Coverage is stated in the terms that matter for contract work, which is clause and lifecycle scope rather than jurisdictions. Named clause and term coverage: payment deadlines, governing law provisions, liability clauses, renewal language and commercial obligations, with batch analysis across large legacy portfolios for M&A due diligence and repository audit. Lifecycle coverage runs pre signature through post signature in one platform, and the user set extends beyond legal to sales, procurement, finance, HR and marketing, which is honest about who actually touches contracts. More than 1,200 customers across the in house market. Held at B rather than A because coverage is not characterised where it would matter to a buyer: no statement of which contract types or languages are supported, no jurisdictional scope for governing law extraction despite that being a named capability, and no indication of extraction depth by agreement type. Independent review also identifies the scope boundary honestly, noting no primary law research capability, which is correct and is a category fact rather than a gap.
Legal Signals
What each signal meansA signal records what public sources say on the date shown. It is not a grade and it is not a recommendation. Where a signal reads Not addressed, it means the index did not locate the material in public sources on that date, which is a statement about disclosure rather than about the product.
Client Data in Training
Can material a lawyer puts into this product be used to train a model?
A public policy or trust page states no training on customer content, with no matching term located in the published agreement.
Policy never, and the scope of the never is the finding. READ THE QUALIFIER: the quoted commitment is to public AI models, and the parallel statement on the LinkAI page is that contract data is never shared with or used to train any third party LLM providers. Both are scoped to models outside the vendor. Neither states that LinkSquares does not use customer contract data to train or tune its own models, and the accompanying phrase that data stays completely private within the LinkSquares platform is consistent with internal training rather than exclusive of it. Recorded at policy never because a real and repeated commitment exists and covers the dominant risk for a CLM, which is contract text reaching an external provider, and erasing it as silent would misdescribe the record. Recorded as policy rather than contractual because it appears on product and comparison pages rather than in terms or a data processing agreement. A carefully drafted sentence that stops precisely where the harder commitment would begin. Checked the LinkAI page, the security page, the comparison material and the home page on 29 Aug 2026.
Prompt and Output Retention
How long does the product keep what a lawyer typed, and can that be set to zero?
No located public material states how long prompts and outputs are retained.
Not addressed, and the vendor's own buyer guidance shows it knows the question. That guidance lists zero retention options among the things a buyer should expect from an AI contract management vendor, alongside audit trails and PII handling. No statement was located as to whether LinkSquares itself offers a zero retention option, what its default retention period is for AI processed contract content or extracted output, or whether any of it is customer configurable. Advising buyers to demand a control without stating whether you provide it is the pattern this record repeats across three axes. Checked the buyer guide material, the LinkAI page, the security page and the data privacy solution page on 29 Aug 2026.
Ethical Walls and Matter Segregation
Does retrieval respect the firm’s ethical walls, or can the model read across them?
No located public material addresses walls or matter level segregation.
Not addressed for this product. The vendor's buyer guidance names MFA and SSO among the controls a buyer should expect, and independent material notes role based access controls as standard across enterprise CLM platforms generally, but neither is a statement about what LinkSquares implements. The structural question is live: the platform is sold for use by legal, sales, procurement, finance, HR and marketing in a single instance holding the whole contract estate, and nothing published describes what separates legal's own analysis, playbooks and risk annotations from the business users working in the same system. No document management system integration exists to inherit permissions from. Checked the security page, the LinkAI page, the solution pages and the home page on 29 Aug 2026.
Third Party Request and Subpoena Notice
If someone subpoenas the vendor for a firm’s data, does the firm hear about it first?
No located term or policy addresses third party requests for customer data.
Not addressed. No government or law enforcement request clause, no commitment to notify a customer before producing their data, and no transparency report were located. The dedicated security page states SOC 2 Type II, ISO 27001, GDPR compliance and encryption and does not reach third party requests. Checked the security page, the data privacy solution page, the home page and the site navigation on 29 Aug 2026.
Primary Law Corpus Provenance
Where does the law in this product come from, and does the vendor have the right to use it?
No located public material identifies the corpus behind the product’s answers.
Not addressed, and inapplicable in the usual sense. The product operates on the customer's own executed and draft agreements rather than on published law, so there is no external legal corpus to name, license or date. Recorded rather than omitted because the underlying question has a live form here that is unanswered: what the extraction models were trained on. Extraction of governing law, liability and renewal terms across contract types implies a substantial training corpus of agreements, and nothing published states whether that corpus was licensed, synthetic, publicly sourced, or built from customer contracts. The commitment not to train third party models on customer data speaks to future flow and not to what already built the extraction capability. Checked the LinkAI page, the security page and the comparison material on 29 Aug 2026.
Good Law Verification
Does the product tell you when the authority it just cited has been overruled?
No located public material addresses whether authority is checked for subsequent history.
Not addressed, and inapplicable on the facts. LinkSquares analyses contracts rather than researching law and produces no citation to legal authority, so a citator would have nothing to check. Independent review material identifies the same scope boundary directly, noting the absence of primary law research on case law, statutes and regulations, which is a category fact rather than a defect. Recorded as a scope fact so a reader does not mistake an inapplicable row for a disclosure failure, consistent with the treatment of this row on Legal Tracker, Mitratech, TrialView and Exterro. Checked the LinkAI page and the comparison material on 29 Aug 2026.
Refusal and Uncertainty Behaviour
What does the product do when the answer is not in the corpus?
No located public material addresses what the product does when it cannot ground an answer.
Not addressed. Nothing published describes an explicit no answer path, abstention behaviour or confidence signal for extraction, review or the agentic layer. The vendor's own buyer guidance recommends maintaining review workflows for exceptions, which implies exceptions are identifiable, and nothing states how LinkAI identifies one: whether a low confidence extraction is flagged, left blank, or filled with a best guess that reads identically to a confident one. For a product whose output is a structured field in a report, an unflagged wrong value and an unflagged missing value are both invisible to the person relying on it. Checked the LinkAI page, the buyer guide material, the comparison content and the home page on 29 Aug 2026.
Fabricated Citation Record
Does a public court record exist involving output from this product?
No court order, opinion or disciplinary record naming this product has been located as of the date shown. This is a statement about the public record, not a finding about the product.
None located, with the instrument named. General web searches combining the vendor and product names with court, order, sanction, contract dispute and extraction error terms returned nothing on 29 Aug 2026, and no named docket database or court record tracker was searched. The product generates no citations to legal authority, so the classic fabricated case failure mode does not arise, and the analogous risk would be a missed or misextracted contract term surfacing in a commercial dispute. Recorded as a statement about what this search found, not as a clearance.
Bar Guidance Alignment
Has the vendor engaged in public with the ethics opinions its buyers are bound by?
No located public material engages with bar or ethics guidance.
Not addressed. No named ethics opinion, no ABA Formal Opinion 512, no state bar guidance and no engagement with professional conduct rules was located, despite the vendor publishing a substantial library of in house counsel guidance covering AI adoption, governance reviews, procurement and change management. The omission is notable given that library's scope: it advises legal departments on how to govern AI adoption without engaging the professional rules those departments' lawyers work under. Checked the buyer guide material, the in house insights library, the LinkAI page and the home page on 29 Aug 2026.
Billing and Fee Posture
Does the vendor address what happens to the bill when the work takes an hour instead of six?
Public materials claim time savings without addressing billing or disclosure.
Savings claims only, including one that cannot be read as stated. Published: a named customer, Softonic, reducing outside counsel costs by 40 percent, which is coherent and attributable, alongside a stated 360 percent ROI over three years and contract review times reduced by up to 400 percent. A reduction of more than 100 percent is not a possible quantity, so the last figure is either a throughput multiple presented as a reduction or an error, and it is recorded here as unreadable rather than credited. Nothing appears on the client side of the equation: no position on billing for AI assisted contract work, and no record a department could produce showing what portion of a review was machine performed. Checked the LinkAI page, the comparison material and the case study content on 29 Aug 2026.
Outside Counsel Guideline Readiness
Can a firm get this vendor through a client’s AI clause without a bespoke negotiation?
No located public material supports a client side disclosure obligation.
Not addressed, with one genuine open element. The dedicated security page publishes SOC 2 Type II, ISO 27001 and GDPR compliance without a login, so a department has something citable immediately, and open publication is better than a gated summary. Everything else a forwardable pack needs is missing: no subprocessor list, no named model provider, no data processing agreement, no trust centre and no documentation request route were located, so there is no path to the underlying reports and no way to answer a client's question about which third parties process its contract data. Recorded as not addressed because a certification summary is not a disclosure pack and no request route exists. Checked the security page, the data privacy solution page, the LinkAI page and the site navigation on 29 Aug 2026.
Court Disclosure Support
If a judge’s standing order requires an AI disclosure, can the product produce one?
No located public material addresses court disclosure or verification certification.
Not addressed, and close to inapplicable in the form this signal usually takes. LinkSquares produces contract analysis and executed agreement data rather than work product filed with a court, so the model used, sources retrieved and human verification export a judicial standing order asks for has no natural object. Recorded as a scope fact rather than omitted. Worth noting the adjacent gap that does apply: nothing indicates the platform records which contract fields were AI extracted as opposed to human entered, or whether a person confirmed an extracted value, so a party relying on repository data in a dispute could not evidence how any given term got into the record. Checked the LinkAI page, the comparison material and the home page on 29 Aug 2026.