Conga CLM vs Lexagle: how they compare in 2026

C
Conga CLM profile
L
Lexagle profile
Last verifiedOctober 16, 2026

Conga CLM is the stronger starting point when contracts must connect with an established revenue process, especially Salesforce or other enterprise business systems. It offers both a Salesforce application and the Conga Advantage Platform, with AiMe supporting review, extraction and proposed redlines. Lexagle centers its pitch on contract collaboration and a rule driven gate before signing, including renewed review after a version changes. Neither should be described as having a blanket prohibition on customer data training. Conga limits customer content training to models for that customer's tenant and prohibits use in shared foundational models; Lexagle reserves broader improvement rights and specific aggregated data uses. Across these provisions, AI Legal Index identifies a more explicit tenant boundary in Conga's training terms. The practical decision is enterprise process integration versus Lexagle's particular compliance routing design.

At a glance

Category
Conga CLMContract Review & Drafting
LexagleContract Review & Drafting
Founded
Conga CLM2006
LexagleNot published
Headquarters
Conga CLMBroomfield, Colorado, United States
LexagleSingapore
Last verified
Conga CLMOct 8, 2026
LexagleOct 16, 2026

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.

Conga CLM
BB on AI CentralityThe models are the engine of a core capability, layered on a product that would still function without them as a document or workflow system.

AiMe is a shared AI layer across the commercial suite. It connects workflow data across CPQ, CLM, price optimization and document automation and suggests next steps, rather than being the CLM itself. Underneath sits a full contract lifecycle platform that long predates it, with template and clause library generation, approval routing, negotiation, electronic signature through Conga Sign, a searchable repository, obligation and renewal tracking, and reporting. The models drive core features on top of that platform. Without AiMe a working CLM remains, as the edition built on Salesforce was for years. Recent releases push AI further in. The June 2026 release extends AI across the platform, including bulk import and extraction for incoming contracts. The March 2026 AiMe release adds agents that act inside quoting and contracting workflows. Conga still sells and prices the platform as a contract system with intelligence on top.

Lexagle
BB on AI CentralityThe models are the engine of a core capability, layered on a product that would still function without them as a document or workflow system.

Lexagle combines a conventional contract workspace with Lexie and Document Guard. Lexie drafts from approved templates, proposes clauses, extracts metadata and answers questions about agreements. Document Guard inspects clauses against a company's playbook and uses the result to permit signing, route a partial match to a person or block an unacceptable contract. It also requires another review when a protected version changes. These functions make AI part of the contract approval process, beyond a separate writing assistant. Templates, collaboration rooms, signatures and the repository still have value without those models, so the wider platform does not depend entirely on AI.

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.

Conga CLM
BB on Citation Accuracy and Hallucination DisclosureGrounding is real and documented, with linked primary sources and a described retrieval method, short of published accuracy figures an outsider can test.

The AI pipeline divides document processing among specialized providers. Google Cloud Vision handles optical character recognition, Amazon Textract table detection, Zuva provision extraction and Azure OpenAI language processing. Output is grounded in the customer's own repository, playbook and clause library, and extraction needs no model training by the customer. AiMe shows how every recommendation is generated, with the reasoning visible and confidence scores wherever it makes a suggestion. The Artificial Intelligence Addendum addresses accuracy only through a disclaimer. It states that outputs may be inaccurate, incomplete or misleading and disclaims any warranty of accuracy or completeness. No accuracy figure, test set, error rate or benchmark result is available. Third party models undergo benchmarking before release, without disclosed results. The product cites no legal authority, so grounding in authority and citator checks do not apply.

Lexagle
CC on Citation Accuracy and Hallucination DisclosureAccuracy is asserted without measurement, or grounding is claimed while output cites sources the reader cannot open and verify.

Document Guard compares agreement language with customer rules, highlights risky provisions and explains why a clause was flagged. The user can inspect the contract and the applicable playbook. Lexie also answers questions using the organization's contracts and institutional information. Lexagle promises consistent assessments through low temperature settings and fixed response parameters, but does not provide a reproducible accuracy test, error breakdown or hallucination rate. A claim of complete playbook alignment is not accompanied by test conditions. The material does not establish that every generated answer carries a link to its supporting passage or that suggested legal language has been independently validated.

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.

Conga CLM
AA on Autonomy and Oversight ModelWhat the system runs alone, what constrains it, and how a lawyer checks it are all published: modes, thresholds, review surfaces, and the route a matter takes back to human judgment. A categorical limit on a named mode or tier, stating what its output may not be used for, meets the threshold limb without a number.

Conga states that AiMe never acts autonomously on high stakes decisions. Three mechanisms constrain it, agent guardrails, approval thresholds and human in the loop confirmation, and each can be built into a workflow. AiMe shows how every recommendation is generated and the reasoning behind AI driven actions. Confidence scores appear wherever it makes a suggestion, users accept or reject redlines, and every action and approval is kept in an audit trail. Much of the oversight model is written into the contract. The Artificial Intelligence Addendum makes the customer solely responsible for evaluating and validating outputs. It says the customer must not rely on AI outputs as the sole basis for any decision with legal, financial, regulatory or other material impact. It also requires human review and independent judgment, and puts authorizing and supervising agent actions on the customer. The guardrails and thresholds are described as configurable rather than as defaults, and the same document states that Conga does not monitor or review AI generated outputs.

