ProgrammableMarketing/firecrawl.dev (opens in a new tab)
PDF

Views

  • Plan
  • Roadmap
  • Research

On this page

  • The brief
  • Start here
  • Idea portfolio
  • Effort vs impact
  • This week · 6
  • This quarter · 10
  • Big bets · 4
  • Wildcards · 4
  • How we can help
Generated Oct 18, 2026
  1. Programmable
  2. Playbooks
  3. Firecrawl
Firecrawl logo

growth playbook · Oct 18, 2026

firecrawl.dev (opens in a new tab)

Firecrawl growth playbook

Diagnosis

Firecrawl has one of the largest developer funnels in AI: 1.25M+ developers, 192k GitHub stars and 400,000+ MCP installs, with eight-figure ARR in year one that more than doubled in year two.

Its 33 open roles show where it is putting the $75M: a sales-led enterprise motion (six Deployment roles, including outbound), a growth team that keeps paid, SEO/GEO, YouTube and launch video, agents as a channel in their own right, the supply side of Alexandria (partnerships and weekly benchmarks), and five legal roles for the least settled ground in the market.

This playbook gives those hires their first 90 days. The gaps it targets are in the paths to money: free users get no usage-based upgrade prompt, paid is judged on signups, accounts created by agents have no human path, and Alexandria asks providers to join without saying what they will earn.

Growth Score

8/10

Biggest Opportunity

Use what Firecrawl can see (agent demand, benchmark results, scrape success and usage growth) as its sales tools: a demand board and benchmark outreach that bring providers in, usage signals that feed the new outbound team, and prompts that move free and agent-created accounts to paid.

Biggest Risk

Agent search APIs are within noise of each other on quality, competitors publish "Firecrawl alternatives" pages, and the law on crawling is unsettled; without proof of reliability and a clear access policy, price and legal caution become the deciding factors.

01

Start here

The three moves to make first. Each one is written up in full below.

  1. 1

    An upgrade prompt at 80% of free credits that names the plan their usage actually needs

    Query how many free accounts crossed 800 credits last month and what share of them paid within 30 days.

    High impact First result in 2 weeks
  2. 2

    Rewrite the Firecrawl vs Tavily page for the Nebius acquisition, with a drop-in migration snippet

    Add one paragraph about the Nebius acquisition and fix the provider count on the Firecrawl vs Tavily page today.

    High impact First result in 2-4 weeks
  3. 3

    A public Alexandria "most requested sources" board so providers come to you

    Pull last month's failed Alexandria lookups and scrape requests by domain and list the top 50 that have an identifiable rights owner.

    High impact First result in 3 weeks

02

Your idea portfolio

24 ideas, grouped by when to run them. Open any idea for how to run it: the steps, who to approach, copy you can use, and how to measure it.

  • 10 ideas are marked Unexpected: plays you are unlikely to have tried.

    2 of these are things Programmable can build and run for you.

Every idea placed by the effort it takes against the impact it could have. Quick wins sit top left; select a number to open that idea. The filters below narrow the list by status, timing, category and what Programmable can build.

Effort vs impactEach number is an idea. Select one to open it.
Impact →
Quick wins · 4Big bets · 15Fill-ins · 2Reconsider · 3
Effort →

Showing 24 of 24 ideas

This week 6

