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 restrictive covenant draft needs jurisdiction-aware scope, duration, step-down language, and non-solicitation structure that an employment counsel reviewer can actually defend.
An AI non-compete agreement generator is a drafting tool that produces restrictive covenant agreements with jurisdiction-aware scope, duration, and step-down structure built in. Gixo's version captures geographic and industry scope, step-down duration options, non-solicitation terms (customer and employee, with any other restriction, such as a supplier non-solicit, added through your own drafting instructions), and garden-leave/consideration language in one draft, under the governing-law jurisdiction you choose. The draft is written to treat non-compete enforceability as jurisdiction-specific and to recommend local law review, which matters most in states such as California, North Dakota, Oklahoma, Massachusetts, and Washington, where enforceability is restricted, so check that position with employment counsel before the document is signed. It does not decide enforceability itself — that call stays with qualified employment counsel — but it surfaces the risk and produces a reviewable first draft in minutes rather than hours or days.
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 mutual non-disclosure agreement of 14 numbered clauses between two invented parties: definitions, what counts as confidential information, exclusions, the receiving party's obligations, permitted disclosures, return of materials, remedies, term, survival, governing law, notices and signature blocks. Its first page says it is a worked example, not a legal document.
Draft a Mutual Non-Disclosure Agreement between Larkfield Analytics Ltd (Party A) and Fenwick & Dale Stores Ltd (Party B). Governing law: England and Wales. Effective date: 2027-01-15. Term: Two years from the effective date. Confidentiality: Three years after disclosure. A mutual agreement: each party may disclose and receive confidential information. 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. The notice email address of Larkfield Analytics Ltd is notices@larkfield-analytics.example and of Fenwick & Dale Stores Ltd is notices@fenwick-dale.example (both invented).
Read mechanically against the intake, not by a lawyer: all 12 facts the intake gave are in the draft, nothing is left as a placeholder, and it states no term the intake did not give.
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 territory, industry vertical, customer segment, and competitor list so the scope is specific enough to defend in review.
Define primary restriction period, optional step-down phases, and fallback shorter durations so counsel can assess the intended fallback and its legal effect.
Layer in customer non-solicit and employee non-solicit terms with distinct scopes and durations from the non-compete itself; any further restriction, such as a supplier non-solicit, is added through your own drafting instructions.
Capture garden-leave compensation, severance-linked restrictions, and bonus-clawback structure so the consideration question is on the page.
Set the governing-law jurisdiction during intake. The draft treats enforceability as jurisdiction-specific and recommends local law review, so counsel checks restricted jurisdictions such as California, North Dakota, Oklahoma, Massachusetts, and Washington early instead of after signature. Lex does not detect or rank those jurisdictions itself.
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 role, the competitive concern, the legitimate business interest, and the jurisdiction the employee works in.
Define the activities restricted, the territory, the period, and the step-down options so the draft is specific and defensible.
Add customer and employee non-solicit terms with their own scope, capture the consideration paid for the restriction, and reference the underlying employment agreement.
Send to employment counsel inside the workspace, capture redlines and approval, then export in PDF, DOCX, HTML, and TXT.
What does an AI non-compete agreement generator draft include?
| Capability | Gixo | HR template | Generic AI | Employment counsel |
|---|---|---|---|---|
| Jurisdiction-aware enforceability prompts | Local-law review note | Generic only | Test on the same inputs | Yes |
| Step-down scope and duration | Structured | Manual edit | Variable | Yes |
| Non-solicit + non-compete in one draft | Built in | Two templates | Manual | Yes |
| Garden-leave and consideration captured | Yes | Test on the same inputs | Test on the same inputs | Yes |
| Time to first reviewable draft | Measure the same task | Measure the same task | Measure the same task | Measure the same task |
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