Announcing o11's backing from Y Combinator.
Legal Teams: AI Contract Drafting in Google Docs
A commercial legal team at a mid-market company might handle 40 to 60 contracts per month. NDAs, vendor agreements, SaaS subscriptions, employment offers, partnership terms, amendment letters. Each one requires drafting or reviewing language with precision, checking for internal consistency, and ensuring alignment with the company’s current risk posture. And each one competes for time with the other 39 to 59.
The bottleneck is rarely legal judgment. Experienced attorneys know what a mutual indemnification clause should say. They know when a limitation of liability is too narrow. The bottleneck is the mechanical work surrounding that judgment: locating the right precedent clause from a prior agreement, adapting boilerplate to the current deal’s specifics, cross-referencing defined terms across a 30-page document, and formatting the final version for execution.
This mechanical work accounts for an estimated 60 percent of contract cycle time. It is the reason a straightforward vendor agreement that should take an hour to draft takes half a day. It is the reason outside counsel bills pile up for work that feels like it should be faster. And it is the reason legal teams are perpetually understaffed relative to the volume of agreements flowing through the business.
Contract Drafting from Term Sheets and Deal Parameters
Most contracts begin life as a set of business terms. A sales team closes a deal with specific pricing, payment terms, and service levels. A procurement manager negotiates vendor rates and delivery schedules. These terms arrive as a term sheet, an email, or a row in a Google Sheet. The legal team’s job is to turn those terms into enforceable language.
o11 For Google Docs works inside Google Docs where legal teams already draft and collaborate. Instead of opening a template, manually replacing bracketed placeholders, and searching old files for the right clause variants, you describe the agreement’s parameters.
“Draft a SaaS subscription agreement based on the following deal terms: 3-year term, $240,000 annual license fee, 99.5% uptime SLA, mutual indemnification, data processing addendum required, California governing law. Use our standard enterprise SaaS template as the base and adjust the limitation of liability to cap at 12 months of fees.”
o11 generates a complete first draft within Google Docs, using your organization’s existing template structure and clause language. The defined terms are consistent throughout. The cross-references are accurate. The attorney reviews for substance and business judgment rather than spending 45 minutes on find-and-replace operations.
“Swap the arbitration clause for our litigation carve-out version. Add a most-favored-customer pricing provision in Section 8 tied to the annual fee in Section 3.2.”
Iterative drafting happens through natural prompts rather than manual editing. The attorney directs the changes; o11 handles the document mechanics. Each revision maintains internal consistency, updating cross-references and defined terms automatically.
Clause Extraction and Comparison Across Agreement Versions
Contract review often involves comparing language across multiple versions of an agreement or across different agreements with the same counterparty. A vendor sends their paper. Your team needs to identify every deviation from your standard terms, flag provisions that shift risk, and prepare a redline that addresses each point.
This comparison work is where attorneys lose the most time. Reading two 25-page agreements side by side, tracking which clauses differ, and categorizing those differences by risk level is slow, tedious, and error-prone when done manually.
“Compare the vendor’s proposed Master Services Agreement in ‘Acme MSA v3’ with our standard MSA template. List every clause where their language differs from ours, categorize each deviation as favorable, neutral, or unfavorable to us, and flag any provision that is missing from their version entirely.”
o11 produces a structured comparison within Google Docs, organized by section. The legal team gets a clear map of where negotiation is needed instead of spending two hours reading to find the same information.
“Extract every indemnification, limitation of liability, and termination provision from the last 5 vendor agreements in the ‘Executed Contracts Q4’ folder. Create a comparison table showing how these clauses vary across vendors.”
This kind of cross-agreement analysis is invaluable for legal teams establishing or updating their standard positions. Instead of relying on institutional memory about what terms were accepted in past deals, the team has a documented comparison built from the actual executed language.
Legal Memo Creation from Case Research
In-house legal teams write internal memos to advise business stakeholders on regulatory questions, contractual risks, and compliance obligations. These memos draw from case research, statutory analysis, and the company’s own prior positions. Writing one from scratch typically takes half a day to a full day, depending on complexity.
The challenge is not the analysis itself. It is the assembly: organizing research findings into a structured memorandum format, ensuring citations are accurate, and presenting the conclusion in a way that a non-lawyer business partner can act on.
“Draft an internal legal memo analyzing our obligations under the new California data privacy amendments effective January 2027. Structure it with an executive summary, regulatory background, impact analysis for our three product lines, and recommended compliance steps. Reference the relevant statutory sections.”
o11 creates the memo framework in Google Docs with proper legal formatting, section structure, and placeholder citations that the attorney can verify and supplement. The attorney’s time goes toward validating the analysis and adding company-specific context rather than building the document from a blank page.
“Add a risk matrix to the memo showing each compliance requirement, our current status, the remediation effort required, and a recommended deadline. Format it as a table the VP of Product can review without reading the full memo.”
Legal writing that would take hours of formatting and organization happens in minutes. The attorney remains the author of the analysis. o11 handles the architecture of the document.
Before and After: The Contract Lifecycle
Before o11: A term sheet arrives from the sales team on Monday. The paralegal locates the most recent template, which may or may not reflect the latest approved clause updates. The associate spends Tuesday morning replacing placeholders and adapting clauses. The partner reviews Wednesday, finds two cross-reference errors and a defined term that was used but never defined. The associate fixes these Thursday morning. The clean draft goes to the counterparty Thursday afternoon. Four days, three people, roughly 10 billable hours of work.
After o11: The term sheet arrives Monday. The associate prompts o11 with the deal parameters and specifies the template. A complete draft appears in Google Docs within minutes, with consistent defined terms and accurate cross-references. The associate reviews for substance Monday afternoon, makes two prompt-based adjustments to the indemnification and termination provisions. The partner reviews Tuesday morning and approves with minor framing changes. The clean draft goes to the counterparty by Tuesday lunch. Two days, two people, roughly 3 hours of attorney time.
The reduction is not just in hours. It is in error rate. When cross-references and defined terms are maintained programmatically rather than manually, the category of errors that comes from human transcription largely disappears. For legal teams, fewer errors mean fewer amendment cycles and faster closings.
Why o11 Instead of a Generic AI Tool
Generic AI can write legal-sounding language. That is actually the problem. A chatbot that generates a plausible indemnification clause is dangerous if that clause does not match your company’s approved risk position, uses terms defined differently than in the rest of the agreement, or conflicts with the governing law provision three sections later.
o11 works inside Google Docs with your existing templates and clause libraries. It does not generate legal language from general training data. It drafts within the framework your legal team has already established, maintaining consistency with your approved terms and your document’s internal structure.
The distinction matters most in cross-referencing. A contract is a system of interlocking provisions. Change the definition of “Confidential Information” in Section 1, and it affects the confidentiality obligations in Section 7, the indemnification in Section 9, and the survival clause in Section 14. o11 understands these relationships within your document. A generic chatbot does not.
Legal teams adopting o11 are not automating legal judgment. They are eliminating the mechanical overhead that prevents their attorneys from spending more time on the work that actually requires a law degree: negotiation strategy, risk assessment, and business counseling.
