Why vendor paper is the legal team's biggest time drain

The problem isn't the contracts. It's where they land.

When a vendor sends their standard Master Services Agreement or Data Processing Addendum, it arrives on their paper—meaning their preferred positions, their liability caps, their data retention schedules. The assumption baked into most legal workflows is that someone senior needs to review it. That assumption is costing enterprise legal teams somewhere between two and four hours per contract, on positions that were already decided at the playbook level six months ago.

Where the hours actually go

We analysed the negotiation activity across a cohort of enterprise legal teams managing between 150 and 600 vendor contracts per year. The breakdown is consistent enough to be useful:

Based on illustrative analysis of enterprise vendor negotiation workflows. Actual figures vary by industry, team size and contract volume.

The structural issue: legal review was designed for first principles

Legal review processes were built for the scenario where every contract deserves fresh eyes. That was appropriate when volume was low and contracts were genuinely varied. At scale, it creates a mismatch: the same analytical rigour is applied to a DPA with a 72-hour breach notification clause (which every enterprise has already decided how to handle) as to a novel indemnity structure in a strategic supplier agreement.

The result is a workflow where senior counsel spend the majority of their contract time not applying judgment, but confirming that what the vendor sent matches the approved position—and if it doesn't, marking it up and sending it back. That loop can run two, three, or four rounds before both parties have positions that are close enough to execute.

Why “AI review” tools haven't solved it

The first generation of AI contract tools accelerated the review step—they flag deviations, suggest alternative language, and reduce the time a lawyer spends reading a document from 45 minutes to 15. That is a meaningful saving per contract. But it doesn't change the structure of the problem.

The bottleneck is not reading time. It is the loop itself: vendor sends paper, legal reviews, legal sends redlines, vendor reviews, vendor counterproposals, legal reviews again. Each exchange requires a human to pick it up, evaluate it, and respond. AI that accelerates the reading step leaves the loop intact.

The question worth asking

If 84% of the time spent on a vendor contract involves positions that are already resolved at the playbook level—either the team's approved position is clear, or the position is identical to one handled in a prior contract with the same vendor—then the question is not “how do we help lawyers review faster?”

It is: “which parts of this workflow require a lawyer at all?”

Governed negotiation systems are designed to run the exchange itself—within the authority the legal team has already approved—and surface only the positions that genuinely need judgment. The lawyer doesn't see a contract that needs reviewing. They see a focused brief containing the one or two decisions the system cannot make without them.