Skip to content
Back to Idea Validation

Pricing Benchmark

Map competitor pricing to understand the market's price range, packaging, and willingness to pay.

Why

Pricing is the most sensitive lever in product success, and you cannot set it in a vacuum. A pricing benchmark reveals the market's price ceiling (above which you lose to incumbents), floor (below which you seem cheap/untrustworthy), and typical packaging (per-seat vs per-usage vs flat). It also reveals expansion paths: how competitors grow revenue from existing customers through add-ons, usage tiers, or seat expansion. Without this map, you either price too low (leaving money on the table, signaling low quality) or too high (losing to competitors who deliver similar value for less). The benchmark also tells you what pricing model your segment expects — fighting the expected model is uphill.

When

After competitor teardown, before setting your price. Takes half a day. Revisit before any pricing change or new tier launch.

How

1. Collect pricing for 8-12 competitors
   - Visit their pricing pages, sign up for trials to see hidden tiers
   - Record: model (per-seat/usage/flat), price points, free tier, trial length
   - Note enterprise "contact us" pricing (estimate from their segment)

2. Normalize to compare
   - Convert all to a monthly per-user equivalent
   - Account for usage caps: "$50/mo for 10k requests" → per-1k-request rate
   - Note what is included vs add-on (support, SSO, integrations)

3. Map the distribution
   - Floor: cheapest viable competitor
   - Median: the middle of the pack
   - Ceiling: most expensive (usually enterprise)
   - Gaps: price points nobody occupies (opportunity or warning)

4. Analyze packaging
   - What is bundled in the base tier? (table stakes for pricing)
   - What triggers an upgrade? (seats, usage, features)
   - What is the expansion path? (how they grow revenue per account)

5. Choose your position
   - Below median: compete on price (risky — signals lower value)
   - At median: compete on differentiation (safest)
   - Above median: compete on premium value (requires clear differentiation)
   - Match the pricing model your segment expects (per-seat for teams, usage for infra)

Example

Product: a team wiki for engineering teams (competitors: Notion, Confluence, Slite, GitBook, Docusaurus).

Pricing benchmark (per user/month, normalized):
  Floor:   Docusaurus  $0 (OSS, self-host)
  Low:     Slite       $4/user
  Median:  GitBook     $8/user
  Median+: Notion      $10/user
  High:    Confluence  $11/user
  Ceiling: Enterprise  $20+ (custom)

Packaging analysis:
  - Base tier table stakes: unlimited pages, search, basic integrations
  - Upgrade triggers: seats > 10, advanced permissions, audit logs
  - Expansion: per-seat (everyone grows by adding people)
  - Free tier: all have one (land-and-expand)

Market gap:
  - $4-8 range is crowded (Slite, GitBook, Notion-ish)
  - $12-15 with "engineering-specific features" (code blocks, API docs, diagrams) is empty

Decision: price at $12/user, positioned as "the wiki built for engineering teams" — above Notion but with dev-specific features that justify the premium. Match per-seat model (expected for team tools).

Common Problems

  • ⚠Comparing list prices without normalizing — "$10 vs $50" ignores that the $50 includes 10x the usage allowance; normalize before comparing.
  • ⚠Ignoring the free tier — a competitor with a generous free tier effectively prices you at $0 for a large segment; account for land-and-expand.
  • ⚠Choosing a price in isolation — "I think $15 is fair" without benchmarking either underprices the market or overprices your value.
  • ⚠Copying a competitor's pricing model without their cost structure — per-usage pricing works for infra companies with low marginal cost, not for a SaaS with high per-user support cost.

Best Practices

  • ✓Normalize all prices to monthly per-user before comparing — this is the only way to compare per-seat, per-usage, and flat pricing on one axis.
  • ✓Map the gaps in the price distribution — an empty price range may be an opportunity (nobody serves it) or a warning (nobody will pay it).
  • ✓Match the pricing model your segment expects — teams expect per-seat, infra expects usage-based, consumers expect flat; fighting this is friction.
  • ✓Test your price with pre-orders at 2-3 price points — the market's willingness to pay is revealed by purchases, not by surveys.