Contract Agent

It depends on the clause type and how clearly your playbook states each position, which is why the pilot runs on one of your own agreements first. Every deviation is quoted in full for a person to accept or reject, so accuracy determines how much reading Pegasus saves, not whether a risk can slip through unseen.

Neither. Pegasus does the first pass that counsel used to do by reading end to end, and counsel keeps every decision. Contracts stay in SharePoint, Google Drive, Box, Dropbox or Salesforce. If you run a CLM, Pegasus reads from it and writes findings back.

A playbook is your standard position on each clause type: the liability cap you accept, the notice period you require, the jurisdictions you allow. Most teams hold this in people's heads rather than a document. During the pilot we write down the positions for the clause types that matter most and refine from there.

Documents stay in your repositories under your existing access controls. Pegasus connects through credentialed, scoped integrations you can revoke at any time, does not become a store of your contracts, and logs every action under CIP governance so you can see exactly what was read and by which process.

You get every finding from your sample agreement, the playbook positions we used, and a plain recommendation on whether a deployment makes sense for your volume. If it does, the Contract Agent goes live against your repository with the same playbook, typically within days rather than months.