# I’m designing pricing for a small developer tool with three p…

[Open the live Fudge conversation](https://design.withfudge.com/share/2d2mkkzo3q/i_m_designing_pricing_for_a_small_developer_tool_with_three_p/)

Last updated: 2026-07-30

I'll search for each pricing page and inspect them to compare the design patterns.

I have the three pricing pages identified. Let me inspect each one visually to compare their design patterns.

I have the Linear and Raycast pricing pages clearly. The Vercel screenshot shows the FAQ section rather than the pricing cards. Let me get a Vercel capture that shows the actual plan cards.

# Pricing Page Comparison: Linear vs Vercel vs Raycast

## Linear — Equal-weight, no emphasis

Linear presents three plans (Free, Standard, Enterprise) as visually identical cards. No "popular" badge, no color differentiation, no scale change. The hierarchy is purely informational: plan name → tagline → price → feature list → CTA. The design trusts the user to compare and choose.

**Strength:** Respects user judgment; works when plans serve genuinely different audiences.
**Weakness:** No guidance for users who don't already know what they need.

## Vercel — Middle plan emphasized

Vercel uses a three-card layout where the middle plan (Pro) carries a "Popular" badge above it and a solid blue CTA, while Hobby and Enterprise use outlined buttons. The cards share the same structure, but the badge + button color create a clear focal point.

**Strength:** Reduces decision paralysis; signals the recommended choice without hiding alternatives.
**Weakness:** Can feel pushy if the "popular" plan isn't actually right for the visitor.

## Raycast — Pro card visually distinct

Raycast uses only two plans (Free, Pro), but the Pro card has a distinct background treatment and a "Most popular" badge. The emphasis is stronger than Vercel's because the card itself looks different, not just the CTA.

**Strength:** Maximum clarity for a simple free-vs-paid decision.
**Weakness:** Only works with two tiers; harder to scale to three.

---

## Key Differences

| Dimension | Linear | Vercel | Raycast |
|-----------|--------|--------|---------|
| Plan count | 3 | 3 | 2 |
| Visual emphasis | None | Badge + CTA color | Badge + card background |
| Recommended plan | None | Middle (Pro) | Paid (Pro) |
| CTA differentiation | All outlined | Middle is filled | Pro is filled |
| Copy tone | Descriptive | Benefit-oriented | Value-oriented |

---

## Recommendation for Your Product

For a small developer tool with three plans, **follow Vercel's pattern**. Here's why:

1. **Three plans need a recommendation.** With three options, users face more choice anxiety than with two. A "Popular" or "Recommended" badge on the middle tier gives them a default without removing the alternatives.

2. **Differentiate the CTA, not the card.** Vercel's approach (same card structure, different button color) is cleaner than Raycast's (different card background). It signals emphasis without making the other plans feel like second-class options.

3. **Keep the middle plan as the recommended one.** For developer tools, the middle tier is usually the best default — it has the features most teams need without enterprise overhead. Putting the badge there guides users toward the plan you'll most often support.

4. **Use benefit-oriented copy.** Vercel's "Everything you need to build and scale your app" works better than Linear's purely descriptive approach because it tells the user *why* this plan exists, not just *what* it contains.

**Concrete pattern to implement:**
- Three identical cards, same height, same internal structure
- Middle card gets a small "Most popular" badge above the plan name
- Middle card's CTA is filled with your accent color; the other two are outlined
- Each card: plan name → one-line benefit → price → 5–7 key features → CTA
- Add a monthly/annual toggle above the cards if you offer both billing cycles

This gives you the clarity of Raycast's emphasis with the scalability of Vercel's three-tier structure, while avoiding Linear's "figure it out yourself" approach that can hurt conversion on a small product where users haven't formed opinions yet.