Quick wins with a clear first action.

  • 01

    1.25M developers start on 1,000 free credits, and the moment they run low is the one moment a self-serve user thinks about paying. Today that moment is a pricing page with five plans and a credit table.

    High impactLow effort First result in 2 weeks Growth Engineer

    First action

    Query how many free accounts crossed 800 credits last month and what share of them paid within 30 days.

    How to measure it

    Paid conversion after the 80% prompt

    Now
    –
    Target
    +30% relative
    By
    6 weeks

    Steps

    1. 1

      Find the baseline

      Free accounts that crossed 800 credits last month, and how many paid within 30 days.

      Growth Engineer 2 hours

    2. 2

      Project the month

      Daily credit burn times days left, split by endpoint, so JSON extraction is counted at 5 credits.

      Growth Engineer 1 day

    3. 3

      Pick the plan

      Smallest plan that covers the projection with 20% headroom; show the yearly price.

      Growth Engineer 2 hours

    4. 4

      Banner and one email

      One in-app banner and one email; no repeated nags.

      Growth Engineer 1 day

    5. 5

      Explain the add-on

      If JSON extraction is most of the burn, say so in one line.

      Growth Engineer 1 hour

    6. 6

      A/B test

      Half get the prompt, half see today's experience, for three weeks.

      Growth Engineer 2 hours

    7. 7

      Report

      Conversion and plan mix by arm, weekly.

      Growth Engineer 30 minutes a week

    First result
    2 weeks
    Cost
    $0, about three days of engineering
    Owner
    Growth Engineer

    Smallest test

    Send the email by hand to the 100 accounts closest to their limit this week.

    Why it works

    When an account passes 800 credits in a month, show an in-app banner and send one email: "At your pace you'll use about 4,200 credits this month. Hobby covers 5,000 for $16." Use their own endpoint mix, including JSON extraction at 5 credits a page, so the recommendation is right.

    The Growth Engineer is measured on conversion. A recommendation built from the user's own usage removes the work of reading the credit table, and the JSON add-on is the most common reason a free user runs out sooner than expected.

    Ready to use

    Email80% credits email

    Subject: You've used 812 of your 1,000 free credits
    
    Hi {first name},
    
    At your pace this month you'll use about {projected} credits, mostly {top endpoint}.
    
    {Plan} covers {plan credits} a month for ${price}, and you can cap pay-as-you-go so nothing surprises you.
    
    Upgrade in one click: {link}
    
    The Firecrawl team

    Risks and how to handle them

    • Projections are wrong for bursty usage

      Use the last 7 days rather than the month to date, and say "about".

    Evidence

    • HiringGrowth Engineer, Product Growth: "Own the growth surfaces end to end: signup, activation, onboarding, and conversion"; "Treat conversion and activation as your number"; experience with playgrounds, docs surfaces and upgrade flows is a bonus.Source
    • Your websitePricing: Free 1,000 credits a month (no card), Hobby $16/month yearly, Standard $83, Growth $333, Scale $599 (yearly), Enterprise custom. Credits roll over only on Scale (one month) and Enterprise. JSON extraction adds 4 credits a page; an error page such as a 403 costs 1 credit. The page shows no customer logos, only testimonials from X users.Source
    • Your websiteHomepage: "Give your AI agents web data and beyond"; claims 150,000+ companies, 1.25M+ developers, 5 billion+ requests, 400,000+ MCP servers installed and 2.5M+ weekly SDK downloads; logos include Shopify, Lovable, Canva, Zapier, Apple, Replit, DoorDash, Gamma and Sierra.Source
  • 02

    Developers who picked a small independent search API now depend on a cloud provider's roadmap. Firecrawl's comparison page doesn't mention the acquisition and still says "90+ data providers" when Alexandria lists 278.

    High impactLow effort First result in 2-4 weeks Head of Growth Marketing

    First action

    Add one paragraph about the Nebius acquisition and fix the provider count on the Firecrawl vs Tavily page today.

    How to measure it

    Signups from Tavily pages

    Now
    –
    Target
    2× the previous month
    By
    6 weeks

    Steps

    1. 1

      State the facts

      Link the acquisition announcement and make no claims about Tavily's future.

      Head of Growth Marketing 1 hour

    2. 2

      Fix the numbers

      Replace "90+ data providers" with the live Alexandria count.

      Head of Growth Marketing 15 minutes

    3. 3

      Map the parameters

      A table from each Tavily search option to its Firecrawl equivalent, with gaps noted.

      Growth Engineer 1 day

    4. 4

      Write drop-in snippets

      Python and Node, before and after, under 15 lines each.

      Growth Engineer 2 hours

    5. 5

      Target the searches

      Title and headings for "Tavily alternative", "Tavily Nebius" and "Tavily vs Firecrawl".

      Head of Growth Marketing 1 hour

    6. 6

      Make it readable by agents

      A markdown version of the migration so a coding agent can do the switch for the user.

      Agent Experience Engineer 2 hours

    7. 7

      Launch quietly

      A post from the Chief Growth Officer and a newsletter note; no attack ads.

      Chief Growth Officer 30 minutes

    First result
    2 to 4 weeks
    Cost
    $0
    Owner
    Head of Growth Marketing

    Smallest test

    Update the page's first paragraph and numbers and watch its signups for two weeks.

    Why it works

    Update the existing comparison page and the "Tavily alternatives" post: what the acquisition means (facts only), a table mapping Tavily search parameters to Firecrawl Search, before-and-after code in Python and Node, and the current Alexandria numbers.

    The Head of Growth Marketing owns SEO/GEO and weekly signups. The page already ranks for "Firecrawl vs Tavily"; an ownership change is when switching feels cheapest, and a parameter map removes the real cost of switching.

    Risks and how to handle them

    • Reads as opportunistic

      Keep it factual and useful; the parameter map is the value.

    Evidence

    • programmable.infoThe site already has 21 "Firecrawl vs" pages (Tavily, Exa, Parallel and others), about 280 Alexandria site pages with "Try in Agent", 232 glossary pages, 10 free tools and a /benchmarks section. The Firecrawl vs Tavily page says "90+ data providers" and does not mention the Nebius acquisition.Source
    • Competitor researchAn independent 2026 benchmark found Brave, Firecrawl, Exa and Parallel within noise of each other on agentic search quality, with latency varying 20×. Parallel published a "Firecrawl alternatives" page on October 11, 2026. Nebius completed its acquisition of Tavily in 2026.Source
    • HiringHead of Growth Marketing: own weekly signup pacing across SEO/GEO, partnerships, brand and paid; "Take over our paid ads program and the agency running it: audit it in your first month and decide to scale, fix, or end it"; inherit product marketing, SEO, paid and YouTube. Eric Ciarla, the Chief Growth Officer, owns narrative, launches and open source.Source
    • Your websiteAlexandria page: "The knowledge library for superintelligence"; 278 providers, 1,672 capabilities, 113M+ indexed sources; featured providers include Shopify, Benzinga, Apollo, Fiscal.ai and FullEnrich. Providers join a waitlist "to get paid"; no payout terms are published. The homepage still says 93 providers and 640 capabilities.Source
  • 03

    The Partnerships Manager is asked to go outbound to "sources ranked by agent demand". That ranking is the strongest pitch Firecrawl has, and it is private.

    High impactLow effort First result in 3 weeks Partnerships Manager

    First action

    Pull last month's failed Alexandria lookups and scrape requests by domain and list the top 50 that have an identifiable rights owner.

    How to measure it

    Providers claiming a listed source

    Now
    –
    Target
    15
    By
    8 weeks

    Steps

    1. 1

      Rank the demand

      Requests and failed lookups by source over 30 days.

      Partnerships Manager, Alexandria 1 day

    2. 2

      Band the numbers

      Show volume bands (10k+, 50k+) rather than exact counts.

      CFO 1 hour

    3. 3

      Check the list

      Remove anything where naming demand would embarrass a customer.

      Partnerships Manager, Alexandria 2 hours

    4. 4

      Build the board

      A simple page with category filters and a "Claim this source" button.

      Growth Engineer 2 days

    5. 5

      Prefill the waitlist

      The claim form carries the source and demand band to the Partnerships Manager.

      Growth Engineer 2 hours

    6. 6

      Send it to the owners

      Email the top 20 with their row linked.

      Partnerships Manager, Alexandria 1 day

    7. 7

      Refresh monthly

      Regenerate the board and post what came online.

      Partnerships Manager, Alexandria 1 hour a month

    First result
    3 weeks
    Cost
    $0
    Owner
    Partnerships Manager, Alexandria

    Smallest test

    Send the email with the demand band to ten owners before building the public board.

    Run this outreach. The sequence sent for you: addresses found and verified, replies routed to your CRM. Usually live within days.

    Book a working session

    Why it works

    Publish a live board of the 50 sources agents request most that Alexandria cannot yet serve (by category, with request volume bands), and a "Claim this source" button that drops the owner straight into the provider waitlist with the demand number attached.

    A rights owner who sees that agents asked for their data 40,000 times last month has a reason to reply. It turns a cold outbound list into inbound, and the board doubles as content about where agent demand is going.

    Ready to use

    EmailSource owner outreach

    Subject: AI agents asked for {source} 40,000+ times last month
    
    Hi {first name},
    
    Firecrawl serves web data to AI agents for 150,000+ companies. {Source} is one of the most requested sources our agents can't yet access properly: it's #{rank} on our public demand board ({link}).
    
    Alexandria pays providers for attributed access when agents use their data. If you own the rights, a 20-minute call would tell you what that demand is worth.
    
    {name}
    Partnerships, Firecrawl Alexandria

    Risks and how to handle them

    • Publishing demand helps competitors prioritise

      Show bands and categories, not exact counts, and only the top 50.

    Evidence

    • HiringPartnerships Manager, Alexandria: triage the provider waitlist, go outbound to "sources ranked by agent demand", negotiate rights and redistribution, and report catalog gaps; measured on "which sources come online, how fast, and on what terms". Providers get "paid, attributed access" to agent demand.Source
    • Your websiteAlexandria page: "The knowledge library for superintelligence"; 278 providers, 1,672 capabilities, 113M+ indexed sources; featured providers include Shopify, Benzinga, Apollo, Fiscal.ai and FullEnrich. Providers join a waitlist "to get paid"; no payout terms are published. The homepage still says 93 providers and 640 capabilities.Source
    • Search resultsSeries B announcement: Alexandria combines paid official data providers, a Research Index, a Developer Index, a Government Index and site connectors; Firecrawl already pays providers such as Wikimedia Enterprise and plans a self-service system for contributors to earn when agents use their knowledge.Source
  • 04

    The homepage lists 93 Alexandria providers and 640 capabilities, the comparison pages say "90+", and the Alexandria page lists 278 and 1,672. The nav says 192.5K stars and the FAQ says "over 180K". For a company selling data accuracy, stale numbers undercut the claim.

    Medium impactLow effort First result in 1 week Member of Design Staff

    First action

    List every page and template that shows a number and where each number comes from today.

    How to measure it

    Public numbers out of date

    Now
    –
    Target
    zero
    By
    1 week

    Steps

    1. 1

      Inventory the numbers

      Every page, email template and asset that shows a count.

      Member of Design Staff 2 hours

    2. 2

      Build the endpoint

      One JSON endpoint updated daily from the source systems.

      Growth Engineer 1 day

    3. 3

      Render from it

      Homepage, Alexandria, pricing and FAQ read from the endpoint.

      Growth Engineer 1 day

    4. 4

      Give design a token

      Launch templates in Alloy pull the current number when exported.

      Member of Design Staff 2 hours

    5. 5

      Round consistently

      One rounding rule (192.5K, 278) so numbers match across pages.

      Member of Design Staff 30 minutes

    6. 6

      Check weekly

      A script that flags any page whose numbers differ from the endpoint.

      Growth Engineer 2 hours

    First result
    1 week
    Cost
    $0, about three days of work
    Owner
    Member of Design Staff

    Smallest test

    Fix the homepage Alexandria counts by hand today.

    Why it works

    Serve every public number (providers, capabilities, indexed sources, stars, requests served, weekly SDK downloads) from one stats endpoint updated daily, and render it everywhere, including launch assets and job posts.

    The Member of Design Staff ships launch assets constantly; each one copies numbers that are already out of date. A single source keeps every surface current and turns growing numbers into a live proof point.

    Risks and how to handle them

    • A number drops and shows in public

      Show monotonic totals (requests served) and review any falling count before it renders.

    Evidence

    • Your websiteAlexandria page: "The knowledge library for superintelligence"; 278 providers, 1,672 capabilities, 113M+ indexed sources; featured providers include Shopify, Benzinga, Apollo, Fiscal.ai and FullEnrich. Providers join a waitlist "to get paid"; no payout terms are published. The homepage still says 93 providers and 640 capabilities.Source
    • programmable.infoThe site already has 21 "Firecrawl vs" pages (Tavily, Exa, Parallel and others), about 280 Alexandria site pages with "Try in Agent", 232 glossary pages, 10 free tools and a /benchmarks section. The Firecrawl vs Tavily page says "90+ data providers" and does not mention the Nebius acquisition.Source
    • Your websiteHomepage: "Give your AI agents web data and beyond"; claims 150,000+ companies, 1.25M+ developers, 5 billion+ requests, 400,000+ MCP servers installed and 2.5M+ weekly SDK downloads; logos include Shopify, Lovable, Canva, Zapier, Apple, Replit, DoorDash, Gamma and Sierra.Source
    • HiringMember of Design Staff: launch videos and social assets "for a constant launch cadence", concepting every launch with the Creative Lead; the work is "the first thing millions of developers see from us".Source
  • 05

    The homepage names Shopify, Canva, Zapier, Apple and DoorDash; the pricing page, where a buyer decides between $83 and $333 a month, shows only tweets from individual developers.

    High impactLow effort First result in 2 weeks Growth Engineer

    First action

    Ask three customers on Growth or Scale for one sentence and a number they would put their name to.

    How to measure it

    Pricing page to paid checkout

    Now
    –
    Target
    +15% relative
    By
    4 weeks

    Steps

    1. 1

      Collect three outcomes

      One sentence and one number from named Growth, Scale and Enterprise customers.

      Chief Growth Officer 1 week

    2. 2

      Confirm logo rights

      Written approval for each logo on pricing.

      Chief Growth Officer 2 hours

    3. 3

      Place by plan

      Each outcome next to the plan that customer is on.

      Member of Design Staff 2 hours

    4. 4

      Keep one developer quote

      One short X quote for the Free and Hobby column.

      Member of Design Staff 30 minutes

    5. 5

      A/B test

      New proof against the current wall for two weeks.

      Growth Engineer 2 hours

    6. 6

      Ship the winner

      Keep whichever lifts checkout starts.

      Growth Engineer 15 minutes

    First result
    2 weeks
    Cost
    $0
    Owner
    Growth Engineer

    Smallest test

    Add the logo strip to pricing alone for a week.

    Why it works

    Move the strongest logos to the pricing page and replace the tweet wall with three short outcomes from named companies (for example AgentOps moving off Apify for a 50× speed-up), placed next to Growth, Scale and Enterprise.

    Conversion is the Growth Engineer's number. On a usage-based pricing page the question is "do companies like mine trust this at volume", which tweets from individual builders do not answer.

    Risks and how to handle them

    • Customers decline to give numbers

      Use relative outcomes ("50× faster") or descriptors ("a public e-commerce platform").

    Evidence

    • Your websitePricing: Free 1,000 credits a month (no card), Hobby $16/month yearly, Standard $83, Growth $333, Scale $599 (yearly), Enterprise custom. Credits roll over only on Scale (one month) and Enterprise. JSON extraction adds 4 credits a page; an error page such as a 403 costs 1 credit. The page shows no customer logos, only testimonials from X users.Source
    • Your websiteHomepage: "Give your AI agents web data and beyond"; claims 150,000+ companies, 1.25M+ developers, 5 billion+ requests, 400,000+ MCP servers installed and 2.5M+ weekly SDK downloads; logos include Shopify, Lovable, Canva, Zapier, Apple, Replit, DoorDash, Gamma and Sierra.Source
    • Your websiteTestimonial: Alex Reibman (AgentOps) "Moved our internal agent's web scraping tool from Apify to Firecrawl because it benchmarked 50x faster"; Steven Tey: "Open-source Clay alternative just dropped".Source
    • HiringGrowth Engineer, Product Growth: "Own the growth surfaces end to end: signup, activation, onboarding, and conversion"; "Treat conversion and activation as your number"; experience with playgrounds, docs surfaces and upgrade flows is a bonus.Source
    • programmable.infoIn the past year the starting price rose from $9 to $16 a month and the headline changed from "Turn websites into LLM-ready data" to "Give your AI agents web data and beyond". npm downloads are about 957k a week across 23 packages; YouTube has 61.7k subscribers and 111 videos.Source
  • 06

    A 403 or 404 page costs a credit and JSON extraction costs five, but a user only sees a balance going down. The Support Engineer's queue is "failed scrapes, blocked sites and rate limits", which is exactly what a receipt would explain.

    Medium impactLow effort First result in 3 weeks Support Engineer

    First action

    Tag last month's support tickets and count how many are about unexpected credit use.

    How to measure it

    Credit-charge tickets per 1,000 paid accounts

    Now
    –
    Target
    -40%
    By
    6 weeks

    Steps

    1. 1

      Count the tickets

      Tag a month of tickets by cause.

      Support Engineer 3 hours

    2. 2

      Define the receipt

      Succeeded, error status, no result, add-ons, total.

      Support Engineer 1 hour

    3. 3

      Add it to the API

      A credits object in the crawl and batch response.

      Growth Engineer 1 day

    4. 4

      Show it in the dashboard

      A receipt panel on each job.

      Growth Engineer 1 day

    5. 5

      Link the runbooks

      Each failure type links to its troubleshooting guide.

      Support Engineer 2 hours

    6. 6

      Teach the AI support agent

      Point the support agent at the receipt fields.

      Support Engineer 1 hour

    First result
    3 weeks
    Cost
    $0, about three days of engineering
    Owner
    Support Engineer

    Smallest test

    Add the receipt to the crawl API response only and watch ticket tags for two weeks.

    Why it works

    Show a per-job breakdown in the dashboard and the API response: pages succeeded, pages that returned error status (and that they cost 1 credit), pages with no result (free), add-on credits, and a link to the runbook for each failure type.

    The Support Engineer is measured on leverage rather than tickets. A receipt answers the most common billing question before it becomes a ticket, and fewer surprise charges protects net revenue retention.

    Risks and how to handle them

    • Showing error charges draws complaints

      The charge exists either way; explaining it lowers disputes.

    Evidence

    • HiringSupport Engineer: first-line technical support for "high-value and enterprise accounts": failed scrapes, blocked sites and rate limits; keep the AI support agents effective and write runbooks and docs fixes; measured on "leverage", not tickets closed.Source
    • Your websitePricing: Free 1,000 credits a month (no card), Hobby $16/month yearly, Standard $83, Growth $333, Scale $599 (yearly), Enterprise custom. Credits roll over only on Scale (one month) and Enterprise. JSON extraction adds 4 credits a page; an error page such as a 403 costs 1 credit. The page shows no customer logos, only testimonials from X users.Source
    • HiringGrowth Engineer, Product Growth: "Own the growth surfaces end to end: signup, activation, onboarding, and conversion"; "Treat conversion and activation as your number"; experience with playgrounds, docs surfaces and upgrade flows is a bonus.Source

