Every operator with more than a handful of vendor contracts faces the same problem twice a quarter. A new supplier or customer sends through a draft MSA. The legal function — internal or outside counsel — reviews it, redlines it, and negotiates. The negotiated draft gets signed. Six months later a similar contract from a different counterparty arrives. The review starts over from a blank page. The negotiated positions from the prior round may or may not get applied, depending on whether the same lawyer is reviewing, whether the matter is logged consistently, and whether anyone remembered to update the internal templates.
The cost of this pattern is not the legal fees, though those add up. The cost is the inconsistency. Two contracts signed in the same year, by the same operator, with similar counterparties, often contain materially different positions on liability cap, indemnity, data processing terms, termination, and IP assignment. Each individual contract is defensible. The portfolio is incoherent. When a dispute arises and the operator's counsel goes looking for precedent, the precedents disagree with each other.
A clause playbook is the antidote. It is a documented set of operator positions per clause: this is our preferred liability cap, this is our walk-away position, this is what we will accept under pressure, this is what we will never accept. The playbook is not a template — it is a policy document, written in plain English, signed off by whoever owns commercial risk for the operator. Once it exists, contract review becomes a comparison exercise rather than a freelance one.
WYRM Legal automates the comparison. An incoming contract is parsed clause by clause, mapped to the operator's playbook, and scored: green where the incoming clause matches the playbook position, amber where it deviates in a way the playbook tolerates, red where it crosses a documented red line. Each verdict carries diff-style evidence — the playbook position, the incoming clause, and the specific delta. A suggested redline is attached where appropriate.
The model works across the five contract document types most operators deal with: MSAs and the underlying frameworks, NDAs (where the failure mode is volume rather than complexity), DPAs (where regulator updates can render baselines stale), and SOWs (where the question is conformance to the MSA above it). Each type has its own playbook section because the relevant clauses differ — a DPA's main risk is sub-processor scope, an SOW's is acceptance criteria.
A practical example. An incoming customer MSA arrives with a liability cap pegged to fees paid in the prior six months. The operator's playbook says: prefer fees paid in the prior twelve months, accept six months only if the gross fee level is below £100k annually, never accept liability uncapped or pegged to a multiple of fees above 1x. WYRM Legal surfaces this clause as amber: the six-month peg is below preferred but within tolerance, and the redline suggests bumping to twelve months with a fall-back. The operator's commercial lead sees the verdict, the diff, and the suggested position in a single view, decides to push back on the twelve-month version, and the negotiation begins from a position rather than from research.
Where the playbook is silent — a new clause type the operator has not negotiated before — Legal flags it explicitly rather than guessing. The right response is for the operator to make a position decision and update the playbook, so the next contract that contains the same clause type benefits from the precedent. This is how the playbook gets richer over time: every new negotiation either confirms or extends it, and the comparison engine gets sharper with each addition.
Pricing: Pro at £19/month covers 10 contract reviews per month across the five document types, the playbook editor, and the weekly legal-monitoring digest. Enterprise at £49/month removes the volume cap, adds daily monitoring with clause-drift alerts (when a regulator update or case-law change renders a playbook position stale), multi-country support, and sector libraries. Legal is one of WYRM's focused add-on modules, sold alongside the flagship engineering products, WYRM MEP and WYRM Data. Where contract review needs to feed back into supplier risk (Procure), cyber attestation (Cyber), or bid drafting (Ledger), those modules run on the same shared substrate.