Skip to content

rampstackco/claude-skills / skills/comparison-tool-design

comparison-tool-design

Verified

Designing side-by-side comparison tools (plan-compare, product-compare, alternative-compare) that help users decide rather than just listing features. Axis selection, default-comparison logic, recommendation discipline. Honest about feature-list-dump (every feature in a row, no decision support), hidden-recommendation (biased comparison pretending to be neutral), and honest-comparison-with-guidance (genuine comparison plus opinionated recommendation) patterns. Triggers on comparison tool, plan compare, product compare, alternative compare, vs page, decision support tool. Also triggers when conversion through comparison stages is poor, when users are abandoning at the comparison step, or when a comparison tool is being scoped for the first time.

references/comparison-tool-decision-criteria.md

View on GitHub
# Comparison-tool decision criteria

When comparison tools earn the build vs when written content serves.

A comparison tool is meaningful work. Axis selection, default logic, recommendation engine, filter UX, ongoing maintenance. The tool earns this investment only when specific conditions are present.

---

## When comparison tools earn the build

Five conditions that, when present, make a comparison tool a strong investment.

**The audience is at a decision moment between known options.** They know the options exist; they need help choosing. Audiences who do not yet know the options need different tools (quizzes, recommendations).

**The options have meaningful differences.** Comparing two options that differ only in branding produces nothing useful.

**The brand can articulate honest distinctions.** Without becoming sales pitch.

**The audience benefits from decision support.** Some audiences want a tool that helps them decide rather than weigh tradeoffs themselves.

**The success metric is defined.** Conversion through the tool, downstream conversion, choice quality.

When all five are present, a comparison tool is strong investment. When two or fewer are present, written content often serves better.

---

## When comparison tools do NOT earn the build

Funnels where comparison tools add cost without lift.

**Options too similar.** Comparing genuinely interchangeable options produces no decision support.

**Options apples-to-oranges.** Comparison axes do not apply across both.

**Brand cannot make honest distinctions.** Tool will become hidden-recommendation; trust suffers.

**A simple table or article would serve.** Static comparison content is cheaper.

**The audience does not face this decision.** Manufactured comparisons feel forced.

---

## Comparison tools vs written vs-pages

Both compare options; differ in interactivity.

**Written vs-pages strengths.** Cheap; SEO-friendly; easy to update.

**Written vs-pages weaknesses.** Static; no recommendation logic.

**Comparison tool strengths.** Adaptive; surfaces recommendations dynamically; lets users explore.

**Comparison tool weaknesses.** Build cost; maintenance burden.

**The combined approach.** Many production teams use both: vs-pages for SEO; tools for decision support.

---

## The opportunity-cost frame

Comparison tools are significant work.

**Build cost.** Axis curation, recommendation logic, filter UX, methodology disclosure, mobile responsiveness. 30-100 engineering hours plus design and content.

**Maintenance cost.** Quarterly updates run 4-8 hours.

**Opportunity cost.** What else could the team have built? Better vs-pages, calculator, quiz. The tool has to clear those alternatives.

The decision frame. Comparison tools earn investment when they produce more decision lift than alternatives.

---

## Decision worked example

A B2B SaaS analytics platform considering a comparison tool against 3 named competitors.

**Conditions check.**

- Decision moment: yes.
- Meaningful differences: yes; pricing, features, integration vary.
- Brand can articulate honest distinctions: yes.
- Audience benefits: yes.
- Success metric defined: yes.

**Decision.** Build the comparison tool.

**Architecture.** 10 axes; 4 options; honest recommendation per audience segment.

The decision was deliberate.

---

## Decision worked example: when written serves

A consumer-facing financial product considering a comparison tool against generic bank accounts.

**Conditions check.**

- Decision moment: yes.
- Meaningful differences: somewhat; many banks similar.
- Brand articulate distinctions: yes for specific competitors.
- Audience benefits: somewhat.
- Success metric: signup; harder to attribute.

**Decision.** Written vs-pages plus a brief comparison table. Full tool not warranted.

The decision was right-sized.

---

## When to retire a comparison tool

Tools can become wrong over time.

**Retire when:**

- Conversion declined consistently.
- Options changed enough that comparison is misleading.
- Competitors deprecated.
- A redesigned vs-page produces equivalent results.

The retire-or-redesign discipline frees capacity.

---

## Methodology-level choices that stay in the public skill

The five conditions that warrant comparison tools. The five conditions that argue against. Comparison tools vs written vs-pages. The opportunity-cost frame. Decision worked examples (yes and no). The retire decision.

## Implementation choices that stay internal

Specific tool decisions for specific products. The team's capacity benchmarks. Specific tooling. Specific success-metric baselines. These vary by team and product.
brainstormingobra/superpowersYou MUST use this before any creative work - creating features, building components, adding functionality, modifying behavior, or planning anything new, in software or out of it (a talk, a business, a renovation).Stars: 322kUpdated Claude CodeCodexVerifiedInstall
brand-guidelinesanthropics/skillsApplies Anthropic's official brand colors and typography to any sort of artifact that may benefit from having Anthropic's look-and-feel. Use it when brand colors or style guidelines, visual formatting, or company design standards apply.Stars: 198kUpdated Claude CodeCodexVerifiedInstall
frontend-designanthropics/skillsGuidance for distinctive, intentional visual design when building new UI or reshaping an existing one. Helps with aesthetic direction, typography, and making choices that don't read as templated defaults.Stars: 198kUpdated Claude CodeCodexVerifiedInstall
mcp-builderanthropics/skillsGuide for creating high-quality MCP (Model Context Protocol) servers that enable LLMs to interact with external services through well-designed tools. Use when building MCP servers to integrate external APIs or services, whether in Python (FastMCP) or Node/TypeScript (MCP SDK).Stars: 198kUpdated Claude CodeCodexVerifiedInstall