The queue is the job. Give most of it away.

Why legal becomes the slowest step

Not because the work is hard, but because every request arrives as an unstructured ask with no context and no boundary on what sales may concede.

• A shared inbox and a template folder: Requests arrive as “can you look at this?” with the document missing
• A shared inbox and a template folder: Sales negotiates terms in email, then asks legal to ratify them
• A shared inbox and a template folder: The same five questions get answered individually, forever
• A shared inbox and a template folder: Nobody knows which version the counterparty actually has
• A shared inbox and a template folder: Approval is an email reply that is not attached to any version
• A shared inbox and a template folder: Renewal dates live in a spreadsheet someone stopped maintaining
• A playbook and an assistant: Requests arrive as a room with the paper, the parties and the ask attached
• A playbook and an assistant: Positions sales may take are encoded, so concessions stay inside policy
• A playbook and an assistant: The known answers execute without reaching a lawyer at all
• A playbook and an assistant: One live instrument, so version is a fact rather than a guess
• A playbook and an assistant: Approvals bind to the exact version and the approver's identity
• A playbook and an assistant: Dates and obligations are extracted from the executed document

Four decisions that hand over the standard work

Delegating to an agent is a policy exercise, not a prompt. You are writing down the judgement you already apply by reflex.

• Name the paper you will sign — Your order form, your NDA, your DPA-style data terms, your standard services agreement. These become templates in a library your team controls.
• Write the playbook — For each clause: your preferred position, your fallback, and the point at which the answer stops being yours to give. This is the mandate the assistant works inside.
• Name the approvers — Which deviations need the GC, which need finance, which need the business owner. Gates attach to clauses, so a change to indemnity always finds the right person.
• Pick an autonomy level — Start in shadow mode and read the transcripts. Move to supervised when the assistant's proposals match what you would have written. The level is per playbook, not all-or-nothing.

Let the business close its own standard deals

The reason legal gets asked about everything is that nobody else can tell whether a request is standard. Encode that judgement once and the question answers itself.

• Structured intake — A request captures the counterparty, the paper, the value and the ask up front, so no agreement starts with a thread asking what the deal actually is.
• Triage before a lawyer looks — Inbound paper is compared against your standard and classified: matches, acceptable variation, or material deviation. Only the last category needs you.
• The assistant finishes the standard ones — It negotiates inside the playbook, routes the approvals it is required to collect, sends for signature and files the result — without a legal touch.
• Hard stops where they matter — Clauses you mark as always-escalate end the run every time, regardless of how small the proposed change looks. Policy is enforced as a boundary, not a reminder.

The part everyone forgets to budget for

Most contract pain is not negotiation. It is the eighteen months afterwards, when someone asks a question the signed document could answer if anyone could find it.

• Obligations as data — Term, notice windows, renewal triggers, caps and conditions are extracted from the executed agreement, so they are queryable instead of remembered.
• Renewals that surface themselves — Notice periods are known from the document, so a renewal appears before the window closes rather than after it has auto-extended.
• A clause library that improves — Positions that keep getting negotiated are visible as patterns, so the next version of your standard paper fixes the clause rather than re-arguing it.
• Answers without archaeology — What did we agree with this counterparty, which version did they sign, and who approved the deviation — answered from the record, with the evidence attached.
• Context that survives turnover — The room holds the conversation, the negotiation and the reasoning, so the next person does not inherit a PDF and a guess.
• An audit you do not assemble — Every version, approval, signature identity and agent action is already recorded. Producing the file is an export, not a project.

What in-house teams want settled first

• Does this mean sales can sign things without legal? Only what you have already decided is acceptable. The playbook is the delegation: inside it, the deal closes without you; at its edge, the run stops and waits for the approver you named. Removing legal from standard paper is the point — removing legal from judgement calls is not possible by design.
• How do we trust it before we rely on it? Shadow mode. The assistant drafts positions, proposes redlines and prepares escalations, but nothing reaches a counterparty. You read the transcripts against what you would have done, and move a playbook to supervised only when it stops surprising you.
• Our playbook is not written down anywhere. Most are not — they live in the head of whoever has been there longest. The practical path is to encode one narrow workflow first, usually NDAs or order forms, where the positions are obvious and the volume is high. The rest follows from the pattern.
• Who is accountable for what the assistant agreed? You are, which is why the record matters. Every turn is attributed, every approval binds to a version and an identity, and every agent action appears in the room timeline. There is no step where something was agreed and nobody can say by whom.