← All workflows
Workflow · 2026-07-31

The Daily Content Scan to Article Pipeline

The exact system that scans sources every morning, applies a real quality bar, verifies against primary sources, and drafts a full article, all before the workday starts.

A "find something to write about" routine that's really just scrolling with extra steps doesn't scale. This is the system that replaced scrolling: a daily scan that reads the sources, ranks what it finds, and only produces a draft when something actually clears the bar.

Step 1: Scan on a schedule, not on demand

Every morning, before anyone is at a desk, an agent pulls the last day's activity across a fixed set of sources: X, LinkedIn, Hacker News, Product Hunt, GitHub's trending repos. It writes one ranked digest: the strongest candidates first, each with its source, the actual numbers behind it, and why it might matter.

Step 2: A quality bar, not a quota

This is the part that makes it worth running: most days produce zero usable articles, and that's treated as a correct outcome, not a failure. The bar is specific: a named primary source, verifiable claims, real numbers or dates, enough substance for a real piece. A vague trend or a warmed-over take doesn't clear it. Forcing a thin article out of a thin day is the failure mode this is built to avoid.

Step 3: Verify before writing a word

If the scan's source for a story is a secondary write-up, the first move is finding the actual primary source: the company's own post, the original paper, the real changelog. Secondary coverage only ever corroborates, it never substitutes. Nothing gets written from a number nobody has confirmed.

Step 4: Pick the keyword, check for duplicates, then write

Before a single sentence gets written, two things happen: a primary keyword gets chosen (the actual phrase someone would search, not a paraphrase of the headline), and the existing published library gets checked so the same ground doesn't get covered twice. Only then does the draft get written, with that keyword worked in naturally rather than stuffed in after the fact.

Step 5: Draft to a review queue, never straight to live

The output lands in a review folder, not on the site. Nothing publishes itself. A person reads it, fixes what needs fixing, and decides if and when it goes out.

Why this beats "just write something today"

The honest cost of a scan-and-verify system is that most days it produces nothing, and you have to be fine with that. What it buys back is real: every piece that does ship has already survived a quality bar, a source check, and a duplicate check, before anyone has spent a minute writing.

Want this built for your business?

Everything here is yours to copy and adapt. If you'd rather have it built around how your business actually runs, tell us what you're trying to automate.

Apply for a strategy call

Read personally, answered within two business days.