Receive a daily market and competitor briefing
This workflow brings industry articles from RSS feeds into a regular briefing. It can be adapted for consulting, marketing agencies, or product teams.
How this works
This workflow brings industry articles from RSS feeds into a regular briefing. It can be adapted for consulting, marketing agencies, or product teams. A daily briefing should distinguish fresh developments from repeated coverage and give readers a reason to care. It should not become a list of generated summaries whose dates, source quality, and relevance are impossible to inspect.
Collect from an approved feed set, cluster articles around underlying events, and draft a short editorial selection. The model proposes relevance and wording; deterministic timestamps and stable IDs control the collection window and deduplication. Sending is a separate authorized action.
Before you start
Audience remit
Specify industry, geography, competitor set, and the decisions the briefing supports.
Source list
Choose available feeds and a fallback for inaccessible items.
Delivery policy
Define the cutoff, maximum length, recipients, and review owner.
Prepare the inputs
- feed_items
- Required
Article metadata and text
Retain publication and retrieval dates.
- cutoff
- Required
Date and timezone
Use the same boundary each day.
- relevance_rules
- Required
Topics and exclusions
Distinguish must-cover events from optional reading.
- previous_digest
- Required
Recent event IDs
Avoid repeating unchanged stories.
- delivery_config
- Required
Approved channel
Do not infer permission to email from a recipient list alone.
Implementation, step by step
Collect the daily window
- Retrieve available feed entries since the previous verified cutoff.
- Record failed feeds and late-arriving items so a quiet source is not mistaken for no activity.
Checkpoint: A dated collection manifest.
Cluster duplicate coverage
- Group articles describing the same event and identify the original or most authoritative source.
- Keep materially different reporting and corrections attached to the cluster.
Checkpoint: An event-level candidate set.
Screen relevance
- Compare each event with the audience remit and explain why it matters.
- Reject generic mentions that do not change a decision or understanding.
Checkpoint: A short ranked editorial queue.
Draft concise items
- State what happened, when, and what remains uncertain.
- Separate reported facts from possible implications and keep an inspectable source reference.
Checkpoint: A briefing draft with evidence.
Review freshness and balance
- Check headlines, dates, numerical claims, and whether one topic crowds out the remit.
- Flag unavailable primary material and reduce certainty rather than fill gaps.
Checkpoint: A reviewed daily edition.
Deliver and record status
- Send only through the authorized channel or provide a ready-to-send file.
- Record the edition ID and confirmed receipt to prevent accidental duplicate distribution.
Checkpoint: A delivery record or clearly labeled unsent draft.
Decisions along the way
No relevant developments are found
Produce a short no-material-update note rather than filler.
A story is an update to yesterday's event
Highlight only the new fact and link the event history.
Important sources disagree
Describe the disagreement and defer a confident conclusion.
What you will produce
daily-brief.md
MarkdownA compact briefing for human review.
Include: edition_date · items · why_it_matters · uncertainties · source_refs
briefing-manifest.csv
CSVPrevents duplicates and records coverage limits.
Include: event_id · article_ids · status · edition_id · delivery_receipt
Check the result
- Verify each item falls within the stated freshness policy.
- Check syndication does not masquerade as multiple confirmations.
- Open the source for every consequential claim.
- Confirm sent status requires an actual receipt.
When something goes wrong
One feed fails
Continue with available sources and disclose the coverage gap.
The model adds an unsupported business implication
Rewrite it as a conditional question or remove it.
Delivery times out
Inspect existing receipt or message history before retrying.
A worked example
SYNTHETIC EXAMPLE · NOT A REPORTED BUSINESS RESULT
Request
Prepare today's retail-technology briefing.
Inputs
Synthetic example. Synthetic A1 and A2 repeat the same product launch; A3 corrects yesterday's release date.
Expected result
Synthetic expected result. The edition contains one launch item and one correction. It does not count three independent developments or resend yesterday's unchanged summary.
Run a small pilot
Start small
One daily edition across several consecutive business days.
Record the baseline
Record reading time, duplicate items, and editor corrections in the current process.
Agree success criteria
Agree relevance and factual-accuracy acceptance criteria before unattended collection.
Stop or revise
Pause sending when key facts or recipient authorization are unresolved.
Keep the scope clear
- The workflow may collect and draft without gaining authority to send externally.
- Public market evidence does not reveal competitors' private operating metrics.
Check before using
Check source coverage and important stories. The briefing depends on the feeds you select.
Business activities
- Research customers and markets
FROM A RECIPE TO YOUR WORKFLOW
Bring the company context together.
This workflow needs reliable inputs before it needs a better prompt. Moat8 Vault brings working information into a readable archive for the AI tools you use.
For this recipe: Industry publication and competitor feeds · Relevance criteria · Recipient list
Start with one recurring task, agree which sources to use, and review the first result with your team.
Discuss this workflow