This quarter 10

The core plays for the next three months.

  • 07

    The new Head of Growth Marketing must audit the paid program and its agency in month one and decide to scale, fix or end it. With 1,000 free credits and no card at signup, cost per signup says little; most of what paid buys may be free accounts that never pay.

    High impactMedium effort First result in 4-6 weeks Head of Growth Marketing

    First action

    Export 90 days of paid campaigns and join them to accounts that paid, by UTM and signup date.

    How to measure it

    Paid-channel cost per paying account

    Now
    –
    Target
    -30%
    By
    end of quarter

    Steps

    1. 1

      Join spend to revenue

      Campaign spend to accounts that paid within 90 days of signup.

      Growth Engineer 2 days

    2. 2

      Score every campaign

      Cost per paid account and 90-day revenue, ranked.

      Head of Growth Marketing 1 day

    3. 3

      Test brand bidding

      Pause "firecrawl" brand terms in one region for two weeks and compare total signups.

      Head of Growth Marketing 2 weeks

    4. 4

      Shift to intent terms

      Competitor and use-case terms with landing pages that already exist (comparisons, use cases).

      Head of Growth Marketing 1 week

    5. 5

      Test sponsorships

      Two developer YouTube channels and two newsletters, each with its own code.

      Head of Growth Marketing 4 weeks

    6. 6

      Set the agency's goal

      Agency judged on cost per paid account from now on.

      Head of Growth Marketing 1 hour

    7. 7

      Decide

      Scale, fix or end, in writing, with the numbers.

      Head of Growth Marketing 1 day

    First result
    4 to 6 weeks
    Cost
    No new spend; reallocates the current budget
    Owner
    Head of Growth Marketing

    Smallest test

    Recompute last quarter's campaigns on cost per paid account before changing any bids.

    Why it works

    Rebuild paid reporting on cost per paid account and 90-day revenue, split by campaign. Then test three changes: stop bidding on "firecrawl" where organic already captures it, move budget to high-intent competitor and use-case terms ("tavily alternative", "scrape website to markdown"), and test sponsorships on developer YouTube channels and newsletters against search.

    Firecrawl clearly values paid enough to keep an agency and make its review a first-month goal. A free tier this generous makes signup-based reporting misleading, and the audit decides the budget for the year.

    Ready to use

    ChecklistMonth-one paid audit

    [ ] 90 days of spend by campaign, joined to accounts that paid
    [ ] Cost per signup vs cost per paid account, by campaign
    [ ] Brand-term holdout in one region
    [ ] Search terms report: which queries bought free accounts only
    [ ] Landing page per campaign: does it match the query?
    [ ] Agency fee as a share of spend
    [ ] Recommendation: scale, fix or end, with the budget for next quarter

    Risks and how to handle them

    • Pausing brand terms lets competitors bid on "firecrawl"

      Hold out one region only and watch competitor impression share.

    Evidence

    • HiringHead of Growth Marketing: own weekly signup pacing across SEO/GEO, partnerships, brand and paid; "Take over our paid ads program and the agency running it: audit it in your first month and decide to scale, fix, or end it"; inherit product marketing, SEO, paid and YouTube. Eric Ciarla, the Chief Growth Officer, owns narrative, launches and open source.Source
    • Your websitePricing: Free 1,000 credits a month (no card), Hobby $16/month yearly, Standard $83, Growth $333, Scale $599 (yearly), Enterprise custom. Credits roll over only on Scale (one month) and Enterprise. JSON extraction adds 4 credits a page; an error page such as a 403 costs 1 credit. The page shows no customer logos, only testimonials from X users.Source
    • programmable.infoIn the past year the starting price rose from $9 to $16 a month and the headline changed from "Turn websites into LLM-ready data" to "Give your AI agents web data and beyond". npm downloads are about 957k a week across 23 packages; YouTube has 61.7k subscribers and 111 videos.Source
    • Competitor researchAn independent 2026 benchmark found Brave, Firecrawl, Exa and Parallel within noise of each other on agentic search quality, with latency varying 20×. Parallel published a "Firecrawl alternatives" page on October 11, 2026. Nebius completed its acquisition of Tavily in 2026.Source
  • 08

    The Search Engineer owns scrape success rate, and the homepage cites a one-off 96% coverage benchmark. The /benchmarks section rates other providers (company enrichment, DevDex), but nothing tracks Firecrawl's own reliability over time.

    High impactMedium effort First result in 1 month Search Engineer

    First action

    Freeze the 1,000-URL set used for the homepage benchmark and publish its methodology.

    How to measure it

    Signups from the success report

    Now
    –
    Target
    300 a month
    By
    third report

    Steps

    1. 1

      Freeze the test set

      The 1,000 URLs, balanced across categories, published openly.

      Search Engineer 2 days

    2. 2

      Automate the run

      A monthly job that records success, latency and tokens.

      Search Engineer 1 week

    3. 3

      Write the regressions honestly

      What got worse, why, and what shipped.

      Search Engineer 2 hours a month

    4. 4

      Design the page

      One chart per category and a downloadable CSV.

      Member of Design Staff 2 days once

    5. 5

      Invite others to run it

      A script anyone can run against any API.

      Search Engineer 2 days

    6. 6

      Launch each report

      Chief Growth Officer post and a short video.

      Chief Growth Officer 1 hour a month

    First result
    1 month
    Cost
    Run costs under $500 a month
    Owner
    Search Engineer

    Smallest test

    Publish one report as a blog post and see whether competitors or writers cite it.

    Why it works

    Publish success rate, P95 latency and token savings every month by category (e-commerce, news, docs, social, government), with the methodology, what regressed and what was fixed, and an open 1,000-URL test set others can run.

    An independent benchmark already found the top agent search APIs within noise of each other, so reliability over time is the difference a buyer can verify. A monthly report gives sales, the CMO and support one number to point to.

    Risks and how to handle them

    • A bad month is public

      That honesty is the point; publish the fix with the regression.

    Evidence

    • HiringSearch Engineer: reverse engineer how sites detect automated traffic, build diagnostics and monitoring, and "Own scrape success rate: Measure it, explain regressions, and ship the fixes."Source
    • Your websiteHomepage benchmark: 96% coverage on a 1,000-URL benchmark against Puppeteer 79% and cURL 75%, a P95 latency of 3,387 ms and 93% fewer input tokens.Source
    • HiringResearch Engineer, Benchmarks: weekly public benchmarks of data providers (for example Apollo vs FullEnrich vs DataLegion, Built In vs ZipRecruiter), public leaderboard pages with marketing, and results that change which provider Alexandria calls. "Our numbers have to survive the vendors who lose." The company enrichment benchmark (October 2) ranked Apollo.io first of six providers.Source
    • Competitor researchAn independent 2026 benchmark found Brave, Firecrawl, Exa and Parallel within noise of each other on agentic search quality, with latency varying 20×. Parallel published a "Firecrawl alternatives" page on October 11, 2026. Nebius completed its acquisition of Tavily in 2026.Source
  • 09

    Credits roll over only on Scale and Enterprise. Teams with uneven usage on Standard and Growth lose unused credits each month, which is the strongest argument for dropping to a smaller plan.

    High impactMedium effort First result in 1 quarter CFO

    First action

    Measure what share of Standard and Growth accounts left more than 30% of credits unused in any of the last three months, and their downgrade rate.

    How to measure it

    Yearly share of new Standard and Growth subscriptions

    Now
    –
    Target
    +10 points
    By
    end of quarter

    Steps

    1. 1

      Measure unused credits

      Unused share by plan and month, and its link to downgrades.

      CFO 2 days

    2. 2

      Model the cost

      Revenue recognized and breakage lost under one-month rollover.

      CFO 2 days

    3. 3

      Decide the rule

      One month, yearly plans only, capped at one month of credits.

      CFO 1 hour

    4. 4

      Build it

      Billing logic and a rollover line on the usage page.

      Growth Engineer 1 week

    5. 5

      Put it on the toggle

      "Yearly: 2 months free and unused credits roll over".

      Growth Engineer 2 hours

    6. 6

      Measure

      Yearly mix and downgrades against the prior quarter.

      CFO monthly

    First result
    1 quarter
    Cost
    Lost breakage, sized in the model before launch
    Owner
    CFO

    Smallest test

    Offer rollover to Growth customers who are about to downgrade and track who stays.

    Why it works

    Offer one month of rollover on yearly Standard and Growth plans, and make it the headline of the yearly toggle. Model the breakage first so the CFO knows the cost.

    The CFO is hired to set credit, prepaid and pay-as-you-go policy; the Growth Engineer owns conversion. Rollover makes yearly plans safer to buy and removes a common downgrade trigger.

    Risks and how to handle them

    • Revenue recognition gets harder

      Cap rollover at one month and agree treatment with the auditor first.

    Evidence

    • Your websitePricing: Free 1,000 credits a month (no card), Hobby $16/month yearly, Standard $83, Growth $333, Scale $599 (yearly), Enterprise custom. Credits roll over only on Scale (one month) and Enterprise. JSON extraction adds 4 credits a page; an error page such as a 403 costs 1 credit. The page shows no customer logos, only testimonials from X users.Source
    • HiringChief Financial Officer: set policy for credits, prepaid and pay-as-you-go plans, enterprise contracts and discount authority; deploy the $75M Series B and prepare the next raise; treat tokens as a P&L line. Hiring "at a pace that will nearly double the team".Source
    • HiringGrowth Engineer, Product Growth: "Own the growth surfaces end to end: signup, activation, onboarding, and conversion"; "Treat conversion and activation as your number"; experience with playgrounds, docs surfaces and upgrade flows is a bonus.Source
  • 10

    Firecrawl is opening an outbound motion with a Technical BDR told to "reference their stack". 150,000+ companies already use the product, many on self-serve plans paid by one developer; their usage is a better target list than any outbound database.

    High impactMedium effort First result in 4 weeks Technical BDR

    First action

    List self-serve accounts on company domains that hit their concurrency limit more than ten times last week.

    How to measure it

    Expansion revenue from routed accounts

    Now
    –
    Target
    $500k annualized
    By
    end of quarter

    Steps

    1. 1

      Write the score

      Domain, keys, credit growth, concurrency hits and add-on use.

      Growth Engineer 2 days

    2. 2

      Enrich the account

      Company size and industry from Alexandria's own enrichment providers.

      Growth Engineer 1 day

    3. 3

      Assign an owner

      Top-tier accounts go to the Technical BDR; technical blockers go to a Forward Deployed Engineer.

      Technical BDR 1 hour

    4. 4

      Send the first note

      A short, technical note about the limit they hit and their stack, not a sales pitch.

      Technical BDR 1 hour

    5. 5

      Offer an Enterprise trial

      Two weeks of higher concurrency and an SLA, within the CFO's discount rules.

      Technical BDR 2 hours

    6. 6

      Review weekly

      Score bands against conversions; adjust monthly.

      Growth Engineer 30 minutes a week

    First result
    4 weeks
    Cost
    $0, about a week of engineering
    Owner
    Technical BDR

    Smallest test

    Email the 20 accounts with the most concurrency hits this week by hand.

    Build the prospect list. The list compiled from public sources, verified, deduplicated and delivered to your CRM. Usually live within days.

    Book a working session

    Why it works

    Score self-serve accounts daily on company domain, number of API keys, week-over-week credit growth and concurrency hits; send the top tier to a named contact with an offer of an Enterprise trial (SLA, zero data retention, SSO).

    Concurrency limits (25 on Standard, 50 on Growth) are a technical ceiling a growing team hits before it thinks about Enterprise. Reaching them first turns a frustrating limit into a sales conversation.

    Risks and how to handle them

    • Developers dislike sales outreach

      Lead with the limit they hit and write as an engineer, which is what the BDR role asks for.

    Evidence

    • HiringDeployment team of six: a Technical BDR to "open Firecrawl's outbound motion", reporting to the VP of Deployment, measured on "qualified pipeline created, not emails sent" and told to "reference their stack"; Forward Deployed Engineers measured "in adoption and expansion"; plus Sales, Success and Implementation roles.Source
    • Your websitePricing: Free 1,000 credits a month (no card), Hobby $16/month yearly, Standard $83, Growth $333, Scale $599 (yearly), Enterprise custom. Credits roll over only on Scale (one month) and Enterprise. JSON extraction adds 4 credits a page; an error page such as a 403 costs 1 credit. The page shows no customer logos, only testimonials from X users.Source
    • HiringSupport Engineer: first-line technical support for "high-value and enterprise accounts": failed scrapes, blocked sites and rate limits; keep the AI support agents effective and write runbooks and docs fixes; measured on "leverage", not tickets closed.Source
    • Your websiteHomepage: "Give your AI agents web data and beyond"; claims 150,000+ companies, 1.25M+ developers, 5 billion+ requests, 400,000+ MCP servers installed and 2.5M+ weekly SDK downloads; logos include Shopify, Lovable, Canva, Zapier, Apple, Replit, DoorDash, Gamma and Sierra.Source
  • 11

    Firecrawl is hiring a Research Engineer to publish provider benchmarks weekly, and Apollo.io already topped the company enrichment benchmark. Each release is a reason to contact every vendor on the leaderboard, and most will want either to promote a win or fix a loss.

    High impactMedium effort First result in 3 weeks Research Engineer

    First action

    Email Apollo.io a dated badge for the company enrichment benchmark and offer quotes for their announcement.

    How to measure it

    Providers signed after benchmark outreach

    Now
    –
    Target
    6
    By
    end of quarter

    Steps

    1. 1

      Design the badge

      Category, rank, date and a link to the methodology; it expires when the result changes.

      Member of Design Staff 2 days

    2. 2

      Write the rules

      When a badge may be used and how it is withdrawn.

      General Counsel 2 hours

    3. 3

      Build the private report

      Per vendor: fields lost, by how much, sample errors.

      Research Engineer, Benchmarks 3 days

    4. 4

      Send with every release

      Winners get the badge; others get the report and an Alexandria invitation.

      Partnerships Manager, Alexandria 2 hours a week

    5. 5

      Track links

      Backlinks and referral traffic from vendor sites.

      Head of Growth Marketing 30 minutes a week

    6. 6

      Hand over replies

      Vendors who reply go into the partnerships pipeline with the report attached.

      Partnerships Manager, Alexandria ongoing

    First result
    3 weeks
    Cost
    $0
    Owner
    Research Engineer, Benchmarks

    Smallest test

    Send the badge to Apollo.io and the private report to two other vendors from the company enrichment benchmark.

    Why it works

    With each benchmark release, send winners an embeddable, dated badge linking to the leaderboard, and send every other vendor a private breakdown of where they lost, with an invitation to list in Alexandria or improve their result through it.

    Vendors who win share the result with their own audience, which links back to Firecrawl. Vendors who lose are the providers the Partnerships Manager needs, and the breakdown gives that conversation a concrete start.

    Risks and how to handle them

    • Losing vendors dispute the method

      Publish the method and data, and accept re-runs with a fixed process.

    Evidence

    • HiringResearch Engineer, Benchmarks: weekly public benchmarks of data providers (for example Apollo vs FullEnrich vs DataLegion, Built In vs ZipRecruiter), public leaderboard pages with marketing, and results that change which provider Alexandria calls. "Our numbers have to survive the vendors who lose." The company enrichment benchmark (October 2) ranked Apollo.io first of six providers.Source
    • HiringPartnerships Manager, Alexandria: triage the provider waitlist, go outbound to "sources ranked by agent demand", negotiate rights and redistribution, and report catalog gaps; measured on "which sources come online, how fast, and on what terms". Providers get "paid, attributed access" to agent demand.Source
    • Your websiteAlexandria page: "The knowledge library for superintelligence"; 278 providers, 1,672 capabilities, 113M+ indexed sources; featured providers include Shopify, Benzinga, Apollo, Fiscal.ai and FullEnrich. Providers join a waitlist "to get paid"; no payout terms are published. The homepage still says 93 providers and 640 capabilities.Source
  • 12

    Firecrawl ships several launches a month (Universal Scrape, the ChatGPT plugin, Alexandria datasets), each announced alone and gone in a day. It is hiring a designer for a constant launch cadence and a Social Video Producer, and already has 61.7k YouTube subscribers.

    High impactMedium effort First result in 10 weeks Chief Growth Officer

    First action

    List everything due to ship in the next ten weeks and pick the five strongest for Launch Week.

    How to measure it

    Signups in Launch Week

    Now
    –
    Target
    3× a normal week
    By
    first Launch Week

    Steps

    1. 1

      Pick five launches

      One per day, strongest on day one.

      CEO 2 hours

    2. 2

      Countdown page

      Email and calendar subscribe, with a teaser per day.

      Member of Design Staff 2 days

    3. 3

      Make five videos

      One launch video per day, cut for X, LinkedIn and YouTube Shorts.

      Member of Design Staff 3 weeks

    4. 4

      Founder takes

      A daily 60-second founder video on why each launch matters.

      Social Video Producer 5 days

    5. 5

      Daily live stream

      20 minutes on YouTube with the engineer who built it.

      Chief Growth Officer 5 days

    6. 6

      Credits giveaway

      Daily challenge with credits as prizes.

      Chief Growth Officer 2 hours

    7. 7

      Recap post

      Everything shipped, with links, on day six.

      Chief Growth Officer 2 hours

    First result
    10 weeks
    Cost
    $5,000 to $10,000 in credits and production
    Owner
    Chief Growth Officer

    Smallest test

    Run a three-day launch mini-week with what ships next month.

    Why it works

    Hold launches for five consecutive days twice a year: one product a day, one launch video, a live stream, a daily giveaway of credits, and a countdown page developers can subscribe to.

    Batching launches gives the Creative Lead and design staff one story to tell instead of twenty, and a week of daily news gets coverage that single launches do not.

    Risks and how to handle them

    • Holding launches slows shipping

      Ship to beta users as usual and hold only the public announcement.

    Evidence

    • HiringMember of Design Staff: launch videos and social assets "for a constant launch cadence", concepting every launch with the Creative Lead; the work is "the first thing millions of developers see from us".Source
    • HiringGrowth team roles also include a Social Video Producer (fast, short-form social video, "a founder with a strong take") and an Open Source Engineer.Source
    • programmable.infoIn the past year the starting price rose from $9 to $16 a month and the headline changed from "Turn websites into LLM-ready data" to "Give your AI agents web data and beyond". npm downloads are about 957k a week across 23 packages; YouTube has 61.7k subscribers and 111 videos.Source
    • Your websiteBlog: more than 20 posts between October 1 and 13, mostly "best X" roundups and tutorials (plugins, APIs, connectors), with launches such as Universal Scrape (October 8) and the official ChatGPT plugin (October 6); benchmarks and customer stories are rare.Source
  • 13

    400,000+ MCP installs and an agent-onboarding skill mean many accounts start inside Claude Code, Cursor or ChatGPT. The human owner may not know which plan they are on or that a dashboard exists.

    High impactMedium effort First result in 4 weeks Agent Experience Engineer

    First action

    Count accounts created through the agent-onboarding skill and MCP in the last 30 days and compare their paid conversion with website signups.

    How to measure it

    Paid conversion of agent-created accounts

    Now
    –
    Target
    equal to website signups
    By
    end of quarter

    Steps

    1. 1

      Tag origin

      Agent skill, MCP, CLI or website on every new account.

      Growth Engineer 1 day

    2. 2

      Compare funnels

      Activation and paid conversion by origin.

      Growth Engineer 1 day

    3. 3

      Write the claim email

      What the agent did, the credit pace, one link.

      Chief Growth Officer 2 hours

    4. 4

      Trigger on real use

      Send after 50 successful calls, never at signup.

      Growth Engineer 1 day

    5. 5

      Add a spend cap prompt

      The claim page sets a monthly cap first.

      Growth Engineer 2 days

    6. 6

      A/B test the skill

      Test whether the onboarding skill telling the user about the dashboard lifts claims.

      Agent Experience Engineer 1 week

    First result
    4 weeks
    Cost
    $0, about a week of engineering
    Owner
    Agent Experience Engineer

    Smallest test

    Send the email by hand to 50 agent-created accounts with real usage.

    Why it works

    Tag accounts by origin (agent skill, MCP, website). For agent-created accounts, send the human a short email after real usage with what their agent did, their credit pace and one link to claim the dashboard and set a spend cap.

    Firecrawl hired an Agent Experience Engineer because agents are now a channel, but paid conversion still depends on a human deciding to pay. Telling the owner what their agent has already done is a concrete reason to look, and a spend cap removes the fear that keeps them on Free.

    Ready to use

    EmailAgent-created account email

    Subject: Your agent has used Firecrawl 50 times
    
    Hi,
    
    An AI agent signed you up for Firecrawl on {date}. Since then it has scraped {pages} pages and run {searches} searches, mostly from {top domains}.
    
    At this pace you'll use about {projected} credits this month (you have 1,000 free).
    
    See everything it did and set a spend cap: {link}
    
    The Firecrawl team

    Risks and how to handle them

    • Owners did not expect an email

      Send one, from the product, with a clear reason and an unsubscribe.

    Evidence

    • Search resultsGitHub: about 192.5k stars and 10.2k forks; AGPL-3.0 with MIT SDKs; the README says the cloud "includes additional features", but the open-source vs cloud comparison is only an image. An agent-onboarding skill lets an AI agent sign a user up and get an API key.Source
    • HiringAgent Experience Engineer: A/B tests across agent-facing surfaces (MCPs, CLIs, skills, APIs, documentation); form hypotheses "about how agents discover, interpret, and select tools", for "an audience that isn't human".Source
    • Your websiteHomepage: "Give your AI agents web data and beyond"; claims 150,000+ companies, 1.25M+ developers, 5 billion+ requests, 400,000+ MCP servers installed and 2.5M+ weekly SDK downloads; logos include Shopify, Lovable, Canva, Zapier, Apple, Replit, DoorDash, Gamma and Sierra.Source
    • HiringGrowth Engineer, Product Growth: "Own the growth surfaces end to end: signup, activation, onboarding, and conversion"; "Treat conversion and activation as your number"; experience with playgrounds, docs surfaces and upgrade flows is a bonus.Source
  • 14

    Alexandria asks providers to join a waitlist "to get paid" but publishes no payout terms. Firecrawl already pays Wikimedia Enterprise and has providers such as Benzinga and Fiscal.ai live.

    High impactMedium effort First result in 6 weeks Partnerships Manager

    First action

    Ask the two longest-live providers whether they would share month-one numbers publicly.

    How to measure it

    Median days from first call to signature

    Now
    –
    Target
    -30%
    By
    end of quarter

    Steps

    1. 1

      Pick the provider

      One with clear demand and a willing contact.

      Partnerships Manager, Alexandria 1 week

    2. 2

      Agree what to share

      Requests, attribution and earnings, or relative figures.

      Partnerships Manager, Alexandria 1 week

    3. 3

      Set the calculator rule

      Earnings range by demand band, set with finance.

      CFO 2 days

    4. 4

      Write the case study

      One page, with the provider's quote.

      Chief Growth Officer 2 days

    5. 5

      Build the calculator

      Demand band in, earnings range out.

      Growth Engineer 3 days

    6. 6

      Use it in outreach

      Link both from every provider email.

      Partnerships Manager, Alexandria ongoing

    First result
    6 weeks
    Cost
    $0
    Owner
    Partnerships Manager, Alexandria

    Smallest test

    Share the case study as a PDF in five provider calls before publishing it.

    Why it works

    Publish one case study with a live provider (requests served, attribution, money earned in month one, with their approval), and a calculator on the provider page that estimates earnings from a source's demand band.

    The Partnerships Manager is measured on which sources come online and how fast. Rights owners sign faster when they can see what peers earned; silence on payouts reads as risk.

    Risks and how to handle them

    • Published earnings set expectations too high

      Show ranges and state they depend on agent demand.

    Builds on

    Evidence

    • Your websiteAlexandria page: "The knowledge library for superintelligence"; 278 providers, 1,672 capabilities, 113M+ indexed sources; featured providers include Shopify, Benzinga, Apollo, Fiscal.ai and FullEnrich. Providers join a waitlist "to get paid"; no payout terms are published. The homepage still says 93 providers and 640 capabilities.Source
    • Search resultsSeries B announcement: Alexandria combines paid official data providers, a Research Index, a Developer Index, a Government Index and site connectors; Firecrawl already pays providers such as Wikimedia Enterprise and plans a self-service system for contributors to earn when agents use their knowledge.Source
    • HiringPartnerships Manager, Alexandria: triage the provider waitlist, go outbound to "sources ranked by agent demand", negotiate rights and redistribution, and report catalog gaps; measured on "which sources come online, how fast, and on what terms". Providers get "paid, attributed access" to agent demand.Source
    • HiringChief Financial Officer: set policy for credits, prepaid and pay-as-you-go plans, enterprise contracts and discount authority; deploy the $75M Series B and prepare the next raise; treat tokens as a P&L line. Hiring "at a pace that will nearly double the team".Source
  • 15

    Lovable, Replit and Gamma are on the homepage logo strip, and their users build apps and decks that need web data. A Firecrawl template inside those builders reaches users at the moment they need it.

    High impactMedium effort First result in 6 weeks Head of Growth Marketing

    First action

    Ask Lovable's partnerships contact which web-data templates their users request most.

    How to measure it

    Signups from builder templates

    Now
    –
    Target
    2,000
    By
    8 weeks after listing

    Steps

    1. 1

      Ask what users build

      Top requested data use cases from each partner.

      Head of Growth Marketing 1 week

    2. 2

      Build five templates

      Each works on first run with a free key.

      Growth Engineer 2 weeks

    3. 3

      Get listed

      Template galleries and partner docs.

      Head of Growth Marketing 2 weeks

    4. 4

      Track runs

      Referral tag on each template's key creation.

      Growth Engineer 1 day

    5. 5

      Co-announce

      Joint post and video with each partner.

      Member of Design Staff 1 week

    6. 6

      Iterate

      Retire weak templates and add one a month.

      Head of Growth Marketing monthly

    Who to approach

    • Lovable

      Customer on the homepage; its users build apps that need live web data.

    • Replit

      Customer on the homepage with a large template gallery.

    • Gamma

      Customer on the homepage; decks built from research need web sources.

    First result
    6 weeks
    Cost
    $0, about three weeks of work
    Owner
    Head of Growth Marketing

    Smallest test

    Publish one template on Replit and count runs for two weeks.

    Why it works

    Co-build five one-click templates with Lovable and Replit (a lead list builder, a price monitor, a docs chatbot, a news digest, a competitor tracker) that use Firecrawl with the user's own key, listed in each builder's template gallery.

    Partnerships is one of the channels the Head of Growth Marketing owns. These customers are distribution channels with millions of builders. A template that works on first run beats any number of "best tools" posts, and each run creates an account.

    Risks and how to handle them

    • Partners prefer their own scraping

      Start with the partner whose users already use Firecrawl the most.

    Evidence

    • Your websiteHomepage: "Give your AI agents web data and beyond"; claims 150,000+ companies, 1.25M+ developers, 5 billion+ requests, 400,000+ MCP servers installed and 2.5M+ weekly SDK downloads; logos include Shopify, Lovable, Canva, Zapier, Apple, Replit, DoorDash, Gamma and Sierra.Source
    • HiringHead of Growth Marketing: own weekly signup pacing across SEO/GEO, partnerships, brand and paid; "Take over our paid ads program and the agency running it: audit it in your first month and decide to scale, fix, or end it"; inherit product marketing, SEO, paid and YouTube. Eric Ciarla, the Chief Growth Officer, owns narrative, launches and open source.Source
    • Your websiteTestimonial: Alex Reibman (AgentOps) "Moved our internal agent's web scraping tool from Apify to Firecrawl because it benchmarked 50x faster"; Steven Tey: "Open-source Clay alternative just dropped".Source
  • 16

    Five legal hires, including a General Counsel who will defend "how we treat robots.txt and publisher opt-outs" in customer diligence, say that legal questions slow enterprise deals. The trust center covers SOC 2; it doesn't answer the questions specific to web data.

    High impactMedium effort First result in 1 quarter Legal Engineer

    First action

    Collect the last ten enterprise security and legal questionnaires and list the questions about crawling, robots.txt and data provenance.

    How to measure it

    Median enterprise legal and security review time

    Now
    –
    Target
    -40%
    By
    2 quarters

    Steps

    1. 1

      Collect questionnaires

      The last ten enterprise questionnaires and redlines.

      Legal Engineer 2 days

    2. 2

      Set the positions

      Robots.txt, opt-outs, provenance and retention, decided by counsel.

      General Counsel 2 weeks

    3. 3

      Write the pack

      Plain policy pages, a standard DPA and approved answers.

      Legal Engineer 2 weeks

    4. 4

      Prove it in code

      Show that robots and opt-out rules are enforced in the pipeline, with logs a customer can review.

      Legal Engineer 2 weeks

    5. 5

      Publish with the trust center

      Gated by NDA where needed, public where possible.

      Legal Engineer 2 days

    6. 6

      Train the deal team

      When to send the pack and when to call counsel.

      General Counsel 1 hour

    First result
    1 quarter
    Cost
    $0, about six weeks of legal engineering
    Owner
    Legal Engineer

    Smallest test

    Send a draft pack to three open enterprise deals and time their review.

    Why it works

    Publish a diligence pack next to the trust center: the crawling and robots.txt policy, publisher opt-out process, data provenance for Alexandria sources, zero data retention terms, a standard DPA and pre-approved answers to the 30 most common security and legal questionnaire items.

    The Legal Engineer is asked for playbooks sales can use without a lawyer, and the Deployment team is growing. A pack that answers the web-data questions up front shortens every enterprise cycle and frees counsel for the novel deals.

    Risks and how to handle them

    • Public positions become a target

      Publish the policy and keep detailed evidence under NDA.

    Evidence

    • HiringLegal team of five: the General Counsel sets "what we crawl and how, how we treat robots.txt and publisher opt-outs, what data provenance we stand behind" and defends it "in customer diligence"; the Legal Engineer builds "playbooks the sales team can use without waiting on a lawyer" and proves systems match the terms "in a customer security review"; Commercial Counsel negotiates data-licensing deals.Source
    • HiringDeployment team of six: a Technical BDR to "open Firecrawl's outbound motion", reporting to the VP of Deployment, measured on "qualified pipeline created, not emails sent" and told to "reference their stack"; Forward Deployed Engineers measured "in adoption and expansion"; plus Sales, Success and Implementation roles.Source
    • Your websitePricing: Free 1,000 credits a month (no card), Hobby $16/month yearly, Standard $83, Growth $333, Scale $599 (yearly), Enterprise custom. Credits roll over only on Scale (one month) and Enterprise. JSON extraction adds 4 credits a page; an error page such as a 403 costs 1 credit. The page shows no customer logos, only testimonials from X users.Source

