A CrewAI crew checks 50 competitor pages, changelogs and news sources every week and sends a short brief covering only what changed.
Keeping tabs on competitors usually means someone opening the same 50 tabs every Monday: pricing pages, changelogs, blogs, job boards and review sites. It takes half a day, gets skipped in busy weeks, and the notes land in a doc nobody reads. Important moves, like a pricing change or a new integration, get noticed weeks late.
Create sources.yaml with one entry per source: competitor, URL and type (pricing, changelog, blog, jobs, reviews, news). Six to eight competitors with six to eight sources each is a good starting mix.
In crew.py, create three agents: a Researcher with a Perplexity search tool, an Analyst that compares results with last week's snapshot, and an Editor that writes the brief. Use Process.sequential so each agent gets the previous one's output.
Build a custom CrewAI tool that calls the Perplexity API with a sonar model, takes a URL and a question, and sets search_recency_filter to 'week'. Reject any answer that comes back without source links.
Set the Analyst and Editor agents' llm to a Claude model through CrewAI's LLM class. Claude handles the long comparison context well and keeps the brief tight.
Save the Analyst's output to snapshots/YYYY-MM-DD.json. Each run loads the latest snapshot so the brief reports only what is new, not everything the crew found.
Run the crew from a GitHub Actions schedule (cron '0 7 * * 1') and email the Editor's Markdown output to the leadership list. Cap the brief at 400 words.
For {{competitor_name}}, check this source: {{source_url}} (type: {{source_type}}).
Report only changes published or detected in the last 7 days. For each change, give:
- what changed, in one sentence,
- the date it appeared,
- the exact URL where you found it.
Changes that matter: pricing or packaging, new features or integrations, homepage positioning, senior hires or open roles in new areas, funding, partnerships, and notable customer reviews.
If nothing changed, reply exactly "NO CHANGE". Do not summarise older content and do not guess.You are writing the weekly competitor brief for the leadership team at {{company_name}}. Below are this week's findings and last week's snapshot.
Write a brief under 400 words with these sections:
1. Top 3 moves this week: what happened, why it matters to us, and a suggested response.
2. By competitor: one or two bullets each, only for competitors with real changes.
3. Worth watching: weak signals such as job postings or roadmap hints.
Every claim must include its source link. Leave out anything already reported last week. Write plainly, with no marketing language.
Findings: {{findings_json}}
Last week: {{last_week_json}}An hour before each discovery call, get a one-page brief on the account, the attendee and recent news, saved to Salesforce.
Each month, find posts whose search clicks dropped, research what changed with Perplexity, and get a Claude-written refresh brief for each one.
Apify scrapes reviews of your products and your competitors', ChatGPT tags each one, and Airtable shows which complaints keep coming up.