Firecrawl Competitive Intel

by firecrawl94cc91229d6cISC185 starsListed Oct 8, 2026Updated Oct 8, 2026Repository updated 6 weeks ago

Monitor competitor pricing, features, changelogs, dashboards, and product changes with Firecrawl. Use for recurring competitive intelligence, pricing tier extraction, feature change tracking, or structured competitor alerts.

AI-generated overview

Monitors competitor pricing, features and changelogs with Firecrawl and produces structured competitive intelligence reports.

What it does
Collects competitor pricing pages, feature pages, changelogs, blogs, release notes and docs using Firecrawl scrape or browser, optionally with parallel sub-agents split by competitor or focus area. It compiles pricing tiers, feature inventories, recent changes, source URLs and confidence notes into a report with alerts, per-competitor breakdowns, a cross-competitor comparison and suggested follow-ups. A structured JSON shape with generatedAt, competitors, pricing, recentChanges, features and sources is available when requested.
When to use it
Use for recurring competitive intelligence, pricing tier extraction, feature change tracking or structured competitor alerts over time. It is intended for monitoring competitors rather than broad one-off competitor analysis. Authenticated dashboards are only collected when the user has legitimate access.
Requirements
Requires a Firecrawl API key (FIRECRAWL_API_KEY) for hosted Firecrawl requests and network access to scrape competitor pages. Instructions only; no scripts are shipped.

Firecrawl Competitive Intel

Use this for monitoring competitors over time. This is not the broad competitor analysis workflow.

Onboarding Interview

Infer competitors, focus, cadence, and output format from context. If competitors are clear, proceed immediately.

Ask at most 1-3 concise questions only if blocked, such as the competitor list, focus area, or whether authenticated pages/profiles are required.

Firecrawl Collection Plan

For each competitor, use Firecrawl scrape or browser as needed:

  • pricing pages, annual/monthly toggles, expanded feature tables
  • feature and product pages
  • changelogs, blogs, release notes, docs updates
  • authenticated dashboards only when the user has legitimate access

Parallel Work

If appropriate, use sub-agents or equivalent parallel task runners. A natural split is one competitor per researcher or one focus area per researcher.

Each researcher should return pricing tiers, features, recent changes, source URLs, and confidence notes.

Final Deliverable

markdown
# Competitive Intel: [Competitors]
## Alerts[Notable pricing, feature, or positioning changes]
## Per-Competitor Breakdown[Pricing tiers, feature inventory, recent changes]
## Cross-Competitor Comparison[Pricing table, feature matrix, key differentiators]
## Suggested Follow-Ups[What to monitor next]
## Sources[URLs visited]
## Rerun Inputsworkflow: firecrawl-competitive-intelcompetitors: [list]focus: [all/pricing/features/changelog]cadence: [one-off/weekly/monthly]

JSON Shape

When structured output is requested, include generatedAt, competitors, pricing, recentChanges, features, and sources.

Quality Bar

  • Extract real plan names, limits, and dates when available.
  • Note contact-sales or gated details instead of guessing.
  • Preserve sources for diffing future runs.

Source and attribution

Source:firecrawl/firecrawl-workflowsinskills/firecrawl-competitive-intelat commit94cc912

License: ISC

Content belongs to its original authors. SourceWeft indexes it from a public repository.

Report or request removal