SaaS Pricing Intelligence Monitor

Monitor public SaaS pricing pages and turn them into structured pricing snapshots and change events.

This Actor is for founders, product marketing teams, RevOps, sales teams, and competitive-intelligence researchers who need to know when a competitor changes plans, prices, limits, or feature packaging.

The best first use case is a focused watchlist, for example AI/devtools pricing pages where model access, usage credits, team seats, and enterprise packaging change often enough to matter.

Run This First

Paste this small AI/devtools watchlist, run it once, then run it again later with the same snapshotStoreName to see change rows:

{
  "pricingUrls": [
    { "url": "https://linear.app/pricing" },
    { "url": "https://www.cursor.com/pricing" },
    { "url": "https://www.pinecone.io/pricing/" }
  ],
  "compareToPreviousRun": true,
  "snapshotStoreName": "ai-devtools-pricing-watchlist",
  "includeHtml": false,
  "includeText": true,
  "maxPages": 3,
  "maxPlansPerPage": 20,
  "dryRun": false
}

Look first at detectedPrices, plans, hasChanges, changes, and BUYER_BRIEF. A practical workflow recipe is in docs/workflow-recipes/saas-pricing-change-alert.md in the GitHub repository.

What It Does

Give the Actor a list of public pricing page URLs. It fetches each page, extracts visible pricing signals, stores the latest snapshot in a named key-value store, and compares later runs against the previous snapshot.

It returns:

• detected company and pricing page URL
• normalized plans, prices, billing periods, and feature bullets
• flattened detectedPrices rows for Sheets, Slack, Airtable, and n8n
• evidence snippets for each detected plan
• confidence scores for extraction and changes
• change events such as price_increase, price_decrease, plan_added, plan_removed, feature_added, feature_removed, and page_text_changed
• run summary in the key-value store

The run also writes key-value outputs:

• RUN_SUMMARY: counts, status, inputs, and failed URLs
• BUYER_BRIEF: a short Markdown brief of pricing changes to review
• SLACK_ALERTS: compact alert objects for webhook or chat workflows

Why Use This Instead Of A Page Monitor

Generic page monitors tell you that HTML changed. This Actor tries to answer the business question: what pricing changed, which plan changed, and what value should a human verify?

The first version is deterministic. It does not require an LLM key, does not log in, and does not collect private data. That keeps scheduled runs cheap and repeatable.

Input

{
  "pricingUrls": [
    { "url": "https://example.com/pricing" },
    { "url": "https://competitor.com/pricing" }
  ],
  "compareToPreviousRun": true,
  "snapshotStoreName": "saas-pricing-intelligence-monitor-snapshots",
  "includeHtml": false,
  "includeText": true,
  "maxPages": 25,
  "maxPlansPerPage": 20
}

Use Apify schedules to run the same input daily or weekly. Use Apify webhooks to send changed rows into Slack, email, Google Sheets, Make, Zapier, or your own dashboard.

The default Store run is a dry-run demo so the Actor succeeds with no setup. Set dryRun to false when you want to monitor real pricing pages.

Use With n8n, Make, or Zapier

Save your input as an Apify Task and schedule it weekly. In n8n, Make, or Zapier, run the Task with wait-for-finish enabled, then read the dataset and the SLACK_ALERTS key-value output.

Typical workflow:

1. Run once to create the baseline snapshot.
2. Schedule the same Task weekly.
3. Filter for rows where hasChanges is true.
4. Send company, url, changes, summary, and evidenceSnippets to Slack, Sheets, Airtable, or a competitive-intel dashboard.

Output

Each dataset item is one analyzed pricing page:

{
  "recordType": "pricing_snapshot",
  "company": "Example CRM",
  "url": "https://example.com/pricing",
  "plans": [
    {
      "name": "Pro",
      "prices": [{ "amount": 29, "currency": "USD", "raw": "$29/month" }],
      "features": ["10 seats", "API access", "Priority support"],
      "confidence": 0.91
    }
  ],
  "detectedPrices": [
    {
      "amount": 29,
      "currency": "USD",
      "raw": "$29/month",
      "billingPeriod": "month",
      "plan": "Pro"
    }
  ],
  "changes": [
    {
      "changeType": "price_increase",
      "plan": "Pro",
      "oldValue": "$24/month",
      "newValue": "$29/month",
      "summary": "Pro price increased from $24/month to $29/month (20.8%).",
      "confidence": 0.9
    }
  ],
  "hasChanges": true,
  "changeCount": 1,
  "extractionConfidence": 0.89
}

Pricing

This Actor uses pay-per-event pricing. Dry-run examples are not charged. Apify free-plan users get the first 10 analyzed pricing pages without this Actor's custom event charge; after that, normal pay-per-event pricing and the user's run spending limit apply.

Event	Price	What counts
pricing-page	$0.02	One public pricing page analyzed and written to the dataset

Paying per analyzed page is intentional. A monitor still provides value when it confirms there was no pricing change.

Limits

This Actor works on public pricing pages. It does not log in, bypass paywalls, solve CAPTCHAs, or access private customer dashboards.

Pricing pages vary a lot. Treat low-confidence rows and high-impact changes as review queues, not legal or financial facts. For JavaScript-heavy pricing pages, use this Actor as a first pass; a browser-rendered version can be added if there is enough buyer demand.

Good Use Cases

• competitor pricing monitoring
• weekly product marketing alerts
• sales battlecard updates
• RevOps pricing-package research
• analyst datasets for SaaS categories
• private dashboards that need structured pricing-change events

Bad Fits

• private pricing hidden behind login
• custom enterprise quote collection
• scraping pages that prohibit automated access
• exact price guarantees for legal or contract decisions