CHAPTERS
- 1:39 – 2:45
Panel setup: Building at the frontier with Gamma, Cognition, and Harvey
Beth Robertson opens the session by framing the shared challenge: designing architectures for frontier AI products that change quickly as models improve. She introduces the panelists and sets the expectation that the conversation will focus on real bets and technical/product nuances.
- •Anthropic’s startup team hosts a frontier-AI architecture discussion
- •Panelists represent AI-native application companies across design, coding, and legal
- •Theme: architectural decisions are moving targets as model capabilities evolve
- 2:45 – 3:39
Founding bets: Harvey’s wager on rapidly improving models for legal work
Niko Grupin explains Harvey’s core bet: foundation models will improve quickly and generalize into the legal/professional-services vertical. He recounts early Harvey work using smaller models for Reddit legal Q&A and how capability gains expanded ambition toward BigLaw workflows.
- •Harvey bet on fast model progress and legal generalization
- •Early days: small-model legal Q&A on Reddit from an Airbnb
- •Model-layer progress raised the product ceiling toward complex legal work
- 3:39 – 5:21
Founding bets: Cognition’s bet on autonomous coding agents
Walden Yan describes Cognition’s thesis behind Devin/Windsurf: software agents should not only write code but run, test, debug, and deliver working PRs. He highlights how recent agentic model improvements made long-horizon autonomy and cloud-based agent usage practical at scale.
- •Core bet: end-to-end autonomous coding agents (not just code completion)
- •Early vision exceeded model capabilities; became viable through incremental progress
- •Agentic models + computer-use/testing enabled long-horizon autonomy
- •Customer agent usage growing rapidly, pointing to ‘cloud agents’ expansion
- 5:21 – 6:32
Founding bets: Gamma’s bet on removing the “90% formatting work” in visual communication
Deanie Fatiha outlines Gamma’s mission: help professionals focus on ideas while AI handles design, structure, and polish across decks, docs, and other visual artifacts. The bet is that AI can remove the time sink of formatting and “futzing,” elevating the user’s core insight.
- •Gamma targets high-stakes visual communication (decks, proposals, marketing pages)
- •Pain point: 10% insight, 90% formatting/design labor
- •AI should structure narrative, design output, and make ideas look great
- •Scale: tens of millions of users using AI-assisted visual creation
- 6:32 – 8:03
What made these products possible: key ecosystem shifts and capability inflections
The panel discusses the moments that turned ideas into feasible products. Gamma cites image-model quality, instruction tuning, tool-calling, and connectors (MCP) as repeated tailwinds; Cognition cites native code editing and better file-system/memory use; Harvey points to foundation models, reasoning, and coding-agent advances enabling workflow automation.
- •Gamma: image models + instruction tuning sparked early “aha”; tool-calling enabled agentic editing
- •Gamma: MCP/connectors changed both product experience and distribution
- •Cognition: native code editing removed workarounds; file-system usage improved planning/memory
- •Harvey: foundation models → reasoning models → orchestration offloaded to models
- 8:03 – 9:40
Gamma’s connector strategy: MCP as workflow embedding + acquisition channel
Deanie explains how MCP-style connectors let Gamma appear inside tools users already live in (including Claude), reducing workflow breaks and increasing frequency of use. This embedding also becomes a discovery and acquisition channel, expanding distribution beyond Gamma’s native surface.
- •Gamma as an agent inside other products/users’ primary workflows
- •Increased retention/engagement by removing context switching
- •New-user acquisition through partner ecosystems (e.g., Claude)
- •Connectors shift how Gamma thinks about GTM and distribution
- 9:40 – 11:14
Cognition’s agent engineering lessons: deleting early systems and relying more on file systems
Walden details how early agent stacks required complex custom workarounds because models couldn’t edit code reliably. As models became RL-tuned for code editing and improved at navigating file systems, Cognition could simplify planning/memory approaches—moving from RAG-heavy patterns toward deeper file-system-based context and persistence.
- •Early limitation: models produced whole files rather than precise edits
- •Custom inference/planning techniques were necessary but later became obsolete
- •Modern agents use file systems natively for context, plans, and memory
- •Shift: from bespoke memory/RAG toward file-system-centric workflows
- 11:14 – 13:03
Harvey’s multi-agent future: mapping law-firm hierarchies onto agent hierarchies
Niko describes how legal work is decomposed through hierarchical teams (partner → senior associate → junior associate). With stronger models and managed agent infrastructure, Harvey can mirror this structure with coordinated multi-agent systems, unlocking broader workflow automation than single-agent task completion.
- •Three inflection points: foundation models, reasoning models, then coding agents/planning offload
- •Workflow automation becomes more feasible with better reasoning and orchestration
- •Multi-agent coordination mirrors real law-firm hierarchies
- •Managed agent infrastructure enables scalable orchestration patterns
- 13:03 – 14:40
Hard-earned lesson: every major model wave can force a full re-architecture
Beth prompts reflections on what the panelists would do differently. Niko emphasizes that each capability inflection required Harvey to rebuild architecture; therefore teams must avoid rigid point-in-time decisions and instead plan for exponential change, revisiting priorities continuously.
- •Model waves triggered repeated full-stack re-architecture at Harvey
- •Avoid locking into architectures; plan for rapid capability shifts
- •Keep quarterly planning but add frequent execution retros to re-prioritize
- •Success requires “agent-native” pivots when the landscape changes
- 14:40 – 16:01
Cognition’s caution: invest in observability, replay, and evals to evolve with models
Walden argues that scrapping systems is normal—what matters is building the instrumentation to change quickly and safely. Strong logging, debuggability, replay tools, and evals let teams compare model versions and understand agent decisions instead of blindly iterating prompts.
- •Accept deletion/rewrite cycles as the default in AI product development
- •Observability is foundational: logs, traces, and decision introspection
- •Replay + evals enable safe upgrades across models and prompts
- •Avoid “building in the dark” with unmeasured prompt tweaks
- 16:01 – 19:06
Gamma’s current rebuild: rebalancing speed vs ‘nailed it’ quality across workflows
Deanie explains Gamma is re-orchestrating its generation architecture because user expectations shifted. Generation can tolerate longer latency for better results, while editing demands snappy responsiveness—so Gamma is building a flexible system that dials speed/quality and can route across multiple models based on context and user need.
- •Early breakthrough was “blank to beautiful deck in a minute” speed
- •New expectation: users wait longer for higher-quality, self-critiqued outputs
- •Editing still requires low-latency responsiveness
- •Architecture goal: parameterized speed/quality, often user-controlled
- •Multi-model orchestration supports different workflow requirements
- 19:06 – 20:41
Big bets now: self-driving codebases and cloud agents as the new software org baseline
Walden describes Cognition’s near-term bet: AI becomes the default driver of software projects end-to-end, pulling humans in only for review or high-level decisions. This shifts engineering roles and enables much higher throughput—effectively multiplying each engineer with many concurrent agents.
- •Trend: cloud agents becoming broadly practical
- •AI drives planning, coding, testing, and review; humans supervise at higher abstraction
- •Each engineer can run many agents in parallel, changing team structure
- •Cognition partners with enterprises to reshape workflows and project management
- 20:41 – 23:18
Harvey’s bet: collaboration + infrastructure constraints to turn personal AI into org productivity
Niko stresses that widespread individual productivity doesn’t automatically translate to organizational gains—and can amplify mistakes if governance is weak. Harvey is prioritizing infrastructure for sensitive legal contexts (ethical walls, data boundaries, public/private separation) to enable safe collaboration among humans and agents in shared workspaces.
- •Org productivity requires new interfaces and collaboration patterns
- •Risk: moving faster can increase blast radius when wrong
- •Infrastructure-first: enforce data constraints and ethical walls in law-firm settings
- •Hard boundaries for client confidentiality and source separation before agent autonomy
- •Memory and workspace design become key enablers for human-agent collaboration
- 23:18 – 24:49
Gamma’s forward-looking bets: ‘taste’ as differentiation and designing for agent-mediated communication
Deanie highlights two focus areas: expanding Gamma’s design range (“taste”) and rethinking the product for a world where agents use tools like humans do. The challenge becomes making the product delightful for humans, agents, and collaborative workflows between them.
- •Doubling down on visual quality and design range as a core moat
- •Preparing for agent-mediated communication where agents are primary users
- •Designing UX for humans + agents + human-agent collaboration
- •Prompting founders to ask whether their product survives in an agent-first world
- 24:49 – 28:15
Lightning round: personal AI wins, near-term predictions, and parting founder advice
The panel closes with quick hits: personal-life unlocks (meal planning, travel, event planning), predictions (tool consolidation, more demand for technical roles, ambient/proactive intelligence), and debates (compute vs evals, specialist vs generalist agents). They finish with concise founder advice on shipping, hiring, and embracing discomfort.
- •Personal unlocks: diet/meal planning, travel planning, AI-run event planning
- •Predictions: AI tool consolidation; rising demand for technical roles; ambient intelligence
- •Debate: better evals vs more compute; generalists vs specialists framed as a false dichotomy
- •Founder advice: ship early, hire great people, seek discomfort