Lexagle
AA on Autonomy and Oversight ModelWhat the system runs alone, what constrains it, and how a lawyer checks it are all published: modes, thresholds, review surfaces, and the route a matter takes back to human judgment. A categorical limit on a named mode or tier, stating what its output may not be used for, meets the threshold limb without a number.

Document Guard has an explicit three state control scheme. A compliant agreement can proceed directly to signing, a partially compliant agreement is diverted for human review, and a noncompliant agreement is blocked or escalated. Legal teams define the rules in plain English, including payment, liability and jurisdiction requirements. Routing is driven by AI extracted information rather than a person selecting every action. A digital seal ties the compliance result to a particular version; external edits or a replacement upload trigger lockdown and another AI evaluation. This explains both the permitted unattended action and the circumstances requiring intervention, although it does not establish error rates.

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.

Conga CLM
BB on Operational and Outcome EvidenceReal deployment evidence with substance, short of full attribution or measurement: a named customer without figures, or figures without the named customer.

Cotality, formerly CoreLogic, describes improving client service with Conga CLM in a September 2024 customer story without a quantified outcome. Two other dated stories, DigiKey on price management and Kalixia at 160 times faster document generation, concern other Conga products. Other named customers include Southwest Airlines, LinkedIn, AXA, Peloton, Cotality, T-Mobile, Adobe, Box and Kraft Heinz. The headline improvement figures are separate from those named customers. A 9 percent revenue increase appears beside the logo strip with no stated basis, and Conga claims 50 percent less review time with AI. Conga also cites G2 Leader recognition across five grids.

Lexagle
BB on Operational and Outcome EvidenceReal deployment evidence with substance, short of full attribution or measurement: a named customer without figures, or figures without the named customer.

Yamaha Motor Philippines is a named customer describing improved contract visibility, approvals and signing. Lexagle also describes deployments for a global financial institution, a property developer and a state lottery, but those organizations are unnamed. Its promotional results include shorter contract cycles, reduced administrative work and a high satisfaction percentage. Those figures do not share a published sampling method or an independently reproducible baseline. The Document Guard testimonials identify job titles and sectors without customer names. There is therefore support for operational use of the broader platform, while the measured accuracy and incremental benefit of its current AI gatekeeper remain uncertain.

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.

Conga CLM
BB on Privilege and Confidentiality PostureSubstantive published commitments on confidentiality and training use, short of the full picture: commonly silence on segregation between users or matters, or on what the underlying model provider may retain.

Under the Artificial Intelligence Addendum, Conga will not use AI Inputs or AI Outputs to train or improve any model beyond a limited license to provide, maintain or improve the Services for that customer. Customer Data will not train global or foundational models serving multiple customers, and no third party may use Customer Data or AI Output to train, fine tune, validate, test or develop any model. Tenants are logically separated with dedicated encryption keys. The Data Processing Addendum limits retention to the time absolutely necessary and requires return and deletion at the customer's election after the agreement ends. Prompts, completions, embeddings and training data sent to Azure OpenAI are not available to OpenAI and are not used to improve OpenAI, Microsoft or third party products. Each document processing provider works under a zero retention arrangement. Conga sells the product to legal departments to hold their agreements, and its addenda, trust center and product pages do not address attorney client privilege or work product. Separate contractual conditions sit in Conga's Master Services Agreement.

Lexagle
BB on Privilege and Confidentiality PostureSubstantive published commitments on confidentiality and training use, short of the full picture: commonly silence on segregation between users or matters, or on what the underlying model provider may retain.

Lexagle describes separate customer datastores, application controls that prevent access across customers and tests that block a release if separation fails. Administrators can assign permissions for individual platform components, and internal collaboration rooms separate private discussion from counterparty work. Its displayed service terms also impose confidentiality obligations, but permit analysis of customer information to improve services and expressly allow certain aggregated or nonidentifying data to train machine learning. That permission matters for confidential contracts even when natural persons cannot be identified. No attorney client privilege preservation undertaking or detailed explanation of how legal matter restrictions apply to AI answers is provided.

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.

Conga CLM
BB on UPL and Professional Responsibility PostureA real position is published on advice versus tooling, short of full treatment: commonly a disclaimer without the supervision and competence dimension, or silence on jurisdiction limits.

Conga's position on advice versus tooling sits in the Artificial Intelligence Addendum. The Addendum states that AI generated outputs may be inaccurate, incomplete or misleading, disclaims any warranty of fitness, and makes the customer solely responsible for validating outputs before use. It says the customer must not rely on AI outputs as the sole basis for any decision with legal, financial, regulatory or other material impact, and that human review and independent judgment should be exercised. It applies the same rule to agents, making the customer responsible for deciding whether agent actions are appropriate and for authorizing and supervising them. Legal, sales and procurement teams use the application as a contracting tool. The service does not specify how a supervising lawyer meets competence or oversight duties over AI drafted contract language. Capability restrictions by buyer group and jurisdictional limits are not specified. The product is marketed to sales and procurement users who generate contract positions in the same tenant as legal.

Lexagle
BB on UPL and Professional Responsibility PostureA real position is published on advice versus tooling, short of full treatment: commonly a disclaimer without the supervision and competence dimension, or silence on jurisdiction limits.

