One draft, three reviewers, one agent
Here's a normal week at Halcyra Payments, a small fintech that processes payouts for marketplaces. Paul, who runs operations, asks his agent for a first draft of a mutual NDA with Riverstone Logistics, a new carrier. The agent pulls the standard NDA template, the standard term clause, and the residuals carve-out Paul prefers. It saves legal/mutual-nda.md and runs gander watch. Paul sends the link to Miriam (counsel), Ellen (finance), and the business owner (Paul himself).
Miriam opens it first and highlights the residuals section. "Our standard residuals clause is narrower. I'd remove it for a logistics partner." Paul replies in the same thread that they keep residuals for inbound logistics too. That's a conversation between two people, so it stays a normal thread. The agent never sees it.
Ellen reads the term clause and starts her own thread: "Term should be three years to match our standard. Two years is short for supplier relationships." Miriam agrees. Paul starts a new comment with agent connect: "@agent make the term three years and update every clause that references it." That lands in Paul's agent session, the one that wrote the draft and still has the standard clauses open. The agent edits the term in section 1, the survival reference in section 7, and replies in the thread with what changed. Everyone's tab updates. Miriam accepts the change in the browser.
When the draft is ready for outside counsel, the team sends a clean copy out of their existing workflow. The file on Paul's machine was the working draft the whole time.