Signal or Noise: Teardown of a Competitor Alert Feed
Objective: Given three synthetic alerts pulled from a week-one competitor monitoring pipeline, find the defect in each one that would cause a sales team to stop trusting the feed.
You're the competitive intelligence analyst at Concord Biotech, the pharmaceutical API manufacturer, reviewing the first week of alerts from a new n8n + Perplexity pipeline tracking three rival API manufacturers.
Review each alert for a specific defect in what it says or how it's framed, not just whether the underlying change matters.
Before you start
What you'll need
Free path (everything below is enough to finish)
Free tier search is enough to verify or debunk one flagged alert at a time
Paid upgrades (optional, faster/deeper)
Adds the unstructured-sentiment layer the n8n + Perplexity pipeline alone doesn't cover
The process
Specimens to review
Review this alert. What's wrong with how it was generated and tagged?
ALERT: HIGH PRIORITY, POSITIONING SHIFT Competitor: RivalPharma API Division Source: FAQ page Summary: The competitor's FAQ page word count increased from 340 to 410 words. This may indicate a shift in their public positioning.
Specimen: synthetic, realistic
Review this alert. What's wrong with how it was generated and tagged?
ALERT: MEDIUM PRIORITY, PRICING Competitor: BioSynth Actives Source: Pricing page Summary: The competitor appears to have adjusted pricing on their standard API tier. Recommend the sales team review before their next call.
Specimen: synthetic, realistic
Review this alert. What's wrong with how it was generated and tagged?
ALERT: MEDIUM PRIORITY, HIRING SIGNAL Competitor: RivalPharma API Division Source: Job postings Summary: Competitor posted a new role today, indicating possible expansion into a new therapeutic category.
Specimen: synthetic, realistic
Final deliverable
Three alert teardowns, each naming the specific defect, its severity, and why it breaks sales team trust in the feed.
See a reference example
Awfis Space Solutions, week-one alert teardown (excerpt) ALERT: 'Competitor added a new pricing FAQ section' DEFECT: Tagged HIGH PRIORITY but contains no actual price figures, just a new FAQ block. SEVERITY: Critical, this is exactly the alert-fatigue pattern that makes sales ignore future high-priority tags.
Success criteria
You're done when you can:
- Identifies the actual defect in each alert, not just restates that the underlying event is minor
- Distinguishes a genuine defect from a plausible-sounding distractor in every item