This is a proposed workflow, not a tested performance claim. The goal is a short report that tells a small team what changed and why it may matter, without turning every social post into an alert.
Start with a narrow watch list
Choose three competitors and provide their product pages, pricing pages, and release notes. Include the questions your report should answer: Did a relevant plan change? Was a missing feature released? Did the product reposition toward your customers?
Public websites and product documentation are a manageable starting point. Add social sources only if they provide information the core pages miss.
Give the Bot a starting prompt
You are my competitor research assistant. Read the three competitors and URLs in the attached watch list. Build a baseline with product positioning, plans, key features, and source links. Separate direct observations from interpretation. Do not invent a historical change when no earlier snapshot exists. Return the baseline for review before setting up recurring checks.Inspect that baseline first. If a price depends on billing period, seat count, or a promotion, the report should preserve those conditions rather than flatten them into one misleading number.
Define the weekly report
Use one row per meaningful change: competitor, source, previous observation, current observation, observed date, and possible relevance. Keep “possible relevance” separate from the observed fact.
For example, a changed pricing page is an observation. “They are targeting larger companies” is a hypothesis unless the company states it. An inaccessible page is a failed check, not proof that nothing changed.
Turn a good report into a routine
Once two manual runs produce useful results, save the process and request a weekly schedule. Include what to compare against, how to avoid reporting the same change twice, and when to notify you.
Check the approved watch list every Monday at 9:00 AM Asia/Shanghai. Compare against the last successful snapshot. Report material changes with evidence. If nothing material changes, keep the run record but do not notify me. Notify me if a required source cannot be checked. Never publish or message competitors.Decide whether the workflow earns its place
After a few runs, look at useful changes found, irrelevant alerts, and the time you spend verifying the report. Expand the watch list only if the small version is useful. See routine setup for scheduling details.