comparison-table-design

name	comparison-table-design
description	Use when designing comparison tables (vs competitors, vs in-house, vs hire). Covers the patterns that don't feel like attack ads, what to include, how to handle the case where competitors don't expose data, and ethical comparison.

Comparison Table Design

Comparison tables are powerful when honest and useful when specific. Done poorly, they read as attack ads.

When to include comparison

Show comparison when:

• You're entering a market with established alternatives
• Your value-prop is "X but cheaper / faster / better"
• Buyers actively compare (research-mode visitors)

Skip comparison when:

• You're creating a new category (no benchmark)
• Competitors are sensitive / legal-aggressive
• Your real advantage isn't feature-level (e.g., brand, support)

What to compare

Row choices, in order of impact:

1. Annual / total cost — biggest mover
2. Features your product has that competitor lacks — show your strength
3. Implementation time / friction — often overlooked
4. Support quality / response time
5. Refund / cancel terms
6. Open-source / transparency (if applicable)

Comparison patterns

Pattern 1: Side-by-side table

Rows = features. Columns = products. ✓ / — for each cell.

Pros: Quick scan. Cons: Easy to look like attack ad.

Pattern 2: Feature highlights

For 3-5 specific features, show what you do vs what alternatives do (paragraph form).

Pros: More nuanced. Cons: Longer, more scrolling.

Pattern 3: "You vs them" calculator

Plug in user inputs, see comparison.

Pros: Personalized. Cons: Complex to build.

Ethical comparison

• ✓ Compare features actually documented on competitor's site
• ✓ Use neutral language ("supports vs doesn't support")
• ✓ Note "as of [date]" since competitors change
• ✓ Link to competitor's own comparison/pricing for verification
• ✗ Fabricate features competitors lack
• ✗ Use red ✗ excessively (looks aggressive)
• ✗ Mock competitors by name

When competitors don't expose data

Some competitors hide pricing or features. Options:

• Mark "Custom" or "Not disclosed" — accurate, not antagonistic
• Estimate based on public sources — "$X-$Y" with note
• Skip the row entirely — don't fabricate

Visual design

• Your column highlighted (background tint, "us" label)
• ✓ in your color, — for absence (not red ✗)
• Footnotes for anything that needs nuance ("¹ Subject to plan tier")
• Date-stamped at top ("Updated September 2026")

Common mistakes

• Six rows where you're identical (waste)
• Red X marks everywhere (mean-spirited)
• Wildly different "feature names" in rows (manipulation)
• No date — looks outdated
• Comparison vs "everyone else" (vague)

Where this fits in X3 Compass

X3 Compass has /compare with 5-column table: Compass / Hire SD / Foley / JJ Keller / Compliance Navigator. Honest cell values, Compass column highlighted, "Spot an error?" mailto at bottom.