Leah vs LinkSquares: how they compare in 2026
Both sell contract lifecycle management to in house teams and both now sell agents, but they serve different buyers. LinkSquares is built for the legal department. It drafts and approves contracts in Finalize, pulls terms out of signed agreements in Analyze, and works inside Word, Google Docs, Salesforce and Slack. LinkAI was rebuilt on an agentic architecture in May 2026, and a Workflow Builder Agent followed in September. Leah aims at large enterprises, with agents for contracting, procurement and finance tied into SAP, NetSuite and Coupa. Leah publishes more of the paperwork. Its master terms, liability caps, subprocessor list and four named model providers are all public, along with a governance loop that logs every agent action. LinkSquares publishes no terms or subprocessor list. It says the platform handles most standard contracts automatically, without describing where that stops. LinkSquares answers with a named result, Softonic's 40 percent cut in outside counsel costs, while Leah's figures come from unnamed customers. Both say outside models never train on customer contracts, and Leah says its contracts train no model at all.
At a glance
All 15 axes, side by side
The same grid applied to every vendor in the index, graded from public sources. 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.
Leah sells AI agents and an orchestration layer that sit on top of a contract lifecycle platform, and that platform works without them. The vendor describes it the other way round. It says other vendors bolted AI onto systems built for manual workflows, while Leah was designed from scratch with orchestration as the foundation. ContractPod Technologies has sold contract lifecycle management since 2012. Leah launched in March 2023 as an AI services hub within that platform, went standalone in May 2023, and Leah Intelligence followed in October 2024. Without the agents, the product is still a working CLM with guided intake, approval routing, DocuSign and Adobe Sign execution and a contract repository. That CLM has its own market and its own Gartner category placement. The orchestration layer on top is model driven.
LinkAI launched on 5 May 2026 as an agentic architecture that replaced the earlier approach. Independent review material describes it as a rebuild on a new architecture rather than a chat sidebar attached to the existing product. Extraction has been the core of the product from the start. Pulling payment deadlines, governing law, liability, renewal and commercial obligation terms out of signed agreements is a model task. The analytics layer the company is known for is built on that extracted output, so the models generate the data the rest of the product works with. The repository, workflow, approval routing and reporting still stand without the model layer. The agentic design is recent, dating from the May 2026 rebuild rather than from the product's origins.
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.
Leah returns to accuracy repeatedly in its materials, and the AI governance page says every action is measured against benchmarks for accuracy, bias and outcome. Neither that page nor the home page publishes a result from that measurement. They give no accuracy figure, no error or hallucination rate, no description of any benchmark or test set and no published evaluation. The product material describes a legal helpdesk that answers contract questions with sources attached, so a user can in principle check an answer against its source. Neither page says what the system does when the customer's own contracts do not support a position.
LinkSquares publishes buyer guidance on evaluating AI contract management. It tells buyers to demand precision and recall benchmarks on their own documents and to keep review workflows for exceptions. LinkSquares publishes no precision or recall figure of its own, for any clause type, on any set of documents. Its comparison content claims extraction accuracy as a strength without a published measurement. It gives no error rate by clause type, no statement of behavior on nonstandard or ambiguous language, no confidence indicator on extracted values and no evaluation method. 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.
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.
Leah's dedicated AI governance page sets out a three stage control loop. In the first stage, policy in, the customer defines which agents may act, on which data, within which thresholds and where escalation is required. Those policies are held as configuration rather than code. In the second, execution governed, every agent action runs through those policies in real time. Approvals, escalations and rejections are applied automatically, and the orchestrator enforces guardrails at each step. In the third, audit out, every decision is logged with the rationale, what the agent did, why, under which policy, on what data and to what outcome. The records are described as tamper resistant and immutable. The loop sets the thresholds, the review points and the route back to human judgment. Leah's home page puts the position in one line, that the workflow runs itself while the judgment stays human. The page does not say what happens after an output is found to be wrong. Default modes are not described, because the customer configures the guardrails rather than receiving them preset.
LinkSquares positions itself as agentic CLM and states that the platform handles the bulk of standard contracts automatically. Its own buyer guidance recommends maintaining review workflows for exceptions. For its own product, it does not publish which contract types or value thresholds can complete without human review, or what makes a contract standard enough to be handled automatically. It does not say whether an agent can send or approve a contract unattended, or what confidence threshold routes an exception to a person. Nor does it say what the audit record shows when an agent rather than a lawyer made the call.
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.
Leah publishes qualitative quotes from four named people. Noelle Perkins is EVP and Chief Legal Officer at Cushman and Wakefield, and Lidia Kamleh is Chief Legal Officer at Dubai Future Foundation. Frances Bain-Cumberbatch is Chief Legal and External Affairs Officer at Ansa McAL, and Zillia Knight is Senior Legal Officer at Terumo Europe. Three results are published with the customer unnamed. A major American logistics company cut contract review time by 91 percent. A global manufacturer protected more than $18 million of revenue, and an American retail REIT tracked more than $2 million of savings. About 54 enterprise logos appear, including Philips, MUFG, Sandoz, Pernod Ricard, Alaska Airlines and Wood PLC. PwC and KPMG appear among them. PwC entered a commercial alliance in March 2024, and Epiq resells Leah in its Service Cloud. Integreon is quoted as an early adopter that resells it, and Pinsent Masons adopted it for managed legal services in July 2025. Partners and customers are shown together without distinction, and the Chief Product Officer of Execo, another services partner, is among the testimonials.
LinkSquares names DraftKings, TIME, ProPharma and Asurion as customers and states more than 1,200 customers in all. G2 has named it a Leader in contract lifecycle management for five years running, including the Winter 2026 Grid Report. On G2, 98 percent of users are reported as saying the product is moving in the right direction. A case study with Softonic, a named customer, reports outside counsel costs cut by 40 percent. The case study says NDAs used to take three to four business days, and that sales reps using templates now spend on average five times less time executing them. A LinkSquares comparison guide describes the same result as NDA processing time cut by nearly 400 percent. The vendor also states a 360 percent return on investment over three years, without a method, sample or baseline.
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.
Leah says customer contract data is never used to train models. The AI governance page treats data leaking into models the customer does not own as a failure it engineered out. It says zero data retention is the only acceptable answer, and that Leah enforces zero retention with OpenAI and Anthropic so they process data but never store it. Encryption is AES-256 at rest and TLS in transit, with keys in Azure Key Vault, rotated and reachable only through controlled service accounts. Role based access control is said to apply at every layer, and single tenant deployment is offered for customers with strict isolation needs. Leah sells to Fortune 500 legal departments, and none of this material addresses privilege or work product.
A dedicated security page publishes SOC 2 Type II, ISO 27001 and GDPR compliance and encryption of all contracts and data. The vendor says customer data stays private within the platform. Independent review material, a practitioner view rather than vendor material, describes the residency and retention controls as mature enough that a public company legal operations lead need not negotiate addenda. Nothing published addresses legal professional privilege or attorney work product. Negotiation playbooks and clause libraries are the closest thing to work product in this product. The security material does not cover their confidentiality, though the vendor says elsewhere that they are isolated. Legal, sales, procurement, finance and HR work in the same instance, and nothing published describes the line between legal's own analysis and the wider business.
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. Where the advice line is not the duty a product raises, the axis is read through the nearest professional duty it does raise: judicial conduct rules and the reviewing duty for products sold only to courts, and the duty to bill for time actually spent for products that draft time entries.
Leah publishes nothing on the line between a tool and legal advice. Its site carries no disclaimer of any kind and no ethics or professional responsibility page, and it names no bar or ethics guidance, including ABA Formal Opinion 512. The platform is sold to run legal work end to end across legal, procurement and finance teams. In the vendor's own framing, agents carry out commercial work in several steps without routing every decision through a person.
The product drafts, reviews and approves contracts and is sold for use by sales, procurement, HR, marketing and finance as well as legal. Staff who are not lawyers act on machine generated contract analysis by design, and the vendor presents that as a feature. LinkSquares publishes nothing on the line between the tool and legal advice. No statement says output is not legal advice, and no guidance says when a contract should reach a lawyer. Nothing covers in house counsel's supervision of business users who write contracts themselves, and nothing engages with bar guidance.
AI Governance and Bias Disclosure
Published governance over model behavior: who owns it inside the vendor, what is tested before release, and what is disclosed about disparate output across matter types, parties, or populations.
A dedicated AI governance page names six failure modes the vendor says it engineered out. They include black box decisions that cannot be defended to a regulator or board, and compliance frameworks retrofitted after the fact. Against them the page sets three pillars and a loop of policy, execution and audit. Each action is logged with its rationale and governing policy, in records described as tamper resistant and immutable. The page also says every action is measured against benchmarks for accuracy, bias and outcome, and that accountability is structural rather than aspirational. It names no person or role accountable for model behavior and describes no testing before release. It gives no benchmark method or schedule and discloses no bias measurement result.
The LinkSquares buyer guide recommends quarterly AI governance reviews to monitor bias, validate accuracy and enforce compliance. It lists model governance covering audit trails, PII handling and zero retention options as things to expect from a vendor. That guidance is written for customers. For LinkAI itself, the published material says only that it is designed with enterprise level data security and governance built in. The vendor publishes no AI policy, model card, bias or fairness testing, evaluation method or result, accuracy monitoring, drift statement or named governance body. The company holds ISO 27001 but has no ISO 42001 certification.
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.
The AI governance page describes TLS in transit and AES-256 at rest. Encryption keys are managed in Azure Key Vault, rotated regularly and reachable only through tightly controlled service accounts. The page also lists multifactor authentication, secure API gateways, network segmentation, real time monitoring and a documented incident response plan. Audit logs are described as comprehensive, tamper resistant and immutable. For outside assurance, the vendor says an independent Managed Security Service Provider audits it every year and that it is penetration tested regularly.
The vendor states that contract data is never shared with or used to train any third party LLM providers. It also says 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. Those statements cover the main risk for a contract lifecycle product, which is customer contract text reaching an outside model provider. Both are limited to third party and public models. Neither says LinkSquares does not use customer contract data to train or tune its own models inside its own platform. Data staying completely private within the platform is consistent with internal training rather than ruling it out. No retention position for AI processed content is published. The vendor's own buyer guide lists zero retention options as something to demand from a vendor, without saying whether this product offers one.
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.
Section 16.5 of the Master Terms and Annexes sets a General Cap equal to fees paid or payable in the twelve months before the first incident. An Enhanced Cap of three times that applies to breaches of its security or data protection terms, meaning the security clause and the data processing addendum. Indemnities, intellectual property claims, breach of confidentiality and anything that cannot legally be limited are uncapped. Section 17.1 gives the customer an indemnity against third party intellectual property claims. Section 8.2 warrants that the service will perform materially as documented, with a thirty day fix period under 8.3 and termination with a refund if the fix fails. Annex A publishes uptime tiers of 99.00, 99.5 and 99.9 percent by support plan. A tier missed in three consecutive months, or in four months out of six, allows termination with a refund. Three limits apply. Breaches of confidentiality involving Customer Data fall outside the uncapped claim, so they stay capped and rise to the Enhanced Cap only where the security or data protection terms are also breached. The agreement gives no indemnity for AI output, such as inaccurate output, hallucination or training data provenance. Section 9.2 bars the customer from submitting Sensitive Data, including GDPR Article 9 categories, and the provider disclaims liability for it. These terms are version 3.0c. Version 4.0, dated 4 January 2026, changes only the trading name, according to the vendor.
LinkSquares publishes no terms page. Its enterprise agreements govern liability and are not public. Nothing published covers liability for AI output, warranties, service levels or remedies when an extraction is wrong, a clause is missed, or an agentic action moves forward a contract that should have been escalated. The vendor says the platform handles the bulk of standard contracts automatically. A missed auto renewal or liability cap in a signed agreement is a loss the customer finds later, and the vendor publishes no position on it.
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.
Leah names its integrations and describes each by function. They cover ERP platforms including SAP and NetSuite, procurement systems including Coupa, financial systems, identity providers including Okta, and existing contract lifecycle tools. DocuSign and Adobe Sign are built in for signing, and a Microsoft Word add in handles redlining. The vendor also describes how the integrations work. It says Leah connects and executes rather than copying data passively, and carries out work across connected systems through the orchestration layer. Leah has a dedicated integrations page, but publishes nothing on what syncs in which direction or what a customer must configure. No document management integration such as iManage or NetDocuments appears, which fits a product built for in house teams rather than law firms.
LinkSquares integrates with Microsoft Word, Google Docs, Microsoft 365, Salesforce, Slack, DocuSign and HubSpot. Drafting runs natively in Word and Google Docs. The vendor says clause libraries and playbooks are available inside the drafting environment, so users do not switch tabs or upload files. The CRM and electronic signature connections cover the path to signature end to end. Independent review material says there is no generally available API for developers, which limits moving contract data into systems the vendor has no connector for. No document management system such as iManage or NetDocuments is named.
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.
The standard deployment is shared. Single tenant deployment is available for customers with strict isolation requirements. The vendor also offers what it calls a dedicated zero trust private environment in Azure OpenAI Studio, described as fully isolating data from all other customers. Leah runs on Azure, with keys held in Azure Key Vault. On data residency the vendor says only that it supports the residency and regulatory needs typical of large multinational enterprises. It names no region or jurisdiction and describes no customer choice.
Independent review material says LinkSquares' data residency and retention controls are mature enough that a public company legal operations lead does not have to negotiate addenda. That is a practitioner's account, not vendor material. No vendor page names a hosting provider, lists regions, states a residency commitment or describes single tenant or private deployment options.
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.
The AI governance page claims SOC 1 Type I and II, SOC 2 Type I and II, GDPR compliance, CCPA compliance, HIPAA readiness and ISO 27001 alignment. The home page FAQ, on the same site, says only that Leah is SOC 2 Type II certified, so the two pages disagree on what is held. For ISO 27001 and HIPAA the governance page says aligned and ready rather than certified. The auditor is described only as an independent Managed Security Service Provider, a category rather than a named firm. No coverage period, report date or audit scope is given. Penetration testing is said to be regular, with no partner named and no summary published. Leah has no trust center or portal, so there is no published route to request a report.
A dedicated security page, open without a login, states SOC 2 Type II and ISO 27001 alongside GDPR compliance and encryption of all contracts and data. Independent review material confirms both certifications and describes them as the two that clear most enterprise procurement checks. The page names no auditing firm for either. It gives no certificate date, examination period or expiry. LinkSquares publishes no trust center or route to request documentation, so there is no stated path to the reports themselves.
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 DPA Setup Page lists four model providers against Leah Functionality, each noted as storing or retaining no customer data and each with named jurisdictions. Anthropic PBC is listed for the USA, Japan, and the EU or UK, and OpenAI LLC for the USA, Japan, and the EU or Switzerland. Cohere Inc. is listed for Canada, the USA, the EU or UK, and Japan. Google AI/ML with Google Cloud is listed for the USA, Japan, and the EU, Switzerland or UK. Microsoft Azure Services is listed for hosting and translation, and the private deployment option runs in Azure OpenAI Studio. DPA clause 4.3 requires any new subprocessor to be added to the published list with at least thirty days' notice before it processes customer personal data. Clause 4.4 gives a thirty day objection right on reasonable data protection grounds. If the objection is not resolved, the affected order can be terminated with a refund of prepaid unused fees. No model or version is named for any provider. The platform is described as choosing among several language models for each task and letting customers extend or customize models. Nothing published shows which provider handled a given piece of work.
LinkSquares commits that contract data is never shared with third party LLM providers, which implies such providers are part of the architecture. It names none of them. It publishes no provider, model family or version and no subprocessor list. Nor does it say what runs on its own infrastructure and what runs on an external model. The product was rebuilt on an agentic architecture, and no published material identifies the models underneath it.
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.
Leah publishes no pricing at any level, including the unit of charge. The primary navigation covers platform, solutions, resources and company, and neither it nor the footer sitemap has a pricing page. There is no tier structure, no unit per seat, contract or agent, no volume banding and no indication of what implementation adds. Every call to action across the site is to request a demo. An implementation FAQ says timelines vary with scope and integrations and that a detailed plan is built during evaluation. It says nothing about cost. No published page gives a view of price before a sales process.
LinkSquares publishes no price, range, tier structure or unit of charge. Its own buyer guidance tells readers to compare user based, usage based and record based pricing models without saying which one LinkSquares uses. A third party estimate puts the median at around $31,000 a year, with a starter tier near $10,000 and enterprise above $75,000. Those figures are independent estimates, not vendor disclosure. If the estimate is accurate, the product is out of reach for small teams.
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.
Leah publishes dedicated industry pages for CPG and manufacturing, energy and utilities, financial services, healthcare, and pharma and medical devices. It describes its customers as Fortune 500 enterprises in regulated industries. By function it publishes pages for legal leadership, legal operations, sales and revenue, procurement, and finance. The pages carry distinct propositions written for the General Counsel, the contract operations team, the Chief Procurement Officer and the finance leader. The customer roster spans banking, airlines, pharmaceuticals, consumer goods and engineering. No published page says which practice areas, contract types or matters the platform does not support, and none addresses smaller organizations. Law firms appear only indirectly, through managed service partners, rather than as a served segment.
LinkSquares describes its coverage by clause and lifecycle scope rather than by jurisdiction. The named terms are payment deadlines, governing law, liability clauses, renewal language and commercial obligations. Batch analysis runs across large legacy portfolios for M&A due diligence and repository audits. The lifecycle runs from before signature to after it in one platform. Users extend beyond legal to sales, procurement, finance, HR and marketing. The vendor states more than 1,200 customers in the in house market. It publishes no list of supported contract types or languages and no indication of extraction depth by agreement type. Governing law extraction is a named capability, but no jurisdictional scope is given for it. Independent review notes there is no primary law research capability, which is typical of the product category.
The 12 legal signals, side by side
Recorded rather than graded. These are the questions a practitioner has to answer before a tool touches a client matter, and the answers are taken from public material only.
Client Data in Training
Can material a lawyer puts into this product be used to train a model?
Leah's security FAQ, on its home page, says customer contract data is never used to train models. The AI governance page treats data leaking into models the customer does not own as a failure it engineered out. It says zero data retention is enforced so that OpenAI and Anthropic process data but never store it. No term in the Master Terms and Annexes v3.0c names training, model training, machine learning or model improvement for customer content, either way.
Two clauses come close. Clause 5.1 limits the provider's use of Customer Data to providing and maintaining the Cloud Service, Support and Professional Services. Clause 5.4 allows use of Usage Data, the provider's technical logs, data and learnings about the customer's use, to run, improve and support the service. Usage Data excludes Customer Data, so the improvement right covers telemetry, not content. Together the clauses fit a ban on training without stating one.
They leave open whether model improvement counts as maintaining the service. The commitment rests on the published policy, not a contract term. Version 4.0 of January 2026 changes only the trading name, according to the vendor.
LinkSquares says contract data and proprietary playbooks are never used to train public AI models. The LinkAI page adds that contract data is never shared with or used to train any third party LLM providers. Both statements are limited to models outside the vendor. Neither says LinkSquares does not use customer contract data to train or tune its own models. The phrase that data stays completely private within the LinkSquares platform is consistent with internal training rather than ruling it out.
The commitment covers the main risk for a contract lifecycle product, which is contract text reaching an outside provider. It appears on product and comparison pages rather than in terms or a data processing agreement.
Prompt and Output Retention
How long does the product keep what a lawyer typed, and can that be set to zero?
Section 14.4 allows export during the subscription and deletion of Customer Data within sixty days of a request after termination. That is subject to standard backup or record retention policies and legal requirements, and the customer cannot change the period. The data processing addendum adds secure deletion to industry standards at clause 8.2, with a certificate of deletion on request. Schedule 1 commits to export in CSV or a similar format within thirty calendar days and to physical destruction of media by a recognized provider.
Prompts and outputs have no separate window. The agreement treats Customer Data as one class, defined at section 23 as any data, content or materials the customer submits, so prompts and outputs follow that regime. Usage Data sits outside it. Section 5.4 lets the provider collect Usage Data, meaning its technical logs, data and learnings about the customer's use, excluding Customer Data. The provider may use it to run, improve and support the service and for other lawful purposes such as benchmarking.
It may disclose Usage Data externally only if deidentified and aggregated across customers. No deletion duty applies to Usage Data, and section 14.5 makes 5.4 survive termination.
The LinkSquares buyer guidance lists zero retention options among the things to expect from an AI contract management vendor, alongside audit trails and PII handling. LinkSquares does not say whether it offers a zero retention option itself. It publishes no default retention period for AI processed contract content or extracted output, and does not say whether the customer can configure one.
Ethical Walls and Matter Segregation
Does retrieval respect the firm’s ethical walls, or can the model read across them?
Leah describes separation at the customer level, through deployment options. The vendor states that single tenant deployment is available for customers with strict data isolation requirements. It says a dedicated zero trust private environment within Azure OpenAI Studio ensures complete isolation from all other customers. Role based access control is stated to be enforced at every layer. That wording makes isolation a deployment option rather than the default, and nothing published describes how customers are separated in the standard shared deployment.
Legal, procurement, finance and shared services teams work in the same system, and nothing published addresses boundaries between them inside a customer.
The platform is sold to legal, sales, procurement, finance, HR and marketing in a single instance that holds the whole contract estate. Nothing published describes what separates legal's own analysis, playbooks and risk notes from the business users in the same system. The vendor's buyer guidance names MFA and SSO among the controls to expect. Independent material says role based access controls are standard across enterprise contract platforms generally.
Neither says what LinkSquares itself implements. No document management system integration exists to inherit permissions from.
Third Party Request and Subpoena Notice
If someone subpoenas the vendor for a firm’s data, does the firm hear about it first?
Section 19, headed Required Disclosures, lets the recipient disclose Confidential Information where the law requires. Where the law permits, the recipient must give advance notice and reasonable cooperation, at the discloser's expense, to obtain confidential treatment. The clause expressly covers Confidential Information including Customer Data. Section 23 confirms that the customer's Confidential Information includes Customer Data, so customer material sits inside the notice duty.
The duty is mutual and binds whichever party receives the demand. Section 14.5 makes section 19 survive termination. Leah publishes no transparency report, so there is no public count of demands received or of how they were answered. These terms are version 3.0c. Version 4.0 of January 2026 changes only the trading name, according to the vendor.
The dedicated security page states SOC 2 Type II, ISO 27001, GDPR compliance and encryption, and does not cover third party requests. LinkSquares publishes no government or law enforcement request clause, no commitment to notify a customer before producing their data and no transparency report.
Primary Law Corpus Provenance
Where does the law in this product come from, and does the vendor have the right to use it?
Leah works on the customer's own material. The vendor states that Leah operates against the customer's policies and playbooks and gains intelligence from the customer's unstructured data and business rules. It answers contract questions from the customer's repository with sources attached. The vendor also refers to Leah operating against established legal precedents, but names no source, jurisdiction, database or rights basis for them.
The product manages a customer's contracts rather than retrieving primary law. No provenance statement backs the precedent reference, and no update cadence is published for anything.
LinkSquares operates on the customer's own executed and draft agreements rather than on published law, so it has no external legal corpus to name, license or date. The vendor does not say what its extraction models were trained on. Extracting governing law, liability and renewal terms across contract types implies a substantial training corpus of agreements. Nothing published says whether that corpus was licensed, synthetic, publicly sourced or built from customer contracts.
The commitment not to train third party models on customer data covers future data flows, not what built the extraction capability.
Good Law Verification
Does the product tell you when the authority it just cited has been overruled?
Leah describes no citator, treatment signal or currency check, and does not say whether legal authority is reviewed for later history. The platform manages contracts, obligations and procurement workflows rather than retrieving case law, so a citator is not part of what it sells. The vendor does refer to Leah operating against established legal precedents, without identifying any source. That is the one place the product invokes primary authority, and no verification step is described for it.
LinkSquares analyzes contracts rather than researching law, and produces no citations to legal authority, so a citator would have nothing to check. Independent review material notes the same boundary. The product has no primary law research on case law, statutes or regulations.
Refusal and Uncertainty Behavior
What does the product do when the answer is not in the corpus?
The home page and the AI governance page describe no explicit path for Leah to decline to answer or abstain, and no confidence or grounding rating. The governance loop does produce rejections. Approvals, escalations and rejections are applied automatically according to the customer's rules. Those are policy outcomes set by configured guardrails, not the model declining because it cannot ground a response. Neither page says what Leah does when the customer's own contract set or playbook does not cover the question in front of it.
LinkSquares publishes no explicit no answer path, abstention behavior or confidence signal for extraction, review or the agentic layer. Its own buyer guidance recommends maintaining review workflows for exceptions, which implies exceptions can be identified. Nothing published says how LinkAI identifies one. It does not say whether a low confidence extraction is flagged, left blank, or filled with a best guess that reads the same as a confident one.
The output is a structured field in a report, so an unflagged wrong value and an unflagged missing value are both invisible to the person relying on it.
Fabricated Citation Record
Does a public court record exist addressing fabricated or hallucinated legal citations in output from this product?
The AI Hallucination Cases database maintained by Damien Charlotin tracks decisions worldwide where a court addressed hallucinated AI content, and records the tool implicated where known. It records no court order, opinion or disciplinary record naming Leah or the former company name ContractPodAi. Published 2026 sanctions trackers and trade press summaries name neither. The platform runs commercial contracting and procurement work rather than producing court filings, so its output does not ordinarily reach a brief.
The AI Hallucination Cases database maintained by Damien Charlotin tracks decisions worldwide where a court addressed hallucinated AI content, and records the tool implicated where known. It records no case naming LinkSquares or LinkAI. Published reporting names neither in a court order, sanction or contract dispute over an extraction error. The product generates no citations to legal authority, so it cannot invent a case. The closer risk is a contract term missed or extracted wrongly that later comes up in a commercial dispute.
Bar Guidance Alignment
Has the vendor engaged in public with the ethics opinions its buyers are bound by?
Leah publishes nothing that engages with bar or ethics guidance. That includes ABA Formal Opinion 512, state bar guidance in the United States, and Solicitors Regulation Authority or Law Society material. The company is headquartered in London and sells into legal departments across North America, Europe, Asia and Australia. Its published compliance material covers regulation and security frameworks, namely GDPR, CCPA, HIPAA, SOC and ISO. None of it addresses the professional conduct obligations that bind the lawyers using the product.
LinkSquares publishes a large library of guidance for in house counsel, covering AI adoption, governance reviews, procurement and change management. The library advises legal departments on how to govern AI adoption. Nothing LinkSquares publishes names an ethics opinion, including ABA Formal Opinion 512, or state bar guidance. Nor does it engage the professional conduct rules those departments' lawyers work under.
Billing and Fee Posture
Does the vendor address what happens to the bill when the work takes an hour instead of six?
Leah frames its public materials around cost and time removed, quantified at portfolio level. It cites a 91 percent cut in contract review time, more than $18 million of revenue protected and more than $2 million of tracked savings. Its headline figures are more than $125 billion of commercial value managed and more than $10 billion of ROI impact delivered. No per matter record of AI assisted work for fee purposes is described, and no guidance on billing, fee or client disclosure treatment is published.
The vendor describes an immutable audit log of every action, which could in principle support such a record, but does not present it for that purpose. Leah sells to in house functions rather than firms billing clients, so the costs in play are internal cost and outside counsel spend. Its materials address neither.
A named customer, Softonic, reports cutting outside counsel costs by 40 percent. Its LinkAI page says customers report a 360 percent return on investment over three years and contract review times cut by up to 400 percent. LinkSquares publishes no position on billing for AI assisted contract work. It describes no record a department could produce showing how much of a review the machine did.
Outside Counsel Guideline Readiness
Can a firm get this vendor through a client’s AI clause without a bespoke negotiation?
The data processing agreement is Annex B of the Master Terms and Annexes v3.0c. The DPA Setup Page lists every subprocessor with its purpose, location and the product it serves. The list names ABBYY OCR SDK, Anthropic PBC, Cohere Inc., DocuSign or Adobe, Google AI/ML and Google Cloud, Jitterbit, Microsoft Azure Services, OpenAI LLC, QlikTech, Sendgrid, ZOHO, Zuva and four ContractPod group entities. Anthropic, OpenAI, Cohere and Google AI/ML are each listed against Leah Functionality as model providers, noted as storing or retaining no Customer Data, with named jurisdictions.
The DPA itself is the Bonterms DPA, published openly in the same PDF and ready to forward. It incorporates EU Standard Contractual Clauses Modules 2 and 3 and the UK International Data Transfer Addendum. It sets out processing details in Schedule 1 and fixes a 48 hour notice period for security incidents. Clause 4.3 commits to listing any new subprocessor and giving at least 30 days' notice before it processes anything.
Clause 4.4 gives an objection right, with termination and a refund if the objection is not resolved. Version 4.0 of January 2026 changes only the trading name, according to the vendor.
The dedicated security page publishes SOC 2 Type II, ISO 27001 and GDPR compliance without a login. LinkSquares publishes no subprocessor list, no named model provider, no data processing agreement, no trust center and no route to request documentation. There is no published path to the underlying reports. Nothing published says which third parties process a customer's contract data, so a department has no way to answer a client who asks.
Court Disclosure Support
If a judge’s standing order requires an AI disclosure, can the product produce one?
The audit stage of Leah's published governance loop logs every decision. Each entry records what the agent did, why, under which policy, with what data and with what outcome. The records are described as tamper resistant, immutable and ready for any audit. That gives the action, the rule, the inputs and the result for each action. The published description of the log does not include the model. The platform chooses among several language models for each task and identifies no model or version, so the log does not show which system produced a given passage.
No export built for court disclosure or AI use certification is described. The audit framing is regulatory and internal rather than judicial.
LinkSquares produces contract analysis and data from signed agreements rather than work filed with a court. A judicial standing order asks for a record of model, sources and human checks, and in this product that record has nothing natural to attach to. Nothing published indicates that the platform records which contract fields were extracted by AI and which were entered by a person. Nor does it say whether a person confirmed an extracted value. A party relying on repository data in a dispute could not show how a given term got into the record.
The questions both sides leave open
Derived from the records above rather than written, so it cannot favor either vendor. Take these into both conversations and ask each side the same question.
- UPL and Professional Responsibility Posture
- Commercial Transparency
- Good Law Verification
- Refusal and Uncertainty Behavior
- Bar Guidance Alignment
Which one fits
Choose Leah if
- You need contract terms and a subprocessor list before you sign. Leah publishes master terms with liability caps and uptime tiers, plus an open data processing agreement. Its subprocessor list names Anthropic, OpenAI, Cohere and Google, with thirty days' notice of changes.
- You want agents with written limits. Leah's customer sets which agents may act, on which data and where escalation is required. Every action is logged with what was done, why and under which policy.
- Your contracts run through ERP and procurement systems. Leah names SAP, NetSuite, Coupa and Okta as integrations. Its procurement and finance agents work in the same platform as its legal ones.
Choose LinkSquares if
- You want to work inside the tools your teams already use. LinkSquares names Word, Google Docs, Salesforce, Slack and HubSpot among its integrations. Clause libraries and playbooks are available inside the drafting environment.
- You need terms pulled out of a large legacy portfolio. LinkAI extracts payment deadlines, governing law, liability clauses and renewal language in batches across old agreements. Teams use it for due diligence and repository audits.
- You want named customers and a result you can check. LinkSquares states more than 1,200 customers and names DraftKings, ProPharma and Asurion. Softonic reports cutting outside counsel costs by 40 percent.
In summary
Leah
Leah, formerly ContractPodAi, is an agentic platform for large enterprises. It covers the contract lifecycle from guided intake and playbook review in Word to approvals, signing and an obligation repository. Its agents handle legal, procurement and finance work under the Leah Maestro orchestrator. The AI Legal Index records a published paper trail. Leah's master terms set liability caps, an intellectual property indemnity and uptime tiers, and its data processing agreement is open. Anthropic, OpenAI, Cohere and Google are named as model providers. Every agent action is logged with its rationale and policy. No price, accuracy measure or region is published.
LinkSquares
LinkSquares sells contract lifecycle management to in house legal teams through two products. Finalize covers drafting, review and approval before signature, and Analyze covers the signed repository with extraction and reporting. Its AI layer, LinkAI, was rebuilt on an agentic architecture in May 2026. It pulls terms such as payment deadlines, governing law and renewal language out of legacy agreements in batches. According to the AI Legal Index, LinkSquares states more than 1,200 customers and names DraftKings, ProPharma and Asurion among them. It states SOC 2 Type II and ISO 27001 on an open security page and says contract data never trains outside models. No terms, model provider or price is published.
Questions buyers ask
Leah vs LinkSquares: which CLM is better for an in house legal team?
LinkSquares is built around the legal department, with drafting in Word and Google Docs, batch extraction across signed agreements and named customers such as DraftKings. Leah is built for a large enterprise that wants legal, procurement and finance agents on one platform, with its contract terms and model providers published. From the AI Legal Index, based on each vendor's own published materials as of October 8, 2026. No vendor pays for placement.
Do Leah and LinkSquares train AI on customer contracts?
LinkSquares says contract data is never shared with or used to train any third party or public model. It does not say whether it trains its own models. Leah says customer contract data is never used to train models, and holds OpenAI and Anthropic to zero retention. Both promises sit on web pages rather than in published terms. From the AI Legal Index, based on each vendor's own published materials as of October 8, 2026. No vendor pays for placement.
How much does LinkSquares cost compared with Leah?
Neither publishes a price or a unit of charge. A third party estimate, not a vendor figure, puts LinkSquares at a median of around $31,000 a year. It ranges from roughly $10,000 for a starter tier to above $75,000 for enterprise. No comparable estimate is recorded for Leah. From the AI Legal Index, based on each vendor's own published materials as of October 8, 2026. No vendor pays for placement.
Which AI models do Leah and LinkSquares use?
Leah names Anthropic, OpenAI, Cohere and Google on its published subprocessor list, each with its jurisdictions, though not model versions. LinkSquares confirms it uses outside model providers by promising not to share contract data with them. It names none and publishes no subprocessor list. From the AI Legal Index, based on each vendor's own published materials as of October 8, 2026. No vendor pays for placement.
What do Leah and LinkSquares both leave unpublished?
Neither publishes an accuracy or error rate for extraction and review, or anything on attorney client privilege. Neither says where its tools stop short of legal advice, though sales, procurement and finance staff use both. Neither names a hosting region for customer contracts. From the AI Legal Index, based on each vendor's own published materials as of October 8, 2026. No vendor pays for placement.
Neither vendor paid for inclusion, placement or a grade, and neither reviewed this page before it published. Everything on it comes from public material on the dates shown. How the index grades.
LinkSquares' training promise covers third party and public models only. It does not say whether customer contracts train or tune LinkSquares' own models, and the promise sits on product pages rather than in terms. Leah's broader promise is also a policy rather than a contract term. LinkSquares' Softonic case study puts the NDA change at five times less time per agreement, which a LinkSquares guide reports as a nearly 400 percent cut. Neither vendor reviewed this page.