Process
How to build a contract playbook your sales team will use
A playbook is the difference between a legal function that scales and one that becomes the bottleneck. It is also the artefact that keeps working after the people who wrote it have moved on.
STDMutual cap, 12 months’ fees. FALLBACK24 months’ fees; super-cap 3x for data breach — deal desk may approve. WALKUncapped liability of any kind — GC + CFO only, in writing.
- A playbook records your positions on each negotiable clause: preferred, acceptable, walk-away — and who can approve each.
- Its purpose is to let non-lawyers close routine deals without asking, and to make escalation a defined event.
- If it is longer than fifteen pages nobody will use it. Precision matters more than coverage.
What it is
A contract playbook is a written record of your company’s positions on the clauses that get negotiated. For each one: what you ask for first, what you will accept if pushed, what you will never agree to, and who is allowed to approve a move from one to the next. It exists so that a salesperson, a deal desk or an outside contract team can handle the eighty percent of negotiations that follow a pattern without a lawyer in the room — and so that the twenty percent that do not are recognised and escalated.
What goes in it
A workable structure, clause by clause:
| Column | What it says |
|---|---|
| Clause | Limitation of liability |
| Our standard | Mutual cap at 12 months’ fees; exclude indirect and consequential loss. |
| Why it matters | One plain-English paragraph a salesperson can repeat to a customer. |
| Acceptable fallback | Cap at 24 months’ fees; super-cap of 3x fees for data breach; carve-outs for confidentiality and IP indemnity. |
| Approval for fallback | Deal desk, no escalation. |
| Walk-away | Uncapped liability of any kind; carve-out for “breach of contract” generally. |
| Approval to exceed walk-away | General Counsel plus CFO, in writing. |
| Standard language | The exact clause text for standard and fallback, ready to paste. |
Fifteen to twenty clauses cover almost every B2B software negotiation: liability, indemnity, warranty, data protection, security, IP, confidentiality, term and renewal, termination, payment terms, service levels, assignment, insurance, governing law, non-solicitation, publicity, most-favoured-customer, audit.
Writing positions people will actually apply
- Be numeric where possible. “A reasonable cap” is not a position. “12 months’ fees, fallback 24” is.
- Give the reason. A salesperson who understands why the cap matters will hold it. One who has only been told to hold it will trade it for a discount.
- Include the words. Pre-approved clause text removes the temptation to improvise.
- Define escalation by trigger, not by feel. “Escalate if the customer asks for anything not in this document” is a rule. “Escalate if it seems risky” is not.
Keeping it alive
A playbook decays fast. Every negotiation that ends outside the fallbacks is either a mistake or new information, and the document should record which. Review quarterly: which fallbacks were used most, which walk-aways were breached and why, which clauses generated escalations that could have been standardised. A playbook that has not changed in a year is not stable; it is abandoned.
Someone who has negotiated your contracts and knows where the deals actually got stuck — not a template downloaded from the internet, and not a first draft from someone who has never seen your customer base. The first version is the hard part; keeping it current is routine. Building it is included on the Engross Legal Desk, and it is the piece of work with the longest shelf life we do.
Next step
Have a contract like this on your desk?
Send it over. We will mark it up and walk you through it in twenty minutes — no cost, and you will know whether the desk is worth it.