Your Clients’ Agents Need a Lawyer

AUGUST / PRODUCT ANNOUNCEMENT

Your clients are adopting agents. Those agents are beginning to buy, negotiate, send, share and act across the business. Eventually, one of them will reach a question it cannot safely answer alone: Can I sign this? Can I send this file? Does this agreement permit what I am about to do?

Today, that agent has two bad choices. It can guess, creating risk. Or it can stop, giving the work back to a person and breaking the automation. There should be a third choice: ask the company’s lawyer.

Today, we are launching August for Agents in beta. It lets a client’s agent call legal services built and supervised by the client’s existing law firm. The firm’s agents run on August. The lawyers remain responsible for the legal work. August provides the infrastructure that makes the service available, governed and auditable.

August already helps firms turn repeatable legal work into software their lawyers can supervise. August for Agents makes that work available inside the systems where clients’ agents operate. The result is simple: when an agent needs legal help, the firm can be there.

The interface to professional services is changing. People will still call and email their lawyers, but software will increasingly initiate the first request. If the firm cannot receive it, the agent may route around the firm and turn to a generic model, an unapproved provider or no legal review at all.

A legal service an agent can call

Imagine a procurement agent preparing to renew a vendor agreement. It finds a clause restricting how customer data may be processed. The agent could invent an interpretation. It could halt the renewal and open a ticket. Or it could send the relevant clause, the proposed action and the company’s approved context to a service operated by the company’s law firm.

The firm’s agent checks the agreement and the firm’s playbook. It returns a sourced answer if the issue falls within its mandate. If the question requires judgment, it routes the matter to a lawyer. The client’s system receives an answer it can use, along with a record of what was asked, what sources were consulted and what happened next.

The same pattern can support an agent deciding whether a marketing claim is approved, whether a data transfer fits an existing agreement or which form of nondisclosure agreement to send. The legal service does not need authority over the entire workflow. It can answer one bounded question, propose a permitted next step or require human review before anything consequential occurs.

That is the product: a sanctioned path from a client’s agent to the law firm the client already trusts.

The client does not need to replace its agents. The firm does not become a generic software vendor. Each side keeps its role. The client controls the business workflow and the authority of its agent. The firm defines the legal service, the sources it may use and the point at which a lawyer must step in. August connects the two.

For the firm, this creates a new delivery channel without turning its advice into an ungoverned chatbot. A practice group can encode recurring issues, maintain the relevant materials and set clear limits. Lawyers spend less time rebuilding routine context and more time on decisions that require them. The service becomes easier to use without becoming detached from the lawyers who stand behind it.

Rules the agent cannot talk around

An instruction in a prompt is not the same as a control in a system. “Do not email anyone outside this list” is guidance. A server that refuses every other recipient is a control. One asks the model to behave. The other limits what the system can do.

Legal work needs the second kind. A capable model can still misunderstand a request, follow a malicious instruction hidden in a document or report success when an action failed. The answer is not a longer warning in the prompt. It is an architecture that assumes the model can be wrong and contains the consequences.

Scoped authority. The service can use only the tools, recipients and data sources approved for that task.

Verifiable work. Material statements can be tied to the documents or authorities that support them, and completed actions are recorded by the system.

Deliberate escalation. The firm decides which questions an agent may answer and which must go to a lawyer.

Governed access. Identity, permissions and retention can be set for the client, the firm and the service instead of being left to the model.

These controls also matter when the instruction is coming from a person. A lawyer, employee or client may ask an agent to do something outside policy. The system should not treat human involvement as automatic approval. It should refuse, narrow the action or escalate it according to the firm’s rules.

Every response has two audiences. The client’s agent needs a clear result it can act on. The supervising lawyer needs enough evidence to understand how that result was produced. August keeps those needs together: structured outputs for the workflow, supporting sources and an execution record for review. Confidence is not treated as proof, and a polished sentence is not treated as a completed action.

The firm remains the lawyer

The legal profession’s core duties do not disappear when software performs part of the work. Confidential information still needs protection. Legal claims still need support. Communications still need to respect professional rules. Lawyers still need to understand the technology they supervise and communicate clearly with the client about how it is being used.

Traditional workflows relied on a person to notice when a matter crossed a line: a represented counterparty, an unsupported citation, an ethical wall or an incomplete filing. In an agent workflow, those safeguards must be designed into the service. The system should make the permitted path easy, the prohibited path unavailable and the uncertain path visible to a lawyer.

August for Agents is designed around that allocation of responsibility. It is not a substitute law firm, and it does not ask a client to trust an anonymous legal answer from the open internet. It gives the client’s chosen firm a new way to deliver work: faster than a traditional intake process, but still within a service the firm defines and supervises.

That distinction is commercially important. Firms have spent years earning trust, learning how their clients operate and developing positions on the issues that recur. Client agents should be able to use that institutional knowledge instead of starting from zero every time. And firms should be able to serve the new software actors appearing inside their clients without surrendering the relationship to a general-purpose platform.

What still needs judgment

Not every legal question should be automated. Some requests are ambiguous. Some involve a conflict, a novel issue or consequences too significant for a preapproved workflow. August for Agents is useful precisely because the boundary can be explicit. The routine path can move quickly; the exceptional path can reach a lawyer with the relevant context already assembled.

Questions about privilege, identity and authority also need care. Whether a communication is privileged depends on its purpose, participants and jurisdiction. Calling it an “agent” conversation does not determine that status. Credentials should be narrow enough to identify the client, the task and the authority granted without giving an external system broad access to firm or client data.

The right scope will differ by service. An answer about an approved contract term may require access to one agreement and one playbook. A request involving litigation, regulated data or a new counterparty may require additional checks before the firm accepts it. That is why August for Agents is built around explicit permissions and escalation, not a single blanket authorization.

These are not reasons to keep legal services outside agent workflows. They are reasons to build the connection deliberately, with the same seriousness firms apply to conflicts, confidentiality and client intake.

Give agents a third option

Agents are becoming an interface to the business. They will encounter legal questions because legal questions are embedded in ordinary business decisions: what can be signed, shared, promised, purchased or changed.

A company should not have to choose between an agent that guesses and an agent that stops. Its agents should be able to ask its lawyers. Its lawyers should be able to answer through a service they control. And every important action should remain bounded, reviewable and accountable.

Your clients’ agents need a lawyer. August for Agents gives them a way to reach your firm.

Contact August to learn more about the beta and discuss your firm’s first service.