skills / legal & compliance

review-contract

what it does

Review a contract against your organization's negotiation playbook — flag deviations, generate redlines, provide business impact analysis. Use when reviewing vendor or customer agreements, when you need clause-by-clause analysis against standard positions, or when preparing a negotiation strategy with prioritized redlines and fallback positions.

Verified Before and after: 2 models 1 try per case View source Download .zip

Compare the answers

Answers from Claude Sonnet 5.5 and GPT-6.1 Sol · try 1 of 1

Same request, same model, once with the skill and once without. Read both and judge for yourself.

“We're the buyer on this 3-year software contract. Finance wants to know if there's anything in the term and pricing sections we should fix before signing.”

Source material given with the request

ORDER FORM AND TERMS: Quillfeather Analytics Ltd. (Vendor) and Daventry Logistics plc (Customer) 4.1 Initial Term: 36 months from the Effective Date. 4.2 Renewal: This Agreement will automatically renew for successive 36-month terms unless either party gives written notice of non-renewal at least 120 days before the end of the then-current term. 4.3 Renewal Pricing: Vendor may increase fees by up to 15% at the start of each renewal term. 4.4 Termination: Customer may terminate only for Vendor's material breach that remains uncured 90 days after written notice. Customer may not terminate for convenience. 4.5 Upon termination, Vendor will delete Customer Data within 10 days.
with the skill
## Contract Review Summary **Document**: Quillfeather Analytics Order Form and Terms, Section 4 (Term, Renewal, Pricing, Termination) **Parties**: Quillfeather Analytics Ltd. (Vendor) and Daventry Logistics plc (Customer, **our side**) **Deadline**: Not provided **Review Basis**: Generic commercial standards. I have no playbook, so "standard" below means common market positions for buyers, not Daventry's own thresholds. **Scope**: Only the five clauses you pasted. I haven't seen the fees, payment terms, SLAs or liability sections, which affect several points below. ## Key Findings Yes, there is a lot to fix before signing. Four of the five clauses are unfavorable to the buyer, and together they compound. 1. **RED: 36-month auto-renewal with a 120-day notice window (4.2).** If nobody sends notice by roughly month 32, Daventry is locked in for another 3 years. 2. **RED: Uncapped-in-practice 15% uplift (4.3), with no requirement that the vendor announce it before the non-renewal deadline.** Daventry could learn the new price after it has lost the right to walk away. 3. **RED: No termination for convenience, and a 90-day cure period (4.4).** Combined with 4.2, a missed notice could mean a 6-year commitment with almost no exit. 4. **YELLOW: 10-day deletion with no export window (4.5).** This is a data-loss and transition risk, and it may not apply on expiry. **Exposure for Finance** (X = annual fees): - Initial term commitment: 3X. - If the renewal is missed: another 3X, at up to 1.15X per year, so about 3.45X. That is 0.45X above the current rate, locked in for 3 years.
Show the rest (81 more lines)
- The 15% applies "at the start of each renewal term" and can repeat. By the third term it compounds to about 1.32× the original rate (1.15 × 1.15). - Total worst-case commitment from signing: 6.45X or more, with no convenience exit. ## Clause-by-Clause Analysis ### 4.1 Initial Term (36 months): YELLOW (business decision) **Contract says**: 36 months from the Effective Date. **Impact**: A 3-year term is fine if it was priced as a multi-year discount. Check that the fees are fixed for all 36 months, because nothing in Section 4 says so. If Daventry gets no discount for the commitment, push for a shorter term or an exit right (see 4.4). **Ask**: Add "Fees are fixed for the Initial Term." ### 4.2 Auto-Renewal: RED **Contract says**: Automatic 36-month renewals, with non-renewal notice at least 120 days before term end. **Market position**: Renewals are typically 12 months, with 30–60 days' notice (90 at most), and the vendor sends a reminder. **Risk**: A long notice window combined with a long renewal term makes a missed deadline very expensive. The notice date falls about a month before the fiscal-year planning cycle ends, which makes it easy to miss. **Clause**: 4.2 Renewal **Current language**: "This Agreement will automatically renew for successive 36-month terms unless either party gives written notice of non-renewal at least 120 days before the end of the then-current term." **Proposed redline**: "This Agreement will automatically renew for successive **12-month** terms unless either party gives written notice of non-renewal at least **60** days before the end of the then-current term. **Vendor will send Customer written notice of the upcoming renewal, including renewal fees, no earlier than 150 and no later than 90 days before the end of the then-current term. If Vendor fails to do so, Customer may give notice of non-renewal at any time up to 30 days after receiving Vendor's notice, and the Agreement will continue on a month-to-month basis until that notice period ends.**" **Rationale**: Short renewal terms and a reminder protect both parties from unintended multi-year commitments. **Priority**: Must-have **Fallback**: 12-month renewals with 90 days' notice, keeping the vendor reminder. Or, if the vendor insists on 36 months, renewal only by mutual written agreement. ### 4.3 Renewal Pricing: RED **Contract says**: The vendor may increase fees by up to 15% at the start of each renewal term. **Market position**: Increases capped at the lesser of CPI and 3–5%, with advance written notice. **Risk**: 15% is high for a single step, and it applies to a 36-month renewal, so the cost is locked in for 3 years. The vendor also has no obligation to give notice before the 120-day deadline. **Clause**: 4.3 Renewal Pricing **Current language**: "Vendor may increase fees by up to 15% at the start of each renewal term." **Proposed redline**: "Vendor may increase fees **for a renewal term by no more than the lesser of (a) 3% and (b) the percentage increase in [CPI index] over the preceding 12 months, and only if Vendor gives Customer written notice of the increase at least 150 days before the end of the then-current term. If no such notice is given, fees for the renewal term will remain unchanged.**" **Rationale**: Customer needs price certainty before its non-renewal deadline in order to budget and decide. **Priority**: Must-have for the notice mechanism, Should-have for the cap level **Fallback**: A fixed cap of 5–7%, with the notice requirement kept in all cases. ### 4.4 Termination: RED **Contract says**: The customer may terminate only for uncured material breach after 90 days' notice, and may not terminate for convenience. **Market position**: A 30-day cure period. Also additional termination rights (insolvency, repeated breach, chronic SLA failure, security or data breach, change of control, sanctions or regulatory). Many buyers also get termination for convenience after an initial period, or a refund of prepaid fees. **Risk**: - 90 days is a long time to remain tied to a failing service. - There is no exit for non-breach events, such as the vendor being acquired by a competitor or discontinuing the product. - Nothing says prepaid fees are refunded on termination. This depends on the payment terms I haven't seen. **Clause**: 4.4 Termination **Current language**: "Customer may terminate only for Vendor's material breach that remains uncured 90 days after written notice. Customer may not terminate for convenience." **Proposed redline**: "Either party may terminate for the other's material breach that remains uncured **30** days after written notice. **Customer may also terminate immediately on written notice if Vendor (a) becomes insolvent, (b) commits repeated material breaches, (c) fails to meet the service levels in [SLA section] in [3] months of any [6]-month period, or (d) experiences a Security Incident affecting Customer Data due to Vendor's breach. Customer may terminate for convenience on 90 days' written notice at any time after the first 12 months, on payment of [50]% of fees for the remainder of the Initial Term. On any termination by Customer under this Section, Vendor will refund prepaid fees for the period after termination.**" **Rationale**: A multi-year commitment needs a workable exit if performance, solvency or security fails. **Priority**: Must-have for the 30-day cure, the additional termination triggers and the refund. Should-have for termination for convenience. **Fallback**: Termination for convenience at the end of month 24 only, or a right to reduce volumes or scope by a set percentage at each anniversary. ### 4.5 Data Deletion: YELLOW **Contract says**: On termination, the vendor deletes Customer Data within 10 days. **Risk**: - No export or return period, so Daventry could lose data before migrating it. - It says "upon termination", which may not cover expiry or non-renewal. - No deletion certificate and no mention of backups. - 10 days is also very short if there is a dispute. **Clause**: 4.5 **Current language**: "Upon termination, Vendor will delete Customer Data within 10 days." **Proposed redline**: "**Upon expiration or termination for any reason, Vendor will make Customer Data available for export in a standard, machine-readable format for 60 days, and will provide reasonable transition assistance on request at its then-current rates. Within 30 days after that period, Vendor will delete all Customer Data, including from backups within [90] days, and will certify deletion in writing on request.**" **Rationale**: This lets Customer move its data safely while still ensuring it is deleted. **Priority**: Should-have **Fallback**: A 30-day export window, with a written deletion confirmation. ## Negotiation Strategy - **Lead with 4.2 and 4.3 together.** Frame them as one request: "no surprise lock-ins". The vendor can still renew and reprice, but with notice and reasonable caps. These carry the largest financial risk. - **Then 4.4.** Start with termination for convenience. It is the hardest ask, so it is a good trade item. Hold firm on the 30-day cure and the additional triggers. - **Concede on 4.1 (the 36-month term)** if the pricing is attractive. Don't concede the term length and the renewal mechanics together. - **4.5** is usually easy to agree, so use it to show cooperation. - **Short-term protection:** whatever the outcome, put the non-renewal deadline in the contract calendar at signing, with alerts at 180, 150 and 120 days before term end. ## Next Steps 1. Tell me **your deadline**, and whether Daventry has a **playbook** or standard positions (such as maximum term length or uplift). I'd then rerun this against them. 2. Send me the **fees, payment terms, SLA and liability sections.** They affect whether the refund, uplift and exit rights above are enough. 3. Confirm whether the **initial 36-month fees are fixed** and whether payments are annual in advance. 4. Have Daventry's legal counsel review the redlines before they go to Quillfeather, and have Finance confirm the fallback numbers (cap percentage, termination fee). 5. Check the data deletion clause against the **UK GDPR / DPA** requirements if personal data is involved. I haven't reviewed the data protection terms. *This is not legal advice. Qualified legal counsel should review this analysis before you rely on it.*
without
# Review of Sections 4.1-4.5 (buyer's perspective) Overall, these terms are vendor-favorable and leave you locked in with little leverage. Here are the issues in rough priority order, with proposed fixes. ## High priority **1. Auto-renewal for 36 months (4.2)** - Missing the notice window by one day commits you to another 3 years. The 120-day window is long and easy to miss. - **Fix:** Renew for 12-month terms, not 36. Shorten the notice period to 30-60 days. Require the vendor to send a written renewal reminder 90-120 days before term end, and if it doesn't, the renewal is month-to-month or cancellable without penalty. **2. Uncapped-ish 15% renewal uplift (4.3)** - This is a ceiling, not a commitment, so the vendor can charge the full 15% every time. It's far above typical CPI. - There is no requirement to tell you the new price before your non-renewal deadline. You could learn of the increase after you're locked in. - Illustration: at $100k/year, the initial term costs $300k. Renewal at +15% is about $345k, and a second renewal at +15% is about $397k, all committed up front. - **Fix:** Cap increases at the lesser of CPI or 3-5%. Require written notice of any increase at least 180 days before renewal (before the non-renewal deadline). Alternatively, negotiate a price lock for the first renewal. **3. Termination rights are too narrow (4.4)** - A 90-day cure period is long, and breach is the only exit. You'd keep paying for a failing product while waiting. - **Fix:** - Shorten the cure period to 30 days.
Show the rest (26 more lines)
- Add termination rights for chronic or repeated SLA failures, security or data breaches, vendor insolvency, change of control to a competitor, and discontinuation or material degradation of the product. - Provide a pro-rata refund of prepaid fees on any termination for vendor cause. - Ideally, add termination for convenience (e.g., after month 12 with 90 days' notice), or at minimum a reduced early-exit fee rather than all remaining fees. **4. Data deletion with no return or transition (4.5)** - Ten days is too short, and nothing gives you a right to export your data first. The clause also says "upon termination," which is unclear for expiry or non-renewal. - **Fix:** - Give you a 60-90 day post-termination window to export all Customer Data in a standard, usable format at no extra cost. - Delete only after that window, or on your written instruction. - Require written certification of deletion, covering backups and subprocessors. - Add reasonable transition assistance. - Confirm that deletion applies to expiry as well as termination. - Check the data protection terms so they line up with UK GDPR processor obligations. ## Also check - **Effective Date (4.1):** If the term runs from signing rather than go-live or acceptance, you pay for the implementation period. Consider tying the start to go-live. - **Initial-term pricing:** The sections you shared only address renewal pricing. Confirm fees are fixed for the full 36 months, and check for volume or usage true-ups, indexation, or other uplift mechanisms elsewhere in the contract. - **Payment timing:** Check whether fees are paid annually in advance or all upfront. If so, refund rights matter more. - **Vendor suspension and termination rights:** Review these elsewhere in the agreement. The vendor shouldn't have broader exit rights than you do. - **Mutuality of 4.2:** Non-renewal is mutual, so the vendor can also walk away at renewal. If the product is critical, consider asking for a minimum transition or support period. ## Suggested negotiating approach If you can't get everything, prioritize: (1) shorter renewal terms and a reminder obligation, (2) a lower renewal cap with early price notice, (3) a data export window, and (4) broader termination rights with refunds. I've only seen these five clauses, so I can't comment on SLAs, liability, or the full fee schedule. I'd have legal counsel review the final redline.

Answers are shown exactly as the model wrote them, from the first try, and nothing is picked by hand.

The models

2 models

Claude Sonnet 5.5

made by Anthropic

claude-sonnet-5-5 · revision not reported by the provider

1 try per case · tested 3 Nov 2026

GPT-6.1 Sol

made by OpenAI

gpt-6.1-sol · revision not reported by the provider

1 try per case · tested 3 Nov 2026

The tasks

written by Carte Blanche
auto-renewal-trap

“We're the buyer on this 3-year software contract. Finance wants to know if there's anything in the term and pricing sections we should fix before signing.”

missing-dpa

“We're the customer. This marketing email vendor will hold our customer list, including about 30,000 people in the EU. Please review the data clauses.”

prioritize-for-one-call

“We're the customer. We get one 30-minute call with their counsel tomorrow. What should we push hard on and what can we let go?”

saas-one-sided-liability

“We're the customer on this SaaS agreement for a support ticketing tool, about $48,000 a year. Can you review the liability and indemnity sections and tell me what to push back on?”

vendor-side-ip-grab

“We're the vendor here: a small dev shop doing a 4-month build for a client. Their lawyer sent their services agreement. What do we need to change?”

Install

Download the .zip and unzip it. Put its files, in a folder named review-contract, here:

Claude Code~/.claude/skills/Every project. For one project only, use .claude/skills/ inside it.
Codex~/.agents/skills/Every project. For one repository only, use .agents/skills/ inside it.
Cursor~/.cursor/skills/Cursor also reads the Claude Code and Codex folders above.

Then start a new session and ask for what the skill does. Other agents that read SKILL.md have their own skills folder; check their docs.

Coming after launch: get skills from inside your agent, no download needed.