Nobody reads the #competitors channel

Every company that takes competition even slightly seriously eventually spins up a #competitors channel. Someone pastes a rival's new pricing page. Someone else drops a screenshot of a LinkedIn post. A sales rep forwards a deck a prospect leaked. It fills up. It feels productive.

It is doing almost nothing.

I've watched a dozen of these channels across different companies, and they all rot the same way. The channel is not a monitoring system. It's a place where evidence goes to be seen once and then buried. And the fact that it exists actively convinces the team they have competitive intel handled — which is worse than knowing they don't.

A feed is not a memory

The core problem is structural. Slack is a feed. Feeds are optimized for recency and forgetting. A competitor's pricing change posted on Tuesday is gone by Thursday, scrolled past a launch announcement, a meme, and three "anyone seen this?" threads.

Nobody scrolls back up. There's no diff, no baseline, no "here's what changed since last month." Every post is an isolated event with no before-and-after. You can't reconstruct a competitor's trajectory from a channel because the channel doesn't store trajectories — it stores moments, out of order, with no index.

This is the same failure as trying to diff a competitor against your own memory. The human brain and the Slack scrollback are both terrible databases. They give you the feeling of a record without the function of one.

Volume masquerades as coverage

The busiest #competitors channels are often the least useful. Somebody wires up a Google Alert, an RSS feed, and a couple of "track this company" tools, and now the channel gets fifteen posts a day. Most of it is a competitor being mentioned in a listicle, a junior marketer's tweet, a job board scrape.

The channel is loud, so it looks like coverage. But the actual signal — the pricing tier that quietly appeared, the enterprise page that added a SOC 2 badge, the integration that got pulled — is drowned under noise nobody filtered. High volume creates the exact opposite of what you wanted: it trains everyone to mute the channel. Once it's muted, it's dead, and the muting happens fast. This is the failure mode I wrote about in building a low-noise alert system — noise doesn't just waste attention, it destroys the channel's credibility.

No owner means no action

Here's the tell. Ask any team with a #competitors channel: "Who owns it?" The answer is almost always a shrug. It's everyone's channel, which means it's nobody's job. Posts get hearts and thumbs-up emoji. Almost nothing generates a decision.

A real competitive program has a person who reads the signal, decides what matters, and routes it — this pricing change goes to the PMM, this hiring spike goes to the founder, this integration ships to the roadmap conversation. A dump channel has none of that. It has react emoji, which is the corporate equivalent of nodding politely and moving on. If a competitor's public move doesn't reliably reach the one person who'd act on it, you don't have intel — you have a bulletin board. This is exactly why competitive intel shouldn't live as one undefined person's side-of-desk job either — undefined ownership and diffuse ownership fail for the same reason.

What the channel is actually good for

To be fair: the channel isn't worthless. It's a fine inbox. A place for humans to toss things they noticed. The mistake is treating the inbox as the system.

The part a Slack channel can never do is the boring, mechanical, continuous work: checking a competitor's pricing page, changelog, and careers page on a schedule and telling you precisely what changed since last time. That's not a human's job, and it's not a feed's job either. This is the narrow thing Seeto does — it monitors public surfaces continuously and surfaces each change as a discrete, timestamped event, so the diff arrives already isolated instead of scrolling past in a channel. It won't decide what the change means or write your strategy; a person still reads it and acts. But it replaces the one function the #competitors channel is structurally incapable of: remembering, and comparing.

Keep the channel. Just stop pretending it's a monitoring program. It's a place people paste things. The monitoring — the diffing, the memory, the "what changed" — has to live somewhere that isn't a feed everyone eventually mutes.