SaaS Pricing Page Intelligence Monitor

Track public SaaS plans, prices, billing periods, feature gates, free trials, and enterprise sales CTAs from vendor-owned pricing pages.

The Actor discovers pricing pages from explicit vendor targets, extracts evidence-backed plan rows, and compares the result with the last successful run. Use it for competitive intelligence, pricing research, product marketing, procurement, and scheduled change monitoring.

What it returns

• One evidence-backed row per pricing plan.
• added, modified, and removed changes compared with the last successful run.
• Optional unchanged rows for full pricing snapshots.
• Previous price, billing, feature-gate, and CTA values on modified or removed plans.
• Canonical vendor-owned source URLs and capture timestamps.

The Actor never emits its G2, Capterra, or Product Hunt discovery pages as pricing evidence.

Recommended use

Create an Apify Task with explicit competitor domains or pricing URLs and schedule it daily or weekly. Explicit vendor targets are more stable than zero-input discovery mode.

Example input:

{
  "pricingUrls": [
    "https://stripe.com/pricing",
    "https://slack.com/pricing"
  ],
  "competitorDomains": [],
  "useDefaultSources": false,
  "queryThemes": [
    "SaaS pricing page plans enterprise",
    "software pricing plans free trial"
  ],
  "maxPages": 20,
  "maxItems": 100,
  "includeUnchanged": false,
  "maxFirecrawlPages": 0
}

On the first successful run, every observed plan is added. On later runs, leaving includeUnchanged disabled produces a change-only dataset.

Inputs

pricingUrls

Direct public pricing-page URLs. Supplying at least one direct URL or competitor domain disables the default discovery sources.

competitorDomains

Public SaaS domains or URLs. For each domain, the Actor examines the homepage and conventional /pricing, /plans, and /pricing-plans paths.

useDefaultSources

When true and no explicit targets are supplied, use bounded G2, Capterra, and Product Hunt pages as candidate discovery hints. Vendor-owned pages remain the only accepted evidence sources.

queryThemes

Pricing concepts used to recognize candidate vendor links during default discovery. They do not invoke a search API.

maxPages

Maximum homepage, discovery, and pricing-page requests attempted in one run. Default: 100; range: 1–5000.

maxItems

Maximum current pricing plans compared with the previous successful snapshot. Default: 100; range: 1–1000.

includeUnchanged

Emit unchanged plan rows alongside changes. Default: false.

firecrawlApiKey

Optional secret bring-your-own Firecrawl API key. Direct HTTP is always attempted first; Firecrawl is used only for blocked or sparse pages. The key is not written to logs or datasets.

maxFirecrawlPages

Maximum Firecrawl fallback attempts per run. Default: 10; range: 0–100. Set to 0 to disable fallback.

Output fields

• recordType: pricingPlan for current/added rows or pricingChange for modified and removed plans.
• changeType: added, modified, removed, or optionally unchanged.
• sourceUrl: canonical vendor-owned pricing page.
• companyName: vendor name evidenced by page metadata or derived from the vendor hostname.
• planName: pricing-plan name.
• priceText: displayed price or Custom pricing.
• billingPeriod: normalized billing unit such as month, year, user, or seat.
• featureGate: up to eight evidenced plan features joined as text.
• ctaText: an evidenced conversion CTA such as Start free trial or Contact sales.
• confidence: extraction confidence from 0 to 1.
• evidenceText: bounded source text supporting the plan row.
• previousValues: prior priceText, billingPeriod, featureGate, and ctaText for modified or removed plans.
• capturedAt: ISO 8601 timestamp for the comparison run.

Example result:

{
  "recordType": "pricingChange",
  "changeType": "modified",
  "sourceUrl": "https://example.com/pricing",
  "companyName": "Example",
  "planName": "Starter",
  "priceText": "$29",
  "billingPeriod": "month",
  "featureGate": "10 projects; Email support",
  "ctaText": "Start free trial",
  "confidence": 1,
  "evidenceText": "Starter $29 per month 10 projects Email support Start free trial",
  "previousValues": {
    "priceText": "$19",
    "billingPeriod": "month",
    "featureGate": "5 projects; Community support",
    "ctaText": "Start free trial"
  },
  "capturedAt": "2026-07-26T00:00:00.000Z"
}

Scheduling and snapshots

The Actor stores the latest successful pricing snapshot in the named saas-pricing-page-intelligence-monitor-state key-value store. Snapshot keys are scoped to the normalized pricing targets, so scheduled runs can compare with earlier runs without different monitoring configurations overwriting one another.

• Schedule the same Apify Task to keep its normalized target set stable.
• A failed crawl or dataset publication does not replace the previous snapshot.
• Deleting or replacing the default key-value store resets history; the next run reports all observed plans as added.
• Running with different target sets against the same default storage can produce removed rows. Use separate Tasks/storages for unrelated competitor groups.

Pricing and safety

The Actor uses pay-per-event monetization. Each emitted dataset row uses event name pricing-result.

Direct HTTP is attempted first. Firecrawl is optional BYOK and bounded by maxFirecrawlPages; Firecrawl usage may consume credits on the supplied account. Fetched content is handled only as untrusted text and is never executed.

Limitations

• JavaScript-rendered or strongly protected pricing pages may require Firecrawl.
• Highly visual pricing tables without semantic headings may not yield plan rows.
• Prices embedded only in images are not extracted.
• Currency conversion, tax normalization, and inferred annualized pricing are intentionally excluded.
• Default discovery sources can change or block automated access; explicit vendor targets are recommended.

Local development

Run commands from this Actor directory:

npm ci
npm test
apify validate-schema
apify run --purge

For local runs, place input at storage/key_value_stores/default/INPUT.json. Local storage is not synchronized with Apify Console.