Notion uses Braintrust to deploy frontier AI models within hours and keep 70 engineers aligned on evaluations
As Notion's AI grew from simple prompt chains to agentic workflows with combinatorial evaluation paths, quality problems became hard to find at scale, and existing databases began breaking under the load of large LLM traces.
Before Braintrust, quality problems at scale went unidentified, and as AI prompts grew to hundreds of thousands of tokens, standard search was too slow to navigate massive traces.
Notion now deploys frontier AI models within hours of release, with 80% of AI team work grounded in Braintrust evaluation feedback, 70 engineers aligned on evaluation practices, and meaningful quality improvements for APAC multilingual customers.
Frequently asked questions
What did this team achieve with this AI workflow?
Notion now deploys frontier AI models within hours of release, with 80% of AI team work grounded in Braintrust evaluation feedback, 70 engineers aligned on evaluation practices, and meaningful quality improvements for…
What tools did this team use?
Braintrust, Brainstore.
What results were reported?
AI team work based on Braintrust eval feedback: 80%; Engineers kept aligned on evaluation: 70; Time to deploy new frontier models: within hours of release; multilingual quality improvement for APAC customers: one of the top improvements that they've had in quality in the past year (source-reported, not independently verified).
What failed first in this deployment?
Before Braintrust, quality problems at scale went unidentified, and as AI prompts grew to hundreds of thousands of tokens, standard search was too slow to navigate massive traces.
How is this quality assurance AI workflow structured?
Customer experience review → Regression eval run → Frontier eval run → LLM-as-judge evaluation → Trace search via Brainstore → Frontier model deployment → Eval-driven iteration.