The AI paradox: More automation, more humans, more work | Dan Shipper

Dan Shipper, founder and CEO of Every, returns to Lenny’s podcast to lay out a concrete, near-term vision for how AI will change daily work — and which people and companies will benefit. Shipper frames his view from Every’s internal practice: the small company doubled in headcount over the past year (from around 15 to almost 30) while converting every role into an AI early adopter. Engineers, designers, writers, sales and support all use Codex/CloudCode/co-work as their daily work surface; that lived experience drives Shipper’s predictions more than abstract prognostication.

Shipper’s core forecast bifurcates into two intertwined platform shifts. First, companies will converge on one or a few enterprise super‑agents (often surfaced in Slack) rather than expect every employee to run a fragile personal agent. He explains that early attempts at personal agents break frequently and require ongoing human ‘gardening,’ so the practical model today is a centrally managed agent maintained by forward‑deployed engineers. Second, the actual locus of daily work will move into agent-first desktop environments (Codex, CloudCode, co-work) where the agent has an in‑app browser and full access to the user’s files and tools. In Shipper’s world, you don’t bake AI into each SaaS product; instead SaaS becomes agent‑accessible and is used from inside the agent — meaning users bring their tokens, preserving SaaS margins and scaling usage.

He backs these claims with operational detail and metrics. Every runs roughly six internal products on this stack; Shipper uses an email agent (Cora) to aggregate and draft replies and says it delivered inbox zero for ten straight days. To test limits, he created a senior engineer benchmark: older coding models scored ~30/100 on his rewrite-from-first-principles task while GPT‑5.5 scored ~62/100 using an Opus plan; a human senior engineer scores in the high 80s–low 90s. Shipper uses that to illustrate that models are rapidly improving and will hit senior‑engineer competence within a year or so, but that autonomy benchmarks can overstate independence because humans still provide supervision, framing, and higher‑level decisions.

From a product and career standpoint Shipper gives pragmatic advice: build products that are simultaneously human‑ and agent‑friendly (think in‑app browser, logs, rollbacks, approval inboxes), plan for agent traffic spikes and new UX patterns, and embrace agent workflows personally — "ride the models." He is unusually bullish on SaaS (contrarian to some market doom narratives), arguing agents will broaden SaaS adoption rather than replace it. On careers, Shipper singles out product managers and full‑stack designers as especially poised to gain leverage because they combine domain sense with lightweight technical fluency; he also highlights the emergent role of forward‑deployed engineers who deploy and maintain agents. Throughout the conversation he balances excitement about capability gains with a recurring refrain: "Every agent needs a human." Lenny and Shipper agree on many points but highlight a useful tension — Shipper has flipped his stance on personal agents to favor centralized ones for now — and they schedule a May 2027 revisit to score how the predictions played out.