Defining the next major product evolution of Notion AI, from market research through PRD, MVP, and rollout strategy.
I live in Notion 5+ hours a day for docs, specs, and meeting notes. What kept bothering me was that it could tell me everything about what my team had written, but nothing about whether the work behind it was actually on track. This case study is my attempt to work through what closing that gap would actually take.
Prepared by Soumi — Associate Product Manager (AI), Portfolio Case Study · July 2026
⚠️ Independent concept case study — not affiliated with or endorsed by Notion Labs, Inc. All competitor and market figures are drawn from public sources / third-party estimates and are directional, not official.
📖 ~20-25 min read. Short on time? The At a glance callout below, plus Sections 4, 5, and 6, carry the core argument.
At a glance (60-second version)
- The bet: the raw signal for delivery foresight already sits inside content Notion owns no new integrations needed to surface it.
- The MVP: one signal type (status-language detection), full explainability on every flag, an auto-generated status digest, unified pricing. No autonomous actions.
- The north star: % of Business-tier workspaces where Foresight measurably cuts duplicated status work, without a drop in engagement.
- Short on time? Sections 4 (vision), 5 (RICE), and 6 (PRD) carry the core argument; everything else is supporting depth.
Notion AI today is excellent at helping people write, draft, summarise, and rewrite content inside a page. It is not yet able to tell a team whether its work is actually on track. That gap is costing Notion real revenue: teams that need delivery foresight are paying for a second tool (ClickUp Brain, at $7–9/user/month) or, at the enterprise level, for Glean’s enterprise search (roughly $45–50/user/month), more than double what Notion Business costs specifically to get intelligence Notion doesn’t yet provide.
This case study proposes Notion Foresight: a new capability that reasons across the docs, comments, and database fields a team already keeps in Notion to surface delivery risk and decision drift before they become a crisis, with every signal traceable back to its source. Unlike Glean, Foresight doesn’t need to integrate with other systems; the content already lives in Notion. Unlike ClickUp Brain, it isn’t bolted onto a separate task tool; it works on the same pages and databases the team is already using.
The MVP is deliberately narrow: one signal type (status-language detection), full explainability on every flag, an auto-generated status digest, and unified Business-tier pricing with autonomous actions (auto-rescheduling, auto-sending) explicitly held back until trust is earned. The rollout is staged through internal dogfooding, a controlled design-partner pilot, and a phased Business-tier release, each gated on precision and engagement guardrails rather than a calendar date.
The core bet Notion’s advantage isn’t out-integrating Glean or out-executing ClickUp; it’s that the raw signal for foresight is already sitting inside content Notion already owns. Foresight turns that owned content into an early-warning system, not just better writing.
Notion currently competes in three categories at once, and that ambiguity is itself the strategic problem this case study resolves:
Notion’s own roadmap shows it trying to compete in all three simultaneously: its Agent can execute multi-step tasks like building a tracker from a meeting summary, AI Meeting Notes auto captures calendar linked meetings, and Enterprise Search is in beta. That is a workspace-automation play and an enterprise-search play layered onto a documents product, with no clearly stated unifying thesis for the gap this case study fills.