AI Engineer World's Fair 2026
Notion's Token Town
Loading slides…
Read the talk
Notion’s Token Town: Building AI Systems You Can Afford to Run
Sustainable AI products require more than cheaper tokens: they need task-specific model choices, credible alternatives, deterministic execution and a durable place for people and agents to collaborate.
From a talk by Sarah Sachs
How do you build an AI company without becoming AI poor?
How do you turn enthusiasm for AI into a product—and an operating company—that can afford its own usage? That is the opening problem of Token Town. Sarah Sachs leads Notion’s AI engineering teams and negotiates its AI contracts. Her team’s Anna Wintour comparison is partly a joke about taste, but it also captures a practical responsibility: choose among suppliers without letting their offerings define the company’s product.
The work extends across the company, not just the people pictured at a launch. Sachs shows rising AI usage during 2026 as the backdrop to a broader change in Notion’s role. A durable system of record once primarily connected people with other people. Now it must also support people working with agents, and agents working with one another. Growth makes that collaboration valuable; it also makes the economics of every repeated operation consequential.
Suggest correction
This note stays in this page until you copy or download it. Nothing is submitted; reloading clears the draft.
From drafting an email to running a system
The first step is familiar: ask ChatGPT to draft an email telling a landlord why you should not pay for repainting, then copy the answer into your email client. The model helps you think and write, but you still carry the result into the world. As AI gains responsibility, the unit of work changes:
| Stage | What AI does | What remains outside it |
|---|---|---|
| Thought partner | Drafts the landlord email | Moving and sending the result |
| Assistant | Executes an individual requested task | Deciding which task comes next |
| Teammate | Performs a repetitive process | Connecting separate processes |
| System | Connects processes into operating workflows | Governing the whole system |
Early Notion AI fit the assistant stage: it saved employee time, but its capabilities were bounded by individual human requests. The teammate stage extends that into repeatable processes. The system stage requires those processes to interface with one another.
Sachs says 88% of people cannot get past AI as an assistant, without identifying the study or population behind that figure. Notion’s explanation is that data remains siloed and collaboration lacks a durable record. If one process cannot reliably find the decisions, context and results of another, adding more agents does not automatically produce a functioning system.
Suggest correction
This note stays in this page until you copy or download it. Nothing is submitted; reloading clears the draft.
An unchanged token price can hide a larger bill
Trying to buy your way from isolated tasks to an operating system can become extravagantly expensive. Sachs illustrates the mismatch with a blowtorch lighting a large cigar: the machinery works, but it is disproportionate to the job. Cost is a structural barrier to scale, not merely a procurement detail to revisit after the product succeeds.
Two upgrade scenarios make the problem concrete:
| Upgrade | What changes | Economic consequence |
|---|---|---|
| Reasoning-model upgrade | Sachs reports unchanged per-token pricing but three times as many output tokens. | The output-token portion of the bill triples for that usage. |
| Successor-model upgrade | Sachs reports a 40% price increase and predecessor deprecation within four months. | Keeping the old price is no longer a durable option. |
These are unnamed scenarios Sachs says Notion has faced; the workloads and billing details are not specified. The first exposes the difference between a unit price and the quantity consumed. The second combines a higher price with a deadline that weakens the buyer’s ability to stay put. Automatically upgrading without corresponding revenue growth passes the resulting loss to customers or investors.
Suggest correction
This note stays in this page until you copy or download it. Nothing is submitted; reloading clears the draft.
The supplier may also be your competitor
Large enterprises can hire consulting teams and develop internal expertise to navigate these changes. Smaller companies—the Fortune five million in Sachs’s framing—usually cannot bring equivalent negotiating power. Her aim is to translate lessons learned with Notion’s traffic volume into practices that remain useful without that volume.
The awkward starting point is that a model supplier may also sell a competing first-party product. That supplier produces the tokens; the application developer buys them at a markup and must then charge enough to support another business on top. Sachs argues that this resale structure is not, by itself, defensible value. Dependence on one provider makes the problem worse because it removes the option to leave.
A subscription-versus-API comparison posted by Dylan at SemiAnalysis illustrates her concern about the gap between first-party access and the economics offered to developers. The talk does not supply the numerical comparison. The product implication is nevertheless clear: a business built principally around reselling access is exposed to a supplier that controls both its input price and a competing customer offer.
Suggest correction
This note stays in this page until you copy or download it. Nothing is submitted; reloading clears the draft.
Match capability to the customer’s task
The defensible work sits above token resale: understand customers, build data flywheels, and use that knowledge to decide when capability, price or latency matters most. Compelling interfaces and orchestration can make purchased inference worth paying for. The most capable model is often also slow, and many customer tasks do not require its full capability. For an applied AI company, the goal is usually the best product using multiple models, rather than training the best model. Sachs’s formulation is: “Bet on the frontier, not on the lab.”
She connects this to an economic split between frontier and everyday usage. The Citadel Securities analysis Tokenomics closely matches the memo she describes: simpler models may provide a more cost-effective path to productivity. But the boundary is product-specific. A capability can be scarce for one workflow and already more than sufficient for another.
Notion’s examples put that distinction into operational terms:
- Large-scale data analysis: Sachs says Notion recommends Opus when the work warrants frontier capability.
- Inbox triage: Paying for that same capability can waste both the customer’s money and the application’s margin.
The routing decision begins with the task and its traffic pattern, not the newest model name.
Frontier tasks still matter. Sachs characterizes the leading providers as an oligopoly racing toward difficult capabilities, then explains why their pricing may not reflect the incremental value of those capabilities to your product. A leader can charge a premium for work that previously could not be done. A follower may only need to undercut the leader slightly—her illustrative example is a dollar per million tokens—to attract the rest of the market. Like adjacent gas stations, competitors can cluster their offers rather than produce a smooth price curve for every level of customer need. Your product team must define task complexity; the price list cannot do it for you.
Suggest correction
This note stays in this page until you copy or download it. Nothing is submitted; reloading clears the draft.
Make the ability to switch real
The provider best equipped for a difficult task changes as new models arrive. Marketing a product around one lab, or accepting a discount that effectively binds the product to that lab, can leave customers behind when another provider takes the lead. Interoperability has an engineering cost, but Sachs treats the ability to walk away as a source of negotiating power that can outweigh the discount.
Notion keeps multiple models available so that a pricing change does not become an existential product problem. Sachs reports that Notion’s Auto model handles about 75% of its traffic; she does not specify the measurement window or traffic denominator. State-of-the-art models remain available, and customers can also choose among them. This is the practical meaning of Notion’s AI Switzerland approach: model choice exists inside the product rather than being fixed by one supplier relationship.
The operating playbook requires more than adding another model to a menu:
- Build interoperability into the harness. Switching models mid-transcript can invalidate caches. Supporting multiple models does not require switching within every thread, but the architecture must make a change possible.
- Evaluate complete trajectories. Compare capability, cost and elapsed time across the full task. Sachs uses Parallel’s web search as an example: an individual call may not look cheapest or fastest, while an entire search trajectory exposes a different set of trade-offs.
- Keep switching practical. Product-specific evaluations provide the evidence needed to change models quickly and repeatedly.
- Bring suppliers useful evidence. Use-case evaluations and early-access feedback have value to frontier labs. Sachs describes exchanging that expertise instead of relying on extraordinarily large purchasing commitments.
The evaluation unit matters: a cheap call that leads to more work can be a poor choice for a finished task.
Suggest correction
This note stays in this page until you copy or download it. Nothing is submitted; reloading clears the draft.
Open weights create a credible alternative
Sachs’s preference is explicit: a discount is not worth losing optionality. Open-weight models expand that optionality for moderate tasks, and reinforcement learning can extend the range of work they handle. Their importance is both technical and commercial. A credible alternative can reduce customer costs while placing pressure on prices that would otherwise be set among a few frontier providers.
Sachs reports that Kimi K2.6 outperformed GPT-5.2, but does not give the task or evaluation conditions for that comparison. She also points to GLM-5.2 as another sign of progress. The useful engineering question is broader than those model names: can an open-weight model already do your work without additional reinforcement learning? Do not assume its only role is supervised fine-tuning for small tasks.
Answer that question with your own system’s tool errors and latency requirements, rather than external benchmark rankings alone. Sachs deliberately shows an older internal benchmark to emphasize the evaluation method rather than a current leaderboard. A conceptual slide credited to Philip at Baseten then makes the longer-term point: open models do not have to lead the frontier to cross a capability threshold your product needs. Its labeled thresholds progress from tab completion to code generation to a reasoning agent.
Sachs predicts that tasks adequately served today will probably be covered by open weights within six months. That is a planning forecast: build the ability to adopt an alternative before the alternative becomes attractive enough to force an urgent migration.
Suggest correction
This note stays in this page until you copy or download it. Nothing is submitted; reloading clears the draft.
Execute deterministic work as code
Some jobs do not need a different model; they need no inference at execution time. Sachs introduces Notion’s recently launched Workers under the principle of CPUs over GPUs. Converting a CSV into a PDF is a discrete program. Invoking Notion operations through a CLI does not inherently require an LLM to mediate each tool call. A deterministic SQL query should run in the database.
For example, counting open tasks by team is ordinary SQL. With a tasks table containing team_id and status, the operation can be expressed directly:
sql
SELECT
team_id,
COUNT(*) AS open_task_count
FROM tasks
WHERE status = 'open'
GROUP BY team_id
ORDER BY team_id;
An agent may help decide that this is the needed query, but repeatedly performing the aggregation does not require asking a model to reason through the rows. The distinction is between deciding what work to do and executing work whose rules are already known.
Governance adds another kind of value beyond inference: visibility into who uses data, maintainability and control. Model optionality also expands the choices a product can offer its customers. Sachs points to Notion’s governance interface without detailing its controls, then closes the economics portion around architecture, open weights and value that transcends tokens.
Suggest correction
This note stays in this page until you copy or download it. Nothing is submitted; reloading clears the draft.
Autonomy makes security and persistence central
Looking beyond Token Town, Sachs expects security rather than raw capability to define the next six months of product work. Simon Willison’s lethal trifecta describes the dangerous combination:
- Private-data access: the agent can read information that should remain protected.
- Untrusted content: ingestion, MCP or email can introduce material an attacker controls.
- External communication: the agent can send information outside the protected environment, including through payloads in web searches.
Together, these capabilities expose a route from malicious instructions in incoming content to private information leaving the system. More autonomy leaves more of that exposure unsupervised. Managing it is part of the product’s value, not an optional layer around model capability.
Sandboxes and computer environments connect the security discussion back to determinism and token economics. Multi-agent orchestration adds another set of questions: what can each agent see, what can it do, and what survives after it finishes? Sachs singles out the persistence of enterprise knowledge as an under-discussed requirement.
Without reliable coordination, a software factory can turn into an engineering team babysitting the factory. Sachs says Notion’s own efforts began that way. Orchestration is difficult because the system must preserve useful context and advance work across boundaries, not merely start several agents.
Suggest correction
This note stays in this page until you copy or download it. Nothing is submitted; reloading clears the draft.
A shared task document coordinates people and agents
A promotional slide featuring T-Pain introduces an openly acknowledged product pitch, followed by the concrete workflow. Sachs starts with a task in a Notion document and a Manage Agent capability she describes as launched that day. Claude Agent can inspect the task and scope the required work.
The important step is what happens when the task is not ready to implement. The agent begins populating a specification but asks a question about missing requirements. Instead of treating the response as the end of a chat, Sachs brings a teammate into the same document, tagging MJ, the product manager. The document is an active collaboration surface where a question can move from an agent to a person without losing the task around it.
MJ does not know the answer in this example either. That opens another handoff: Claude Code may be useful for implementation, while Decagon agents are better suited to collecting customer-voice evidence. Sachs asks those agents for the relevant data, then advances through part of the flow. A team lead replies in the shared document, supplying the human input needed to proceed. Claude can then create the pull request.
Claude reports that it has put up a PR. The selected frame shows the customer research and a human instruction to build above the Claude Agent reply, which includes a pull-request link and a Code explainer link. Implementation is now a concrete artifact in the ongoing discussion, but Sachs does not treat that as the end: she asks Codex to review it.
Sachs reports that Codex finds two issues in the demonstrated pull request. The workflow therefore crosses both human and provider boundaries: an agent scopes, people clarify, a specialist supplies evidence, a coding agent implements, and another agent reviews. The shared task record coordinates those contributions without requiring the whole factory to commit to one lab.
Suggest correction
This note stays in this page until you copy or download it. Nothing is submitted; reloading clears the draft.
From a demonstration to everyday operations
Sachs follows the demonstration with an internal example shared with Rajiv’s permission. She says almost all Notion polish work and larger feedback of the illustrated kind is coordinated through its software factories: work is routed to the right teams, and coding agents take the first implementation attempt. She also cites Vercel using the workflow from staging through shipping and closing.
Sachs reports over three minutes saved on a given customer task, without specifying the task, baseline or measurement conditions. The larger operational point is that repeated savings depend on knowing which models each task requires and preserving the option to change them. Factory economics emerge from the whole workflow, including coordination and review, rather than from a model’s token price alone.
That leaves product builders with an ongoing responsibility in a young, opaque and fast-moving market. Sachs credits communities such as AI Engineer with making these trade-offs discussable in public. Customers depend on application teams to scrutinize model purchasing and product decisions on their behalf—even as the available capabilities, prices and suppliers keep changing.
Suggest correction
This note stays in this page until you copy or download it. Nothing is submitted; reloading clears the draft.
Resources
From the talk
Frank Flight examines inference costs, physical constraints and the economic split between frontier and everyday AI workloads.
Simon Willison explains how private-data access, untrusted content and external communication combine to create prompt-injection risks.
Official model weights, deployment examples, licensing terms and task-specific evaluation results for Moonshot AI's Kimi K2.6.
Parallel's web-search product for AI applications, with access to documentation and a search playground.
Further reading
Notion introduces Workers, its CLI and external-agent building blocks, with links to developer setup resources.
Full transcript
Loading transcript…