Build an Evidence-Based Vendor Renewal Decision

Required inputs

Have these details available before following the usage instructions.

• Current contract, amendments, renewal and notice dates, pricing, terms, and approval thresholds
• License, usage, adoption, service-performance, incident, support, and business-outcome evidence
• Direct, internal, dependency, transition, and risk-related cost evidence
• Security, privacy, compliance, resilience, financial, and operational findings
• Integration, data, identity, workflow, switching, export, deletion, coexistence, and rollback dependencies
• Credible renewal, resize, renegotiation, consolidation, replacement, extension, and exit options
• Commercial owner, finance reviewer, legal reviewer, security reviewer, operational owner, signature authority, and decision deadline

How to use this Skill

When to use:
- Preparing for a vendor renewal, price or scope renegotiation, license resize, consolidation, replacement, temporary extension, or exit.
- Maintaining a recurring renewal record before contractual notice and approval deadlines.
- Reassessing value, utilization, service, risk, dependency, and transition evidence after material change.

When not to use:
- Initial vendor sourcing or pre-purchase procurement readiness.
- Treating an imminent auto-renewal deadline as permission to skip contractual, financial, legal, security, or operational review.
- Making an emergency service-continuity decision that belongs in incident or continuity procedures.
- Contacting the vendor, accepting terms, issuing notice, or committing funds without the applicable authority.

Reusable renewal-governance method:
1. Maintain the renewal clock: authoritative contract, covered scope, end date, notice method and deadline, approval lead time, negotiation window, transition lead time, and accountable roles.
2. Maintain an evidence register for contracts, invoices, utilization, outcomes, service records, incidents, risks, dependencies, alternatives, export tests, and transition estimates. Mark conflicts and evidence limitations.
3. Assess business outcomes and meaningful utilization separately; do not treat assigned seats, activity, sentiment, or sunk cost as proof of value.
4. Normalize total cost and assumptions across renewal, resize, renegotiation, consolidation, replacement, extension, and exit scenarios.
5. Review service performance, supplier risk, concentration, security, privacy, compliance, resilience, and operational dependencies with the relevant reviewers.
6. Test credible alternatives and transition readiness, including data portability, coexistence, integration changes, user migration, service continuity, rollback, retention, and deletion evidence.
7. Define negotiation objectives, required terms, tradeable terms, approval limits, fallback options, and a no-agreement plan without exposing restricted negotiation positions.
8. Issue a recommendation with conditions, unresolved evidence, dissent, decision rights, next actions, deadlines, and a reusable decision record for the next lifecycle review.

Expected output:
A living renewal record containing the renewal clock, evidence register, outcome and utilization review, normalized cost and scenario comparison, service and risk findings, dependency and transition map, negotiation gates, recommendation, accountable roles, approval questions, and implementation or exit actions.

Constraints and accountability:
- Do not treat vendor claims, demonstrations, roadmap statements, contract summaries, or internal estimates as verified evidence.
- Do not disclose confidential pricing, negotiation limits, security findings, personal data, or legal advice outside the authorized review group.
- Keep commercial approval with the commercial owner, financial validation with the finance reviewer, contractual interpretation with the legal reviewer, security conclusions with the security reviewer, operational feasibility with the operational owner, and signature with the authorized signatory.
- Use AMO-P-000259 as source grounding and for deeper analysis; maintain this Skill as the recurring governance method.

Based on an Amo.ng Prompt

Vendor Renewal Decision Pack

Open the linked Prompt to read the instructions this Skill is based on.

Completion criteria

Complete when:
- The contractual notice deadline, decision timetable, covered products and entities, and approval roles are confirmed or visibly unresolved.
- Value, meaningful utilization, service performance, cost, risk, dependencies, alternatives, and transition readiness are supported by dated evidence or labelled limitations.
- Relevant scenarios use comparable scope, time horizon, currency, cost categories, and assumptions.
- The recommendation states renew, renew with conditions, resize, renegotiate, consolidate, replace, extend, or exit, with rationale and conditions.
- Negotiation and transition actions have owners, deadlines, evidence needs, decision gates, acceptance conditions, and fallback or rollback provisions.
- The final decision record distinguishes recommendations from approvals and can be reused at the next renewal review.