Concord vs Lexagle: how they compare in 2026
Concord is a more concrete commercial starting point for a smaller organization that wants contract collaboration, AI extraction and signatures under a published subscription. Essentials starts at $499 a month for five users with annual billing; workflow and integration needs may require a higher plan. Lexagle quotes a tailored package and offers a different control mechanism through Document Guard, where compliance states determine whether an agreement advances and later edits force reevaluation. Concord's Horizon agents instead extract custom properties across a chosen set of agreements after sample testing. The contractual data distinction is also significant: AI Legal Index identifies an express training exclusion for Concord customer data and specific output, compared with Lexagle's permission for certain aggregated or nonidentifying uses. Choose around the required action, not merely the presence of an AI assistant.
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.
Concord's AI extracts contract terms, answers questions about agreements and proposes wording changes in its Copilot. Horizon adds custom extraction agents that populate properties across both existing agreements and future uploads within a chosen scope. Those properties can feed reports and workflow conditions, making the models part of ongoing contract operations. The platform also retains drafting, approval routing, electronic signatures, version control and renewal reminders that function independently of AI. Its value therefore extends beyond the models, while the extraction and conversational tools form a central capability rather than an isolated writing feature. Access to Horizon matters when evaluating the agent functionality.
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.
Concord attaches explanatory notes to AI extracted properties so a reviewer can understand how a value was identified. The agent builder also lets users test extraction on sample agreements before activation. These are useful review aids, but the material does not establish linked support for every generated legal assertion or a reproducible accuracy benchmark. The service terms expressly acknowledge hallucinations and require customers to evaluate outputs, including human review. A separate ethics statement recognizes incorrect, biased and misleading responses. Explanations of extracted values consequently support inspection without establishing that suggested clauses or answers have been validated against authoritative legal sources.
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.
Customers build extraction agents by describing a desired property, reviewing the definition and testing it on up to ten sample agreements. They can limit deployment by folder, dates, creator, amount or other properties. Once activated, an agent processes future agreements in scope, with a separate action for existing agreements, and respects existing access permissions. Results include explanations for review. The terms require human evaluation of output, while later releases allow properties to drive workflow events. The published account does not fully define which consequential downstream actions require approval or how uncertain extraction returns to a person, leaving those controls partly specified.
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.
Concord identifies customers and individual users across several industries. PAAY describes importing files through Google Drive and extracting their data; Vecna Robotics describes avoiding missed dates and transposed numbers; and LeoVegas describes reviewing governing law and renewal information across its portfolio. Navarino also describes transferring completed agreements to SharePoint through Zapier. These accounts establish practical use beyond a list of logos. Broad claims about hours saved and reduced contract delays do not include a common baseline, sample definition or independent measurement method. They should not be read as a measured accuracy result for the newer custom extraction agents or every Copilot task.
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.
Customer data is confidential information under Concord's commercial agreement, with access restricted to personnel who need it and obligations before compelled disclosure. The agreement gives Concord broad rights to maintain and improve the service, but expressly prohibits using customer data or the customer's specific output to train its AI models. Administrators control roles, contract access and sharing permissions. The extraction agent explanation also states that inaccessible agreements are not processed or revealed to the user. These controls address access and model use directly, although no distinct attorney client privilege undertaking or professional work product framework is provided for law firm matters.
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.
Concord requires customers to evaluate the accuracy of AI output with human review and acknowledges that it may contain hallucinations. Its ethics principles treat AI as assistance to people and warn against entering sensitive information unrelated to the contract being handled. The product is nevertheless promoted to business teams that manage agreements without routinely involving legal counsel, and Copilot can explain risks and suggest changes. The commercial agreement does not expressly disclaim the provision of legal advice or map those tasks to a lawyer's professional duties. Approval workflows provide organizational controls without a published jurisdiction specific framework for legal supervision.
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.
Concord publishes AI principles addressing privacy, human accountability, bias mitigation and transparency. Product and engineering teams are to receive education on fairness, with training scenarios intended to represent different industries and legal frameworks. The company also promises indications when an automated system is being used and acknowledges potentially biased responses. These commitments identify concerns and broad practices, but not a named accountable risk owner, release criteria, published bias test or results across contract types and languages. Customer feedback is part of the stated improvement process. The available account remains a principles statement rather than a verifiable program of model evaluation and oversight.
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.
Concord specifies encryption in storage and transit, restricted employee access, customer roles, multifactor authentication, daily encrypted backups and external penetration testing twice a year. Its model provider is described as bound to zero data retention, and named subprocessors have listed processing locations. The privacy policy caps debug data at six months, allows indefinite anonymized analytics and offers a data copy on request within thirty days of termination. Commercial terms require return or destruction of confidential information when the subscription ends. Precise backup removal and prompt schedules remain incomplete, and the incident policy does not state a customer notification deadline.
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.
The commercial agreement provides an ordinary intellectual property indemnity for the system and caps aggregate liability at fees paid in the preceding twelve months. It also warrants material conformity with service documentation. However, the AI disclaimer expressly excludes liability for damages resulting from or relating to output and warns that output may be inaccurate or hallucinated. The customer indemnity separately includes claims arising from use of generated content. Those provisions leave no affirmative protection for the legal correctness of an AI clause or contract analysis. The general service indemnity should therefore not be treated as a specific remedy for an AI error.
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.
Concord's Salesforce guide explains installation, account connection, Opportunity layout changes, template selection and fields sent from account, opportunity, contact and product objects. Agreements can be generated from Salesforce and populated with its data, with synchronization in both directions. Administrators also set the maximum sharing rights available for templates and uploaded files. This is a concrete implementation path rather than a connector logo. Other integrations include storage services, calendars, a Word plugin, Zapier, APIs and MCP access through Claude or ChatGPT. Those connections have different plan requirements, with the Salesforce workflow available on Business and Enterprise and the open API listed on Enterprise.
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.
Concord is a hosted service with customer storage choices in the United States and Europe. Its subprocessor list places AWS hosting in the EU for European customers and North America for North American customers. The same list places OpenAI extraction in North America and Google model tooling and OCR in North America and the EU. Storage selection consequently does not establish that every AI processing step remains in the selected storage region. No private deployment or complete tenancy description is provided. The privacy policy also permits international transfers under stated safeguards, so regional processing requirements need to be matched to the selected features.
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.
Concord offers a SOC 2 Type II report through its Conveyor portal and states participation in the Cloud Security Alliance STAR Level One program. The latter is a self assessment rather than an independent audit. It also states certification under the Data Privacy Framework and its British and Swiss extensions. Separate references to AWS certifications describe infrastructure assurance and should not all be attributed to Concord itself. The public security explanation does not identify the SOC auditor, examination period or full service scope. Encryption, penetration testing and incident procedures provide additional operational detail without establishing the quality of AI contract interpretation.
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.
OpenAI is named as a provider for AI based extraction, Google for model tooling and OCR, and LangSmith for model tooling. The subprocessor list supplies processing locations and transfer mechanisms for those services, alongside AWS hosting and other operational suppliers. Concord also says its AI provider has agreed to zero data retention. The disclosure does not identify every model version or explain which provider handles each Copilot and agent operation. There is no public commitment to advance notice before a model version or supplier changes. Buyers can therefore identify important suppliers while still lacking the complete model configuration for a particular workflow.
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.
Essentials costs $499 a month with annual billing and includes five users, AI Copilot, extraction and unlimited agreements, signatures, viewers and guests. Business costs $899 and Enterprise $1,299 on the same billing basis, each also including five users. Extra users cost $49, $69 or $89 monthly respectively. The plan comparison identifies workflow, integration and administration differences, with volume discounts offered on Enterprise. Commercial terms cap renewal price increases at five percent and require sixty days of notice for cancellation or downgrade. A separate implementation fee is not clearly stated, so the published subscription amounts do not establish every possible deployment charge.
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.
Concord addresses legal, procurement, finance, sales, HR, operations and IT teams handling their organization's agreements. Essentials targets a small business or one department; Business supports multiple teams; Enterprise adds subsidiary management and other controls for larger organizations. Named customers span robotics, gaming, construction, payments and education. Templates, approvals and guest collaboration let legal teams set boundaries while colleagues conduct routine contract work. The claim to support any contract is not accompanied by a tested matrix of languages, jurisdictions or specialist legal issues. Its main audience is corporate contracting, without a detailed published workflow for law firms delivering advice across separate client matters.
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?
The commercial agreement grants broad rights to maintain and improve the service but expressly excludes using customer data or the customer's specific output to train Concord's AI models. Its security commitment also prohibits customer data being used for model training and describes zero retention obligations for the AI provider. Aggregate analytics remain permitted. Those improvement rights should be read with the explicit training exclusion, rather than treated as an unrestricted permission to train on client contracts.
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?
Users can edit or delete their content through Concord. The privacy policy limits debug data to six months, retains anonymized analytics indefinitely and offers a data copy on request within thirty days of termination. The commercial agreement separately calls for return or destruction of confidential information when the subscription ends. Model provider zero retention is an additional protection, not a promise that the entire account retains nothing. A complete schedule for backups and every AI interaction is not published.
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?
Administrators define roles and categories, assign feature rights and control which agreements each user can access. Custom roles also govern folders and properties. Concord's extraction agent explanation makes the AI behavior explicit: contracts outside the user's permissions are not extracted, and the user does not see which inaccessible contract is involved. This is an internal permissions model rather than inherited rights from a legal document management system. A separate account of professional ethical walls across law firm clients is absent.
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?
Section 4.2 of the commercial terms commits to prompt written notice before compelled disclosure of confidential information and a reasonable effort to obtain a protective order. Customer data falls within that confidentiality definition. The privacy policy separately allows law enforcement disclosure with or without notice at Concord's discretion, so the public language is not uniform. The contractual commitment supports notice for covered customer information; the broader privacy statement should not be presented as the same protection for every category of data.
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?
Concord's AI works with agreements, templates and properties supplied through the customer's workspace. The company names model service providers, but does not identify a licensed external legal research collection supporting contract explanations or proposed wording. Explanatory notes on extracted values describe how a contract field was derived, not the provenance of underlying legal knowledge. No inventory of authorities, commentary licenses or update schedule establishes the external legal corpus behind the models.
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?
Concord extracts terms and explains contract risks without identifying a licensed citator or a judicial treatment mechanism. Approval of an agreement and a note explaining a value do not establish that a legal authority remains valid. The system's contract repository is therefore distinct from a service that tracks later treatment of cases or changes to legislation. Legal conclusions drawn from its suggestions still require an appropriate independent method of confirming the applicable law.
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?
Concord warns that AI responses may be incorrect, biased or misleading and requires human evaluation. Extraction notes and sample testing help users inspect results before an agent is activated. The product does not publish a defined refusal response for inadequate legal support, an unsupported jurisdiction or contradictory information. The builder's clarifying questions concern the property being configured, rather than a general abstention policy during execution. A reviewer cannot infer uncertainty handling solely from the availability of a test preview.
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?
The October 16, 2026 review of the Charlotin database returned no entry naming Concord's contract platform in the AI tool field. One case includes Concord as a litigant in Concord v. Anthropic, with Claude.ai identified as the tool; that is not a finding about this vendor. A company name match alone would misattribute the incident. No named case does not establish the accuracy of Concord's contract summaries or generated wording.
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?
Concord's ethics principles discuss human accountability, privacy and bias, and its terms require customers to evaluate generated output. They do not connect these controls to a named bar opinion, professional conduct rule or jurisdiction specific framework for lawyers. The platform's electronic signature compliance addresses a different legal question. Corporate legal teams receive review and access tools, but no published mapping explains how their use satisfies professional obligations when advising others with AI assistance.
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?
Concord is sold to organizations managing their own contracting operations, with business colleagues using templates and approvals defined by legal teams. The advertised savings concern administrative work, agreement delays and missed renewals within that organization. Its subscription does not record lawyer time for a client invoice or allocate a model expense to a represented client. No client fee disclosure process accompanies the product, and the corporate contracting relationship remains outside the ordinary lawyer client billing workflow.
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?
The subprocessor list identifies OpenAI, Google and LangSmith for AI related work, with processing locations and transfer mechanisms alongside other suppliers. Concord offers its data processing agreement on request and provides access to its SOC report through a portal. These materials can support a client's supplier review, but no dedicated outside counsel AI disclosure pack is published. A legal team still needs the applicable plan, processing configuration and professional engagement requirements to complete a client approval response.
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?
Concord's audit trail records activity, users and timestamps, including changes after signing, and signature certificates can be downloaded. AI extraction notes add an explanation of individual values. These records can help reconstruct contract handling, but do not establish a complete export of prompts, model identities and a lawyer's verification. The March 2026 release notes also state that completed workflow job records are removed after ninety days. A contract audit history should therefore not be assumed to preserve every AI execution detail indefinitely.
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.
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.
- Good Law Verification
- Refusal and Uncertainty Behavior
- Bar Guidance Alignment
Which one fits
Choose Concord if
- A published five user subscription provides the needed budget baseline.
- The desired automation is custom property extraction across a portfolio.
- The contract must expressly exclude customer data from model training.
Choose Lexagle if
- Approval should depend on a defined green, amber or red compliance state.
- A changed contract must automatically lose its previous compliance result.
- A tailored mix of legal and business modules is preferable to standard plans.
In summary
Concord
Concord supplies drafting, approvals, signing and a repository with Copilot and extraction. Horizon users can test custom extraction agents and run them over selected agreements; its Salesforce setup guide describes mappings, account connection and permissions.
Lexagle
Lexagle uses Lexie for agreement assistance and Document Guard for policy enforcement. Its digital seal connects an approval result to the reviewed version, while its commercial proposal combines modules around the customer's operational needs.
Questions buyers ask
Is Concord's $499 amount an individual seat price?
No. The current Essentials offer includes five users at $499 monthly with annual billing. Additional Essentials users cost $49 monthly, and Business or Enterprise may be needed for the intended workflow. From the AI Legal Index, based on each vendor's own published materials as of October 16, 2026. No vendor pays for placement.
Do Concord extraction agents perform Lexagle's approval gate?
Concord agents populate custom properties within a selected scope and can feed workflow events. Lexagle explicitly describes compliance states that permit signing, divert human review or block an agreement. From the AI Legal Index, based on each vendor's own published materials as of October 16, 2026. No vendor pays for placement.
Does choosing European storage settle Concord AI residency?
No. Concord lists OpenAI extraction in North America and Google processing in North America and the EU. The storage region does not by itself determine every model processing location. From the AI Legal Index, based on each vendor's own published materials as of October 16, 2026. No vendor pays for placement.
Which public contract gives a clearer training restriction?
The two services make different commitments despite both offering contract automation. In this comparison, AI Legal Index finds Concord's express exclusion of customer data and specific output from AI model training clearer than Lexagle's permitted aggregated data use.
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.
Concord's agent features depend on Horizon access and its integrations vary by plan. Lexagle's quoted scope and processing configuration require an explicit commercial specification.