Notion's Strategy for AI Model Agnosticism and Cost Control
AI Engineergo watch the original →
the gist
Notion avoids vendor lock-in and token bloat by using an auto-routing model, prioritizing open-weight models for mid-tier tasks, and offloading deterministic workflows from LLMs to CPUs.
The Breakthrough
Notion maintains AI cost efficiency and operational leverage by treating model providers as competitors rather than partners, implementing an 'AI Switzerland' architecture that dynamically routes traffic based on cost-per-capability rather than raw token volume.
What Actually Worked
- Auto-Model Routing: Notion routes approximately 75% of its AI traffic through an internal orchestration layer that swaps providers based on the specific task requirements, preventing dependency on any single frontier lab.
- Task-Specific Model Selection: The team avoids using frontier models (like Claude 3.5 Opus) for low-complexity tasks such as email triage, reserving them only for high-complexity data analysis where the capability is strictly required.
- Open-Weight Adoption: Notion utilizes open-weight models for moderate-complexity tasks, which provides a credible alternative to frontier labs and exerts downward pressure on pricing while maintaining performance.
- Deterministic Offloading: The engineering team identifies workflows that do not require LLMs, such as converting CSVs to PDFs or executing SQL queries, and moves these to standard CPU-based workers to avoid unnecessary token consumption.
- Multi-Agent Orchestration: By building a system that allows different agents (e.g., Claude for scoping, Decagon for customer voice) to collaborate within a single persistent document, Notion creates a workflow where agents can tag teammates and open pull requests autonomously.
Context
Notion faces the common industry trap of monthly model upgrades that increase token usage or costs without proportional revenue growth. By treating AI suppliers as competitors, the company preserves optionality. This approach allows them to pivot providers instantly if pricing becomes untenable, ensuring that their product value remains tied to their proprietary data flywheel and orchestration capabilities rather than the specific model provider of the month.
Notable Quotes
- "Buy tokens from a lab that also sells the first party product and you are paying a markup on a markup for something you cannot defend, with no exit if you lock yourself to one provider."
- "Route by cost per capability per second, not per token."
- "If you don't have the capability to walk at any point you are stuck and again I think that's probably the most expensive decision you'll make."