Sigblaze
Sign inJoin the waitlist

Watchlists that re-check pages and queries and keep the history

A watchlist re-checks the public pages and search queries you choose, compares each check with the last snapshot and raises a signal only when something changed. The signal tells you what changed and what to do next.

Join the waitlist See the workflow

In the product

monitor / watchlistSynthetic data
Competitor watchlistChecked weekly

Meridian pricing & product pages

Page
meridian.example/pricing
Page
meridian.example/changelog
Search
“Meridian alternative for agencies”
Snapshot · 26 Aug
  • Get your whole team live in a day.
  • Pro: $49 per seat per month
  • 10-seat minimum
Snapshot · 5 Oct
  • Get your whole team live in a day.
  • Pro: $59 per seat per month
  • 10-seat minimum
  • 26 AugBaseline captured3 sources checked
  • 2 SepNo meaningful change3 sources checked
  • 5 Oct1 page changed → 1 signal3 sources checked
The first check is a baseline. From the second check on, only real differences are raised.

The problem

Competitor tracking depends on a calendar reminder

Someone is meant to re-read the pricing page every month. They forget, or they read it without remembering what it said last time, so a change slips through.

How it works

  1. Create a watchlist. Choose competitor, customer, market or topic. Add public pages (pricing, product, docs, changelog, careers, blog) and search queries (complaints, alternatives, news).
  2. Capture a baseline. The first check stores what each page says today. No signals are raised, because nothing is being compared yet.
  3. Check on a schedule. Daily, weekly or on demand. Each check fetches the page, compares it with the last snapshot and keeps the new one.
  4. Keep the history. Snapshots are retained, so you can see how pricing or positioning moved over time.
  5. Raise signals. Real differences become signals with evidence. A source that fails is shown as a warning, and the rest of the check continues.

Evidence and provenance

  • Snapshots are bounded excerpts with retrieval dates. Pages are not mirrored.
  • Fetching is limited to public web pages. Private and local addresses are refused.
  • Pages containing instruction-like text are excluded from analysis and flagged.
  • A baseline is set only after a source has been read. A failed check is shown as failed.

Capability status

  • WatchlistsCompetitor, customer, market and topic watchlists made of public pages and search queries.
    Private alpha
  • Change detectionEach check is compared with the last stored snapshot; only real differences become candidates.
    Private alpha
  • Scheduled checksDaily or weekly re-checks, plus run-now. Scheduling needs a cron trigger on self-managed deployments.
    Private alpha
  • Historical snapshotsObservations are kept, so you can see how a page changed rather than only its latest state.
    Private alpha

Monitor feeds Signals, and Signals feed Briefs. A watchlist re-runs its checks on the schedule you set.

FAQ

Monitor: common questions

What can it watch?

Public web pages you can reach without signing in, and search queries through the configured search provider. Pages that need a login or JavaScript to render are not read today. Dedicated Reddit, social, app-store and video sources are later.

How often does it check?

Daily, weekly, or when you press run. On self-managed deployments a scheduler needs to call the product’s cron endpoint for scheduled checks.

Does it send alerts?

Signals appear in the product and in briefs. Email and chat alerts are a later capability.

Next: Brief

Join the waitlist for the private alpha

Sigblaze is built for agencies, fractional GTM teams and B2B SaaS teams that research the same markets on a schedule. Pricing is not set.

Join the waitlist See how it works