21 Media · content · United States Live

A research digest that writes its own first draft on a schedule

It pulls its sources and summarises them, then posts the draft to Slack and logs it.

Before
Hours each cycle reading and summarising sources
After
A first draft every cycle, pulled from feeds and searches, summarised, posted to Slack and logged, on a schedule
41 steps from sources to a posted draft
The work, before and after
Before and afterBefore: Sources, then Read by hand, then Summarised by hand, then Draft from blank. After: Feeds and searches, then Auto summaries, then Draft written, then Posted to Slack, then Logged. Result: 41, steps from sources to a posted draft.BEFORE3 OF 4 PAIN POINTSAFTER4 OF 5 AUTOMATEDSourcesRead by handSummarised byhandDraft from blankFeeds andsearchesAuto summariesDraft writtenPosted to SlackLogged41steps from sources to a posted draftBefore and afterBefore: Sources, then Read by hand, then Summarised by hand, then Draft from blank. After: Feeds and searches, then Auto summaries, then Draft written, then Posted to Slack, then Logged. Result: 41, steps from sources to a posted draft.BEFORE3 OF 4 PAIN POINTSAFTER4 OF 5 AUTOMATEDSourcesRead by handSummarised by handDraft from blankFeeds and searchesAuto summariesDraft writtenPosted to SlackLogged41steps from sources to a posted draft
First draft
ready every cycle
On schedule
without manual chasing
How the system runs
Input
  • Content sources
ArrAI
Read & summarise pipeline
Output
  • Structured first draft
  • On a schedule

01 What changed

  • The digest starts from a draft, not a blank page
  • Hours of weekly reading and summarising disappear
  • The operator spends their time on judgement, not collection
The full story The problem, how we approached it, and what we built

A content operator was spending hours each week reading and summarising sources for a recurring digest. We automated the read-and-summarise so the work starts from a draft.

02 The problem

Producing a regular digest meant manually working through a stack of sources every cycle: reading, picking what mattered, and summarising it.

It was hours of repetitive work before any real editing or judgement could happen.

03 The approach

We built a pipeline that gathers the sources, reads them, and produces a structured first-draft digest automatically.

The operator's judgement still decides what ships. The machine just removes the hours of reading and summarising that came before it.

04 What we built

  • Pulls from RSS feeds and targeted news searches on a schedule
  • Summarises each article and writes the newsletter draft
  • Posts the draft to Slack and logs it to a sheet
  • 41-step workflow, running on its own

Want this kind of result mapped for your business?

Book a discovery call