The service terms expressly state that Lexagle is not a law firm, does not provide legal advice and does not create a lawyer client relationship. They also state that it carries no professional indemnity insurance and leave legal suitability and conclusions with the customer. Document Guard can apply a legal team's playbook, but passing its rules does not establish the legal effect of an agreement. The product is promoted to law firm partners and associates as well as corporate teams, while the displayed terms restrict third party service provision. That unresolved scope difference matters before using it for external client work.

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.

Conga CLM
BB on AI Governance and Bias DisclosureA published governance framework with real substance, short of testing results or a named owner.

Conga's AI governance framework sits in the Artificial Intelligence Addendum rather than on a principles page. The Addendum records a cross functional AI Governance Committee responsible for oversight of AI within the Services. The committee focuses on risk management, accountability and compliance, and periodically reviews AI risks, controls and mitigations. Conga commits to internal policies on responsible AI covering oversight of training data, bias mitigation and human interpretability, to staff training, and to full cooperation with a customer's own AI impact assessments. Governance is tied to the NIST AI Risk Management Framework and its four functions, Govern, Map, Measure and Manage. The vendor classifies its products as minimal or limited risk AI systems under the EU AI Act. It states that third party models are tested, audited for bias and benchmarked before release, with rollback to any prior model version within hours. Results from that testing, bias audit findings, evaluation outputs and model cards are not available, including performance differences across contract types.

Lexagle
DD on AI Governance and Bias DisclosureNo governance position published for a system whose output affects legal outcomes.

Lexagle describes client defined rules, low temperature model settings and automated checks on software access controls. These explain parts of application behavior, but not a company program for governing AI development and release. There is no named AI risk owner, published bias evaluation, testing across languages or report of recurring model failures and corrective action. The platform's regional compliance claims and security certifications address other responsibilities. Legal teams can control the standards used to approve their own contracts, yet the vendor does not explain how it assesses systematic errors in the underlying models or decides when a changed model is ready for use.

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.

Conga CLM
AA on AI Safety and Data StewardshipRetention, deletion, access control, subprocessors and incident practice are all published, current, and specific enough to hold the vendor to.

The Data Processing Addendum says retention of personal data should generally not be required and is limited to the time absolutely necessary to perform the Services. Daily backups are kept for thirty days, and each third party document processing provider works under a stated zero retention arrangement. Data is returned or deleted at the customer's election within a reasonable period after the agreement ends, and the CCPA attachment requires prompt compliance with deletion requests. Access controls include role based authorization, least privilege, quarterly access reviews, multifactor authentication, encryption at rest, TLS of 256 bits or stronger in transit, and per tenant encryption keys. The subprocessor terms provide fifteen days' notice before additions, a right to object with termination and refund, and Conga's responsibility for provider acts. Incident notice comes within 48 hours of Conga becoming aware, backed by a response plan with root cause analysis and a 24/7 security team.

Lexagle
BB on AI Safety and Data StewardshipSubstantive published policy covering most of the ground, short of the full set: commonly no named subprocessor list or no stated incident practice.

The security policy describes encryption in storage and transit, isolated customer datastores, component permissions and an incident process with prompt written notice once a breach affecting customer data is verified. The privacy notice names several service providers and describes retention for account operation, legal requirements and other stated purposes. It promises deletion or anonymization once information is no longer needed, without a complete schedule for contract content, AI prompts, outputs and backups. The service terms separately permit some improvement and machine learning uses after the subscription ends. This provides several concrete controls, while leaving the full AI data lifecycle and model processor arrangements incomplete.

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.

Conga CLM
CC on AI Liability and RecourseLiability is addressed only through a standard limitation clause that disclaims the exposure the product creates.

The Artificial Intelligence Addendum states that Conga makes no warranty, express or implied, on the accuracy, completeness, noninfringement or fitness for purpose of AI generated output. The customer is solely responsible for evaluating and validating that output. To the maximum extent permitted by law, Conga is not liable for any losses, damages or claims arising from the customer's use of or reliance on AI output or on actions by agentic AI features. That includes third party claims. One allocation runs the other way. The Data Processing Addendum makes Conga liable for its subprocessors' acts and omissions as if it had performed the services itself, and much of the AI pipeline sits with those third parties. The addenda do not state a general liability cap, an indemnity scope or an insurance position. Conga's Master Services Agreement is a separate document.

Lexagle
BB on AI Liability and RecourseA real published position on liability, short of the full picture: commonly a stated indemnity without scope or caps.

Lexagle undertakes to defend customers against specified infringement claims concerning the service, including Singapore patent, copyright, trademark, database and confidentiality rights. That is an ordinary service indemnity, with procedural conditions and an exclusive remedy provision; it does not expressly cover fabricated legal analysis or defective AI drafting. The displayed terms disclaim legal suitability and accuracy, assign responsibility for conclusions to the customer and exclude consequential losses. They also state that Lexagle has no professional indemnity insurance. The combination provides some recourse for a defined class of service claims, without an affirmative warranty or specific remedy for an AI generated clause that causes loss.

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.

Conga CLM
BB on Practice Systems Integration DepthReal integrations exist and are documented, short of depth: named connections without a description of what they actually move.

