Engineering brief

Bridgewater's data platform: humans need precision, agents need scale.

AI Engineer3 min read · saves 14 min

At a glance

The brief is enough

Relevance
Practical value
Radar
Time horizon
Now
Warnings
None

Bridgewater built a 100M-document data platform for both human investors and AI agents. The key insight: humans need precision, agents need scale.

Designing data platforms for both humans and agents is a new challenge most teams are unprepared for.

Watch if you are building a data platform that will serve both human analysts and AI agents.

Summary

The motivating example. Sam Green opened with a simple query about AI's impact on the Korean won. A generic agent searched the web, found 15 sources, but only used two, one of which was three months old—an eternity in markets. The same query against Bridgewater's Vault platform returned 52 relevant documents from the correct time window and cited seven. The lesson: great data and proper connectors make agents impactful.

The platform. Bridgewater built Vault to house over 100 million unstructured documents from 135 external sources plus internal memos and transcripts. Every document is enriched with internal ontology tags—countries, concepts, markets, and time periods—so both humans and agents can filter and retrieve with high relevance. This curation turns raw data into a first-class asset for investment research.

Designing for two consumers. Aaron Linsky described the fundamental challenge: humans and agents read at vastly different speeds (300 vs 30,000 words per minute) and have different tolerances. Humans need high precision; agents can consume large result sets. Bridgewater benchmarked precision at 10—top 10 results correct—and found it at 60%. After iterative improvements with agentic search, they reached 90-95%.

The filtering bottleneck. Most vector database filtering falls into post-filtering (fast but low recall) or pre-filtering (accurate but slow). Bridgewater needed a middle ground for time-sensitive queries. They switched to Turbopuffer, which uses native filtering—scoring only nearest clusters that match metadata conditions. The result: speed near post-filtering with recall close to pre-filtering.

Habit migration, not just tooling. The team learned a great platform won't get used if it breaks existing workflows. Researchers lived in email with subscribed lists and folders. Vault replicated these as saved searches and collections. Only after matching old habits could Bridgewater introduce new capabilities like agent-driven question answering and dynamic feeds. This was the real product-market fit moment.

Proactive agents and compounding. The latest capability, the investor workbench, moves agents from reactive to proactive—surfacing topics needing attention. The agent proposes topics with summaries and evidence; the investor can dig deeper alongside it. Every interaction gets captured back into Vault, creating a compounding loop where the platform improves with each use.

My take

I've seen many AI platform projects fail because the team built one search experience and called it done. Bridgewater's talk is a useful reality check: humans and agents consume data at different speeds and with different expectations. The benchmarking effort (200 examples, less than a week) is a great low-cost way to measure quality. The filtering discussion is also valuable, many teams default to vector search without considering performance implications. What I'd add: the habit migration part is underrated. Researchers won't switch because the new tool is better; they switch because it replicates their existing workflow. That's a lesson for any internal platform team. The proactive agent workbench is aspirational but the foundational work is solid.

What to do with this

  1. Benchmark your search precision at 10 with a small set of curated examples to identify gaps.
  2. Separate query patterns for human users and automated agents in your data platform requirements.
  3. Audit existing researcher workflows and map them to platform features before building new ones.

Watch the video

This video is blocked due to your privacy settings. To watch this video, please accept YouTube marketing cookies.

Related breakdowns

Get TL;DW

Too Long; Didn't Watch.

A concise breakdowns of the AI and devtools videos that actually matter for engineering leaders.

Free. Weekly. No hype.

Video and thumbnails remain the property of their respective creators. tldw.news provides editorial analysis, commentary, and discovery links to original content.