Big bets 4

Larger plays that can change the trajectory.

  • 17

    Firecrawl says it plans a self-service system for contributors to earn when agents use their knowledge. A published share and a self-serve onboarding turns one Partnerships Manager into a marketplace.

    High impactHigh effort First result in 2 quarters Partnerships Manager

    First action

    Have the CFO set the revenue share and payout rules.

    How to measure it

    Self-serve providers live

    Now
    –
    Target
    200
    By
    2 quarters after launch

    Steps

    1. 1

      Set the economics

      Revenue share, minimum payout and schedule.

      CFO 2 weeks

    2. 2

      Ownership checks

      Domain verification and rights attestation.

      Partnerships Manager, Alexandria 2 weeks

    3. 3

      Provider dashboard

      Requests, attribution and earnings live.

      Growth Engineer 4 weeks

    4. 4

      Payouts

      Monthly payouts with tax forms.

      CFO 3 weeks

    5. 5

      Quality gate

      Automated checks before a source goes live.

      Search Engineer 2 weeks

    6. 6

      Launch

      Launch Week day one, with the first 20 providers.

      Member of Design Staff 1 week

    First result
    2 quarters
    Cost
    About a quarter of engineering plus payout operations
    Owner
    Partnerships Manager, Alexandria

    Smallest test

    Onboard ten long-tail providers through a manual version with the published share.

    Why it works

    Let any rights holder list a source: verify ownership, set access rules, publish a revenue share, see requests and earnings live, and get paid monthly. Keep negotiated deals for large providers.

    The long tail of sources agents request is too large to sign one by one. A clear, self-serve offer is what made app stores and ad networks scale, and every new source makes Alexandria harder to copy.

    Risks and how to handle them

    • Low-quality or unlicensed sources

      Rights attestation, quality checks and the right to delist.

    Builds on

    Evidence

    • Search resultsSeries B announcement: Alexandria combines paid official data providers, a Research Index, a Developer Index, a Government Index and site connectors; Firecrawl already pays providers such as Wikimedia Enterprise and plans a self-service system for contributors to earn when agents use their knowledge.Source
    • HiringPartnerships Manager, Alexandria: triage the provider waitlist, go outbound to "sources ranked by agent demand", negotiate rights and redistribution, and report catalog gaps; measured on "which sources come online, how fast, and on what terms". Providers get "paid, attributed access" to agent demand.Source
    • Your websiteAlexandria page: "The knowledge library for superintelligence"; 278 providers, 1,672 capabilities, 113M+ indexed sources; featured providers include Shopify, Benzinga, Apollo, Fiscal.ai and FullEnrich. Providers join a waitlist "to get paid"; no payout terms are published. The homepage still says 93 providers and 640 capabilities.Source
    • HiringChief Financial Officer: set policy for credits, prepaid and pay-as-you-go plans, enterprise contracts and discount authority; deploy the $75M Series B and prepare the next raise; treat tokens as a P&L line. Hiring "at a pace that will nearly double the team".Source
  • 18

    Apple, Shopify and DoorDash-scale buyers have committed cloud spend and slow vendor onboarding. Enterprise already includes zero data retention, SSO and an SLA; procurement is the remaining friction.

    High impactHigh effort First result in 2 quarters CFO

    First action

    Ask the five largest open enterprise deals whether they buy through a cloud marketplace.

    How to measure it

    Sales cycle for marketplace deals

    Now
    –
    Target
    30% shorter than direct
    By
    3 quarters

    Steps

    1. 1

      Check demand

      How the largest prospects buy software.

      CFO 1 week

    2. 2

      Register as a seller

      AWS first, Azure second.

      CFO 2 weeks

    3. 3

      Build listings

      SaaS contract listings with private offers.

      Growth Engineer 2 weeks

    4. 4

      Attach compliance

      SOC 2 Type II, DPA and pen test summary.

      CFO 2 days

    5. 5

      Train the team

      When to offer the marketplace path.

      CFO 2 hours

    6. 6

      Co-sell

      Apply to the cloud ISV programs once deals close.

      CEO ongoing

    First result
    2 quarters
    Cost
    Marketplace fees on transacted revenue plus a month of setup
    Owner
    CFO

    Smallest test

    Offer one enterprise prospect a private offer on AWS.

    Why it works

    Publish private-offer-ready marketplace listings for Enterprise with the SOC 2 Type II report attached, and give sales a standard marketplace path for deals above a set size.

    The CFO owns enterprise contracts and discount authority. Marketplace deals clear procurement faster and draw down budgets that are already approved.

    Risks and how to handle them

    • Fees cut margin

      Price the fee into private offers.

    Evidence

    • Your websiteHomepage: "Give your AI agents web data and beyond"; claims 150,000+ companies, 1.25M+ developers, 5 billion+ requests, 400,000+ MCP servers installed and 2.5M+ weekly SDK downloads; logos include Shopify, Lovable, Canva, Zapier, Apple, Replit, DoorDash, Gamma and Sierra.Source
    • Your websitePricing: Free 1,000 credits a month (no card), Hobby $16/month yearly, Standard $83, Growth $333, Scale $599 (yearly), Enterprise custom. Credits roll over only on Scale (one month) and Enterprise. JSON extraction adds 4 credits a page; an error page such as a 403 costs 1 credit. The page shows no customer logos, only testimonials from X users.Source
    • HiringChief Financial Officer: set policy for credits, prepaid and pay-as-you-go plans, enterprise contracts and discount authority; deploy the $75M Series B and prepare the next raise; treat tokens as a P&L line. Hiring "at a pace that will nearly double the team".Source
  • 19

    The General Counsel is hired to set and defend Firecrawl's positions on crawling, robots.txt, opt-outs and provenance, and to help "shape where the law lands". Turning those positions into a public standard, with evidence, moves them from risk to selling point.

    High impactHigh effort First result in 2 quarters General Counsel

    First action

    Have counsel write the first version of the standard from the positions in the diligence pack.

    How to measure it

    Registry sites that choose paid access over opt-out

    Now
    –
    Target
    10%
    By
    3 quarters

    Steps

    1. 1

      Write the standard

      Versioned, plain-language, with the technical rules.

      General Counsel 4 weeks

    2. 2

      Build the registry

      Opt out, opt in to paid access, verify ownership.

      Legal Engineer 6 weeks

    3. 3

      Enforce it in the pipeline

      Registry and robots rules applied to every request, with logs.

      Search Engineer 4 weeks

    4. 4

      Commission an audit

      An independent firm checks compliance quarterly.

      General Counsel 1 quarter

    5. 5

      Brief policy and press

      Share it with regulators, publishers and reporters.

      Chief Growth Officer 2 weeks

    6. 6

      Link it in deals

      Every enterprise contract references the standard.

      General Counsel ongoing

    First result
    2 quarters
    Cost
    Audit fees plus about a quarter of legal engineering
    Owner
    General Counsel

    Smallest test

    Publish the robots.txt and opt-out policy alone and count how often sales sends it.

    Why it works

    Publish a versioned web access standard (what Firecrawl crawls, how it honours robots.txt and opt-outs, how it identifies itself, how Alexandria sources are licensed), a registry where any site can opt out or opt into paid access, and a quarterly independent audit.

    Enterprise buyers and publishers both want to know a crawler behaves. A checkable standard answers diligence, gives the policy conversation something concrete, and turns opt-outs into a path into Alexandria's paid program.

    Risks and how to handle them

    • Commitments limit what the product can do

      Version the standard and change it in public with notice.

    Builds on

    Evidence

    • HiringLegal team of five: the General Counsel sets "what we crawl and how, how we treat robots.txt and publisher opt-outs, what data provenance we stand behind" and defends it "in customer diligence"; the Legal Engineer builds "playbooks the sales team can use without waiting on a lawyer" and proves systems match the terms "in a customer security review"; Commercial Counsel negotiates data-licensing deals.Source
    • Search resultsSeries B announcement: Alexandria combines paid official data providers, a Research Index, a Developer Index, a Government Index and site connectors; Firecrawl already pays providers such as Wikimedia Enterprise and plans a self-service system for contributors to earn when agents use their knowledge.Source
    • HiringPartnerships Manager, Alexandria: triage the provider waitlist, go outbound to "sources ranked by agent demand", negotiate rights and redistribution, and report catalog gaps; measured on "which sources come online, how fast, and on what terms". Providers get "paid, attributed access" to agent demand.Source
  • 20

    Most agents reach the web through a framework or platform default. Firecrawl already ships SDKs in nine languages and an official ChatGPT plugin; being the default in more places is distribution that compounds.

    High impactHigh effort First result in 2 quarters CEO

    First action

    List the ten frameworks and platforms that send the most API traffic today by user agent.

    How to measure it

    Share of new paid accounts from framework defaults

    Now
    –
    Target
    20%
    By
    3 quarters

    Steps

    1. 1

      Find the channels

      Traffic and signups by framework user agent.

      Growth Engineer 2 days

    2. 2

      Set the share

      Percentage of first-year revenue from attributed accounts.

      CFO 1 week

    3. 3

      Pitch the top five

      Maintainers and platform teams.

      CEO 4 weeks

    4. 4

      Attribution

      Partner keys and referral codes in SDK init.

      Growth Engineer 2 weeks

    5. 5

      Co-market

      Joint docs, launches and templates.

      Head of Growth Marketing ongoing

    6. 6

      Pay monthly

      Partner dashboard and payouts.

      CFO 2 weeks

    First result
    2 quarters
    Cost
    Revenue share on attributed accounts
    Owner
    CEO

    Smallest test

    Sign one framework and measure attributed signups for a month.

    Why it works

    Offer framework and agent platform maintainers a revenue share on paid usage that starts in their product, plus co-marketing, in return for Firecrawl as the default or first-listed web tool.

    2.5M weekly SDK downloads show developers already pick Firecrawl when asked. A share aligns the platforms with promoting it, and attributed usage gives the CFO a channel with a measurable cost.

    Risks and how to handle them

    • Open-source projects resist paid defaults

      Offer the share as sponsorship of the project, disclosed openly.

    Evidence

    • Your websiteHomepage: "Give your AI agents web data and beyond"; claims 150,000+ companies, 1.25M+ developers, 5 billion+ requests, 400,000+ MCP servers installed and 2.5M+ weekly SDK downloads; logos include Shopify, Lovable, Canva, Zapier, Apple, Replit, DoorDash, Gamma and Sierra.Source
    • Search resultsGitHub: about 192.5k stars and 10.2k forks; AGPL-3.0 with MIT SDKs; the README says the cloud "includes additional features", but the open-source vs cloud comparison is only an image. An agent-onboarding skill lets an AI agent sign a user up and get an API key.Source
    • Your websiteBlog: more than 20 posts between October 1 and 13, mostly "best X" roundups and tutorials (plugins, APIs, connectors), with launches such as Universal Scrape (October 8) and the official ChatGPT plugin (October 6); benchmarks and customer stories are rare.Source
    • HiringChief Financial Officer: set policy for credits, prepaid and pay-as-you-go plans, enterprise contracts and discount authority; deploy the $75M Series B and prepare the next raise; treat tokens as a P&L line. Hiring "at a pace that will nearly double the team".Source

