Vendor renewal radar

Surfaces upcoming SaaS and vendor renewals with spend history, usage-vs-license context, and a drafted negotiation brief per renewal. Use when the user mentions vendor renewals, SaaS spend, contract renewals coming up, software cost review, or "what are we paying for that we don't use."

The most reliable way to light money on fire is to let a renewal auto-fire while nobody was looking. The second most reliable is to walk into the negotiation without your own usage data. This skill fixes both: every renewal surfaced at T-minus-90 with the spend history, the seat-utilization truth, and a negotiation brief that took zero human hours to assemble.

When to run

Recurring: monthly radar sweep (recommended)
On demand: "what renews this quarter" / before budget planning

Computer scopes

Finance sync: vendor contracts, invoices, payment history
IT: license inventories and SSO/usage signals where synced
Docs: prior negotiation notes and contract terms
Chat + tickets: internal sentiment about the tool (support burden, complaints, praise)

Workflow

Build the renewal horizon: everything renewing in the next 120 days, with auto-renew flags and notice-period deadlines — the notice deadline, not the renewal date, is the real date.
Per renewal, compute the utilization truth: seats licensed vs. seats active, feature-tier usage where visible, spend trend across terms.
Gather leverage inputs: internal sentiment, overlapping tools in the stack (consolidation candidates), prior negotiation outcomes, and public list-price context where synced.
Draft the negotiation brief: recommended posture (renew as-is / rightsize / renegotiate / sunset-candidate), the utilization evidence, the asks, and the walk-away framing. Sunset recommendations include the migration-cost caveat honestly.
Route each brief to the contract owner with the notice-deadline countdown; escalate unactioned briefs at T-minus-30.

Guardrails

Autonomy: L0. Radar and briefs only — never contacts vendors, never cancels or modifies contracts, never sends notices. Every external act is a human act.
Utilization claims cite the license and usage records; unknowns are stated as unknowns.

Output

Monthly radar: horizon table (vendor, spend, renewal, notice deadline, utilization, posture) → per-renewal negotiation briefs → sunset-candidate list with caveats.

Eval fixtures

Set: sandbox vendor book of 30 contracts with seeded utilization data, 4 auto-renew traps inside notice windows, and 3 consolidation overlaps.
Rubric: horizon completeness; notice-deadline math exact; utilization accuracy; all 4 traps flagged; overlap detection.
Ship gate: deadline errors 0; trap recall 100%.

Run vendor renewal radar on your own data.

MORE SKILLS

Ops & Finance · L2

Meeting actions sync

Extracts decisions and action items from meeting notes and transcripts, writes them into the tracker with owners and due dates, and chases completion before the next occurrence. Use when the user mentions meeting follow-ups, action items, "who owns this," meeting notes to tasks, or wants recurring meetings to actually produce outcomes.

Ops & Finance · L2

Meeting actions sync

Extracts decisions and action items from meeting notes and transcripts, writes them into the tracker with owners and due dates, and chases completion before the next occurrence. Use when the user mentions meeting follow-ups, action items, "who owns this," meeting notes to tasks, or wants recurring meetings to actually produce outcomes.