Skip to content

How a Frontier Team Can Help Your Company Keep Up With AI

The Every Podcast

43m
Transcript

Original podcast

Where to listen

Summary

Written by a model from the transcript; not yet reviewed.

This episode explores how a dedicated frontier team can help a company stay ahead of rapid advancements in artificial intelligence without overwhelming the rest of the organization. The host and guests discuss the structural necessity of separating experimental work from daily execution, highlighting the collaboration between fast-moving experimenters and system-oriented architects. Through concrete examples—such as automated video editing, custom personal benchmarks, usage dashboards, and bespoke writing tools—the participants demonstrate how modern AI capabilities allow non-engineers to build functional internal software and dramatically accelerate workflows.

Listeners get a practical look at how a media and software company structures its internal innovation engine, manages token spend, and translates experimental prototypes into production-ready products. The discussion provides specific insights into agentic workflows, prompt engineering, and the challenge of managing cognitive load in an AI-saturated work environment. It is valuable for leaders and operators trying to balance the pressure to adopt new AI tools with the need for stable, long-term business execution.

  • Establish a dedicated frontier team to separate experimental AI exploration from day-to-day product execution. 0:37
  • Combine fast-moving experimentalists with systematic architects to turn messy prototypes into maintainable internal tools. 2:53
  • Give AI models full access to your personal work context, including call notes, emails, and Slack messages, to improve output relevance. 11:24
  • Build custom internal applications and specialized editors to protect personal attention and manage conditions like ADHD. 22:44

Chapters

  1. 0:00
    Why Every Company Needs a Frontier Team

    Dan explains the dilemma of staying productive while keeping up with AI and introduces the concept of a frontier team to separate experimentation from execution.

  2. 0:53
    Introducing the Frontier Team at Every

    Dan welcomes Natalia and discusses the formation and transformative impact of the frontier team at Every.

  3. 2:53
    Pirates and Architects: Team Archetypes

    Dan describes the two roles—pirates who experiment rapidly and architects who structure and refine experiments—for effective frontier work.

  4. 4:10
    Impact of the Frontier Team on Company Confidence

    Dan highlights how the frontier team boosts confidence, allows rapid innovation, and reduces distraction for the rest of the organization.

  5. 4:57
    Mike Taylor on Evaluations and Model Limits

    Mike explains his role as head of evals, how he pushes models to their limits, and shares insights on video editing and content creation.

  6. 12:53
    Ariel as the Frontier Wrangler

    Ariel discusses his role in organizing experiments, building systems, and turning insights into content and products for the organization.

  7. 30:57
    Yannick on Architectural Clean‑ups

    Yannick explains his role in refining prototype projects into maintainable, production‑ready solutions, emphasizing the need for reliable architecture.

  8. 35:51
    Kiran’s Experimentation Loop

    Kiran shares his weekly experiment cadence, how he tests new model capabilities, and his focus on sharing learnings to inspire broader adoption.

Highlights

  • 0:37

    The Need for a Frontier Teaminsight

    The speaker explains how companies struggle between ignoring AI and chasing endless shiny objects, making a dedicated frontier team necessary to separate experimentation from core execution.

  • 2:53

    Pirates and Architects Working Togetherinsight

    Two distinct archetypes drive the frontier team: pirates who move fast and break things, and architects who compress messy code into reliable, maintainable systems.

  • 11:24

    Feeding All Context to AIstrategy

    Mike Taylor explains why users should stop hesitating and grant AI models access to all work context across email, Slack, and calendars for better results.

  • 15:13

    Tracking Token Spend and Usagedata

    Ariel demonstrates a usage dashboard that tracks total token counts, dollar spend, and categorizes token consumption by person and task.

  • 19:26

    Building a Custom Tabless Browserstory

    Jack Chang explains how he built his own tabless browser with an integrated agent pane to eliminate context switching and improve his editing workflow.

  • 26:43

    Adding Audience Context to Writingstrategy

    Katie Parrot discusses adding an audience metadata document to her writing plugin to evaluate drafts for audience fit and tone.

  • 32:57

    Orchestrating Multi-Agent Projectsstrategy

    Yannick demonstrates an orchestrator tool that breaks down projects into plans, allowing users to manage AI agents at the goal level.

Quotes

  • “The reason why you need a frontier team is it separates things out.”
    Unnamed speaker · 0:37
  • “I think there's two archetypes that work really well together, pirates and architects.”
    Unnamed speaker · 2:53
  • “I think it lets us, it lets us move incredibly quickly on what's new without distracting the whole team.”
    Unnamed speaker · 4:09
  • “I think one thing that people are not doing enough of is just giving all their context over to AI.”
    Unnamed speaker · 10:45
  • “If you like this video, you should check out every dot T O.”
    Unnamed speaker · 42:23

About this episode

Check out Gemini Audio: https://goo.gle/Every-Gemini-Audio Every time a new AI model drops, companies face the same dilemma: Figure out what’s new and how to use it, or focus on getting work done. Every solves this dilemma with a frontier team: a small group that tests new models and turns useful experiments into tools and workflows for the rest of the company. On this week’s episode of The Every Podcast, Natalia Quintero sits down with all seven members of Every’s frontier team to ask what they’re building—from a tabless browser that helps protect your attention to a personal agent orchestrator called Minga—and what they want to try next. Subscribe to Every (free for 14 days): https://every.to/youtube-every-offer?utm_source=podcast&utm_medium=audio&utm_campaign=companyagentepisode Links to resources mentioned in the episode: Follow Every: https://x.com/every Compound Writing plugin: https://every.to/guides/compound-writing Every’s vibe checks: https://every.to/vibe-check Follow Dan Shipper: https://x.com/danshipper Follow Natalia Quintero: https://x.com/NataliaZarina Follow Mike Taylor: https://x.com/hammer_mt Follow Jack Cheng: https://x.com/jackcheng Follow Arielle Shipper: https://x.com/ArielleShipper Follow Katie Parrott: https://x.com/kplikethebird Follow Jannik Jung: https://x.com/JannikJung 0:00 Introduction: Why every company needs a frontier team 2:42 Why the best frontier teams have pirates and architects 4:57 How Head of Evals Mike Taylor builds personal benchmarks 6:46 How Opus edited an explainer video using Slack messages and meeting notes 10:20 Working with AI means protecting other people’s attention 12:26 Why a frontier team needs a “wrangler” like Arielle Shipper 18:58 Why senior editor Jack Cheng built a tabless browser 24:37 How resident writer Katie Parrott teaches her AI writing plugin who the reader is 30:51 Inside engineer Jannik Jung’s personal AI orchestrator 35:41 Compound engineer Kieran Klaassen uses AI to build power tools

Transcript

0:00
43:01

7,520 words · 8 speakers

Topics

  • frontier team
  • Every
  • AI
  • Gemini
  • Opus
  • Compound Writing
  • Proof
  • Google
  • vibe checks
  • Claude

Page updated · transcript and summary are machine-generated