Wildcards 4

Unexpected experiments, each with a cheap way to test it.

  • 21

    Firecrawl made news by advertising jobs for AI agents. It is now hiring a person to make every team use agents well, starting with revenue, and to manage token spend as a P&L line. That work is exactly what its customers want to copy.

    Medium impactMedium effort First result in 2 months AI Enablement Lead

    First action

    Agree with the AI Enablement Lead that the first revenue-team workflow will be written up when it goes live.

    How to measure it

    Signups from the series

    Now
    –
    Target
    500
    By
    third issue

    Steps

    1. 1

      Pick the first workflow

      The revenue team's first agent workflow in production.

      AI Enablement Lead 1 week

    2. 2

      Measure it

      Hours saved, token cost, output.

      AI Enablement Lead 2 weeks

    3. 3

      Write it up

      What it does, the config, the cost, what failed.

      AI Enablement Lead 1 day

    4. 4

      Open the repo

      Skills and configs, with secrets removed.

      AI Enablement Lead 1 day

    5. 5

      Publish monthly

      One workflow a month, including the ones turned off.

      AI Enablement Lead 1 day a month

    6. 6

      Promote

      A short video of each workflow running, plus the newsletter.

      Social Video Producer 1 day a month

    First result
    2 months
    Cost
    $0
    Owner
    AI Enablement Lead

    Smallest test

    Publish one internal workflow as a blog post.

    Why it works

    Publish a monthly post and repo from the AI Enablement Lead: the agent workflows each team runs, the skills and MCP configs, token spend against output, and what was switched off because it did not pay. Every workflow that uses web data uses Firecrawl.

    It is honest content no other vendor can write about itself, it continues a story the press already covered, and it shows Firecrawl being used inside real business workflows rather than demos.

    Risks and how to handle them

    • Sharing internal workflows exposes sensitive detail

      Review every post for customer data and secrets.

    Evidence

    • HiringAI Enablement Lead: build the internal agent setup, start with the revenue team, review token spend for usage without output; "measured by who's using agents well now who wasn't before".Source
    • Search resultsFirecrawl drew coverage in 2025 for job ads seeking to hire AI agents as employees, first at $15k a year and later with $1M for three agents.Source
    • HiringChief Financial Officer: set policy for credits, prepaid and pay-as-you-go plans, enterprise contracts and discount authority; deploy the $75M Series B and prepare the next raise; treat tokens as a P&L line. Hiring "at a pace that will nearly double the team".Source
  • 22

    Publishers are fighting AI crawlers and asking to be paid. Firecrawl is a crawler that has started paying sources. That story fits media trade press and brings rights owners to the provider program.

    Medium impactMedium effort First result in 4-6 weeks Chief Growth Officer

    First action

    Pull the publisher categories from the demand board and write the one-paragraph pitch.

    How to measure it

    Publishers joining the provider waitlist

    Now
    –
    Target
    30
    By
    8 weeks

    Steps

    1. 1

      Find the data

      Publisher content requests by category.

      Partnerships Manager, Alexandria 2 days

    2. 2

      Get one provider quote

      Wikimedia Enterprise or another live source on what they earn.

      Partnerships Manager, Alexandria 1 week

    3. 3

      Agree the position

      The General Counsel signs off on what Firecrawl says about crawling and payment.

      General Counsel 2 days

    4. 4

      Write the pitch

      One paragraph, one chart, a CEO interview offer.

      Chief Growth Officer 2 hours

    5. 5

      Pitch four outlets

      Personal emails to the AI and media reporters.

      Chief Growth Officer 1 day

    6. 6

      Publisher landing page

      Provider page section written for publishers.

      Chief Growth Officer 1 day

    7. 7

      Follow up

      One follow-up with a second chart.

      Chief Growth Officer 1 hour

    Who to approach

    • Nieman Lab

      Covers publisher business models and AI licensing.

    • Press Gazette

      Tracks publisher deals with AI companies.

    • Digiday

      Media business coverage read by publisher executives.

    First result
    4 to 6 weeks
    Cost
    $0
    Owner
    Chief Growth Officer

    Smallest test

    Pitch one reporter and see what they ask before the rest.

    Why it works

    Pitch Nieman Lab, Press Gazette, Digiday and Axios Media Trends with a data-led story: which kinds of publisher content agents request most (from the demand board), what Alexandria pays, and a CEO interview.

    The Partnerships Manager needs publishers and research indexes to come online. Coverage in the press publishers read reaches the people who decide on licensing, and reframes Firecrawl for the next raise.

    Risks and how to handle them

    • Reporters focus on Firecrawl's scraping instead

      Be ready with robots, opt-out and payment policies on the page.

    Builds on

    Evidence

    • Search resultsSeries B announcement: Alexandria combines paid official data providers, a Research Index, a Developer Index, a Government Index and site connectors; Firecrawl already pays providers such as Wikimedia Enterprise and plans a self-service system for contributors to earn when agents use their knowledge.Source
    • HiringPartnerships Manager, Alexandria: triage the provider waitlist, go outbound to "sources ranked by agent demand", negotiate rights and redistribution, and report catalog gaps; measured on "which sources come online, how fast, and on what terms". Providers get "paid, attributed access" to agent demand.Source
    • HiringLegal team of five: the General Counsel sets "what we crawl and how, how we treat robots.txt and publisher opt-outs, what data provenance we stand behind" and defends it "in customer diligence"; the Legal Engineer builds "playbooks the sales team can use without waiting on a lawyer" and proves systems match the terms "in a customer security review"; Commercial Counsel negotiates data-licensing deals.Source
  • 23

    10.2k forks and AGPL self-hosting mean many companies run Firecrawl themselves. They hit blocked sites that the cloud handles, because the Search Engineer's anti-bot work lives in the cloud.

    Medium impactMedium effort First result in 2 months Open Source Engineer

    First action

    Ask ten self-hosting companies in the Discord what share of their pages are blocked.

    How to measure it

    Self-hosted instances paying for fallback

    Now
    –
    Target
    300
    By
    2 quarters

    Steps

    1. 1

      Ask self-hosters

      Blocked rates and what they do today.

      Open Source Engineer 1 week

    2. 2

      Build the fallback

      Opt-in setting, cloud retry on block, clear logs.

      Search Engineer 3 weeks

    3. 3

      Show the blocked rate

      A count in the self-hosted logs and admin view.

      Open Source Engineer 1 week

    4. 4

      Price it

      Per-page price for fallback pages.

      CFO 1 week

    5. 5

      Document it

      README section replacing the comparison image with text.

      Open Source Engineer 1 day

    6. 6

      Announce

      Release notes and a Discord post.

      Open Source Engineer 1 hour

    First result
    2 months
    Cost
    About a month of engineering
    Owner
    Open Source Engineer

    Smallest test

    Offer fallback by hand (an API key and a code snippet) to five self-hosting companies.

    Why it works

    Add an optional setting to the open-source version: when a self-hosted scrape is blocked, retry it through the cloud with an API key and pay per page. Show self-hosters their blocked-page rate so they can see what they are missing.

    It turns the self-hosting community into a paying channel without changing the license, and the open-source vs cloud difference becomes something users experience rather than an image in the README.

    Risks and how to handle them

    • Community sees it as upselling

      Opt-in, off by default, with no change to self-hosted features.

    Evidence

    • Search resultsGitHub: about 192.5k stars and 10.2k forks; AGPL-3.0 with MIT SDKs; the README says the cloud "includes additional features", but the open-source vs cloud comparison is only an image. An agent-onboarding skill lets an AI agent sign a user up and get an API key.Source
    • HiringSearch Engineer: reverse engineer how sites detect automated traffic, build diagnostics and monitoring, and "Own scrape success rate: Measure it, explain regressions, and ship the fixes."Source
    • HiringGrowth team roles also include a Social Video Producer (fast, short-form social video, "a founder with a strong take") and an Open Source Engineer.Source
    • HiringJob posts: "We hit 8 figures in ARR in year one and more than doubled it in year two"; $75M Series B led by Smash Capital (September 2026); 192k+ GitHub stars, "top 40 repositories of all time"; 11 to 50 employees in San Francisco with a Toronto hub.Source
  • 24

    The Head of Growth Marketing owns SEO/GEO, and the Agent Experience Engineer tests how agents "discover, interpret, and select tools". Neither has a weekly number for how often Claude Code, Cursor, Codex or ChatGPT reach for Firecrawl unprompted.

    High impactMedium effort First result in 4 weeks Agent Experience Engineer

    First action

    Write the 200 prompts across ten web-data tasks and run them once by hand in Claude Code and Cursor.

    How to measure it

    Tool choice share across tracked agents

    Now
    –
    Target
    +10 points
    By
    2 quarters

    Steps

    1. 1

      Write the prompt set

      200 prompts across ten tasks, without naming any tool.

      Agent Experience Engineer 2 days

    2. 2

      Automate the runs

      Weekly runs in clean environments for each agent and assistant.

      Agent Experience Engineer 1 week

    3. 3

      Record the choice

      Tool, library or API chosen, and whether it worked.

      Agent Experience Engineer 2 days

    4. 4

      Find the losses

      Tasks and agents where another tool wins, and why.

      Agent Experience Engineer 1 day

    5. 5

      Run experiments

      Change MCP descriptions, skill text and docs; measure share the next week.

      Agent Experience Engineer ongoing

    6. 6

      Report weekly

      Share by agent next to signups in the growth review.

      Head of Growth Marketing 15 minutes a week

    First result
    4 weeks
    Cost
    Under $1,000 a month in agent runs
    Owner
    Agent Experience Engineer

    Smallest test

    Run 20 prompts by hand in two agents and see how often Firecrawl is chosen.

    Why it works

    Run a fixed set of 200 prompts ("scrape this site into markdown", "find pricing for these companies", "monitor this page") weekly across the major agents and chat assistants, record which tool or library each chooses, and treat that share as a growth metric with experiments on docs, skills and MCP descriptions.

    More and more developers let an agent choose the tool. A weekly share by agent and task shows where Firecrawl loses the choice, and the Agent Experience Engineer's A/B tests can then target those surfaces.

    Risks and how to handle them

    • Agent behaviour changes with each model release

      Track by model version and treat drops after releases as signals, not noise.

    Evidence

    • HiringAgent Experience Engineer: A/B tests across agent-facing surfaces (MCPs, CLIs, skills, APIs, documentation); form hypotheses "about how agents discover, interpret, and select tools", for "an audience that isn't human".Source
    • HiringHead of Growth Marketing: own weekly signup pacing across SEO/GEO, partnerships, brand and paid; "Take over our paid ads program and the agency running it: audit it in your first month and decide to scale, fix, or end it"; inherit product marketing, SEO, paid and YouTube. Eric Ciarla, the Chief Growth Officer, owns narrative, launches and open source.Source
    • Your websiteHomepage: "Give your AI agents web data and beyond"; claims 150,000+ companies, 1.25M+ developers, 5 billion+ requests, 400,000+ MCP servers installed and 2.5M+ weekly SDK downloads; logos include Shopify, Lovable, Canva, Zapier, Apple, Replit, DoorDash, Gamma and Sierra.Source
    • Search resultsGitHub: about 192.5k stars and 10.2k forks; AGPL-3.0 with MIT SDKs; the README says the cloud "includes additional features", but the open-source vs cloud comparison is only an image. An agent-onboarding skill lets an AI agent sign a user up and get an API key.Source

