❌ The Problem

Slack is built for sending messages, not reading them. It is a firehose: roughly 750 million messages a day across the platform, the average worker spending about 90 minutes a day actively in it and signed in for nine hours. Threads die the second they slip down the list, you still can't reply to a single message inside a thread, and search makes you want to throw your laptop across the room.

The cost of all that noise is now measurable. Microsoft's 2025 Work Trend Index found knowledge workers get interrupted every two minutes by a meeting, email or ping - about 275 interruptions a day - and it takes 23 minutes to fully refocus after each one. RescueTime put a number on it: messaging overload costs companies an average of $28,209 per employee per year in lost productivity. We have built a tool that punishes deep work with 47 unread badges and called it collaboration.

The one product that actually nailed the better primitive, Workplace from Meta and its 7 million paid users, got switched off for good on June 1st. Posts instead of flat channels, infinite nested replies, and old threads bumping back to the top when someone responded. The best abstraction for team comms just left the building, and nobody picked up the keys.

And then there's the user nobody designed for: agents. Teams are now running coding agents, research agents and ops agents daily, and asking one to follow a buried Slack thread is a recipe for a face-plant. Slack was architected for humans typing to humans, not for a model that needs to read the full state of a conversation, act on it, and report back. Here's the idea.

✅ The Idea

Concord is a Slack alternative built on posts instead of channels, where humans and AI agents share the same room. You post the thing you're working on, anyone (or any agent) can reply underneath it and reply to those replies, and the moment a post gets a new reply it jumps back to the top of the feed. Active work surfaces itself; finished work sinks quietly out of the way. It is async by default, agent-native from day one, and built for a team of three as happily as a team of three hundred.

🛠️ How It Works

The MVP (the wedge):

The roadmap (where it gets defensible):

⏰ Why Now

Three clocks are striking at once. First, Workplace's shutdown on June 1st vacated the one product with the right primitive, days before this idea went out - the lane is genuinely open. Second, agents went from novelty to daily driver in the space of a year, and none of the incumbents were architected for a non-human participant that reads and acts on entire conversations. Third, Slack fatigue has tipped from grumbling into a quantified productivity tax, while Microsoft is busy bundling Teams free into every Office seat and Salesforce is auto-provisioning Slack into every new customer from summer 2026 - both pushing a generation of small, fast, AI-native teams to actively want something that is theirs and not an enterprise default.