Foundries vs Navigators: Lowering the Cost of Science
- ID
- 28133
- Status
- summarized
- Published
- 24 Sep 2026, 11:03 PM
- Fetched
- 24 Sep 2026, 11:35 PM
- Provider
- Latent Space
- Category
- developer-ai
- Original URL
- https://www.latent.space/p/foundries-vs-navigators-lowering
- Source URL
- https://www.latent.space/feed
Summary
- Score
- 4.0
- Created
- 24 Sep 2026, 11:35 PM
- Tags
- Audience
- foundersai_ml_learnersdevelopers
What happened
In a Latent Space guest post, Adrian Sanborn (Endura Therapeutics) argues that in science 'thinking got cheap and doing did not': LLMs speed up code, data wrangling and planning, but physical experiments still take days or weeks to verify, so AI barely moves experimental throughput. He splits the response into Foundries — companies industrializing measurement to generate data an order of magnitude faster (Xaira, NewLimit, Octant, Tahoe, Endura via sequencing/multiplexing; Insitro, Eikon, Noetik via high-throughput microscopy; Lila and Periodic Labs via physical automation) — and Navigators, companies that spend the 'surplus of thinking' on better decisions without needing a proprietary model or large dataset. Foundries are visible, capital-heavy, multi-year bets; Navigators are invisible because operational gains and rejected paths never get a press release. The post cites Anthropic opening a wet lab but offers no metrics, benchmarks or case-study numbers.
Why it matters
Useful as a scoping lens, not as news: if your product's verification step is cheap (software), cheaper thinking converts straight into more output, but if verification is a slow real-world step, AI only improves decision quality, not throughput — so don't budget for the same speedup curve. For founders, the essay's claim is that navigation is available to every company while foundry-style advantages require capital and years, which suggests where defensibility can and cannot be bought. No Malaysian or Southeast Asian angle appears in the text, so treat this as general strategy framing rather than local opportunity.
Discussion angle
Ask each person in the room to name one thing their team does that takes days to verify — a deploy, an approval, a lab or field test. That list is their 'doing' bottleneck, and it's the concrete test of whether the foundry or the navigator framing applies to them.