03

How Programmable can help

Where an idea in this playbook is something Programmable builds or runs, it's listed here with what we'd do. Everything else is yours to run.

Have it built

ProgrammableAgency

2 of the 24 ideas are things Programmable builds and runs for its customers: pages, outreach, prospect lists, booking flows and monitors. Pick one, or send the whole list.

Outreach1The sequence sent for you: addresses found and verified, replies routed to your CRM.

Prospect lists1The list compiled from public sources, verified, deduplicated and delivered to your CRM.

A 30-minute session with the engineer who would build it, not a sales call. You leave with a plan whether or not you hire us.

Book a working session

Usually live within days.

Tools for the rest

ProgrammableDigital

Show it, don't just describe it

These ideas need something to show: a demo, a video, an animation, graphics or a deck. Digital turns screenshots or the site into all of them, in the company's own brand.

Make a demo (opens programmable.digital in a new tab)
More example playbooks and reviews

More growth playbooks

Other companies we have researched, each read from what they are hiring for.

  • Plug growth strategyA St. Louis direct-to-consumer seller of Certified Pre-Owned iPhones, Samsung and Pixel phones, iPads, MacBooks, watches and audio, with a…21 growth ideas
  • Onnit growth strategyAn Austin supplement brand, part of Unilever's Wellbeing Collective, selling Alpha BRAIN, Total Human, New Mood, Shroom Tech, creatine…20 growth ideas
  • Cabify growth strategyA ride-hailing and urban mobility platform: VTC and taxi rides, airport transfers, motorbikes, deliveries and logistics, corporate…23 growth ideas
  • Caribou growth strategyAn online auto refinance marketplace (Caribou Financial) that pairs drivers with credit unions, banks and finance companies, plus optional…21 growth ideas
  • eMAG growth strategyThe largest online marketplace and retailer in Romania, also in Bulgaria and Hungary, with a third-party marketplace, Fulfilment by eMAG…21 growth ideas
  • Preply growth strategyAn online tutoring marketplace with 100,000+ tutors teaching 90+ languages and non-language subjects, with AI lesson summaries and…21 growth ideas
  • Evergreen Nephrology growth strategyValue-based kidney care: care teams (nurses, care coordinators, social workers, dietitians) that support patients with chronic and…22 growth ideas
  • Code for America growth strategyA civic tech nonprofit that builds and runs public services (GetYourRefund, SimpleFile, GetCalFresh and others) and works with state and…21 growth ideas

