How we handle GDPR data-subject requests on a deadline
Legal
A daily agent that checks competitor sites, changelogs, and pricing pages, diffs them against the last run, and posts a short summary of what changed to Slack.
Competitors ship changes quietly. A pricing tier moves, a feature lands in the changelog, a landing page gets rewritten — and unless someone happens to check that week, the team finds out late. Manually visiting a dozen sites every morning is the kind of task that gets done for a while and then quietly stops.
We watch our market with an agent that runs every day on Kortix. It checks competitor sites, changelogs, and pricing pages, diffs them against the last run, and posts a short summary of what actually changed to a Slack channel.
Keeping up with competitors is a standing task with no natural owner. The information is public, but it's spread across pages that change on no schedule, and most days nothing moves — so a person checking manually spends most of their time confirming that nothing happened.
The workarounds thin out. A page-change alerting tool fires on every edit, including cosmetic ones, and buries the real signal in noise. A shared doc of "things to check" depends on someone remembering to check it. The task needs to run daily, compare against what it saw last time, and only surface what's worth reading.
A cron trigger runs an agent every day. Each run spawns an isolated session that fetches the competitor pages we track, compares them against the previous run's snapshot, and writes a short summary of what changed to Slack. Cosmetic edits are filtered out; pricing moves, new features, and messaging changes are called out.
Open your Kortix workspace, start a new session, paste this prompt and send it. The agent writes the agent file, the competitor-diff skill and the daily trigger, and opens a change request for you to review. Prefer clicks? Choose Use this template instead.
Set up a daily competitor watch agent in this workspace.
Create the agent agents/competitor-watch.md. Its job is to check competitor pages for real changes and post a daily summary. It may fetch public web pages and use the Slack connector.
Create the skill skills/competitor-diff/SKILL.md with these rules:
Add a cron trigger daily-competitor-watch to kortix.yaml. It runs the competitor-watch agent every day at 06:00 with the prompt "Load the competitor-diff skill and run today's competitor-watch sweep."
Tell me which of these connectors are not connected yet.
Open a change request with all of it. Do not merge it.
The agent reads public pages with its built-in fetch, so the watch list needs no connector. Open Connectors in your workspace and connect Slack for the summary. Credentials are brokered server-side and never enter the agent's machine.
Posts the daily summary of real competitor changes.

Stores the competitor research you want to keep.

Merge the change request, then start a session with the competitor-watch agent and send this prompt. The first run only stores snapshots, so run it a second time to see a diff before you let the schedule take over.
Run one competitor-watch sweep.
The change request added this trigger to kortix.yaml. From now on the agent
runs every day at 06:00 and picks up from its ledger in memory/. To change the time, edit the cron line, or open
Triggers in the workspace.
triggers:- slug: daily-competitor-watch name: Daily competitor watch on: cron: "0 0 6 * * *" run: agent: competitor-watch prompt: Load the competitor-diff skill and run today's competitor-watch sweep.The agent sends plain GET requests to public pages and writes only to one Slack channel. It never logs in to a site and has no access to internal systems. The watch list changes only through a reviewed change request.
Each run ends with one message in the channel. This is what a run looks like in the session:
Checked 12 tracked pages and found 2 real changes. One competitor raised its team plan by $5 per seat, and another shipped 1 new changelog entry for an API feature. The other 10 pages had no meaningful change.
Once it works, paste any of these into the same session.
Also track each competitor public review page, and report new reviews that mention pricing or a missing feature.
On the first of each month, draft updates to our battlecards from the changes you reported, and open a change request for review.
When a competitor changes a price, post the change to #sales as well as #growth.
Even a read-only agent runs with the same controls as the rest of the platform:
The team learns about a competitor's pricing move or feature launch the morning after it happens rather than whenever someone next looks. Because each run diffs against the last, the channel stays quiet on quiet days and speaks up only when something actually changed.