Who hurts
Engineering and product leads at 20–200 person companies.
The problem
Decisions are made in Slack and lost immediately. New hires re-litigate settled questions, and nobody can reconstruct why a constraint exists — so it gets removed and the outage returns.
What you build
Detect decision-shaped conversations, propose a short record — question, options considered, choice, reasoning, who decided — and post it back to the thread for one-click confirmation. Searchable forever.
Why now
Detecting 'a decision just happened' in a noisy channel is a classification problem that only recently got good enough to not be annoying.
Validate it this week
Read one team's Slack for two weeks and write the log by hand. If they start referencing your doc unprompted, it's real.
Why you'd keep winning
The accumulated log. Value is zero on day one and enormous at eighteen months, which is also the go-to-market problem.
The honest risk
Slack access is a security review at every serious company, and the payoff is delayed. Expect long sales and slow proof.
The prompt is written to make an AI argue with you before it writes code — that first round of pushback is worth more than the scaffold.