78 / 100

Firecrawl pricing teardown

https://www.firecrawl.dev/pricing

Firecrawl's pricing page uses a clean, credit-based slider model with transparent self-serve prices from $0 to $599, plus an Enterprise tier for custom needs, and a clearly marked 'Recommended' Standard plan to anchor purchase decisions. It's well optimized for self-serve conversion with a generous free tier and clear per-plan feature breakdowns, though the credit system and rate-limit fine print add some cognitive load.

Tier structure

Free Plan

$0/mo

Hobby

$16/mo

Standard

$83/mo (Recommended)

Growth

$333/mo

Scale

$599/mo

Enterprise

Custom

Value metric

usage-based credits consumed per API request (scrape/crawl/map/search/etc.), scaled via monthly credit allotment

How limits scale

Monthly credits 1,000 5,000 100,000 500,000 1,000,000 Custom
Concurrent requests 2 5 25 50 100 Custom
Support level Low rate limits Basic support Standard support Priority support Priority support Dedicated support & SLA

Escalation logic

An interactive slider lets users pick a monthly credit volume and see the matching plan/price, with each tier bundling more credits, higher concurrency, and better support as price rises; Enterprise breaks from self-serve into custom quoting with added security/compliance features.

Psychological anchors

  • Recommended badge — Standard plan ($83/mo) is highlighted with an orange 'Recommended' tag and distinct card styling, nudging users toward the mid-tier decoy.
  • Free tier as entry anchor — $0 Free Plan with 1,000 credits, no card required, lowers signup friction and anchors all paid tiers as incremental upgrades.
  • Annual discount framing — Each paid plan shows 'Billed yearly, Save $X' (e.g., Save $38, $198, $798, $1,798) rather than a percentage, emphasizing absolute savings.
  • High-priced tier anchor — Scale ($599/mo) and uncapped Enterprise sit above Growth, making the $83–$333 range look moderate by comparison.
  • Interactive credit slider — Slider spanning 1k to 1M+ credits reframes pricing as a continuous scale rather than discrete jumps, reinforcing 'pay for what you use' framing.
  • Charm-adjacent pricing — Prices like $16 and $83 (vs. round $15/$80) suggest usage-derived, credit-calculated pricing rather than arbitrary tiers.

What this page is optimizing for

Primarily self-serve conversion — prices, credits, and feature deltas are all fully visible with instant 'Subscribe' CTAs, and the free tier plus slider let users self-select a plan without sales contact; Enterprise exists only as a lead-gen escape valve for custom/compliance needs.

Red flags

  • Six tiers (including Enterprise) with a Scale plan positioned oddly close in features to Growth may cause some decision fatigue.
  • Credit-cost variability across features (Scrape=1, Search=2/10 results, Interact=2/min) adds complexity that isn't fully clear from the pricing cards alone.
  • No pay-per-use/overage option outside Scale's '$397 per extra 350k credits' add-on, which could frustrate users near a tier boundary.
  • Credits do not roll over on self-serve plans, a meaningful limitation buried in the FAQ rather than on the pricing cards themselves.
  • No visible free trial for paid tiers — users go straight from free credits to a paid subscription.

Best-practices scorecard

What works · 7

  • Clear recommended tier — Standard is explicitly labeled 'Recommended' with distinct visual treatment.
  • Visible prices — All self-serve tiers show exact monthly prices; only Enterprise is 'Contact sales'.
  • Annual discount offered — Yearly billing shows explicit dollar savings per tier (e.g., Save $198 on Standard).
  • Value metric matches usage — Credit-based system directly ties cost to scrape/crawl/search volume, matching how the product is consumed.
  • FAQ or objection handling — Detailed FAQ covers billing, credit rollover, failed requests, and tax questions.
  • Trust signals present — Y Combinator backing, SOC 2 Type 2 badge, GitHub star count (171K), and customer testimonials are all shown.
  • Clear CTAs per tier — Each plan has a distinct action button (Get started, Subscribe, Contact sales/us).

Half measures · 1

  • Tier differences are scannable — Core limits (credits, concurrency, support) are clear, but credit costs per feature require checking a separate table.