ClawKit Logo
ClawKitReliability Toolkit
Back to Registry
Official Verified

Contract Renewal & Expiration Manager

Skill by flynndavid

skill-install — Terminal

Install via CLI (Recommended)

clawhub install openclaw/skills/skills/flynndavid/contract-renewal-manager
Or

Contract Renewal & Expiration Manager

Framework: Renewal Readiness Protocol Output: A proactive renewal calendar + decision framework + renegotiation prep package

Missing a contract renewal costs real money — auto-renewals at bad rates, emergency re-sourcing, lost leverage. This system gives you a structured process to manage every vendor contract renewal proactively: alert triggers, renewal decisions, renegotiation prep, and documentation.


Phase 1: Renewal Inventory & Calendar Setup

Step 1 — Build your renewal calendar

For every active vendor contract, capture:

FieldWhat to Record
Vendor NameLegal name + DBA
Contract StartDate
Contract EndDate
Auto-Renewal ClauseYes/No — if yes, notice period required
Notice DeadlineContract end date minus notice period
Annual Value$ACV or total contract value
CategorySoftware / Services / Suppliers / Professional Services
OwnerInternal stakeholder responsible for this vendor

Priority flag: Any contract with ACV > $10K or auto-renewal clause = Priority tier (review 90 days out). All others = Standard tier (review 60 days out).


Phase 2: The 90/60/30-Day Alert Protocol

90 days before renewal:

  • Owner receives automated/calendar alert
  • Trigger: Vendor Performance Audit (see Vendor Performance Audit skill)
  • Decision: Is this vendor still the right solution? Flag for review.
  • Action: Schedule renewal decision meeting

60 days before renewal:

  • Complete renewal decision (renew vs. renegotiate vs. replace)
  • If renewing as-is: confirm terms, draft renewal notice
  • If renegotiating: begin prep (Phase 3)
  • If replacing: begin vendor search, trigger parallel onboarding timeline

30 days before renewal:

  • All paperwork finalized and signed
  • If auto-renewal with notice clause: send written notice by this date
  • Confirm successor vendor is ready (if replacing)
  • Update renewal calendar for next cycle

Emergency Protocol (< 30 days discovered): If a renewal is discovered < 30 days out:

  1. Immediate owner notification
  2. Assess: Can we extend month-to-month? Is auto-renewal acceptable short-term?
  3. If replacing: begin emergency sourcing
  4. Document the miss and add this vendor to Priority tier going forward

Phase 3: Renewal Decision Framework

For each renewal, score across 4 dimensions (1-5 each):

DimensionScore 1Score 3Score 5
PerformanceConsistently below SLAMeets SLA most of the timeExceeds SLA reliably
ValueOverpriced vs. marketMarket rateBelow market, strong value
Strategic fitNo longer fits our directionNeutral / functionalCore to our operations
RelationshipDifficult to work withProfessional, transactionalStrong partnership

Metadata

Stars2387
Views0
Updated2026-03-09
View Author Profile
AI Skill Finder

Not sure this is the right skill?

Describe what you want to build — we'll match you to the best skill from 16,000+ options.

Find the right skill
Add to Configuration

Paste this into your clawhub.json to enable this plugin.

{
  "plugins": {
    "official-flynndavid-contract-renewal-manager": {
      "enabled": true,
      "auto_update": true
    }
  }
}
Safety NoteClawKit audits metadata but not runtime behavior. Use with caution.