Several of Conga CLM's integrations are structural. One edition runs natively on Salesforce and is listed on the Salesforce AppExchange. Authoring and review run inside Microsoft Word and Google Docs, and Microsoft Dynamics is named on the product page. The platform edition supports connections to CRM, ERP and procurement systems. Within Conga's own products, pricing, terms and configurations flow from CPQ into a contract. Documents are generated through Composer and signed through Conga Sign, and price optimization feeds contract pricing. Developer resources cover APIs and integrations. Field mapping and sync directions for individual external connectors are not specified alongside the broader connections.

Lexagle
BB on Practice Systems Integration DepthReal integrations exist and are documented, short of depth: named connections without a description of what they actually move.

Lexagle supports single sign on through Microsoft Azure and offers APIs for connecting contract information with existing business systems. Its service terms describe optional transfers of completed contracts to Google Drive and individual PDF downloads. Collaboration rooms keep internal discussion separate from external negotiation, while the repository supplies contract data for reminders and other workflows. The vendor also describes Oracle connectivity and transfers to ERP systems. These are identifiable connection and transfer functions, although the published material does not provide a complete implementation account covering field mappings, permission inheritance, synchronization failures and conflict handling across those systems. Custom integration scope is settled during the commercial discussion.

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.

Conga CLM
BB on Deployment Model and Data ResidencyDeployment model is stated clearly with partial residency detail, or residency is offered without the processing location being addressed, or the tenancy model is stated on its own with no residency detail published.

The CLM has two delivery forms. One is the original application built on Salesforce. The other is a software as a service edition on the Conga Advantage Platform that gives buyers a CLM interface independent of Salesforce. The Data Processing Addendum treats them differently. It states that Conga does not back up customer data for services hosted on Salesforce and sets no recovery point objective for them. Elsewhere it keeps daily backups for thirty days, with a one hour recovery point objective and a twenty four hour recovery time objective. Infrastructure is named as Salesforce, Amazon Web Services and Azure, with data on servers managed by Salesforce and AWS. Each logical tenant boundary has its own encryption key. Availability is described as spanning the United States, the European Union and Asia Pacific with residency options included, which names continents rather than regions. A region list, the method of choosing a tenant's region and separate processing locations are not specified. Content reaches Azure OpenAI, Google Cloud Vision, Amazon Textract and Zuva, and the processing locations are not specified.

Lexagle
BB on Deployment Model and Data ResidencyDeployment model is stated clearly with partial residency detail, or residency is offered without the processing location being addressed, or the tenancy model is stated on its own with no residency detail published.

Lexagle's security policy places its hosted service and customer data on AWS in Singapore. The displayed service terms nevertheless allow personal data to be transferred or stored outside Singapore, and the privacy notice also contemplates processing at partner facilities. A newer product article describes Lexie processing as resident with the client, with no client data sent to Lexagle servers or third parties. It does not explain how that arrangement relates to the hosted platform or which product configurations receive it. Customers therefore have several location statements, but no single published architecture that resolves storage, inference, remote access and the available deployment choices.

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.

Conga CLM
BB on Security Certifications and Trust CenterCertification is real and stated, short of accessible evidence: a named standard without scope, date, or a way to obtain the report.

SOC 2 Type II covers the full platform under annual audits, according to Conga. The trust center also lists ISO 27001, ISO 27701 as its privacy extension, PCI DSS, HIPAA Security with annual audits, GDPR and CCPA. It adds alignment to the NIST AI Risk Management Framework and certification under the EU-U.S. Data Privacy Framework. The Data Processing Addendum links that certification to the Department of Commerce register. The security program includes annual third party penetration testing, application vulnerability assessment twice a year, continuous automated threat hunting and code analysis before release. It also covers a patching service level by severity, background checks, annual security training and a vulnerability disclosure program. Auditor names, report periods, observation windows and certificate numbers are not available alongside those claims, and reports require a request. The Data Processing Addendum makes reports available on a customer's request under confidentiality, so a prospective buyer cannot read the audit scope before signing.

Lexagle
BB on Security Certifications and Trust CenterCertification is real and stated, short of accessible evidence: a named standard without scope, date, or a way to obtain the report.

Lexagle names ISO 27001:2022, SOC 2 Type I and Type II, and CSA STAR Level 2 among its security credentials. Its security policy adds details about encryption, deployment tests, access controls, incident response and AWS hosting. Those statements are more specific than a generic promise of secure contracts. The public materials do not supply the audit period, named assessor or complete reports establishing which services and AI components were covered. Separate claims of alignment with other industry and regulatory frameworks should not be treated as additional certifications. The credentials concern information security controls rather than the legal accuracy of generated contract language.

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.

Conga CLM
BB on Model Supply Chain DisclosureThe supply chain is partly disclosed: providers named without change notification, or architecture described without the providers.

Generative features run on Microsoft Azure OpenAI. The document processing agents also use Google Cloud Vision for optical character recognition, Amazon Textract for table detection and Zuva for provision extraction, each under a stated zero retention arrangement. The Azure OpenAI Service is described as fully controlled by Microsoft, hosted in Microsoft's own Azure environment and not interacting with any system operated by OpenAI. Prompts, completions, embeddings and training data are tokenized in transit, are not available to OpenAI, and are not used to improve OpenAI, Microsoft or third party models. Change notice is contractual. The AI providers are subprocessors, and the Data Processing Addendum gives fifteen days' notice before a new one is appointed, with its name, location and activity. It also gives a right to object, and termination with a refund if no workaround exists. No specific model is named. The Addendum refers to Azure OpenAI GPT, which is a family rather than a version, and nothing states which model writes a summary or a redline or when that changes.

