Why We’re Building Unmeeting

The problem nobody wants to admit

Remote teams average 30+ meetings per week. Thirty. Let that sink in. That’s six hours a day where people sit on calls, half-listening, waiting for their turn to talk, while their actual work piles up in another tab.

Here’s the uncomfortable truth: 90% of those meetings could be async. The standup that takes 25 minutes? That’s a thread. The “quick sync” to make a decision? That’s a two-paragraph message with a clear ask. The all-hands where 40 people listen to updates they could read in 3 minutes? That’s a decision log entry.

We don’t have a communication problem. We have a defaults problem. The default is “schedule a call.” It should be “write it down.”

Slack isn’t the answer

Slack was a revolution when it launched. Real-time messaging for teams — brilliant. But real-time is the problem. Slack creates urgency by design. The typing indicator. The presence dots. The red notification badge that screams “someone needs you RIGHT NOW.” It fragments deep work and buries important context in scrollback that nobody will ever find again.

And email? Email is where decisions go to die. Buried in reply-all chains, lost between “per my last email” and “circling back on this.” Nobody knows who decided what, when, or why. Six months later, the same decision gets relitigated because there’s no record anyone can find.

• Slack creates urgency and fragments deep work
• Email buries decisions in unstructured reply chains
• Notion is for docs, not discussions
• Loom is async video — one direction, no structured decisions
• No tool treats async communication as the default, not the exception

What Unmeeting actually is

Unmeeting is an async-first collaboration platform built on two core primitives: threaded discussions and decision logs. That’s it. We’re not building another chat app. We’re not building a project management tool. We’re building the place where teams think, discuss, decide, and move on — without scheduling a call.

Threaded discussions give every conversation structure. A title. A body. Replies that stay organized. No “typing...” indicators. No presence dots. No urgency by design. You respond when you’ve had time to think — not when someone’s staring at a blinking cursor waiting for your reply.

Decision logs make outcomes first-class citizens. Every decision has a clear structure: what was decided, why, who decided it, and when. Linked to the thread where it was discussed. Searchable across your entire workspace. Never hear “wait, when did we decide that?” again.

Why AI changes everything

Here’s where it gets interesting. The biggest friction in decision-making isn’t the discussion — it’s the logging. Nobody wants to manually write up what was decided after a long thread. So decisions don’t get recorded. Context gets lost. The same arguments happen again three months later.

AI fixes this. Our AI reads your threads and auto-detects when a decision has been made. “Let’s go with option B.” “Final call: we’re using Postgres.” “We agreed to ship by Friday.” The AI surfaces these moments and drafts the decision log entry for you. You confirm, edit, or dismiss — but the friction of writing it from scratch is gone.

AI-powered decision extraction

As threads progress, the AI monitors conversations and identifies decision-like statements. It surfaces a card: “It looks like a decision was made — want to log it?” Pre-filled with title, outcome, reasoning, and participants. Linked to the exact messages that led to the decision. Context is never lost.

AI advisor with institutional memory

The AI advisor is the team member who remembers everything. Invoke it in any thread and it surfaces related past decisions: “FYI, 3 months ago the team decided X on a similar topic — here’s the reasoning.” It identifies blind spots: “Nobody has mentioned the impact on the mobile team — should they weigh in?” It summarizes long threads so latecomers can catch up in 30 seconds instead of reading 47 messages.

• AI reads threads and auto-detects decisions — no manual logging required
• AI advisor surfaces past decisions and identifies blind spots
• AI summarizes long threads for latecomers
• Timezone-aware notifications — no 3am pings, ever
• Meeting cost calculator shows the ROI of going async

The math that makes this obvious

Let’s talk money. The average meeting costs $300–$1,000 when you factor in the hourly rates of everyone in the room plus the opportunity cost of what they could have shipped instead. A 20-person team on our Team plan pays $240/month — less than the cost of one unnecessary all-hands meeting.

Our meeting cost calculator makes this visible. Every thread displays the estimated cost of the meeting it replaced. Your dashboard tracks cumulative savings: “Your team saved $14,200 this quarter by going async.” It’s not abstract productivity advice. It’s dollars and hours, right there on screen.

The vision: decisions as first-class citizens

Most tools treat decisions as afterthoughts. They’re buried in chat scrollback, lost in email chains, or scribbled in meeting notes that nobody reads. We think decisions deserve better. They’re the atoms of progress — every feature shipped, every strategy chosen, every direction set starts with a decision someone made.

Unmeeting makes decisions visible, searchable, and connected. You can trace any decision back to the discussion that produced it. You can see how decisions relate to each other over time. New team members can onboard by reading the decision log instead of sitting through a week of “context download” meetings.

Decisions are the atoms of progress. Every feature shipped, every strategy chosen, every direction set starts with a decision someone made. They deserve to be first-class citizens — not afterthoughts buried in chat scrollback.

This is just the beginning

We’re building Unmeeting because we’ve lived the problem. We’ve sat through the meetings that should have been messages. We’ve searched Slack for 20 minutes trying to find a decision someone made last quarter. We’ve watched teams relitigate the same choices because nobody recorded the outcome the first time.

The future of work isn’t more meetings with better video quality. It’s fewer meetings because teams have better tools for thinking, discussing, and deciding together — on their own time, in their own timezone, with full context preserved.

That’s what we’re building. And we’re just getting started.