LawVu vs Lexzur: how they compare in 2026
LawVu and Lexzur both combine matters and contracts, but their operating scope differs. LawVu centers on the corporate legal department, connecting intake, agreement work, knowledge and outside counsel spend. Lexzur also serves law firms, with PRACTICE adding client intake, time entries, invoices and accounting beside CONTRA's agreement workflows. Their AI can participate in configured processes rather than only answering isolated questions. LawVu offers AI Workflows and a separate MCP connection, while LEXA lets administrators assemble specialized agents and subworkflows within the Lexzur environment. Lexzur is particularly relevant when regional invoicing, Arabic work or customer server deployment belongs in the same project. LawVu is a closer fit when an internal legal team wants its matters, agreements and spend organized around a corporate workspace. Hosting choices and AI processing locations still need to be distinguished.
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.
LawVu's matter records, intake forms, contract repository and invoice approvals operate without generative AI. Intelligence adds extraction, billing guideline review, answers and record changes to that foundation. The Assistant replaces the earlier Workspace Intelligence chat and works across the spend module as well as matters and contracts. Its invitation beta and the Business Portal proxy preview have narrower availability than the general LegalOS marketing. Lens is an early access contract analysis feature, with Data Protection and Confidentiality available and other category templates still planned. Draft supplies Word redlining and clause reuse. Administrators can build AI Workflows that classify new matters, route contracts or create tasks. Manual and new-record triggers are supported; scheduled triggers remain forthcoming. AI reaches several operational jobs, while the underlying system of records remains useful without it.
LEXA operates within CONTRA and PRACTICE, bringing contract analysis, matter summaries, translation and drafting into the same records used for daily legal administration. Teams define agents with persistent instructions, reference files and tools, then combine them into sequential, dependent or routing workflows. A workflow can call another workflow and be enabled or disabled centrally. The Knowledge Base supplies organizational templates and policies, while chat settings select jurisdiction and response preferences. The underlying products still manage matters, agreements, permissions, billing and signatures without generating answers. AI is consequently an important working capability within a broader operational system, rather than the sole function of the platform.
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.
Lens lets a reviewer expand an extracted clause and open its source contract in context. It accepts DOCX and PDF files, with citation highlighting currently available only for PDFs. A sample run can cover up to 25 contracts before a full extraction. Its grid separates Not Found, where no relevant provision is identified, from Unclear, where conflicting or ambiguous language cannot be mapped confidently to a value. The Business Portal assistant can supply source excerpts and direct unsupported questions into a legal request. Draft compares proposed wording with the customer's clauses and playbooks. These controls help a person verify an answer; they do not establish an accuracy rate. The AI service terms require human review and disclaim completeness and accuracy. No measured legal error benchmark accompanies these features.
LEXA compares agreement language with the customer's templates, clause library and policies, presenting the clause or passage behind each finding. Review covers missing provisions, unusual wording, indemnities, obligations and ambiguity. Administrators can upload reference files, index selected material and apply custom instructions across responses. This gives analysis an identifiable organizational context instead of relying only on a general question. Matter checks also use the file's correspondence and attachments. No measured citation accuracy, described legal evaluation set or error rate accompanies these features. A retrievable contract passage supports inspection of a finding but does not verify an external legal authority or its continuing validity.
Autonomy and Oversight Model
What the system decides on its own, what a lawyer must approve, and whether the vendor documents where the review point sits. A tool that drafts under review and a tool that files without one are different products and different risks.
The conversational Assistant asks for approval before creating or updating records and groups batch operations into at most ten actions per approval. Changes and declined approvals enter its audit history. AI Workflows are different: an administrator configures actions, conditions and optional approval steps, then activates the workflow for manual or event-driven execution. The editor has test mode, version restoration and step-by-step execution results; scheduling is still forthcoming. MCP-connected external tools can create matters, assign tasks and trigger contract workflows. LawVu recommends human confirmation for their writes but does not describe a mandatory approval on every MCP action. Existing user permissions constrain each connection. The acceptable use policy bars consequential automated decisions without oversight, testing or prior risk evaluation, while product-specific workflow settings determine when a person intervenes.
Administrators configure each agent's task, response behavior, available tools and reference files. Workflows run sequentially, pass earlier results to later agents or route work to an appropriate agent or subworkflow; each can be disabled from settings. Users select the workflow and supporting material, with an optional buyer, seller or neutral review perspective. LEXA returns source passages for review and records AI actions against the underlying record. Its stated boundary excludes signing, approving and making the final legal risk decision. The agreement requires human verification and approval before reliance, execution or filing, and permits binding AI action only through a separate written arrangement.
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.
Sizzling Platter corporate counsel Samuel Gray attributes a three-month implementation to LawVu's migration support, including the bulk creation of more than 700 matters from spreadsheets. The customer story estimates that avoiding manual entry saved up to 175 hours. It also describes faster access to matter context, links between stores and acquisition agreements, SharePoint collaboration and a Mexico team's contract creation wizard. Its estimate of ten to fifteen hours saved each week depends on assumed daily matter activity, rather than a controlled study. The story has no visible publication date and does not isolate AI's contribution. Named users at Axel Springer and AES also describe Word adoption and shared drafting knowledge. These are identifiable customer accounts of operating benefits, without independent measurements of the newer Assistant or Lens.
Al Marbae & Partners Law Firm in Jeddah began using PRACTICE in December 2023. Its administration and business development manager, Mohammad Ali, describes improved efficiency, reduced operating effort and more accurate billing. The account identifies the firm, responsible user, product and adoption period, but supplies no numerical baseline or measurement method. CONTRA separately promotes faster contract creation, lower costs and extensive approval automation without connecting those figures to that firm's experience. The named deployment therefore supports actual operational use of Lexzur, while the size of any improvement attributable specifically to LEXA remains undetermined. General customer totals do not establish AI performance.
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.
LawVu's AI service terms prohibit third parties from using customer data or outputs to improve or train AI models. Its AI FAQ extends the no-training position to LawVu itself and says Azure OpenAI monitoring is disabled under an exemption. Restricted matters admit named members, and the native Assistant and MCP server enforce the requesting user's existing permissions. A significant history limitation remains: a conversation is not removed when a user later loses access to the matter discussed in it. Organization administrators can review Business Portal conversations. MCP also transmits relevant legal data to the customer's chosen AI provider, whose processing terms are outside LawVu's control. The SaaS confidentiality clause protects customer information but permits necessary disclosures and professional advisers; it does not promise that uploading material preserves legal privilege.
The agreement protects confidential information through purpose restrictions, reasonable care and obligations on authorized recipients. Lexzur separates customer databases and attachment paths, with privacy settings for individual matters and folders. LEXA follows the workspace's user permissions, while account administrators retain broad access. Product guidance states that customer files do not train Lexzur models or improve others' outputs. The contract nevertheless permits derived anonymous statistics for development and improvement, and the data addendum includes system improvement among AI processing purposes without an express training exception. Provider retention, a complete processor schedule and privilege specific handling remain unresolved, so the marketing commitment does not supply the entire contractual boundary.
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.
LawVu's AI service terms say output is not legal or other professional advice and require review before decisions or further processing. The acceptable use policy prohibits substituting the service for licensed advice, allowing unqualified people to rely on legal outputs without professional supervision, or making legal determinations solely from AI. The Business Portal preview turns conversations into legal requests when human input is needed and identifies the customer's legal team as the source of legal advice. It currently serves in-house users acting as proxies, with standard business users excluded from that beta. These are concrete professional boundaries within an internal legal workflow. They do not vary by jurisdiction or map individual features to local rules on authorized legal practice.
LEXA is presented as assistance with review, extraction, summaries and drafting, with the lawyer retaining professional judgment. The agreement excludes legal and regulatory advice and requires independent verification and approval before generated material informs filings, contracts or other decisions. The product also serves procurement, sales and other business users, so this boundary extends beyond licensed lawyers. A country selector provides jurisdictional context, and a general framework applies when no country is selected. That setting does not establish jurisdiction specific authorization, professional competence or legal correctness. No detailed allocation of supervision duties across those countries accompanies the available workflows.
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.
LawVu's six AI principles address user needs, transparency, reliability, security, trust and privacy. They apply to AI in the business and its products and are intended to be reviewed annually. Its AI FAQ commits to privacy impact assessments for new features and places AI within the existing security and privacy program. Organization administrators control generative AI enablement; some non-generative functions, including invoice extraction, are enabled by default. Workflow administrators can test actions and inspect execution outcomes before broader use. The MCP guide explicitly describes prompt injection, tool impersonation and external-provider risks. Neither those guides nor the principles provide bias test results or a named AI governance owner. ISO 42001 certification claims also conflict with the older FAQ's statement that an audit is still being pursued.
The security exhibit lists grounded answers, citations, estimates of certainty, approval mechanisms and monitoring as optional AI controls, applied where appropriate. General operational provisions cover development changes, testing and security procedures without a defined AI release assessment. Customer administrators can constrain agent instructions, reference files and tools, and can disable workflows; those settings govern customer use rather than establishing the vendor's own testing program. No accountable AI governance owner, model acceptance criteria or results across legal tasks and populations are identified. Educational discussion of bias and human judgment does not supply a measurable assurance process for current LEXA agents.
AI Safety and Data Stewardship
Retention, deletion, access control, and what happens to prompts and documents after they are processed. Whether the vendor states its subprocessors and its incident practice, or leaves the buyer to assume.
The data processing addendum requires breach notice without undue delay and, where feasible, within 72 hours. New subprocessors require thirty days' advance notice, with fifteen days to object on data protection grounds. Personal information must be returned or destroyed at termination or request, subject to the agreement and legal retention. The SaaS terms allow a request within one month after termination and backup retention for up to one year. Azure inference is transient, but Assistant conversations, actions and approvals persist: logs are visible for thirty days and available from LawVu afterward, without a stated final deletion date. Restricted membership, SAML authentication with SCIM provisioning, enforceable multifactor authentication, AES-256 encryption and TLS 1.2 or later control access. Backups provide a 35-day point-in-time restore.
Lexzur combines encrypted storage and transport with user permissions, access logging and backup procedures. Its data addendum requires notice without undue delay after a confirmed personal data incident, aiming for seventy two hours where feasible. The agreement sets deletion within ninety days after termination, but the addendum preserves legal, compliance and temporary backup exceptions. Chat History retains conversations for later continuation, without a separate prompt retention window. Subprocessors must accept protective obligations, although their full list is supplied on request and change notice is conditional on applicable law. These controls cover substantial operational ground without a complete, fixed account of every AI processing layer.
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 SaaS terms, which apply to order forms signed after 13 May 2024, cap each party's liability in a calendar year at the fees paid or payable for that year. They exclude indirect and consequential loss, lost profits and loss of data, and lift the cap only for personal injury, death or fraud. LawVu indemnifies the customer against third party claims that its use of the services or platform infringes intellectual property. The indemnity excludes unauthorized use or modification, breach of the agreement, materials LawVu did not supply, and third party or personal data. The AI service terms, effective 30 April 2026, carve AI output out. LawVu does not warrant that outputs are complete or accurate, accepts no liability for loss relating to them, and requires the customer to review every output before use. The services are provided as is. New Zealand law governs, or Delaware law for customers in the United States, with arbitration in each.
The agreement provides a vendor defense and indemnity for infringement claims concerning the program and services, with exclusions for customer material, modifications, misuse and combinations with other products. It limits aggregate liability to fees paid during the preceding twelve months and excludes consequential losses. AI output carries no accuracy, completeness or legal sufficiency warranty, and the customer must verify its use. Service interruption credits are a separate, limited remedy, capped at five percent of the monthly fee under the stated availability schedule. These contractual remedies address defined service and intellectual property risks, without a distinct promise to compensate for an erroneous legal conclusion.
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.
LawVu's MCP setup requires support activation, followed by an organization administrator enabling the integration tile. External AI clients connect to its remote endpoint with OAuth 2.0. Read tools retrieve matters, contract details, files and knowledge; write tools create matters or wizard contracts, assign tasks, post status updates and trigger contract workflows. Each action respects record membership and enters the activity log. Microsoft's Power Platform connector provides a separate commercial authentication route and distinct United States Government and demo connections; connections are not shared between users. Draft operates inside Word and supports side-by-side Word or PDF comparison. Sizzling Platter's customer account describes linking matters to SharePoint folders and using the API for Power BI. The buyer controls the security of external AI clients and licenses for third-party platforms.
Lexzur webhooks send outbound HTTPS POST requests when matters, intellectual property records, matter containers or contracts are added or edited, and when supported workflow statuses change. Administrators configure a primary endpoint and optional second endpoint, then trigger an event to verify delivery. The receiving systems must process the event data. Microsoft connections associate Outlook mail with matter records and support Word work, Teams and external storage. Signature integrations return signed copies and audit trails to the contract record. Google Calendar synchronization exchanges calendar, meeting, attendee and timing information in both directions. API availability and some integrations depend on the purchased plan.
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.
LawVu hosts customer data in Microsoft Azure and contractually commits to the chosen storage region: Australia, the United States, Europe, Canada or the UAE. Primary and secondary data centers remain within that geographic boundary, with logical segregation between customers. The subprocessor list specifies a separate route for some AI processing. United States and European Azure OpenAI data stacks follow the SaaS agreement; Australian and UAE customers' requests run in Europe, and Canadian requests run in the United States. The AI FAQ describes that processing as transient, while the customer's system of records stays in its selected region. A customer-selected AI provider connected through MCP receives relevant data under its own terms, outside that native inference arrangement. The service availability commitment is 99.95 percent.
Lexzur offers cloud hosting, private service, hybrid arrangements and installation on customer servers. The cloud description identifies Microsoft Azure, while the data addendum names Saudi Arabia, the United Arab Emirates and the European Union among available hosting locations. Product guidance places local residency on Business and higher plans, with the chosen arrangement defined in the order or proposal. Customer databases and attachment paths are separated. LEXA uses Azure OpenAI, but its inference region and the treatment of remote support or other processors are not mapped to each hosting choice. Keeping the core repository in a selected country therefore does not establish identical residency for every AI operation.
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.
LawVu dates its ISO 27001 certification to April 2019, its first SOC 2 audit to January 2020 and its first SOC 1 audit to February 2021. It also claims 2025 certification against Dubai's cloud service provider standard and AssuranceLab compliance seals for HIPAA, GDPR and CCPA. The certificates, statement of applicability, SOC reports and penetration test reports require access to a confidential security pack. The open pages do not identify the current ISO or SOC auditor and reporting period. Annual penetration testing uses CREST-certified providers, with daily Qualys vulnerability scans. AI marketing now claims ISO 42001 certification, while the March 2026 AI FAQ still describes certification as being pursued. That unresolved difference prevents treating the newer claim as a verified certificate.
Lexzur identifies ISO/IEC 27001:2022 certification with certificate number AE24060703. Its trust center lists ISO certification and separate SOC 2 Type II compliance entries for Saudi Arabia, France and the United Arab Emirates. It also lists resources covering encryption, backups, disaster recovery, secure development and security fixes. Detailed reports and control material require access; the open overview does not supply auditor opinions, examination periods or full service scope. Other explanations attribute SOC certifications to the hosting provider, which is a separate assurance boundary. Encryption, authentication and role controls supplement these statements without independently proving the quality of AI answers.
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.
LawVu identifies Microsoft services by feature. Azure AI Foundry supplies models for contract extraction, bulk imports, billing guidelines and drafting. Azure Document Intelligence handles invoice extraction; Content Understanding also supports Workspace Intelligence and billing guidelines, and Azure's retrieval service supports Draft. The Assistant uses Microsoft's Agentic Framework with Azure OpenAI, while Lens combines Azure Document Intelligence and Azure OpenAI models. Specific model versions and an advance model-change notice are not stated for those features. LawVu provisions and manages the native models. Its separate MCP server connects customer-chosen tools such as Claude, ChatGPT and Copilot agents, with provider processing outside LawVu's control. The subprocessor list maps Azure OpenAI processing countries, and the DPA adds notice before new subprocessors.
LEXA identifies Microsoft Azure OpenAI as its generative AI technology. The application allows agents to use Precise or Creative response behavior, but those labels do not identify foundation model names or versions. Administrators also choose reference files and available tools, shaping context without selecting a fully described provider chain. The agreement permits third party model and infrastructure services with their own technical and regional constraints. It does not promise advance notice of particular model substitutions, and the complete subprocessor list is available on request. The provider is therefore identifiable, while model versions, processing regions and change handling remain only partly specified.
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.
LawVu quotes subscriptions from selected capabilities and user numbers without a starting amount or standard seat rate. Matters covers intake and matter management, Essentials adds contracts, and Ultimate adds spend. Draft can be purchased separately or added to a subscription; the agentic workflow builder is a paid addition. The plans FAQ specifies a first-year onboarding fee, while support and customer success are included. Some integrations cost extra. Spend pricing uses the number of outside firms rather than a percentage of legal expenditure. The invitation AI beta is initially available to selected Essentials and Ultimate customers at no additional cost, with future consumption tiers under evaluation. Standard terms renew annually unless either party gives thirty days' notice; renewal increases generally have a fifteen percent ceiling, excluding consumption-based rate cards.
Both PRACTICE and CONTRA use subscriptions priced per user, with cloud Basic starting at $9 per month billed annually or $11 monthly. Basic covers three to five users; Business supports up to twenty five and Enterprise up to fifty, with Enterprise Plus quoted for larger arrangements. Annual Business and Enterprise rates are $29 and $39 per user per month. LEXA includes fifty trial credits per instance, followed by purchased transaction bundles. Portals and selected connectors add separate charges. Implementation scope and residency require a proposal. The subscription and usage structure is clear, but the full cost depends on deployment, external access and the purchased services.
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.
LawVu serves in-house legal departments across healthcare, higher education, software, financial services, government, energy, manufacturing and insurance. Its role-specific workflows address general counsel, legal operations, IT and teams adopting their first legal system. Customer groupings span Asia-Pacific, North America, the United Kingdom, Europe and the UAE. LegalOS combines intake, matters, contracts, files and reporting, with outside counsel spend in the Ultimate plan. Law firms participate as service providers through matters, invoice submission and billing guidelines; this is not a law firm's client-accounting or court-filing system. Draft supports common commercial agreements such as NDAs, MSAs, supplier and sales contracts inside Word. The Business Portal AI remains a restricted preview, so its broad intended business audience should not be mistaken for general availability.
PRACTICE serves law firms and corporate legal departments handling matters, litigation, hearings, contacts, time, billing and intellectual property administration. CONTRA extends agreement workflows to procurement, sales, finance, human resources and government teams. Plan sizes range from three users to enterprise arrangements, with separate portals for clients and outside counsel. The interface includes English, Arabic, French and Spanish, and LEXA supports Arabic review and translation. Regional features include Saudi electronic invoicing and local signature options. A jurisdiction setting gives AI additional context, but no complete matrix identifies supported legal authorities, practice specific performance or excluded uses across all offered countries and languages.
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?
LawVu's AI service terms, part of the customer agreement, bar third parties from using customer data or outputs to improve or train AI and machine learning models, including LawVu's AI services. The AI security and privacy FAQ adds that LawVu trains no models on customer data, directly or indirectly, and does not let its service providers train theirs. Inputs and outputs to the AI services are not used for training. LawVu operates under an exemption from Microsoft's standard Azure OpenAI monitoring, so Microsoft may not access or monitor that usage.
The SaaS terms let LawVu collect anonymized statistical data from use of the services, such as session data, page loads and which features are used, to improve services and develop new ones. This native-service commitment does not establish the terms of a customer's separately connected MCP provider.
The October agreement permits aggregated, anonymized statistics for research, system improvement and product development. The data addendum also allows AI processing of customer data for system improvement and functionality enhancement, without an express exclusion for model training. This is broader than LEXA's promise that customer files do not train models or improve others' answers. The Knowledge Base uses a Train action to index reference files; that interface label alone does not establish foundation model training. The contractual improvement permission has no stated opt out.
Prompt and Output Retention
How long does the product keep what a lawyer typed, and can that be set to zero?
Native AI requests are transient at the inference service, while the results and conversations can persist inside LawVu. Assistant conversations, actions and approvals form an audit record visible for thirty days, with older logs available from LawVu on request and no final retention period specified. Business Portal conversations remain available to the user and authorized administrators. Changing a user's matter permissions does not revise prior conversation history.
The SaaS terms allow a copy request within one month after termination and backup retention for up to a year. External AI tools connected through MCP have separate retention terms controlled by the customer's chosen provider.
LEXA Chat History lets users reopen and continue past conversations, confirming that the application retains exchanges. No distinct prompt or output retention period, configurable window or zero retention option is specified. The agreement's ninety day deletion period follows subscription termination rather than each AI request. Its data addendum permits legal and internal compliance retention and temporary copies in backup or recovery systems.
Those exceptions mean the termination period cannot be treated as an absolute purge deadline for all conversation material or provider records.
Ethical Walls and Matter Segregation
Does retrieval respect the firm’s ethical walls, or can the model read across them?
LawVu restricts a matter to named members, including external legal service providers where invited. Administrators can see limited identifying fields in a restricted-entities report, but not the matter contents. Contracts, statements of work and amendments created within restricted parents inherit membership; previously linked contracts and newly created child matters do not automatically inherit the restriction. Delegates also require explicit membership.
The native Assistant and MCP connections apply the user's access rights, using LawVu's own permission model. Saved conversations are not revised after later permission changes, so a user can retain previously discussed material in chat history.
Lexzur controls access through user groups and module permissions, with additional privacy at matter and folder level. Administrators can assign permissions for individual activities in PRACTICE, CONTRA and Billing; administrators have all permissions by default. Client and advisor portals provide separate, restricted participation, including field controls for outside counsel. LEXA follows the workspace's permissions.
These are Lexzur's own controls rather than demonstrated inheritance of an external document system's ethical walls. Knowledge Base administration also requires care because indexed reference material can influence responses across modules.
Third Party Request and Subpoena Notice
If someone subpoenas the vendor for a firm’s data, does the firm hear about it first?
LawVu's data processing addendum commits it to notify the customer promptly of any legally binding request for disclosure of customer personal information by a regulatory body, unless the law prohibits notice. The commitment covers requests addressed to LawVu or any of its subprocessors. The addendum also commits LawVu to tell the customer about monitoring or investigations by a regulatory body. Regulatory bodies are defined to include government departments and regulatory and statutory bodies entitled to regulate or investigate data security and privacy.
The SaaS terms add that a party required by law to disclose the other's confidential information must notify the other immediately in writing where permissible and disclose only what is required. LawVu issues no transparency report. Once a calendar year, under a nondisclosure agreement, a customer can have the latest independent audit report, with an audit at its own cost where the report is not enough.
The confidentiality clause requires reasonable advance notice of compelled disclosure where legally permitted and cooperation with protective measures at the customer's expense. For personal data, the data addendum promises commercially reasonable efforts to notify before disclosure where lawful and reasonably practicable. Authorities may still require production, and the commitment is subject to those legal and practical qualifications.
No transparency report describing request volumes or handling outcomes accompanies the terms. Incident notification addresses unauthorized access separately and should not be confused with notice of legal process.
Primary Law Corpus Provenance
Where does the law in this product come from, and does the vendor have the right to use it?
LawVu's AI works from the customer's own material. The Assistant draws on matters, contracts, policies, knowledge repositories and legal notes in the customer's LegalOS. LawVu Draft drafts and reviews from the customer's clause library, precedents and imported playbooks, with LawVu's base templates as a starting point. The Business Portal assistant answers business users from knowledge content the legal team makes available, and LawVu Lens reads the customer's executed contracts. No primary law collection, licensed legal content or update cadence sits behind the answers.
LEXA lets a user select a country whose legal framework should guide the response, with a general framework used when none is chosen. It also analyzes uploaded agreements, matter files and organizational reference material. The country setting does not identify the underlying statutes, judgments or commentary, their licensing basis or their update schedule. Customer templates and policies provide a distinct source of organizational context, but they are not a complete primary law collection. No inventory maps the available jurisdiction settings to named, maintained legal corpora.
Good Law Verification
Does the product tell you when the authority it just cited has been overruled?
LawVu works on contracts, matters and invoices rather than case law, so a citator sits outside the product. Draft checks contracts against the customer's playbooks and clause library, and Lens cites back to the source contract rather than to legal authority. Lens identifies risky terms and inconsistencies across a contract portfolio against the customer's own standards. Keeping playbooks, clauses and policies in step with changes in law is the work of the legal team that maintains them.
LEXA can analyze legal issues, governing law and compliance questions using matter material and selected jurisdictional context. Contract findings point back to relevant clauses, supporting review of the working agreement. No integrated citator or subsequent treatment process is identified for judicial authorities, and the general requirement to verify output does not describe such a function. A country selector and an accessible source passage cannot determine whether a cited judgment was overturned or limited. That verification remains separate from the contract and matter analysis described for LEXA.
Refusal and Uncertainty Behavior
What does the product do when the answer is not in the corpus?
Lens distinguishes a provision it cannot find from language it cannot confidently interpret. Not Found means no relevant clause was identified; Unclear marks ambiguous or conflicting wording that cannot be mapped to a defined value. Reviewers can open the source contract and inspect the text, with citation highlighting for PDFs. The Business Portal preview also declines unsupported answers, suggests another retrieval attempt or escalates to a legal request.
These are stated product behaviors, not an independently measured refusal rate. The AI terms still require review, and the current preview is available only to in-house proxy users.
The security exhibit mentions optional confidence indicators without identifying a current display, calibration or threshold. LEXA's agents can follow precise instructions and return the clauses behind findings, but no explicit no answer path is described when source material cannot support a legal conclusion. The stated prohibition on signing or approving concerns action authority, not whether the model abstains from an unsupported answer. General warnings about mistakes and required human review therefore do not establish runtime refusal behavior.
Fabricated Citation Record
Does a public court record exist addressing fabricated or hallucinated legal citations in output from this product?
The AI Hallucination Cases database maintained by Damien Charlotin, which records court decisions worldwide that address hallucinated AI content and the tool involved where known, has no entry naming LawVu, LawVu Draft, LawVu Lens or ClauseBase. LawVu drafts contracts and answers questions from an in house team's own records rather than producing court filings.
The AI Hallucination Cases database contained no entry identifying Lexzur, App4Legal or LEXA as the responsible tool as of October 16, 2026. Incidental matches involving names such as Alexander and Alexa concerned other subjects and did not identify this product. The absence of an identified case does not measure LEXA's accuracy or prove that generated legal analysis is reliable. Its internal matter and agreement work may never appear in a reported court dispute, and users retain responsibility for verifying material used in proceedings.
Bar Guidance Alignment
Has the vendor engaged in public with the ethics opinions its buyers are bound by?
LawVu's acceptable use policy refers to professional duties in general terms. It bars using the AI services as a substitute for licensed legal, financial or other professional advice. It also bars letting unqualified individuals generate or rely on outputs such as legal documents without appropriate professional legal supervision, and relying solely on AI output for legal or regulatory determinations without human review.
The policy incorporates Microsoft's Enterprise AI Services Code of Conduct and forms part of the SaaS agreement. LawVu's guide to AI for in house teams covers adoption and procurement. These terms do not name a bar opinion, such as ABA Formal Opinion 512, or a professional conduct rule in New Zealand, Australia or elsewhere.
Lexzur's educational material refers generally to American Bar Association guidance, competence, client interests, confidentiality and the risks of biased AI output. Its current agreement independently requires human verification and excludes professional advice. No named ethics opinion is connected to a specific LEXA control or mapped across jurisdictions. The older educational article's broad regulatory discussion does not establish the current legal position in each country.
Selecting a jurisdiction for a response also does not determine whether a firm's client consent, candor and supervision obligations have been satisfied.
Billing and Fee Posture
Does the vendor address what happens to the bill when the work takes an hour instead of six?
LawVu's spend module is the payer's record of outside counsel fees. Firms upload invoices, including LEDES files, and see their matters, invoices and billing guidelines in a self service portal. The legal team receives, adjusts and approves invoices, routes approvals through drag and drop workflows and sends approved invoices to finance. AI extracts cost details from PDF invoices and flags discrepancies with billing guidelines, such as rate or scope issues, in real time.
Reporting tracks spend by firm and matter. Legal teams send RFPs with scope and budget, compare firm proposals side by side and receive AI provider recommendations. Spend management is priced by the number of firms a customer works with rather than by its spend. The billing guidelines are the customer's own, so any rule on how firms bill AI assisted work is set by the legal team in those guidelines.
PRACTICE tracks time and expenses, supports hourly, fixed fee and capped arrangements, and generates invoices from approved entries. Lexzur promotes time savings from LEXA and improved billing efficiency, including a law firm customer account. These administrative features do not establish an invoice record identifying which billable work used AI, the actual time saved or the appropriate client charge. General AI activity logs record another part of the workflow.
No fee guidance connects compressed drafting or review time to the amount a lawyer may bill or the disclosure owed to the client.
Outside Counsel Guideline Readiness
Can a firm get this vendor through a client’s AI clause without a bespoke negotiation?
LawVu supplies a provider list with processing countries, an AI feature-to-provider mapping, a DPA and AI service terms. The subprocessor list distinguishes mandatory infrastructure from optional services and includes Azure OpenAI routing for each customer storage region. Its DPA adds incident notice, subprocessor objection and annual independent audit-report access. Certificates and detailed reports require the confidential security pack.
The MCP guide separately explains that connected AI providers receive customer data under their own terms. This gives a legal team material for a client or auditor disclosure, but the team must add the particular external AI services it enables and resolve the conflicting ISO 42001 claims.
Lexzur makes its terms, data addendum, security exhibit and Azure OpenAI identification available for diligence. The full subprocessor list is supplied on request, and the trust center requires access for detailed resources. Those materials can support an initial explanation of the platform but do not provide a complete, immediately usable client disclosure package. Model versions, AI processing locations, retention exceptions and the difference between marketing and contractual improvement rights still affect an organization's assessment. No dedicated workflow applies a client's AI restrictions across LEXA features.
Court Disclosure Support
If a judge’s standing order requires an AI disclosure, can the product produce one?
Assistant conversations, approvals and actions enter LawVu's audit logs, as do writes from connected MCP tools. Logs remain visible in the product for thirty days and available from LawVu afterward on request. Lens can export extracted clauses and values to Excel, respecting each user's contract permissions; a reviewer can open the original contract to verify an extraction. These records help explain an internal legal workflow, but do not form a court-specific declaration identifying the model and human review for every submitted document. LawVu primarily manages contracts, matters and invoices rather than filing generated legal arguments.
LEXA retains chat history and states that AI actions are logged against the relevant record. The System Audit Log spans contracts, matters and tasks, with user, time, action and changed field information; filtered results can be exported to Excel. Contract activity includes approvals, signatures and negotiations. These features preserve useful portions of the work history, but no combined export ties every generated passage to the exact model version, retrieved sources and a lawyer's independent verification. A court declaration or certification therefore requires information beyond the described activity report.
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
Which one fits
Choose LawVu if
- The project belongs to an internal legal department. LawVu connects corporate intake, matter work, contracts and outside counsel spend within that operating model.
- Staff need to connect an external AI assistant to legal workspace activity. LawVu's MCP connection supports authorized retrieval, updates and workflow execution after administrator enablement.
- The team uses Word for agreement revisions and needs a dedicated drafting surface. LawVu Draft supplies playbook review and comparison alongside the wider workspace.
Choose Lexzur if
- A law firm needs matter operations and client billing in the same system. PRACTICE supports time, expenses, hourly work, fixed fees and capped arrangements.
- Arabic review and regional operations are central requirements. LEXA handles Arabic contract and matter material, with multiple interface languages and Saudi electronic invoicing support.
- The organization requires a customer server or private service arrangement. Lexzur offers those deployment options alongside its cloud plans.
In summary
LawVu
LawVu brings internal legal intake, matters, contracts and spend into one workspace. For teams connecting that workspace to external AI assistants, the AI Legal Index highlights its MCP support for authorized reads, writes and workflow execution. Those connections depend on administrator enablement and the external assistant's own data terms.
Lexzur
Lexzur combines PRACTICE for matter, client and billing work with CONTRA for agreements. LEXA analyzes material within those records and can run configured agents in sequence or route work between them. Separate client and advisor portals give external participants restricted access, while the core service can run in cloud or customer controlled environments.
Questions buyers ask
How do LawVu and Lexzur configure repeatable AI tasks?
LawVu AI Workflows can begin manually or from new matter and contract events, with testing, versions and optional approval steps. For administrators assembling specialized roles, the AI Legal Index highlights Lexzur's configurable agents, reference files and sequential, dependent or routing workflows. These controls define the work process without removing the user's responsibility for the result.
Does Lexzur's regional hosting establish where LEXA processes data?
The core hosting choices include Saudi Arabia, the UAE and the European Union, but LEXA's Azure OpenAI processing is not mapped to each choice. LawVu provides more explicit AI routing information, including Australian and UAE environments processing in Europe and Canadian environments processing in the United States. Storage residency alone does not answer the inference question. From the AI Legal Index, based on each vendor's own published materials as of October 16, 2026. No vendor pays for placement.
Can a law firm use either product to invoice its own clients?
Lexzur PRACTICE expressly supports client billing from approved time and expense entries, with hourly, fixed fee and capped arrangements. LawVu's spend workflow primarily addresses the internal legal department paying outside counsel. Those fee relationships are different even when both products contain invoices. From the AI Legal Index, based on each vendor's own published materials as of October 16, 2026. No vendor pays for placement.
How do their starting subscription structures compare?
Lexzur's cloud Basic rate is $9 per user per month billed annually, with a minimum of three users and separate PRACTICE and CONTRA subscriptions. LEXA credits and portal seats can add charges. LawVu uses a proposal based on users, modules and related services rather than a comparable public entry rate. From the AI Legal Index, based on each vendor's own published materials as of October 16, 2026. No vendor pays for placement.
Neither vendor paid for inclusion, placement or a grade, and neither reviewed this page before it published. Everything on it comes from public material on the dates shown. How the index grades.
LawVu's early access and beta surfaces are distinct from its generally available workflows. This comparison uses current product scope and separates storage location from AI processing. Neither vendor reviewed this page.