reddit · SaaS · 09-26 06:50 54 分 ← 返回列表

we killed 6 products before launch. the problem kept changing shape

in early 2025 i started with one thesis: models could do a lot, but they lacked the company context to do useful work. we built apps to probe that gap, then infrastructure to feed context to agents when opus 4.5 arrived, a github repo replaced a big piece of what we'd built. we pivoted to a context API for companies. six weeks of sales conversations gave us a harder answer: teams didn't have a budget for another API. they wanted their people to get work done with AI so we went back to an

五维评分

付费意愿

需求真实度

个人可落地

竞争空间

新鲜度

AI 分析

痛点：企业不想再采购一个孤立的上下文/API，而是希望员工能在 Slack 等日常工具里直接用上有权限感知和公司上下文的 AI 代理来完成工作。

目标用户：中大型企业团队、IT/平台负责人、希望让员工安全使用 AI 完成工作的业务团队。

证据：teams didn't have a budget for another API. they wanted their people to get work done with AI ... one shared agent in slack, with permissions & context scoped to each person

变现：按席位订阅的企业 SaaS，基础版按人数收费，高级版增加权限映射、审计日志、数据源连接器和私有化部署。

MVP：做一个 Slack 应用：连接 Google Drive/Notion/Slack 历史，按用户 OAuth 权限过滤上下文，在频道中提供共享 AI 代理，支持@提问、检索和简单任务执行，并记录审计日志。

竞品：Slack AI、Glean、Dust、Microsoft Copilot、Moveworks、ChatGPT for Slack

摘要：创始人回顾 2025 年杀死 6 个产品后，发现企业不愿为另一个上下文 API 付费，而是想让员工用 AI 完成工作。最终方向是 Slack 内共享 AI 代理，按个人权限和上下文隔离，并从 6 月起与设计伙伴共建后上线。帖子未给出收入数据，但提供了销售对话和设计伙伴验证信号。