The cap refers to three months of fees.
This observation describes the selected text. Whether the position is appropriate is a separate question for the lawyer, the matter instructions and the agreed scope.
Source location / Clause 11.2Margo by Margo Legal
In controlled development. Not available for confidential live client matters.
Keep legal work moving.
Margo is being built to help you ask, check and draft alongside your documents, with less switching between tools.
Synthetic document / No client data
Customer agreement
11.2 The Supplier’s total liability shall not exceed fees paid in the previous three months.
MargoSource linked · Clause 11.2
A position to review.
Illustrative interface concept. Synthetic document.
Fictional demoCommercial agreement · excerpt
11. Limitation of liability
11.1 Neither party excludes liability for fraud or any liability that cannot lawfully be excluded.
11.2 The Supplier’s total liability shall not exceed fees paid in the previous three months.
11.3 All indirect and consequential loss is excluded.
Illustrative clause only. Not legal drafting guidance.
Ambient, not hidden. Every answer shows its source.
This illustration does not access your screen, microphone or documents.
The companion direction
Your work is the centre.
The conversation is one part.
Margo is a governed legal-AI workspace and document companion in controlled development. The direction is simple: keep the document in view, bring the relevant evidence beside it, and leave the next decision with the lawyer.
Beside the work
One matter.
Different moments.
A contract, an open document, a set of review materials. These illustrative interface concepts explore the same relationship. They do not depict a shipping desktop overlay or support for arbitrary applications.
Synthetic document / No client data
The open document
11.2 The Supplier’s total liability shall not exceed fees paid in the previous three months.
MargoIllustrative approval state
No change applied.
Fictional matter / No client data
Review materials
- Customer agreement Document
- Review instructions Scope
- Issues for consideration Review
MargoOne connected matter
Context before action.
Illustrative clauses only. Not legal drafting guidance. The public preview does not process documents.
An answer with a receipt
Read the finding.
Check the source.
11. Limitation of liability
11.2 The Supplier’s total liability shall not exceed fees paid in the previous three months.
Illustrative clause only. Not legal drafting guidance.
The source above is the same text shown in the demonstration. The design keeps the finding traceable to text a lawyer can read.
Four stages. Three deliberate beats.
Context first.
Then a scoped review.
- 01 / Firm
Set the firm profile.
Begin with the firm context and its approved workflow and privacy boundaries.
- 02 / Matter + scope
Define this review.
Connect the matter, jurisdiction, contract type, represented side, law-as-of date and approved instructions.
- 03 / Review
Make the next call.
Examine the sources. Confirm, correct or reject findings before exporting or applying approved changes.
The underlying workflow retains four stages: firm, matter, scope and review. Lawyer approval is not compressed away.
Contract review / Local preview
Find the issue.
Keep the context.
A position to review.
Not a decision made.
Margo Assistant connects questions to the matter. Structured Review organises contract analysis into findings, positions, citations and lawyer decisions. A defined review scope keeps the relevant matter instructions beside the work.
Synthetic document / No client data
Customer agreement
11.2 The Supplier’s total liability shall not exceed fees paid in the previous three months.
Fictional workflow / No client data
Review instructions
- Jurisdiction
- England and Wales
- Contract type
- Commercial agreement
- Represented side
- To be confirmed
- Law-as-of date
- To be confirmed
Workflows / Framework implemented
Your way of working.
Made reviewable.
Reusable instructions, with their boundaries intact.
The local workflow framework supports versioned instructions scoped by jurisdiction, contract type, represented side and effective date. Projects and Library keep documents, reviews and reusable materials connected to the relevant matter.
Rights, legal quality and model evaluation remain release gates. A framework is not an approved legal workflow.
Microsoft Word / Design direction
The final word
is yours.
The open document stays the working document.
The Word direction is to keep review beside the open document, with a lawyer approving any proposed edit. This public scene is an interface concept, not evidence of a qualified Word integration.
Controlled development and live qualification remain separate. This scene illustrates the approval boundary, not a running add-in.
Synthetic document / No client data
11. Limitation of liability
11.2 The Supplier’s total liability shall not exceed fees paid in the previous three months.
Illustrative disclosure / No live model call
Review route record
- Model and provider
- Approved route required
- Firm privacy profile
- To be confirmed
- Processing region
- Deployment evidence pending
- Retention terms
- Contract review pending
Models and providers / Qualification pending
The route matters.
So do its terms.
A model name is not a privacy commitment.
The disclosure direction is to make the model and provider handling a task explicit. Approved routes, provider retention, subprocessors and support-access terms must be confirmed for the relevant deployment.
This public preview makes no model calls. It does not promise a particular provider, automatic substitution or live regional availability.
England and Wales first
One defined workflow. A stated jurisdiction.
The first scope is England and Wales only: commercial-contract teams at boutique firms reviewing supplier-side customer paper. NDAs, MSAs and supplier agreements come first. A contract's governing law and the location of its processing are separate decisions; a UK legal scope is not a data-residency promise.
England and Wales workflow
Qualification remains open. The public preview is not a deployed client-matter service.
Distinct decisions
Hosting and provider route
Qualification remains open. The public preview is not a deployed client-matter service.
Status note: Regional availability and residency claims will be published only after the relevant deployment, provider settings and contractual evidence have been verified.
Security architecture and product status
Trust claims should show their evidence state.
Local controls are not presented as production proof. Exact data location, provider retention, subprocessors and support-access terms must be verified before a client-matter deployment.
Implemented locallyDeployment evidence pendingContract review pendingProduction proof required
Firm and matter separation
Per-firm isolation and matter-access controls have local synthetic tests. Independent technical assurance and production isolation proof remain pending.
Access and identity
Authentication and per-firm isolation have local test evidence. Independent assurance and deployment-specific identity controls remain gates before confidential client use.
Document controls
Current extraction qualification covers synthetic TXT, Markdown and CSV. PDF and DOCX are not qualified. This website does not accept documents.
Audit boundaries
The local build includes a per-firm audit log and CSV export. Retention and handling of document-derived evidence require an approved policy; no content-free logging guarantee is made here.
Lifecycle controls
The retention policy, backup and restore behaviour require implementation qualification and owner approval before any customer-data claim.
Incident preparation
Incident-response, malware and restore exercises remain launch gates rather than published assurances.
Product status
A bounded build. Evidence before access.
The current build is being tested with synthetic text. There is no production client-matter deployment. Hosting location, provider terms, independent security review and recovery evidence remain open.
What you can review
The product concept, workflow model, local interface and current boundaries.
What you cannot do
Upload confidential documents, start a live matter or rely on the preview for legal work.
What opens access
Deployment evidence, provider contracts, legal-workflow review, security exercises and an approved trust pack.
Frequently asked questions
What the preview does and does not mean.
What is Margo?
Margo is a contextual legal-AI assistant in controlled development. Its companion interface is a design concept; the product modules cover governed commercial-contract review, structured analysis and reusable firm workflows.
Is it recording my screen or listening to audio?
No. This public illustration does not access your screen or microphone. The companion panel is an interface concept, not an implemented desktop overlay.
Does it read my documents?
Not on this page. The demonstration uses a fictional clause embedded in the page and does not process documents. The local product preview includes document workflows, but confidential live client documents are not authorised today.
Can others see the companion?
The illustration makes no concealment promise. Future visibility, sharing and access behaviour must be qualified for the relevant product surface and firm controls. Do not treat the concept as a private layer over other applications.
Does Margo replace lawyers?
No. Margo is assistive technology. A qualified lawyer remains responsible for reviewing and approving its output.
Which jurisdictions does Margo support?
The initial scope is England and Wales only, for supplier-side review of NDAs, MSAs and supplier agreements. Legal quality still requires qualified-lawyer review. Other jurisdictions are outside this release scope.
Where is data stored?
The production hosting location is not yet selected. Data-flow, retention and provider commitments will be published only after they are verified for the proposed deployment.
Does Margo train models on firm data?
Training and retention terms depend on the approved model route and contracted provider controls for the relevant deployment.
Does it work in Microsoft Word?
Word is a planned delivery surface. This page illustrates it; it does not run an add-in or demonstrate qualified document editing.
Can we upload live client documents today?
No. Margo is currently in controlled development. It is not yet available for confidential live client matters.
How are workflows governed?
Workflows are versioned and can record jurisdiction, law-as-of date, contract type, represented side, provenance and review status. Rights, legal quality and model evaluation remain release gates.
AI-use notice
Margo uses assistive AI within bounded workflows. Outputs require appropriately qualified legal review before use or communication.
Cookie notice
Optional Google Analytics 4 stays off unless a visitor accepts analytics. Margo Legal uses no advertising pixels or session-replay tools.
Accessibility
The preview uses semantic landmarks, keyboard-operable navigation, visible focus states and reduced-motion support. Report an access problem by email.
Explore the fit
Bring the workflow.
Keep the judgment.
Discuss your firm’s needs and the current product boundaries.
Please do not send confidential client material.