Announcing o11's backing from Y Combinator.
AI for Notion
AI that builds the doc and the database.
- Draft structured docs and databases in place.
- Sync linked pages and properties without manual cleanup.
Acme HQQ2 Planning
Q2 Planning
- Owner: M. Chen
- Status: In progress
- Quarter: Q2
- Last edited: Apr 21
💡
Single source of truth for the Q2 platform plan, OKRs, and roadmap. Edit freely.
Roadmap
- Beta of structured logs to internal users
- Public docs refresh
- Pricing experiment readout
OKRs
| Key | Objective | Owner | Status |
|---|---|---|---|
| Q2-1 | Cut p95 latency 30% | M. Chen | On Track |
| Q2-2 | Hit 90% audit trail coverage | L. Park | On Track |
| Q2-3 | Land Kafka migration | A. Tanir | At Risk |
| Q2-4 | Improve mobile NPS to +30 | P. Singh | On Track |
| New |
Engineering threads
Open questions for the platform team
- Add a 'Pricing experiment' page under Engineering and link it from Roadmap.
Reasoning
I'll create the page in the Engineering.
o11 for Notion: an AI agent layer for the company workspace
o11 is an AI execution layer that runs inside Notion. The agent creates pages, edits databases, and keeps linked content in sync — without sending a teammate into a separate AI tool to draft something that has to be hand-pasted back into the right database row.
If you have searched for AI for Notion, a Notion AI agent, or an alternative to Notion AI for actual workflow execution, the difference comes down to one question: does the AI write a paragraph or run the workspace?
What teams use o11 for in Notion
- Doc creation. Build wikis, OKRs, runbooks, and meeting notes with the right hierarchy, templates, and properties from the start.
- Database edits. Update properties, relations, and rollups across pages — including bulk changes that would be tedious to do by hand.
- Cross-page sync. Keep linked databases, related pages, and synced blocks consistent when source-of-truth content changes.
- Intake to structure. Turn raw notes, transcripts, and external docs into properly-structured Notion pages and database entries.
Why o11 differs from Notion AI
Notion AI ships in-line as writing assistance, summaries, and Q&A across the workspace. The execution still ends with a human creating the page, editing the property, or wiring the relation. o11 is built to drive those edits. The chat is the control surface, Notion is where the structure lands.
Built for teams that live across systems
Notion is one part of a much larger stack — usually paired with Slack, GitHub, a CRM, and a project tool. o11 is positioned to act across all of them. A product spec discussion in Slack can become a Notion PRD, a set of GitHub issues, a CRM update for affected accounts, and a synced status page without anyone re-typing the same intent into four tools.
Where Notion teams typically start with o11
- Startup ops with company wikis and process docs.
- Engineering teams with PRDs, ADRs, and on-call runbooks.
- People teams with onboarding hubs and policy pages.
- Knowledge and research teams with structured note databases.
How o11 respects Notion permissions
The agent operates with the user’s own account. Workspace, teamspace, and page-level permissions apply exactly the way they do for that user in the UI. Nothing is bypassed. That is what makes o11 deployable in organizations that cannot trust a tool that edits the workspace as an over-privileged service account.
FAQ
How is this different from Notion AI?
Notion AI focuses on writing assistance and Q&A; o11 creates and edits structured pages and databases.
Who is it for?
Startup ops, engineering, and knowledge teams that run on Notion.