Monitor competitor pricing
Check competitor pricing pages on a schedule and flag real changes to Slack.
Competitor price monitoring by hand means someone opens six pricing pages every Monday and tries to remember what they looked like last week. This workflow checks the pages on a schedule, compares against what it saw last time, and alerts you in Slack only when something changed: a new tier, a moved price point, a feature shifted between plans, or new packaging language.
What does this workflow do?
You give the workflow a list of competitor pricing pages. On each run, the agent reads every page, extracts the structure (tiers, prices, billing terms, feature allocation, trial terms) and diffs it against the previous run.
No change, no message. When something does change, you get a Slack alert with the before and after, a link to the page, and a note on what the change likely means: "Competitor X removed the free tier and raised Pro from $29 to $39. Their entry price is now above yours." The full history accumulates in Notion or a Google Sheet, so pricing discussions start from a record.
How does it work?
- Add the pages to watch. Competitor pricing pages, plans pages, or any page where packaging changes matter. Set the schedule: daily for fast-moving markets, weekly otherwise.
- The agent reads each page on schedule. It extracts tiers, prices, billing terms and feature lists into a structured snapshot.
- It diffs against last run. Cosmetic edits are ignored. Structural changes (price, tiers, features, terms) trigger an alert.
- It posts the change to Slack. Before and after, source link, and a short read on the competitive implication, informed by your own positioning docs.
- It keeps the history. Every snapshot lands in your tracking sheet or Notion database, building a pricing timeline per competitor.
Why put this check on a schedule?
Pricing changes are quiet. Competitors rarely announce a price increase or a feature demotion, and a rep discovering it mid-deal is the worst way to learn. A scheduled check turns "someone should keep an eye on this" into a system.
Because the workflow runs on Agentwork's knowledge layer, the alert is more than a diff. The agent knows your pricing, your positioning against each competitor and your battlecards, so it can say whether a change strengthens or weakens your position. When an alert needs a decision (say, sales asks whether to match a discount), the workflow can route the question to whoever owns pricing and record the answer for next time.
Works with
Web, Slack, Notion, Google Sheets. Runs on a daily or weekly schedule.
Frequently asked questions
How many competitor pages can I track?
As many as you like. Each page is checked independently on the schedule you set, and you can group alerts by competitor or by market.
Will I get noise from small page edits?
No. The agent compares extracted pricing structure, not raw HTML, so copy tweaks and design changes don't trigger alerts. Only changes to prices, tiers, features or terms do.
What does an alert look like?
A Slack message with the change summarized in one line, a before-and-after comparison, a link to the live page, and a short note on what it means for your positioning.
Can it monitor more than pricing pages?
Yes. Point it at changelogs, feature pages or plan comparison pages. The same watch-extract-diff loop applies. For broader competitor news coverage, pair it with the daily industry digest template.
Where does the history go?
Each snapshot is stored in a Notion database or Google Sheet you choose, so you can see any competitor's pricing evolution over months.