Lexagle
CC on Model Supply Chain DisclosureThe vendor refers to advanced or proprietary models without identifying what sits underneath.

Lexie is described as Lexagle's proprietary legal AI engine, trained on client specific contracts, approval knowledge and other institutional information. Document Guard adds low temperature settings, fixed response parameters and customer playbook context. These details identify the intended behavior and some training inputs, but not a foundation model family, inference provider or complete chain of model subprocessors. AWS hosting alone does not establish which model performs a review. There is also no published procedure for notifying customers before a model supplier or model version changes. The branded engine name consequently offers limited visibility into the technology handling confidential legal content.

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.

Conga CLM
DD on Commercial TransparencyNo pricing information published at any level, including the unit of charge.

Conga CLM uses custom quotes without a numeric starting rate, a defined billing unit or a plan table. The application combines drafting, negotiation, approvals, electronic signature, contract storage and obligation management, with AI review and extraction inside that workflow. Additional products connect CPQ, document generation and signing to the wider suite. An advanced CLM feature set includes clause libraries, version control and redlining, but its incremental charge is not specified. Subscription duration, renewal provisions, price increase limits and implementation fees are not given with the quote request. The Master Services Agreement is separate from the AI and data processing addenda.

Lexagle
CC on Commercial TransparencyPricing is gated behind a demo request while tier names and feature splits are published, so the shape is visible and the number is not.

Lexagle prices a selected combination of modules after a discussion of business workflows, localization needs and implementation scale. Its menu includes contract management, signing, document management, vendor management and intellectual property management. The resulting package is customized, with no published entry amount, standard user allowance, contract volume unit or AI consumption rate. The acceptable use policy allows extra charges or restricted capacity for excessive usage, but supplies no numerical boundary. Implementation fees and a separate price for Document Guard are also unspecified. A proposal must therefore establish both the functional scope and the cost of growth before a buyer can estimate ongoing spend.

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.

Conga CLM
BB on Firm and Practice CoverageSegment and practice coverage is described with substance, short of the boundaries: what is supported is clear, what is not is left open.

Legal, procurement, sales, finance, IT, business operations and pricing teams use the suite. Their CLM tasks differ. Legal gets workflow, authoring, AI review and redlining, compliance and risk management. Procurement gets obligation management, AI extracted terms and pricing. Sales gets generation, AI assisted negotiation and renewals. Industry uses cover technology, financial services, healthcare, life sciences, manufacturing, transport and logistics, and distribution. Named customers span airlines, insurance, media, retail and property data. No practice area inside a legal department is named as supported or unsupported, and nothing states what the product is not for. Capability restrictions for users who are not lawyers are not specified inside a shared tenant. Jurisdiction and language coverage boundaries are also unspecified, although the product is localized into German and French.

Lexagle
BB on Firm and Practice CoverageSegment and practice coverage is described with substance, short of the boundaries: what is supported is clear, what is not is left open.

Lexagle serves legal, sales, procurement and HR teams, with industry examples in banking, telecommunications, manufacturing, property and other sectors. Its headquarters and regional focus are in Singapore, and it describes customers across Asia Pacific and other markets. Document Guard is also promoted to law firm partners, associates, legal operations and compliance professionals. Malaysian contract and digital signature laws receive explicit attention in the product explanation. Broader claims of multilingual and jurisdictional adaptability do not include a tested coverage matrix or exclusions for particular legal tasks. The displayed restriction on providing services to third parties also needs reconciliation with the law firm audience.

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?

Conga CLM
Permitted, in the contract

The Artificial Intelligence Addendum expressly permits training on customer content, within written limits. Section (c) says Conga will not use Customer Data to train global or foundational models that serve multiple customers. Any training on Customer Data is limited to models specific to the customer's instance or tenant. Permitted training is limited to the customer's own data and a model only that customer uses, and neither the Addendum nor the trust center describes an opt out.

Conga does not use Customer Data to train third party foundational models, naming Azure OpenAI GPT as the example. Section (d) says Conga will not let any third party use Customer Data or AI Output to train, fine tune, validate, test or otherwise develop any AI model. Section (b) says that, beyond a limited license to provide, maintain or improve the Services for that customer, Conga will not use AI Inputs or AI Outputs to train or improve any model.

The trust center adds that models trained on one customer's data are never used for another. One carve out is reserved. Service Attributes, defined as anonymized and aggregated usage information, may be used to train and refine models and are stated not to be Customer Data.

Lexagle
Permitted, in the contract

The displayed service terms permit analysis of customer information to improve Lexagle offerings during and after the subscription. They expressly allow use or disclosure in aggregate form, or another form that does not identify a natural person, including training machine learning algorithms. A separate confidentiality clause permits customer insights to improve services for other customers. This is a contractual permission with stated limits, rather than an assurance that confidential agreement content is excluded from all model development.

Prompt and Output Retention

How long does the product keep what a lawyer typed, and can that be set to zero?

Conga CLM
Customer controlled, no zero option

The Data Processing Addendum lets the customer control retention by contractual instruction. Attachment A sets the default. Retention of personal data should generally not be required, and any retention is limited to the time absolutely necessary to perform the Services. Section 9.6 requires return and deletion at the customer's election within a reasonable period after the agreement ends, with the customer deleting within the Services and Conga helping where it cannot.

