Define the pilot
The teams intend to test a shared workshop booking process from 6 September to 17 October 2027. The pilot covers scheduling and orientation.
Use Gixo when teams need a memorandum of understanding shaped by collaboration scope, party responsibilities, confidentiality terms, and binding-section logic before formal agreement drafting or review.
An AI memorandum of understanding generator prepares MOU first drafts by structuring collaboration scope, party responsibilities, confidentiality and IP terms, and binding-vs-non-binding sections before formal review. Gixo supports up to 10 parties on a single MOU, keeps binding and intent sections explicit, and can use prior MOUs or reference files to inform the draft. It exports to PDF, DOCX, HTML, and TXT and does not provide legal advice or replace professional review.
Lex · worked example
The fictional draft sets out what Calder Studio and Alder Works intend to contribute to a six-week workshop pilot. Each party has an owner, deliverables and dates. The reviewer can see which terms still require a decision.
The teams intend to test a shared workshop booking process from 6 September to 17 October 2027. The pilot covers scheduling and orientation.
Calder's operations lead supplies the space, equipment list and safety briefing. Alder's program lead coordinates participants and provides weekly feedback.
The parties still need to agree on the cost split, access to participant data and ownership of jointly prepared materials. The draft assigns owners and a review date.
Scope and deliverables are marked as statements of intent in the example. Confidentiality and any terms intended to bind go to counsel for review and approval.
The fictional example shows how to record responsibilities, open terms and review decisions for qualified counsel.
The job is not to ask AI for a legal answer. The job is to prepare a draft or artifact that a qualified reviewer can actually work with.
Capture the reason for the arrangement, what each side is doing, and how the work is meant to progress before drafting begins.
Bring the obligations, milestones, and resource commitments into the draft instead of leaving them as loose narrative.
Shape the first draft around the confidentiality, data-sharing, or IP assumptions reviewers will need to see clearly.
Make it explicit which sections are meant to bind and which sections are still statements of intent before a final contract.
Reference files and governing context can shape the draft. Cited sources can show which draft sentences are supported by supplied reference files. This in-app support does not establish legal authority or statutory compliance and is not inserted into the contract or its exports; reviewers still check the facts and law independently.
After the first draft, Lex runs an AI contract review of the whole contract, with every quotation checked against the text, beside rule checks: clause coverage against a versioned playbook, clause-conflict detection, and defined-term and cross-reference checks. Findings, tracked-change DOCX redlines, comments, review state, assignees, due dates, and version history all stay attached to the same document. A contract imported from Word can go back as that same DOCX, with the Lex edits shown as Word tracked changes; where Lex cannot track an edit faithfully, such as inside a field, an existing revision, a header or a footer, it refuses the export instead of altering the document. Reviewers still verify every clause and conclusion.
Start with the collaboration type, the parties involved, and the purpose of the arrangement.
Define deliverables, milestones, responsibilities, and resource commitments before the first draft is generated.
Bring confidentiality, IP, exclusivity, and any other binding logic into the workflow so the reviewer sees the distinction clearly.
After the first draft, Lex runs an AI contract review of the whole contract, with every quotation checked against the text, beside rule checks: clause coverage against a versioned playbook, clause-conflict detection, and defined-term and cross-reference checks. Findings, tracked-change DOCX redlines, comments, review state, assignees, due dates, and version history all stay attached to the same document. A contract imported from Word can go back as that same DOCX, with the Lex edits shown as Word tracked changes; where Lex cannot track an edit faithfully, such as inside a field, an existing revision, a header or a footer, it refuses the export instead of altering the document. Reviewers still verify every clause and conclusion. Agreement Packs connect related documents, proposed party and obligation facts, version-bound approval receipts, and execution records on the same matter. Fields stay proposed until a reviewer confirms, disputes, or marks them inapplicable. Then export in PDF, DOCX, HTML, and TXT.
| Capability | Gixo | Static templates | General AI | Outside counsel |
|---|---|---|---|---|
| Main job | Structured first-draft preparation | Generic forms | Prompt output | Custom drafting |
| Multi-party collaboration structure | Up to 10 parties | Check its party limit | Test on the same inputs | Any number |
| Turnaround to first reviewable draft | Measure the same task | Measure the same task | Measure the same task | Measure the same task |
| Binding/non-binding distinction | Structured | Test on the same inputs | Test on the same inputs | Yes |
| Reference-file input | Yes | Ask if it accepts your files | Paste or upload; verify current support | Yes |
| Legal advice | Not included | No | No | Professional |
The other columns describe what each kind of tool is generally for, not a test of a named product, and products differ. Ask how many parties it takes, whether it accepts a prior MOU, and how it marks which sections bind. Run the same brief and reference files through anything on your shortlist, then compare the draft, the review trail and the export.
Updated