Skip to content

Case Study · Product

Case Study: Product Team Ships Weekly Competitive Briefings

How a B2B SaaS product team automated competitor tracking and delivered cited Monday briefings to Slack for $6/week.

B2B SaaSRouteStack (fictional)Stack: Claude Haiku + Sonnet, Tavily Search, n8n self-host, Slack, S3 snapshot store
Competitive IntelResearchAutomationn8nSlack
Edited by The AIKnowHub team · Editorial team

Results

Competitors tracked

8

Weekly briefing cost

$6

PM weekly time saved

4 hrs

Uncited claims in briefings

0

Background

RouteStack sells workflow software to mid-market ops teams. Leadership wanted systematic competitor tracking. Reality: PMs checked rival sites when something went viral on Twitter.

The problem

GapImpact
No weekly rhythmSurprised by launches
Notes in NotionStale, uncited
Manual search4+ hours/PM/week
Leadership asks in SlackScramble mode

They implemented Build a Competitive Intel Monitor on self-hosted n8n.

Architecture

Cron Monday 7am
  → Load competitor YAML from git
  → Load last-week snapshot from S3
  → Per competitor (parallel):
      Search news, pricing page, changelog RSS, jobs
      Haiku: extract deltas vs snapshot
  → Sonnet: synthesize 1-page briefing with citations
  → Post to #competitive-intel Slack
  → Save new snapshot to S3

Results (12 weeks)

MetricBeforeAfter
PM manual research time~4 hr/week~30 min review
Monday briefing deliverySporadic12/12 weeks
Roadmap decisions citing briefing03
Monthly pipeline cost—~$25

What worked

  1. Git-versioned competitor list — PR review when adding rivals
  2. Snapshot diff — only new deltas in briefing
  3. Citation required — zero uncited bullets policy
  4. Separate search vs synthesis models — Haiku then Sonnet

What they'd do differently

  1. Add pricing page hash — detect silent pricing changes without NLP
  2. Include investor/portfolio pages — caught one stealth launch late
  3. Archive briefings in Notion automatically — Slack scrollback was lossy

Takeaway

Competitive intel fails when it is sporadic and uncited. A $6/week n8n pipeline with mandatory URLs beats heroic manual research. Start with the workflow guide.

Lessons learned

  • 01

    YAML competitor config in git was the source of truth — not the n8n canvas.

  • 02

    Diffing against last week's snapshot prevented repeating old news.

  • 03

    Haiku for search summarization, Sonnet only for final briefing prose — cut cost 70%.

  • 04

    PMs ignored briefings until every bullet had a URL — citations earned trust.

  • 05

    Job board signals predicted two competitor launches a month early.

Frequently asked questions

A part-time analyst was $3k/mo. The pipeline cost ~$25/mo total and ran reliably every Monday 8am.

Related on AIKnowHub