with the skill
## Contract Review Summary
**Document:** Quillfeather Analytics Ltd. / Daventry Logistics plc — Sections 4.1–4.5
**Your side:** Customer/buyer
**Review basis:** No organizational playbook was provided; this is a buyer-side review using general commercial standards. Only the supplied excerpt has been reviewed.
**Bottom line:** Negotiate before signing. The main concern is the combination of **three-year automatic renewals, a 120-day notice deadline, a potential 15% renewal increase, and very limited exit rights**. Together, these could lock you into another substantial commitment before you know the final renewal price.
## Key Findings for Finance
| Issue | Assessment | Business impact |
|---|---|---|
| Automatic renewal for another 36 months | **YELLOW — high priority** | Missing the notice deadline could commit you to three additional years. |
| Renewal increase without advance price notice | **YELLOW — high priority** | You must decide whether to renew without a contractual right to know the price beforehand. |
| No convenience exit; 90-day breach cure | **YELLOW — high priority** | Reduced ability to exit an unsuitable product or respond to persistent service failures. |
| Data deletion within 10 days | **RED if business-critical data is held** | No express export or transition period; data could be lost before migration is complete. |
**Illustrative exposure:** If current annual fees are **£100,000**, the initial three-year fees would be **£300,000**. A renewal at the maximum increase would cost **£345,000 over the next three years**, assuming unchanged scope and no other adjustments. The 15% is a step-up per renewal, **not an annual increase under this clause**.
## Clause Review and Proposed Changes
Show the rest (65 more lines)
### 4.1 — Initial Term: YELLOW, depending on commercial value
**Current language:** “36 months from the Effective Date.”
A three-year commitment is not inherently problematic, but it should buy meaningful pricing certainty and preferably a discount. Confirm whether the Effective Date could precede implementation or usable access.
**Proposed replacement — should-have:**
> “The Initial Term is 36 months from the date the contracted software is made available to Customer in accordance with the agreed implementation requirements. Subscription fees are fixed throughout the Initial Term, except for additional products or quantities expressly ordered by Customer.”
**Fallback:** Keep the Effective Date commencement, but obtain a clear service-delivery deadline and express fixed pricing for all 36 months.
**Rationale:** Align payment commitment with delivery and ensure the longer commitment provides budget certainty. The excerpt does **not** establish whether another provision already fixes initial-term pricing.
### 4.2 — Renewal: YELLOW, high priority
**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 replacement — should-have:**
> “Following the Initial Term, this Agreement will 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.”
**Fallback:** Retain the 120-day deadline but reduce renewal terms to 12 months and require a vendor reminder before that deadline.
**Rationale:** Annual renewals preserve continuity without imposing a fresh three-year commitment by default. If three-year renewals remain, seek a material discount and an annual customer break right.
### 4.3 — Renewal Pricing: YELLOW, high priority
**Current language:** “Vendor may increase fees by up to 15% at the start of each renewal term.”
**Proposed replacement — should-have; coordinate with 12-month renewals:**
> “Fees will remain fixed during each term. Any increase at renewal will not exceed 3% of the fees for the immediately preceding term for the same products and quantities. Vendor must notify Customer in writing of the exact renewal fees at least 150 days before the current term expires. If Vendor fails to provide timely notice, no increase will apply for the next renewal term.”
**Fallback:** A 5% cap per annual renewal, with the same advance-notice protection. These percentages are proposed negotiating positions, not universal market requirements.
**Rationale:** Finance needs the actual price **before** the non-renewal deadline. If the 120-day deadline remains, 150-day price notice gives only 30 days to decide; extend that window if internal procurement takes longer.
### 4.4 — Termination: YELLOW, high priority
**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 replacement — should-have:**
> “Customer may terminate for Vendor’s material breach not cured within 30 days after written notice, or immediately if the breach is incapable of cure. Customer may also terminate for convenience after the first 12 months on 90 days’ written notice. On termination, Customer will pay fees accrued through the termination date, no future subscription fees will become due, and Vendor will refund prepaid fees attributable to the period after termination.”
**Fallback:** If convenience termination is rejected, require a 30-day cure period, express termination for repeated material service failures, and a refund of unused prepaid fees following termination for Vendor breach.
**Rationale:** A 90-day cure period can prolong operational disruption. Termination rights should also specify the financial consequences; the excerpt does not do so.
### 4.5 — Data Exit: RED if material data is at risk
**Current language:** “Upon termination, Vendor will delete Customer Data within 10 days.”
**Proposed replacement — must-have if the platform holds important data:**
> “On expiry or termination, Vendor will make Customer Data available for export in a commonly used, machine-readable format and provide read-only access for 60 days without additional subscription fees. Vendor will not delete Customer Data during that period unless Customer instructs otherwise. Thereafter, Vendor will securely delete Customer Data and confirm deletion, subject to legally required retention and documented backup-deletion schedules.”
**Rationale:** A practical export period avoids data loss and emergency migration costs. Escalate to Legal and IT/data owners if the vendor will not provide workable exit arrangements.
## Negotiation Strategy and Next Steps
1. **Lead with the package:** annual renewals, capped increases, and price notice before the cancellation deadline.
2. **Confirm the economics elsewhere:** initial-term fee increases, minimum quantities, usage overages, mandatory support fees, payment acceleration, and implementation charges are not addressed here.
3. **Secure an exit:** shorter breach cure, clear refund treatment, and data-export rights.
4. If signing unchanged, calendar the 120-day deadline with earlier internal reminders—though that does not solve the missing price-notice protection.
**Useful remaining context:** What is the signing deadline, annual contract value, and importance of the software/data to operations? Those determine which points warrant business escalation.
This is contract-review assistance, not legal advice; qualified legal counsel should review the proposed changes before reliance or signature.