The CCPA attachment adds a duty to follow any customer deletion instruction promptly. Daily backups are kept for thirty days, except for services hosted on Salesforce, which Conga does not back up. At the model layer, Conga states a zero retention policy with each third party document processing provider. Documents sent to Azure OpenAI, Google Cloud Vision, Amazon Textract and Zuva are therefore processed in real time and not stored. No zero retention setting is offered to the customer inside the Services.

Lexagle
Disclosed without a period

Lexagle retains personal information for the account relationship and other stated legal or operational needs, then deletes or anonymizes it when no longer required. The service terms preserve some analysis and improvement rights after termination. Neither statement supplies a complete retention timetable for prompts, generated clauses, model logs or backup copies. The separate claim of client resident AI processing does not establish a default zero retention setting for the hosted contract repository or its supporting systems.

Ethical Walls and Matter Segregation

Does retrieval respect the firm’s ethical walls, or can the model read across them?

Conga CLM
Own model, documented

Conga CLM has its own permission model, which the customer administers. Between customers, separation is built into the architecture. Tenant environments are logically separated, each with its own encryption keys, and models trained on one customer's data are never used for another customer's recommendations or scores. Inside a tenant, the Data Processing Addendum's security attachment requires role based authorization, least privilege, quarterly access reviews, multifactor authentication and the customer's ability to limit access to authorized personnel.

Rules based access controls, audit logs and admin tools help the customer configure and manage AiMe, which leaves the alignment work with the customer. The product does not apply an outside document management system's access model at query time. The addenda and trust center do not address segregation between matters or business units inside one tenant. The platform is sold to legal, procurement, sales, finance and IT in the same instance, and the assistant answers questions across the whole contract repository.

Lexagle
Own model, documented

Customer information sits in separate datastores, with application controls intended to prevent one customer accessing another's data. Lexagle describes tests of that separation that run on each code update and prevent release on failure. Administrators can set permissions for individual components, and internal rooms separate private collaboration from counterparties. These are described tenant and workspace controls.

They do not establish a complete ethical wall model within a law firm or prove that every AI response inherits exclusions for a particular client matter.

Third Party Request and Subpoena Notice

If someone subpoenas the vendor for a firm’s data, does the firm hear about it first?

Conga CLM
Notice committed

Section 4 of the Data Processing Addendum's security attachment is headed Disclosure by Law. If Conga is required by law to disclose customer data, it will notify the customer as soon as practical where the law permits. It will also take all steps to give the customer an opportunity to prevent or limit the disclosure, an obligation to help and not only to inform. The CCPA attachment adds a slightly stronger commitment for personal information.

For a legally required disclosure unrelated to the contracted business purpose, Conga must first tell the customer and give it a chance to object or challenge the requirement, unless the law prohibits notice. Conga will also redirect a misdirected data subject request to the customer and will not respond without the customer's prior written consent unless legally required. No transparency report, aggregate demand count or reporting cadence is available.

Lexagle
Disclosure addressed, notice absent

The privacy notice permits disclosure to courts, regulators and other authorities where required, and the displayed confidentiality terms make an exception for legally required disclosure. Neither gives the affected customer a specific advance notification commitment or a process for contesting a demand. Security breach notices concern a different event and cannot substitute for notice of compelled access. There is also no recurring report of government requests that would explain how such demands have been handled.

Primary Law Corpus Provenance

Where does the law in this product come from, and does the vendor have the right to use it?

Conga CLM
Sources named, basis unstated

Conga CLM works from the customer's own material. That means contracts imported in bulk, including third party, legacy and acquired agreements, plus the customer's clause library, negotiation playbook and approved templates. The vendor states that precise models are built from the customer's own documents without the customer having to train them. The generative layer is named too. Azure OpenAI handles language processing, with Google Cloud Vision, Amazon Textract and Zuva for optical character recognition, table detection and provision extraction.

Conga states no rights basis for any of these sources and does not describe what the underlying foundation models were trained on. Zuva's extraction models are trained on contract collections rather than on the customer's documents, and they are named without any account of what sits behind them. On the customer's side, the Artificial Intelligence Addendum leaves the customer with all right, title and interest in its AI Inputs and AI Outputs and grants Conga only a limited license.

Lexagle
Jurisdictions only

Document Guard describes training on principles of the Malaysian Contracts Act 1950 and refers to Malaysian digital signature requirements. Lexie also uses customer contracts and institutional approval knowledge. The product does not enumerate a licensed collection of statutes, cases or commentary behind its legal suggestions, nor explain how external legal material is updated. Naming a jurisdiction and selected legislation gives some geographic context without establishing the provenance or usage rights for the full legal knowledge used by the models.

Good Law Verification

Does the product tell you when the authority it just cited has been overruled?

Conga CLM
Not addressed

The product cites no cases, statutes or regulations, so checking authority for later history does not arise in its usual form. It works on the customer's own agreements, comparing drafts to a negotiation playbook, matching against an approved clause library, extracting obligations and dates, summarizing, and answering questions about the repository. Nothing it produces is a statement about the law that a lawyer would check for later treatment.

The nearest point is obligation and renewal tracking, where the question is whether a contractual date or duty is still live, and alerts and dashboards handle that. No feature checks legal authority for subsequent history.

