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 ClickoAI
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.
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
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.
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 / Beta
The final word
is yours.
The open document stays the working document.
A Margo Word add-in is in beta. It can work with the open document, run approved actions and apply approved suggestions as tracked changes. The lawyer reviews the wording and context before a change is applied.
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.
UK and US architecture
Built around separate firm data and legal-jurisdiction decisions.
Margo is being designed for independently operated UK and US data planes. A firm’s approved privacy profile determines where its confidential data is processed. The governing law of a matter remains separate workflow metadata and does not silently move the matter between regions.
UK data plane
A separately operated application, API and identity route, subject to deployment and provider evidence.
Separated
US data plane
A separately operated application, API and identity route, subject to deployment and provider evidence.
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 will be confirmed contractually for each deployed region.
Implemented locallyDeployment evidence pendingContract review pendingProduction proof required
Firm and matter separation
The architecture separates firms, matters, memberships and restricted matters. Production isolation proof remains pending.
Access and identity
Roles, invitations, suspension, offboarding and firm-required MFA are implemented locally. SAML and SCIM foundations exist, but live identity-provider proof remains pending.
Document controls
Quarantine, parser isolation and provider allowlists have local foundations. Production qualification remains open.
Audit boundaries
Metadata-only audit controls are designed to retain review evidence without copying document content into logs.
Lifecycle controls
Retention, deletion, legal hold and recovery foundations require deployment exercises and evidence.
Incident preparation
Incident-response, malware and restore exercises remain launch gates rather than published assurances.
Product status
Extensive local product. Controlled public claims.
Margo has not been deployed into separate production UK and US cloud planes. Provider contracts, regional evidence, lawyer qualification, recovery exercises and the final trust pack 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 workflow model separates England and Wales, US federal law and individual US states. A jurisdiction is offered only when the relevant workflow and evaluation material have been reviewed.
Where is data stored?
Margo is being prepared for separate UK and US deployments. Exact commitments will be stated for each contracted deployment after infrastructure and provider evidence are verified.
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?
A Margo Word add-in is in beta. It can work with the open document, run approved actions and apply suggestions as tracked changes.
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. ClickoAI 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.