Contractbook vs Lexagle: how they compare in 2026
Contractbook fits a business trying to turn signed agreements into usable fields, reminders and connected workflows without starting with a large enterprise implementation. AI Import ties extracted values to highlighted agreement text for human verification, and HubSpot can supply contract data and receive updates after signing. Lexagle offers a more prescriptive review gate: its Document Guard interprets customer rules, diverts partial matches to people and protects the evaluated version against unnoticed changes. The commercial and data choices should accompany that workflow decision. Contractbook varies its packages by users, templates, agreement volume and automation, while Lexagle assembles a custom module proposal. For model use, AI Legal Index identifies a consent condition in Contractbook's terms and an express permission for certain aggregated or nonidentifying information in Lexagle's. Neither feature list establishes a legal accuracy guarantee.
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.
AI Import reads existing contracts, extracts structured fields and helps turn a collection of files into a usable agreement database. The Contract Assistant adds plain language questions, summaries, risk identification and clause revisions. Both operate inside a wider application with template drafting, collaboration, electronic signatures and ongoing contract management. Templates and configured workflows still handle repeat agreements independently of the assistant. Customers can combine the extracted dates and obligations with reminders, while CRM data populates new agreements. Essential includes the assistant; higher plans add broader data extraction, custom fields, automation and team administration around these AI functions.
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.
AI Import connects extracted data to the text it came from. Selecting a purple field in the sidebar moves the reader to its exact location in the original agreement and highlights the passage. Users can inspect individual values or verify all fields together, and the repository marks completed verification. Import first processes the uploaded files and extracts their contract data, with OCR included for relevant files. This is source based verification of customer agreements, rather than a legal citator. No test set, measured accuracy result or explicit unsupported answer behavior accompanies the Contract Assistant's broader clause recommendations.
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.
An AI import can be canceled during upload, OCR or extraction, and the canceled file is discarded. After processing, a reviewer checks the proposed data against highlighted source text and marks the fields verified. That verification can become the trigger for a reminder or a move into a shared space. Users need the relevant company permissions to import files and manage custom contract types. Template workflows also support approval steps before signing. These controls give teams review and cancellation surfaces, but the assistant has no stated confidence cutoff or defined escalation path for an answer that cannot be supported.
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.
Bizzkit's compliance officer describes saving 15 to 20 hours extracting data from about 50 legacy data processing agreements. That is a named example of AI extraction in use, with the time estimate supplied by the customer. Lenus separately describes reducing contract preparation from 15 minutes to five through templates and integrations with Salesforce, Greenhouse and HiBob. Those automation results are not presented as a measurement of the newer Contract Assistant. GANNI and Pave also discuss repository and extraction benefits. No dated comparative study isolates the assistant's effects on review quality or legal outcomes.
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.
Section 9.12 of the service terms bars AI model training on retained platform data unless the customer gives consent in writing or through the application. Confidential information is limited to service delivery and remains protected after termination. AI imports start in the user's private contract view, while sharing depends on the application's space permissions. Google Cloud hosts platform data and Azure hosts the language model, both with EU locations in the processor list. Privilege and work product handling are not addressed directly, and the terms do not specify what the model provider retains from individual prompts or responses.
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.
The service is restricted to business activity and is not offered to consumers. Section 8 describes the supplied templates as drafting inspiration rather than legal advice, and the company profile makes the same tooling distinction for the product. Legal teams can control templates, approvals and shared spaces while other employees generate routine agreements. The customer remains responsible for using suitable agreements and deciding whether electronic signatures are appropriate. No jurisdiction specific competence guidance or named professional supervision standard accompanies the assistant. Its explanation and rewriting features therefore sit inside the customer's own legal review and contracting responsibilities.
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.
Contractbook's trust center describes security policies, change management and an incident response program. Management reviews that security program at least annually, and production data is restricted in development and testing environments. The AI features separately support source highlights, user verification and consent for model training. None of these materials sets out an AI release evaluation process, a responsible AI framework or results showing uneven performance across contract types or user groups. The page titled AI Policy Page is a company and product profile for automated readers, rather than a policy assigning accountability for the behavior of the language model.
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.
Customers can remove or archive their own data through the application and request removal at termination. Signature verification information has separate retention rules and generally requires all signers' consent before deletion. The privacy policy gives a general service data retention period with legal exceptions, while the processor list identifies providers, roles and locations. Space permissions, encrypted storage, logging and a trust center incident plan add operational controls. Confidentiality breaches require prompt notice under the terms. A specific retention window for assistant prompts and outputs, together with a deletion schedule at the model host, is not stated.
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 service agreement limits liability to fees paid in the 12 months before the first claim arose. It excludes lost profit, business opportunity, third party liabilities, data loss and several other categories of loss, and supplies the service as is. Death or personal injury caused by negligence, fraud and fraudulent misrepresentation are outside the stated limitations. The customer, rather than the vendor, gives the agreement's indemnity. Contractbook promises customary insurance without naming its amount or scope. These provisions do not provide a specific warranty or recovery route for a mistaken AI clause explanation, extraction or revision.
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.
The HubSpot integration moves deal and company data into contract templates and can synchronize negotiated values back after signing. Setup requires defined template fields, the appropriate Contractbook template or company permissions, and specified HubSpot CRM, product library and marketplace rights. The administrator connects the accounts through Integrations and accepts the requested permissions, then configures triggers and actions. HubSpot quotes can become attachments, and its widget displays contract status and activity. Disconnecting unpublishes related automations without deleting generated files. Salesforce, API access, Zapier and Make extend other workflows, with availability and charges varying by plan.
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.
Contractbook runs as an online contract workspace with organization accounts, shared spaces and individual access rights. The subprocessor list places Google Cloud platform hosting and Azure language model hosting in the EU. It also identifies United States services for email, messaging, monitoring, traffic management and integrations, so the EU hosting entries do not describe every supporting data flow. The privacy policy permits transfers outside the EU and EEA with safeguards. No country selection, customer hosted installation or private tenancy option is specified, and the available material does not allocate storage and processing locations separately for each subscription plan.
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.
The security page states SOC 2 compliance and describes recurring penetration tests, encrypted credentials, verified accounts and two factor signing. A Secureframe trust center offers a SOC 2 report through a request control and lists security policies covering access, change management, risk and incident response. Its public material does not identify the assessment period, report type, auditor or detailed system scope. The separate Openli profile could not be accessed, so any material there remains unknown. Customer signatures and identity controls support contract execution, while the SOC 2 claim addresses service controls rather than measured accuracy of the AI assistant.
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.
Microsoft Azure hosts the large language model used for the product's AI functions, with the processor list assigning that service an EU location. Google Cloud is separately responsible for storage and platform hosting. The application combines document import, OCR, field extraction and a conversational contract assistant, but the specific model name and version are not identified. The terms require customer consent before retained platform data is used for model training. A general notice rule for contractual updates does not provide a specific commitment to notify customers about model replacements or changes to the inference supply chain.
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.
Essential, Centralize and Accelerate include one, five and ten users, with annual signed contract allowances of 100, 350 and 500. Template limits are five, 15 and 25. The current pricing page shows no base subscription amount; a company profile updated in March 2026 gives a starting rate of €89 per month. The pricing FAQ lists five extra users at €50 per month, or €600 annually. Automation and provisioning are optional for Centralize and included in Accelerate, while several integrations cost extra. Custom setup uses a quote, and the terms provide for upgrades or additional charges when usage limits are exceeded.
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.
Small and midsize sales, legal, HR and operations teams use the platform for standard recurring agreements such as NDAs, sales contracts and employment agreements. The Lenus case describes legal counsel setting templates and boundaries for colleagues across several markets. Bizzkit uses extraction for legacy data processing agreements, while GANNI and Pave describe contract visibility and renewal work. The company focuses on European markets and also offers industry pages for government, healthcare, construction and procurement. Its own profile excludes legal advice and simple one off signing as its intended role, without supplying a jurisdiction by jurisdiction support matrix.
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?
Section 9.12 prohibits use of retained platform data for AI model training unless the customer consents in writing or through the platform. Section 9.1 separately refers to anonymized development data where consent has been given. The general service processing license covers delivery, maintenance, fixes, security and legal obligations. It does not override the express training consent requirement, and no default training permission is stated for a new customer.
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?
Customers may remove or archive their data at any time through the platform under section 9.4, and may request removal of their own data when the agreement ends. Signature verification information follows a separate rule requiring signer consent. The privacy policy supplies a broader service data retention period with legal exceptions. No explicit zero retention setting or separate fixed period for assistant prompts and answers is specified.
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?
AI imports are private in the importing user's contract view until shared directly or moved to a shared space. Space access separates viewing, contract management and space management, while external collaborators receive view rights only. Company user groups can also receive access, with direct permissions surviving removal from a group. This is Contractbook's own access model, without an identified connection that inherits a firm's document system ethical walls.
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 9.8 requires written notice before legally compelled disclosure whenever possible. The confidentiality clauses also permit information to be supplied to other signers of an agreement completed through the platform. The privacy policy covers legal obligations and requests from authorities. No transparency report accompanies these commitments. The separate Disclosure Policy concerns security vulnerability reporting and does not describe the handling of subpoenas or other demands for customer contracts.
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?
AI Import processes the customer's legacy agreements and points extracted fields back to text in those files. The contract assistant also works with the selected agreement, while customers can create templates or use the vendor's template library. No licensed case law or statute collection is identified for those functions. The supplied templates are drafting material, and the agreement expressly distinguishes them from legal advice for the customer's situation.
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?
The platform's verification feature checks extracted information against the source contract, with highlighted passages and a completed verification marker. It does not track judicial treatment of cases or statutory amendments. The assistant can explain and rewrite clauses, but no connection to a legal citator or warning that an authority has been overturned is specified. Renewal reminders and signature status concern the agreement's lifecycle, rather than the legal status of an authority.
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?
Reviewers can inspect AI extracted fields beside highlighted source passages and verify them individually or together. They can also cancel an import during processing, which discards the file. These controls let a person check the extraction, but no explicit unsupported answer response or confidence indicator is described for the conversational assistant. The option to stop an upload is a user action, not a model refusal when information is insufficient.
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?
No court order or disciplinary record concerning fabricated legal citations from Contractbook appears in the AI Hallucination Cases database. The product extracts data from customer agreements and offers questions, summaries and clause revisions within its contract workspace. That database result does not measure extraction or drafting accuracy. Its source highlights support a user's review of contract data, without constituting a check of every legal assertion produced by the assistant.
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?
The service terms limit the platform to business users and explain that the template library does not provide legal advice. Legal departments can control templates, permissions and review steps for other employees. No named bar opinion, jurisdiction specific competence requirement or product mapping to professional ethics guidance accompanies these controls. The statement that the service is a business tool does not specify how a lawyer should record supervision of its AI functions.
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?
The stated buyers are business teams managing their own sales, employment, supplier and compliance agreements. Named legal customers include internal counsel at Lenus, GANNI and Pave, and the product describes savings in their contract administration. Bizzkit reports less manual extraction work on legacy agreements. No law firm client billing workflow is identified in the current buyer materials, and those savings relate to the organization's own time and contracting costs.
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 processor register names Google Cloud for platform hosting and Azure for the language model, both in the EU, alongside supporting providers and their locations. Customer terms set a training consent requirement and confidentiality duties. The data processing agreement is generated through a workflow that requests customer details and acceptance of terms. No separate client consent pack or exact model version inventory accompanies the public processor register.
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?
Imported agreements retain extracted fields, highlighted source passages and a verification state that users can inspect in the contract view. The application also tracks versions, collaboration and signature activity. These elements provide part of the record of a user's review, without a specified export connecting each AI response to its model version and a named human verifier. No court specific certification form or complete AI disclosure bundle is described.
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.
- AI Governance and Bias Disclosure
- Good Law Verification
- Refusal and Uncertainty Behavior
- Bar Guidance Alignment
Which one fits
Choose Contractbook if
- The first problem is extracting usable data from legacy agreements.
- HubSpot should populate contracts and receive completed agreement information.
- Small or midsize business contracting is the intended operating model.
Choose Lexagle if
- Contract compliance must directly control movement toward signature.
- Approval results need protection against later external modifications.
- Legal reviewers want plain English rules for payment, liability and jurisdiction.
In summary
Contractbook
Contractbook combines AI Import, a contract assistant, signatures and obligation tracking. Shared spaces govern repository access, and integrations with HubSpot, Salesforce, Zapier, Make and APIs can connect contract information to business events.
Lexagle
Lexagle supports negotiation and execution in internal and external rooms. Document Guard applies customer playbooks before signing and reruns the review when a protected file is changed, with separate Lexie assistance for drafts and questions.
Questions buyers ask
How can a reviewer verify Contractbook's imported fields?
AI Import links values to highlighted passages in the original agreement. A person verifies the information before it drives reminders or automated actions, which is different from Lexagle's compliance state assignment. From the AI Legal Index, based on each vendor's own published materials as of October 16, 2026. No vendor pays for placement.
Do these products disclose a comparable entry subscription?
Their commercial structures differ. Contractbook describes named packages with users, templates, signed agreements and automation; Lexagle prepares a custom proposal around modules and implementation needs. From the AI Legal Index, based on each vendor's own published materials as of October 16, 2026. No vendor pays for placement.
Does Contractbook still operate as an independent product?
Scrive acquired Contractbook in June 2025, and the service continues under the Contractbook name. The purchase decision should use Contractbook's current package and contractual terms. From the AI Legal Index, based on each vendor's own published materials as of October 16, 2026. No vendor pays for placement.
What separates their customer data permissions?
The agreement governing each service matters more than a general privacy assurance. For these two products, AI Legal Index identifies required consent for Contractbook model training and a defined aggregated or nonidentifying data permission at Lexagle.
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.
Contractbook's current packaging and Scrive ownership are reflected here. Lexagle's proposed modules determine the scope of its quoted subscription.