Lexagle
Not addressed

Lexagle's review process measures contract language against organizational rules and highlights deviations. It does not identify a licensed citator, a judicial treatment database or an equivalent mechanism for determining whether a cited legal authority remains reliable. The reference to Malaysian contract law is not a treatment history service. A green compliance result therefore concerns the supplied playbook and workflow, while the continuing validity of the legal assumptions behind that playbook remains a separate responsibility.

Refusal and Uncertainty Behavior

What does the product do when the answer is not in the corpus?

Conga CLM
Confidence signal only

Conga commits that AiMe shows how every recommendation is generated, that users see the reasoning behind AI driven actions, and that confidence scores appear wherever AiMe makes a suggestion. That gives a reviewer a signal for each suggestion. Conga does not describe what the system does when it cannot ground an answer. An explicit refusal response or unsupported extraction marker is not specified. Nor does it say what happens when a clause cannot be matched to the playbook or a question cannot be answered from the repository.

No evaluation results for that behavior are available. The Artificial Intelligence Addendum allocates the consequences instead. It says outputs may be inaccurate, incomplete or misleading, makes the customer solely responsible for validating them, and states that Conga does not monitor or review AI generated outputs. The precise behavior of the guardrails is not specified.

Lexagle
Not addressed

Amber and red outcomes divert or block agreements that fail customer rules. They are defined compliance states, rather than an explanation of how Lexie responds when it lacks enough information to answer a legal question. No refusal policy describes unsupported jurisdictions, conflicting authorities or uncertain interpretation, and no published confidence measure supplies a defined response to those problems. Low temperature settings may limit variation in responses, but they do not by themselves show when the system will decline to answer.

Fabricated Citation Record

Does a public court record exist addressing fabricated or hallucinated legal citations in output from this product?

Conga CLM
None located

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 Conga CLM or Conga. Two independent sanctions trackers of decisions on AI generated fabricated citations do not name them either. Conga CLM works on contracts and cites no legal authority, so its output does not ordinarily reach a court filing.

Lexagle
None located

The October 16, 2026 review of the Charlotin database found no Lexagle entry in the AI tool field or elsewhere in the case information. Lexagle's primary workflow concerns private contract review and approval rather than generation of court submissions, which may affect the visibility of an incident in a litigation database. This absence does not establish a hallucination rate or rule out unsupported legal assertions in suggested clauses, explanations or answers about agreements.

Bar Guidance Alignment

Has the vendor engaged in public with the ethics opinions its buyers are bound by?

Conga CLM
Not addressed

No bar or ethics guidance is named for the service. ABA Formal Opinion 512 does not appear, no state guidance on generative AI in legal practice is referenced, and nothing maps a capability to a jurisdiction's rules of professional conduct. Conga does cite outside frameworks, but none of them is professional responsibility guidance. The Artificial Intelligence Addendum ties governance to the NIST AI Risk Management Framework, and the trust center classifies the products as minimal or limited risk AI systems under the EU AI Act.

Both are addressed to the vendor as an AI provider. The nearest thing to a professional responsibility statement is the Addendum's requirement that the customer not rely on AI outputs as the sole basis for a decision with legal impact. It also requires the customer to exercise independent judgment. It names no guidance.

Lexagle
Not addressed

Lexagle expressly distinguishes its software from legal advice and assigns responsibility for conclusions to customers. Its regional materials discuss contract, signature and data protection requirements, but do not map AI features to a named bar opinion or professional conduct framework. Approval routing and private collaboration rooms may assist a lawyer's working practices. The vendor does not explain how those controls satisfy jurisdiction specific duties of competence, client communication, confidentiality and supervision when using generative AI.

Billing and Fee Posture

Does the vendor address what happens to the bill when the work takes an hour instead of six?

Conga CLM
Outside the fee relationship

The product serves corporate teams managing their own commercial agreements. The named audiences are in house functions, legal, procurement, sales, finance, IT and business operations, each with its own page. The named customers are corporate, among them an airline, an insurer, a property data business, a consumer fitness company and a professional network. Nothing is addressed to a law firm billing a client. Conga's efficiency claims include a 9 percent revenue increase, 50 percent less review time with AI, faster deal cycles and lower supplier costs.

All of them concern the buyer's own cost, cycle time or revenue, and none reaches a client bill. The platform also runs quoting, pricing and billing, but that is the customer billing its own customers rather than a lawyer billing a client. No client fee disclosure workflow for AI assistance is specified.

Lexagle
Savings claims only

Document Guard is promoted to law firm partners and associates for faster due diligence and routine review. Lexagle also advertises reduced administrative work and shorter contract cycles across its wider customer base. It does not provide a client fee allocation method, a billing disclosure template or a record of how time saved by AI changes the charge to a legal client. Those efficiency claims therefore remain separate from the lawyer's professional responsibility for the fee ultimately billed.

Outside Counsel Guideline Readiness

Can a firm get this vendor through a client’s AI clause without a bespoke negotiation?

Conga CLM
Disclosure pack published

Customer counsel can use the AI and data processing addenda to address a counterparty's AI clause. Conga's trust center names Google Cloud Vision for optical character recognition, Amazon Textract for table detection, Zuva for provision extraction and Azure OpenAI for language processing. It states a zero retention arrangement with each and explains what Azure OpenAI does and does not do with prompts and completions.

