How Northwind cut engineering status updates from 6 hrs/week to zero
Northwind's engineering lead replaced the weekly Google Doc with an AutoReport-generated Slack digest. Managers stopped asking, engineers stopped writing, and the post has more readers than it ever did.
6 → 0
hrs/week spent writing updates
+340%
open rate vs old doc
100%
of Fridays delivered on time
“We killed the weekly engineering doc. AutoReport pulls from GitHub + Linear, writes the summary, and posts it to #engineering every Friday at 4pm. Zero upkeep, everyone reads it.”
AM
Alex Morales
Engineering Lead, Northwind
The challenge
Every Friday at 3pm, one engineer spent most of their afternoon compiling what the team shipped that week into a Google Doc. Half the team never opened it. The exec team wanted a summary but got either too much detail or none at all.
What they built
Connected GitHub (merged PRs + commits) and Linear (closed issues) as sources
Wrote a single prompt: `Summarize shipped features, bugs fixed, and top risks for an exec audience in under 250 words.`
Scheduled the report for Fridays at 4pm, posting to #engineering and cc'ing leadership
Added automatic retries to handle GitHub rate limits on big weeks
The outcome
Engineers got their Friday afternoons back
Open rate in Slack tripled vs the old doc in Notion
Execs stopped asking "what shipped this week?" in 1:1s
New hires onboard faster — the weekly post is a searchable history of everything we built
