Noise‑Cancelling News Filter Prompt (Firehose Inputs → Relevance Scoring → Clean Daily Feed)
Quickly cut noise and keep only high‑signal items tied to your company, competitors, customers, and market.
Prompt Overview
Tips For You
Set the relevance threshold to 4 on high-volume days to keep the brief tight. | Maintain a living list of priority topics and entities and paste it at the top daily. | Ask for a second pass with a different threshold when the kept list feels thin. | Pin trusted sources so they win ties during deduplication.
From Operations TeamNexusAi TechnologyProblem It Solves
Unstructured feeds and newsletters bury the few updates that actually affect your roadmap or revenue.
Relevance Scoring
Ranks items 0–5 against your entities and priorities.
Deduplication
Removes near-identical coverage and keeps the clearest source.
Action Tagging
Labels each item as risk, opportunity, neutral, or watch.
Tight Output
Produces a compact, shareable table ready for Slack or Notion.
AI Prompt Instructions
Act as: An editorial analyst who filters a large daily feed into only the top few items relevant to our business priorities.
Why this task matters: Teams waste time reading low‑value items while missing material signals. A clean feed improves decisions and focus.
Important boundaries:
- Do not include duplicates or thin rewrites.
- Exclude generic funding rounds unless they impact our segment or rivals.
- Flag conflicts of information and unclear sources.
User inputs (provide below):
- Business focus: [industry, products, target customers, regions]
- Priority topics: [e.g., pricing changes, regulation, outages, partnerships]
- Entities: [our company], [top competitors], [key customers], [vendors]
- Daily feed: paste headlines + 1–2 sentence blurbs or links (20–200 items)
Objectives:
1) Score each item 0–5 on relevance to our focus and priorities.
2) Keep only items with score ≥3, sorted by score then recency.
3) Deduplicate near‑identical coverage; keep the clearest source.
4) Add a one‑sentence why‑it‑matters note for each kept item.
Analysis workflow:
1) Normalize: canonicalize names and merge duplicates.
2) Match: check each item against entities and priority topics.
3) Impact guess: infer likely impact area (product, GTM, finance, legal, ops).
4) Risk/opportunity tag: classify as risk, opportunity, neutral, or watch.
5) Keep/Drop: threshold ≥3; justify borderline cases.
Required output format:
- Header: date, total reviewed, kept count, drop reasons (top 3 patterns).
- Kept items table (rank, title, source, relevance 0–5, tag, why it matters, link).
- 3 bullets: What to watch tomorrow.
Quality controls:
- No more than one item per duplicate cluster.
- Eliminate clickbait lacking a credible source.
- Ensure at least one item addresses each priority topic if present in feed.
Verification checklist:
- Spot‑check 3 kept items for source credibility.
- Confirm entity names and ticker symbols are correct.
Final instruction: Produce the output exactly in the format above, concise, with clear, decision‑oriented wording.
Expected Outcome
Date: 2026-08-25 | Reviewed: 86 | Kept: 9 | Drop patterns: duplicate rewrites, generic funding news, vendor marketing posts. 1) Rival X launches SMB tier (TechCrunch) | Relevance 5 | Opportunity | Why: Directly targets our ICP with aggressive pricing. [link] 2) EU proposes data portability rule (Politico) | Relevance 4 | Risk | Why: Could require roadmap changes in Q4. [link] 3) Key customer signals vendor consolidation (WSJ) | Relevance 4 | Opportunity | Why: Chance to expand account before contract renewal. [link] What to watch: early SMB churn signals, regulator hearing schedule, consolidation RFP timeline.
Implementation Journey
Filter the firehose in ChatGPT
Paste your entities, priority topics, and today’s headlines into ChatGPT with this prompt. Expect a scored, deduped list ranked by relevance and tagged by risk/opportunity.
10 minStage the shortlist in Sheets
Copy the kept items table to Google Sheets. Add columns for owner and due date. Use conditional formatting to highlight Relevance ≥4 and risks in red.
8 minPublish a daily digest
Export the table to Markdown and post in your team’s Slack channel or Notion page. Assign one owner per item and add checkboxes for follow-up.
5 min