The subprocessor register identifies the supporting services. The Data Processing Addendum applies Clause 9(a) Option 2 of the Standard Contractual Clauses to that list, with fifteen days' notice, a right to object and termination with a refund. The Data Processing Addendum includes the standard contractual clauses and their UK and Swiss adaptations, alongside the separate Artificial Intelligence Addendum.

Lexagle
Subprocessors listed

The privacy notice names several service providers, including Heap, FullStory, Google analytics services, Intercom and SendGrid, and the security policy identifies AWS hosting. That gives part of the supplier information needed for a client approval discussion. It does not identify the complete model supply chain or provide a prepared outside counsel AI disclosure package. A legal team would still need the applicable contract, processing configuration and client specific restrictions to assess whether a proposed matter can use the service.

Court Disclosure Support

If a judge’s standing order requires an AI disclosure, can the product produce one?

Conga CLM
Partial record

The platform keeps a complete audit trail of every action, approval and signature across the contract lifecycle, which the vendor describes as supporting legal or internal reviews. It also keeps version control, tracked edits and inline comments. AiMe shows how every recommendation is generated and the reasoning behind AI driven actions, and confidence scores accompany each suggestion, so the basis of a proposed clause is visible at review.

No report or extract is described as identifying which model produced a passage, and the model is not named beyond a family. Conga describes no document level export, no marking of machine generated text against human edited text in a form a party could give a court, and no disclosure template, certification form or court guidance.

Lexagle
Partial record

Lexagle records contract changes, approval activity and signing events. Document Guard binds its compliance result to a version and requires renewed evaluation after an external change, helping distinguish an approved draft from a later upload. These controls can support an account of the agreement's history. They do not supply a complete export of model identity, prompts, generated text and counsel's verification, or a prepared court declaration explaining AI use in a filed document.

What neither one publishes

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.

Signals neither addresses in public material
  • Good Law Verification
  • Bar Guidance Alignment

Which one fits

Choose Conga CLM if

  • Contract work begins in Salesforce or a broader revenue management process.
  • Authors need a choice of Word, Google Docs and browser editing.
  • Tenant specific model training boundaries need to be stated explicitly.

Choose Lexagle if

  • A simple compliance state should determine whether work moves to signing.
  • Separate internal and external rooms fit the negotiation process.
  • APAC contract operations and version protection are the main selection criteria.

In summary

Conga CLM

Conga CLM connects contract creation, negotiation and obligations with Conga's commercial suite. AiMe processes legacy agreements, compares drafts with playbooks and proposes wording in Word, Google Docs or a browser, with generative services using Azure OpenAI.

Source: AI Legal Index, 2026

Lexagle

Lexagle combines contract workspaces and signing with Document Guard's three state gate. Legal teams define requirements in plain English, and the platform reopens review when a version protected by its digital seal is changed.

Source: AI Legal Index, 2026

Questions buyers ask

Does choosing Conga require a Salesforce deployment?

No. Conga offers its original Salesforce application and a service on the Conga Advantage Platform that can work with other CRM, ERP and procurement systems. The selected edition changes implementation. From the AI Legal Index, based on each vendor's own published materials as of October 16, 2026. No vendor pays for placement.

Can Lexagle route reviews without someone choosing each step?

Document Guard uses extracted agreement information and customer rules to route, block or escalate work. Green agreements may proceed to signing; amber results go to a human. From the AI Legal Index, based on each vendor's own published materials as of October 16, 2026. No vendor pays for placement.

Are Conga's training limits equivalent to Lexagle's?

Conga permits training within the customer's own tenant while barring customer content from shared foundational models. Lexagle's displayed terms allow certain aggregated or nonidentifying uses and customer insights for improvement across its services. From the AI Legal Index, based on each vendor's own published materials as of October 16, 2026. No vendor pays for placement.

What does the supplier disclosure add to this comparison?

Knowing the model service helps a procurement team assess the proposed processing arrangement. Here AI Legal Index identifies Azure OpenAI in Conga's supply chain, while Lexagle's proprietary engine description leaves its underlying providers unspecified.

Disclosure

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.

Edition choice is material for Conga, while Lexagle quotes a combination of modules. The comparison does not treat a Salesforce connector as the whole Conga product.

Contact

Correct a record, or ask how something was graded

Every grade and every signal on this index is drawn from public sources and dated. If a record is wrong, out of date, or missing an artifact the index did not locate, send the source and it will be reviewed and the record redated. Vendors are welcome to submit documentation. Nothing on this index is for sale, including a listing, a placement, or a grade.

AI Legal Index

The AI Legal Index is an independent index that tracks changes to AI vendors in legal. It holds 462 vendors across 9 categories, each graded on the same 15 capability axes and recorded against 12 legal signals, from public sources. No vendor pays for inclusion, placement, or rating.

Index Status
Last index update
October 16, 2026
The AI Legal Index is an editorial reference. It is not a regulatory body, not a law firm, and nothing published here is legal advice or a recommendation to retain or avoid a vendor. Records are verified against published sources, bar guidance and public court records. Where a record reads not addressed, the material was not located in public sources on the date shown. See the Methodology page for evaluation standards and limitations.
© 2026 AI Legal Index
3801 N Capital of Texas Hwy, Ste E240 · Austin, TX 78746