See every playbook and website review

Independent research. Programmable wrote this playbook from public sources, as they stood on October 18, 2026, and cites them throughout. Firecrawl did not commission, review or endorse it, and Programmable is not affiliated with Firecrawl. Company and product names are trademarks of their owners, used only to identify them. The ideas are suggestions and opinion, not professional, legal or financial advice, and not statements about how Firecrawl runs its business.

Something wrong, or do you represent Firecrawl? Email [email protected] and we will correct it or take it down.

30/60/90 roadmap

What to focus on in each month, and the ideas that carry it.

  1. Days 1 to 308 ideas

    Fix the paths to money (upgrade prompt, pricing proof, credit receipts), rewrite the Tavily page, start the demand board, and run the month-one paid audit and the first success report.

    Programmable can ship 1 of these in days.

  2. Days 31 to 607 ideas

    Build the engines the new hires own: rollover pricing, the BDR usage feed, benchmark outreach, agent-created account activation, the diligence pack, tool choice share and cloud fallback.

  3. Days 61 to 909 ideas

    Distribution and story: Launch Week, the provider case study, builder templates, the agents playbook and publisher press; then commit to the big bets on the first 60 days of evidence.

The research behind the plan

3 research areas, each summarised in a few lines. Open any of them for the full detail.

Customers

