Vendor Review
Evaluate a vendor — cost analysis, risk assessment, and recommendation. Use when reviewing a new vendor proposal, deciding whether to renew or replace a contract, comparing two vendors side-by-side, or building a TCO breakdown and negotiation points before procurement sign-off.
MCP get_skill({ skillId: "vendor-review-e9845c4f" })Use this skill with your agent
Create a free account and connect via MCP
# /vendor-review > If you see unfamiliar placeholders or need to check which tools are connected, see [CONNECTORS.md](../../CONNECTORS.md). Evaluate a vendor with structured analysis covering cost, risk, performance, and fit. ## Usage ``` /vendor-review $ARGUMENTS ``` ## What I Need From You - **Vendor name**: Who are you evaluating? - **Context**: New vendor evaluation, renewal decision, or comparison? - **Details**: Contract terms, pricing, proposal document, or current performance data ## Evaluation Framework ### Cost Analysis (Total Cost of Ownership) - Total cost of ownership (not just license fees) - Implementation and migration costs - Training and onboarding costs - Ongoing support and maintenance - Exit costs (data migration, contract termination) ### Risk Assessment - Vendor financial stability - Security and compliance posture - Concentration risk (single vendor dependency) - Contract lock-in and exit terms - Business continuity and disaster recovery ### Performance Metrics - SLA compliance - Support response times - Uptime and reliability - Feature delivery cadence - Customer satisfaction ### Comparison Matrix When comparing vendors, produce a side-by-side matrix covering: pricing, features, integrations, security, support, contract terms, and references. ## Output ```markdown ## Vendor Review: [Vendor Name] **Date:** [Date] | **Type:** [New / Renewal / Comparison] ### Summary [2-3 sentence recommendation] ### Cost Analysis | Component | Annual Cost | Notes | |-----------|-------------|-------| | License/subscription | $[X] | [Per seat, flat, usage-based] | | Implementation | $[X] | [One-time] | | Support/maintenance | $[X] | [Included or add-on] | | **Total Year 1** | **$[X]** | | | **Total 3-Year** | **$[X]** | | ### Risk Assessment | Risk | Likelihood | Impact | Mitigation | |------|-----------|--------|------------| | [Risk] | High/Med/Low | High/Med/Low | [Mitigation] | ### Strengths - [Strength 1] - [Strength 2] ### Concerns - [Concern 1] - [Concern 2] ### Recommendation [Proceed / Negotiate / Pass] — [Reasoning] ### Negotiation Points - [Leverage point 1] - [Leverage point 2] ``` ## If Connectors Available If **~~knowledge base** is connected: - Search for existing vendor evaluations, contracts, and performance reviews - Pull procurement policies and approval thresholds If **~~procurement** is connected: - Pull current contract terms, spend history, and renewal dates - Compare pricing against existing vendor agreements ## Tips 1. **Upload the proposal** — I can extract pricing, terms, and SLAs from vendor documents. 2. **Compare vendors** — "Compare Vendor A vs Vendor B" gets you a side-by-side analysis. 3. **Include current spend** — For renewals, knowing what you pay now helps evaluate price changes.
Related Skills
More skills in Business, Marketing & Sales
Ab Testing
When the user wants to plan, design, or implement an A/B test or experiment, or build a growth experimentation program. Also use when the user mentions "A/B test," "split test," "experiment," "test this change," "variant copy," "multivariate test," "hypothesis," "should I test this," "which version is better," "test two versions," "statistical significance," "how long should I run this test," "growth experiments," "experiment velocity," "experiment backlog," "ICE score," "experimentation program," or "experiment playbook." Use this whenever someone is comparing two approaches and wants to measure which performs better, or when they want to build a systematic experimentation practice. For tracking implementation, see analytics. For page-level conversion optimization, see cro.
Ab Test Setup
When the user wants to plan, design, or implement an A/B test or experiment. Also use when the user mentions "A/B test," "split test," "experiment," "test this change," "variant copy," "multivariate test," "hypothesis," "conversion experiment," "statistical significance," or "test this." For tracking implementation, see analytics-tracking.
Ab Test Setup
Ab Test Setup linked from Corey Haines marketing skills, with the upstream skill instructions available on GitHub.
Ab Test Store Listing
When the user wants to A/B test App Store product page elements to improve conversion rate. Also use when the user mentions "A/B test", "product page optimization", "test my screenshots", "test my icon", "conversion rate optimization", "CPP", or "custom product pages". For screenshot design, see screenshot-optimization. For metadata optimization, see metadata-optimization.
Account Research
Research a company or person and get actionable sales intel. Works standalone with web search, supercharged when you connect enrichment tools or your CRM. Trigger with "research [company]", "look up [person]", "intel on [prospect]", "who is [name] at [company]", or "tell me about [company]".
Account Research
Research a company using Common Room data. Triggers on 'research [company]', 'tell me about [domain]', 'pull up signals for [account]', 'what's going on with [company]', or any account-level question.
Explore Other Categories
Skills from other categories with shared topics
Audit Support
Support SOX 404 compliance with control testing methodology, sample selection, and documentation standards. Use when generating testing workpapers, selecting audit samples, classifying control deficiencies, or preparing for internal or external audits.
Compliance Check
Run a compliance check on a proposed action, product feature, or business initiative, surfacing applicable regulations, required approvals, and risk areas. Use when launching a feature that touches personal data, when marketing or product proposes something with regulatory implications, or when you need to know which approvals and jurisdictional requirements apply before proceeding.
Compliance Tracking
Track compliance requirements and audit readiness. Trigger with "compliance", "audit prep", "SOC 2", "ISO 27001", "GDPR", "regulatory requirement", or when the user needs help tracking, preparing for, or documenting compliance activities.