The group chat problem
Every plan happens in a thread. None of them survive it. Here's what we think it takes to fix that.
Pango
May 18, 2026·1 min read
Six weeks before a kitchen remodel, four people decided on quartz. Two weeks later, someone re-asked "what counter did we land on?" and got three different answers. Nobody was lying. The decision happened in a group chat. The decision didn't survive the group chat.
This is the failure mode every plan hits. The thinking happens in messages — fluid, easy, where the people already are. The output should be a plan: a budget that knows what's in and out of cap, a schedule that knows what's blocked on what, a record of why you chose A over B that's still answerable six weeks later. Group chats give you the first half and nothing of the second.
People have papered over this with spreadsheets, Notion pages, shared docs. They mostly fail for the same reason: somebody has to keep them up. The moment the group's attention moves on, the doc rots, the spreadsheet falls out of sync, and the next time you ask "what did we decide?" you're back in the thread scrolling.
The thing we kept coming back to: the structured artifact has to maintain itself, from the conversation, as the conversation happens. Not as a separate task. Not as homework. Not as a thing one person becomes responsible for. The chat is the input. The plan is the output. The system in the middle is what's been missing.
That's what we built. You bring the people you'd already be planning with. You talk it through like you would. And the budget, the schedule, the decisions — they build themselves, get updated when you make a call, and stay current without anyone maintaining them.
It's a small idea on its face. In practice it changes what a group is capable of finishing.
