The job is not “the page changed.”

Website change monitoring is an old category. Visualping, Distill, Hexowatch, Wachete and others already do the fetch-and-diff well. PulseDiff sits in that category on purpose. We do not pretend we invented page watching.

What we do differently is the output. After a fetch, we classify the diff and only email when the change looks material to a buyer or an operator — pricing, plans, features, jobs, terms.

What a brief contains

• What changed — short bullets, tied to the new text.
• Why it matters — one paragraph for a business reader. Not legal or financial advice.
• Ignore — what moved and should not waste your time.
• Next step — one concrete action, or none.

How often we look

Free is one public URL on a limited cadence. Pro is up to fifteen URLs, checked about every eight hours, plus a weekly “all quiet” note if nothing material moved. That cadence is honest: we are not a second-by-second incident tool.

Limits we will not hide

• Public pages only. No login bypass, no CAPTCHA solving, no private dashboards.
• Heavy JavaScript apps often will not render fully. If the first fetch fails, we say so.
• Automated watches miss things. If a decision is expensive, open the page yourself.
• We rate-limit and use an identifiable user agent: PulseDiffBot.

Where this sits in THE HUB

When Chronos (THE HUB) is online, PulseDiff’s operating state — watches, signups, Pro, next cash action — is written into shared memory. That is internal. It does not change what you receive in email.