Make the intake specific
Supply the parties, document kind, jurisdiction, obligations, dates and reference material. Review imported content and retain its source identity before using it in a new matter.
Use Gixo when a services engagement needs a SOW first draft shaped by deliverables, acceptance criteria, milestones, pricing, and a clean reference back to the master agreement before counsel review and signature.
An AI SOW generator drafts a statement of work with deliverables, acceptance criteria, milestones, dependencies, and a pricing model. Gixo prompts for the governing master-agreement reference and prepares a separate SOW draft with a deliverables matrix, change-order structure, review state, and export. It does not automatically link documents or validate inherited terms; qualified reviewers confirm every cross-document relationship.
This is a real Lex export for invented parties. Inspect the input and clauses as a worked example, with professional review kept separate from automated drafting and checks.
A consulting agreement of 26 numbered clauses between two invented parties: scope, services, deliverables, exclusions, fees and expenses, intellectual property, confidentiality, liability, termination, notices, governing law and signature blocks. Its first page says the parties, people and addresses are invented and that it is a worked example, not a legal document.
Draft a Consulting Agreement: repairs satisfaction measurement between Larkfield Analytics Ltd (Consultant) and Harbourside Housing Association (Client). Governing law: England and Wales. Effective date: 2027-02-01. Term: Ten weeks from the effective date. Confidentiality: Three years after the engagement ends. The Consultant will review the Client's current repairs satisfaction survey and the data behind it, recommend a method for measuring repairs satisfaction by contractor, and leave the Client with a reporting approach that the repairs team and the board can use. Excluded: building or buying software, and running surveys. Dependencies: the Client provides the survey data within five working days of the effective date and two days a week of its operations manager's time. State on the first page that the parties, people and addresses in this agreement are invented and that it is a worked example, not a legal document. Keep the agreement short and plain. The notice email address of Larkfield Analytics Ltd is notices@larkfield-analytics.example and of Harbourside Housing Association is notices@harbourside-housing.example (both invented).
Read mechanically against the intake, not by a lawyer: all 12 facts the intake gave (names, registration numbers, addresses, representatives, the effective date and the governing law) are in the draft, nothing is left as a placeholder, and it states two terms the intake did not give, 30 days and 10 business days, which Lex chose.
Supply the parties, document kind, jurisdiction, obligations, dates and reference material. Review imported content and retain its source identity before using it in a new matter.
Use the legal workspace's permitted structural tools, Draft Checks and review paths. Compare proposed changes with the saved draft and original material; unsupported Word edits must be handled explicitly.
Have qualified counsel review enforceability, local requirements and the actual commercial intent. Check the current approval state and the downloaded document after a change.
Select the target clause and give Ask Lex a bounded instruction. Missing facts remain visible for review. Inspect the before-and-after proposal, required clause checks and any explicit outside-matrix or mandatory-clause override before versioned application. Use the legal workspace's structural allowlist rather than assuming every general content-editor block is available.
Inspect immutable playbook versions, anchored findings, provenance and precedent variants before staging a change. Matters retain original sources, quotation findings and source-version comparisons. Review extracted obligations for timing, ownership and source revision; negotiation turns and agreement-pack review cells have their own decisions and current-version requirements.
Original-format Word export, tracked changes against an original and saved-version redlines are separate paths. Unsupported edits must be surfaced rather than silently claimed as preserved. Inspect the layout, validator notes and downloaded file, then retain its delivery receipt. Counsel's review applies to the actual matter and version.
Every contract in Lex, drafted or imported, gets an AI contract review: each clause the document type expects marked present, weak or absent; up to 25 risks with a level, the party each falls on, why it matters and replacement wording; and provisions that cannot both be followed. Every quotation is checked against the contract text, findings are decided before approval, and there is no single risk score. The same review reads the key terms and obligations with the words they quote and proposes them into the Agreement Pack. Review every document puts up to 25 documents of an Agreement Pack, or up to 200 in a matter, into one table with your own questions as columns and an Excel export. Approvers can be named in order, and signing supports up to 10 signers with an optional signing order and automatic reminders; it is a simple electronic signature, not a qualified one. A qualified reviewer still decides what the contract says.
Lex does not provide legal advice or certify compliance. The public specimen is not a universally reusable legal template. Word fidelity depends on the supported original-document and saved-version path; unrestricted Power Edit and image insertion are not legal editing features.
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 deliverables with acceptance criteria, owner, dependency, and review path so the SOW reads as an execution document, not a wish list.
Bring milestone dates, dependencies, contingency reserves, and acceptance windows into the draft instead of retrofitting them after kickoff.
Time-and-materials, fixed-fee, milestone-based, retainer, or hybrid — capture the right pricing structure with rate cards, caps, and overage handling.
Capture the master-agreement reference and intended relationship. Reviewers verify IP, confidentiality, liability, and warranty terms against the signed MSA.
Define the change-order trigger, the approval path, the fee impact, and the timeline impact before scope shifts during execution.
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.
Define the services, the duration, the team, the location, and the business outcome the engagement is buying.
Define each deliverable with the criteria that decide done, the owner, and the dependencies blocking it.
Add the governing MSA context, then verify the contractual framework, IP terms, and confidentiality scope against the signed agreement.
Review with project leads and counsel inside the workspace, then export in PDF, DOCX, HTML, and TXT for signature.
| Capability | Gixo | Word template | Generic AI | Project mgmt tool |
|---|---|---|---|---|
| SOW-shaped intake (scope, deliverables, pricing) | Structured | Form fields only | Test on the same inputs | Task list |
| Master-agreement reference field | Structured drafting input; reviewer verification required | Manual paste | Manual | Ask the vendor |
| Acceptance criteria per deliverable | First-class | Free text | Variable | Variable |
| Change-order and overage handling | Structured | Free text | Variable | Ask the vendor |
| Optional reference-file input from prior SOWs | Supported | Test on the same inputs | Paste or upload; verify current support | Ask the vendor |
The other columns describe what each kind of tool is generally for, not a test of a named product, and products differ. Run the same brief and reference files through anything on your shortlist, then compare the draft, the review trail and the export.
Updated