What customers say

Customers value clean, LLM-ready markdown from one API call. The most cited problem: blocked sites and failed scrapes.

  • Speed (AgentOps: "benchmarked 50x faster" than Apify)
  • Credits used faster than expected (error pages, JSON add-ons)
  • In their words: “LLM-ready”

Market

Competitive landscape

4 competitors compared: Exa, Parallel, Tavily (Nebius) and Apify and Bright Data.

  • Gap to exploit: A neutral, repeatable benchmark for agent web data
  • Exa: Less full-page extraction and crawling
  • Parallel: No crawl, map or browser interaction

Hiring signals

Firecrawl has 33 open roles (Engineering 12, Deployment 6, Growth 6, Legal 5, plus finance, partnerships, support and operations), and the mix shows what it values.

  • Head of Growth Marketing: Paid stays: audit the paid program and its agency in month one; owns SEO/GEO, partnerships and YouTube. Ideas 2, 7, 15, 24.
  • Technical BDR (Deployment team of six): Opening outbound alongside forward-deployed, sales and success engineers: a sales-led enterprise motion on…
  • Chief Financial Officer: Pricing economics (credits, prepaid, pay-as-you-go, enterprise discounts) and the next raise. Ideas 9, 18.

From the team that wrote this playbook

All products
  • ProgrammableAgencyWorking AI systems in days, not quarters (opens programmable.agency in a new tab)
  • ProgrammableInfoAn agent that finds, researches and asks first (opens programmable.info in a new tab)
  • ProgrammableDigitalScreenshots in, an animated product demo out (opens programmable.digital in a new tab)
  • ProgrammableWatchKnow the day a supplier falls out of compliance (opens programmable.watch in a new tab)
  • ProgrammableTalkGet registrants for your events, and know who’s coming (opens programmable.talk in a new tab)
  • ProgrammablePageText what you need, your customer gets a page that works (opens programmable.page in a new tab)
  • ProgrammableCommunityForums with labelled AI members, never empty (opens programmable.community in a new tab)
ProgrammableMarketing
ExamplesLeaderboardsProductsTermsPrivacyCookiesDPALegalContact

© 2026 AI-Powered Growth Intelligence