Benefits vendor comparison matrix

Purpose

Convert a stack of benefits vendor proposals into a single scored, apples-to-apples comparison matrix — weighted across cost, coverage, compliance, service, and integration — so a Benefits Manager can rank options objectively and defend the selection to finance and leadership without hand-building a spreadsheet.

When to Use

Invoke this skill when the user asks to:

• Compare competing benefits vendor or carrier proposals side by side
• Evaluate finalists in a benefits or Total Rewards RFP
• Score a medical, dental, vision, 401(k), TPA, PEO, or point-solution vendor selection
• Build a decision matrix to justify a vendor choice to a benefits committee or CFO
• Break a tie between two vendors that look similar on paper
• Standardize how proposals are graded across an evaluation cycle

Inputs Required

Before starting, collect:

• Benefit type: What's being sourced (e.g., medical carrier, dental, 401(k) recordkeeper, benefits admin platform, PEO, mental health point solution)
• Vendor proposals: 2–6 vendor summaries — name plus what each proposal states on pricing, coverage/plan design, compliance, service model, and integration/tech
• Employee population: Headcount, and any relevant demographics or eligibility tiers
• Priority weighting: Which of the five categories matter most (or accept the default weighting below)
• Budget context: Target PEPM/PMPM, total annual budget, or current spend to beat
• Must-haves and dealbreakers: Non-negotiable requirements (e.g., specific network, ERISA/ACA compliance features, existing HRIS integration)
• Incumbent status: Whether any vendor is the current provider

If priority weighting is not provided, use the default: Cost 30, Coverage 25, Compliance 20, Service 15, Integration 10. If a proposal is missing data in a category, score it conservatively and flag the gap rather than inventing figures.

Instructions

Step 1: Normalize the Proposals

Restate each vendor's proposal into a consistent internal format before scoring. For every vendor, extract:

• Cost: PEPM/PMPM or per-participant fee, admin fees, implementation cost, rate guarantee length, and any performance credits or hidden pass-through fees
• Coverage: Plan designs, network breadth, covered services, exclusions, and flexibility to customize
• Compliance: ERISA/ACA/HIPAA handling, 5500 filing support, nondiscrimination testing, fiduciary services, and data security posture
• Service: Dedicated account team, implementation timeline, SLAs, member support channels/hours, and reference strength
• Integration: HRIS/payroll connectivity (named systems), API/EDI/SSO support, data feed reliability, and reporting/analytics

Where a vendor omits an item, mark it "Not stated" — do not assume parity.

Step 2: Score Each Category on a 0–10 Scale

Grade every vendor 0–10 within each of the five categories, then multiply by the category weight to get weighted points.

Use these anchors so scores are consistent across vendors:

• 9–10: Clearly exceeds requirements; a competitive advantage
• 7–8: Fully meets requirements with no material gaps
• 5–6: Meets baseline but with notable limitations or caveats
• 3–4: Partially meets; requires workaround or concession
• 0–2: Fails a must-have, or data not provided to confirm

Cost scoring notes: Lowest sticker price does not automatically win — weight rate guarantee length and fee transparency. A slightly higher PEPM with a 2-year rate lock and no pass-through fees may outscore a cheaper year-one number.

Compliance scoring notes: Any vendor that fails a stated dealbreaker or cannot confirm a legal requirement (e.g., 5500 support, nondiscrimination testing) is capped at 4 in this category regardless of other strengths.

Step 3: Build the Comparison Matrix

Produce the primary scored table — vendors as columns, the five categories as rows, with weighted scores per cell and a total row.

Below the table, add a short category-by-category breakdown — one tight paragraph per category naming which vendor leads and why, using the extracted specifics (not generalities).

Step 4: Flag Red Flags and Gaps

List any of the following per vendor: capped compliance scores, "Not stated" data gaps in a weighted category, hidden or pass-through fees, short/absent rate guarantees, missing named integrations, or SLA vagueness. These are what get a selection challenged later — surface them explicitly.

Step 5: Ranked Recommendation

Rank the vendors 1 through N by total weighted score. Then:

1. Name the recommended vendor and state the total score and the margin over runner-up
2. Give 2–3 sentences of rationale tied to the buyer's stated priorities and must-haves
3. Note the strongest reason a stakeholder might object, and the counterpoint
4. List 3–5 follow-up questions to send the top vendor(s) before signing (targeting the biggest data gaps or caveats found)

Be decisive — recommend a winner even in a close race, and say when the race is close enough to warrant a best-and-final round.

Output Format

• Structure: Normalized proposal summaries → scored comparison matrix (table) → category breakdown → red-flag list → ranked recommendation with follow-up questions
• Length: 900–1,300 words
• Format: A markdown table for the matrix; structured bullets and short prose for everything else
• Sections: Proposal Snapshot (per vendor) → Comparison Matrix → Category Breakdown → Red Flags & Gaps → Ranked Recommendation → Questions Before Signing
• Tone: Total Rewards director — analytical, evidence-anchored, and decisive; written to survive scrutiny from finance and a benefits committee

Quality Checklist

Before delivering output, verify:

• [ ] Every vendor is scored in all five categories with both raw (0–10) and weighted values shown
• [ ] Category weights sum to exactly 100 and each total is the correct weighted sum
• [ ] Any vendor failing a stated must-have or unable to confirm a compliance requirement is capped at 4 in Compliance
• [ ] Missing proposal data is marked "Not stated" and appears in the Red Flags list — never fabricated
• [ ] A single vendor is recommended, with the score margin over the runner-up stated
• [ ] 3–5 specific follow-up questions target the actual gaps and caveats found, not generic boilerplate

Notes

• The cheapest year-one price is the most common reason a bad vendor gets picked — rate guarantee length and fee transparency belong inside the cost score, not as afterthoughts.
• When two totals are within ~5 points, treat the decision as a tie and recommend a best-and-final (BAFO) round rather than forcing a false winner.
• If an incumbent is in the mix, note switching costs (implementation, member disruption, data migration) as context in the recommendation — they don't change the score but affect the real decision.
• For point solutions and admin platforms, integration should often be weighted higher than the default; suggest reweighting when the buyer's stack has fragile or legacy HRIS/payroll systems.

How to use this skill

This file is a Claude Code skill in Anthropic's standard format — markdown with YAML frontmatter at the top.

Installing in Claude Code:

• ~/.claude/skills/<folder-name>/SKILL.md — auto-loads in every session anywhere on your machine (recommended for skills you'll use across multiple projects)
• <your-project>/.claude/skills/<folder-name>/SKILL.md — auto-loads only when working in that project (recommended for project-specific skills)

Restart Claude Code or open a new session to register.

Using in Claude.ai, ChatGPT, Gemini, or other AI tools:

1. Drag this file into a new chat, or copy and paste its contents
2. Send your task or request as your next message — the AI will apply the skill where it fits

For Claude Code skill details: https://docs.anthropic.com/en/docs/claude-code/skills