Skip to main content
Intempt
Coming soon

Weekly competitive intel briefing

Weekly scheduled AI agent scrapes competitor websites, review sites, social, and news, then posts a summarized competitive intel briefing to Slack.

Authored by Intempt Technologies

Recipe curators

Agentic workflow

Coming soon

8 steps Blu runs end to end. It drafts a plan and nothing runs until you approve it.

  1. 1

    Replace the Monday check

    Coming soon

    Blu builds a step

  2. 2

    Run it Monday at 7am

    Coming soon

    Blu builds a step

  3. 3

    Go through each competitor

    Coming soon

    Blu builds a step

  4. 4

    Read their public pages

    Coming soon

    Blu builds a step

  5. 5

    Compare against last week

    Coming soon

    Blu builds a step

  6. 6

    Write the briefing

    Coming soon

    Blu builds a step

  7. 7

    Post it to the channel

    Coming soon

    Blu builds a step

  8. 8

    Publish and spot check it

    Coming soon

    Blu builds a step

About this recipe

When to use it

Competitive intel usually means someone remembering to check five different sources on a Friday. This runs it as a scheduled agent and delivers a structured briefing to Slack instead.

What it delivers

A weekly scheduled AI agent monitors competitor websites, review sites, social, and news for material moves - pricing changes, feature launches, big customer wins, leadership changes - and summarizes them into a structured briefing posted to Slack.

How you prompt this

Describe the outcome in your own words and Blu Agent maps it to this recipe, or run it by name. It drafts a plan first and nothing runs until you approve it.

Tell Blu Agent what you want

“Weekly scheduled AI agent scrapes competitor websites, review sites, social, and news, then posts a summarized competitive intel briefing to Slack.”

recipe.md preview

Built from the published catalog. Blu Agent's full step prompts load in your workspace when you run it.

Sign up to read the full recipe.md and run it with Blu Agent.

Sign up to see the full recipe

Inputs & outputs

What the recipe needs before it runs, and what it leaves in your workspace.

Inputs

  1. Nothing declared beyond an Intempt workspace. Blu asks for anything else it needs as it goes.

Outputs

    How the recipe runs

    Blu follows the steps in order and shows you each one before anything goes live.

    1. 01Replace the Monday checkCreate a workflow 'Weekly competitive intel' scheduled to run every Monday morning. Goal: replace the manual 'check what competitors did this week' task with a structured AI-generated briefing the product and sales teams can consume in 3 minutes.
    2. 02Run it Monday at 7amThis step builds a workflow. Configure scheduled trigger: Every Monday at 7am local time. Skip if workspace is paused or no competitors are configured. Track last-run timestamp so weekly scrapes only fetch new content since prior run. Use the result of "Replace the Monday check".
    3. 03Go through each competitorThis step builds a workflow. Configure loop step that iterates over a configured list of competitor domains (configurable per workspace, typically 3-7 named competitors). For each competitor, run the subsequent scrape + analyze steps. Rate-limit between iterations to be polite to sources. Use the result of "Replace the Monday check", "Run it Monday at 7am".
    4. 04Read their public pagesThis step builds a workflow. Configure web scrape step for each competitor: pricing page, product/features pages, blog (last 7 days), changelog/release-notes page, careers page (hiring signals), G2/Capterra review summary, recent press releases. Respect robots.txt; cache to avoid re-fetching unchanged content. Use the result of "Replace the Monday check", "Go through each competitor".
    5. 05Compare against last weekThis step builds a workflow. Configure AI research step that compares this week's scraped content to last week's snapshot and flags material changes. Material = pricing changes, new features announced, leadership changes from careers/about pages, big customer wins from press releases, sentiment shifts on review sites, hiring trends suggesting product-area expansion. Outputs structured per-competitor briefing: what changed, what didn't, what to watch. Use the result of "Replace the Monday check", "Read their public pages".
    6. 06Write the briefingThis step builds a workflow. Configure AI write step that consolidates per-competitor findings into a single weekly briefing. Structure: (a) Top 3 most material competitive moves this week, (b) Per-competitor highlights, (c) Watch-list for next week (developing stories), (d) Recommended responses (e.g. 'Competitor X just launched [feature]: our differentiator is still Y; product marketing may want to update positioning'). Tone: factual, concise, scannable. Use the result of "Replace the Monday check", "Compare against last week".
    7. 07Post it to the channelThis step builds a workflow. Configure Slack step that posts the briefing to the configured competitive-intel channel (e.g. #competitive-intel). Format: rich block layout with sections, links to source pages, and a thread for team discussion. Tag product + marketing leads for major moves. Use the result of "Replace the Monday check", "Write the briefing".
    8. 08Publish and spot check itThis step builds a workflow. Validate and publish. Monitor: weekly briefing delivery (must not fail silently), team engagement (reactions, threads), and accuracy (occasional human spot-check that AI correctly identified material changes). Use the result of "Replace the Monday check", "Post it to the channel".

    Install Intempt and run it

    1. 1

      Sign up

      Create a free Intempt workspace.

    2. 2

      Connect your data

      Add the sources this recipe reads from.

    3. 3

      Ask Blu

      Type /competitive-intel-monitoring-workflow in Blu once this recipe is live there.

    4. 4

      Review and approve

      Blu builds each step and waits for your OK before anything goes live.

    Related recipes

    Intempt TechnologiesDiscovery call qualification fieldsGenerates an AI summary for Discovery calls from meeting data using the qualification framework in the summary recipe.View recipe Intempt TechnologiesPost demo nurtureKeeps a demo warm for 90 days with a playbook, a case study, an ROI calculator and a customer story, and pulls the AE in early if they bite.View recipe Intempt TechnologiesReturn rate by categoryShows which product categories get returned most, and which ones have got worse since last quarter.View recipe

    More recipes by Intempt Technologies

    Discovery call qualification fieldsGenerates an AI summary for Discovery calls from meeting data using the qualification framework in the summary recipe.View recipe Post demo nurtureKeeps a demo warm for 90 days with a playbook, a case study, an ROI calculator and a customer story, and pulls the AE in early if they bite.View recipe Product swap in a sceneReplaces the product in a shot you already have with a different one, keeping the scene, lighting and shadow the same.View recipe

    Got a play worth sharing?

    Publish it to the Intempt Collective Marketplace and earn when other teams run it.

    Submit a recipe