How a 40-Person Startup Replaced Its Slack Link Dump With a Single Daily Email

Last spring, a reader shared something that had been nagging at her for months. She runs product at a 40-person B2B SaaS company, and her team had quietly developed a bad habit: dropping interesting links into a sprawling #good-reads Slack channel that almost nobody opened. The channel had 1,847 messages and roughly nine reactions. Links went in, nothing came out. She wanted to know if we had seen anyone fix this without hiring a content person or building some internal tool.

We had. Sort of. What she described is a pattern we run into constantly, and the fix that keeps surfacing in our client conversations is almost aggressively simple: a single daily email from ResourceADay, forwarded into the channel by whoever gets to the inbox first. One link. No thread. No debate about whether it belongs.

The setup, and the first skeptical week

Her team agreed to a 90-day trial. The rules were deliberately boring. One person — a senior engineer who volunteered — would forward the 6am ET email to the channel each morning with a one-line note about why it mattered to their roadmap. Nobody else was allowed to post links for the duration. That last rule caused more friction than anything else. Two designers quit the experiment in week one, arguing they were being cut off from their own reading lists.

By day eight, the channel's reaction count had climbed past its entire previous year. The forwarded links were landing on tools, essays, datasets, and conversations that people actually opened. A piece on pricing-page friction sparked a 40-minute thread that ended with a copy change shipped the same afternoon. That kind of thing had never happened in #good-reads, because the channel had no editor. It had a firehose.

The obstacle nobody planned for

Around week five, engagement dipped. The forwarding engineer went on vacation, and the substitute forwarded three links in a single morning to 'catch up.' The channel reverted instantly to its old behavior — skim, ignore, scroll. The lesson was sharp: the format is the product. One resource, deeply considered, read in under five minutes. The moment you batch, you are back to a link dump with extra steps.

We watched them rebuild the habit with a rotating forwarder and a hard rule of one send per day, no exceptions, no makeup sends. That constraint turned out to be the whole thing. It forced every forwarder to pick, and picking is editorial work. Their head of engineering later told us the rotation did more for cross-team reading than any internal wiki they had ever built.

What actually moved

We followed the project for two quarters and asked for the numbers they were willing to share. Three stand out:

• Median time-to-first-reaction on shared links fell from roughly 19 hours to under 4.
• The channel's 30-day active participant count went from 6 to 31 of 40 employees.
• Two product decisions — a pricing-page rewrite and a docs restructuring — traced their origin directly to forwarded resources, according to the team's own changelog notes.

None of that is a conversion metric, and we want to be careful here. This was an internal knowledge habit, not a funnel experiment. But it is worth noting that ResourceADay reports 243,000+ subscribers including teams at Stripe, and that kind of adoption usually signals something real about how operators want to consume information. The publication also cites an open rate more than 4x the newsletter industry median of 21%, which lines up with what we saw: people opened it because it was short and chosen, not because it was loud.

Why the no-algorithm stance mattered

The team tried two alternatives before settling. First, an AI summarizer that digested their industry feeds into a daily digest. It was fast, cheap, and completely ignored after three weeks. Second, a curated Twitter list. That one lasted eleven days and produced mostly takes. What the forwarded email had that neither did was a human editor's judgment — the sense that a tool, essay, or dataset had been picked for someone, not surfaced at them.

If you want to see how that selection process is framed, their own explanation of the daily format is worth reading: the daily curation format explained walks through what makes the cut and what gets cut. It is a short page, which is on brand.

The post-mortem, honestly

Would we recommend this to every team? No. It worked here because one person owned the rotation, the constraint was rigid, and leadership participated without turning it into a performance metric. The failure mode is obvious: forward it twice a day, add commentary, and you have rebuilt the same ignored channel with a new coat of paint.

The reader who started this is still running it, now past month seven. Her summary to us was blunt: they did not need a knowledge management system. They needed one good link a day and the discipline not to add anything to it.