💡

InsightHunt

Hunt the Insights

D

Dan Shipper

Episode #69

Co-founder and CEO

Every

🎯Product StrategyExecution👥Team & Culture

📝Full Transcript

18,929 words
Lenny Rachitsky (00:00:00): The business you're building, the team you're building, the way you're operating is the very bleeding edge of how companies are trying to operate in this AI era. Dan Shipper (00:00:07): We have a head of AI operations. She's just constantly building prompts and building workflows that I and everyone else on the team are just automating as much as possible. Lenny Rachitsky (00:00:16): What are some things that you believe about AI that most people don't? Dan Shipper (00:00:20): I hate the headlines that are like, "Entry-level jobs are taken away by AI." Whenever I see a kid with ChatGPT, I'm like, "Holy shit, they're going to go so much faster than any other person that I've worked with." We have this guy, he made a year's worth of progress in two months because every time I sat down with him and told him, "Okay, here's how you tell a story, here's how you think about a headline," he recorded all of it, put it into a prompt, and he never made the same mistake twice. Lenny Rachitsky (00:00:40): There's this sense we're getting to a place where you don't have to write any code, you have a product team not writing code at all. Dan Shipper (00:00:46): No one is manually coding anymore. Organizations like ours, people who are playing at the edge, we're doing things that, in three years, everybody else is going to be doing. Lenny Rachitsky (00:00:55): Today, my guest is Dan Shipper. Dan is the co-founder and CEO of Every, which is a company that is at the very bleeding edge of what is possible with AI. Their team of just 15 employees has built and shipped four different products. They publish a daily newsletter, and they have a consulting arm that helps companies adopt the latest AI best practices. On their product team, their engineers don't handwrite a single line of code and instead use an arsenal of agents who help them craft requirements and build their products. (00:01:22): Their editorial arm uses AI to publish better work faster, ...

💡 Key Takeaways

  • 1Hire a 'Head of AI Operations' whose sole KPI is to audit internal workflows and build prompts/automations to remove repetitive tasks for the team.
  • 2Shift engineering metrics from 'lines of code' to 'agent management'; at Every, engineers no longer write code manually but instead manage suites of agents (like Claude Code) via detailed PRDs.
  • 3Utilize 'Local Agent' workflows (e.g., Claude Code, Gemini CLI) to process sensitive local files (meeting notes, codebases) for deep analysis without uploading to a web chat interface.
  • 4Adopt the 'Service Unbundling' strategy for product ideation: Identify expensive services (legal, chief of staff, copy editing) and build AI wrappers that democratize access to them.
  • 5Implement 'Compounding Engineering': Every unit of work should produce a prompt or automation that makes the next unit of work faster (e.g., a prompt that writes PRDs based on rough notes).
  • 6Foster AI adoption through 'Social Proof Loops': CEOs must use the tools visibly, hold weekly 'prompt share' meetings, and publish internal usage stats to gamify adoption.

📚Methodologies (3)

🎯 Product Strategy

A framework for ideation that focuses on taking expensive, exclusive human services (lawyers, therapists, chiefs of staff) and democratizing them via AI wrappers. Instead of inventing new behaviors, it automates existing high-value behaviors that were previously cost-prohibitive.

Core Principles

  • 1.Identify 'Luxury' Services: Look for services only rich people or large companies buy (e.g., on-call lawyers, professional copy editors, chiefs of staff).
  • 2.Internal Dogfooding: Build a 'wrapper' (simple interface over an LLM) to solve this problem for your own team first.
  • 3.The Vibe Check: Evaluate success based on internal 'vibes' and high-frequency usage by your own team, rather than external market research.
  • +1 more...

"There are a lot of expensive services that rich people and big companies are paid for right now... what cheap intelligence does is it makes those kinds of things affordable for small companies and individuals."

#service#unbundling#strategy
View Deep Dive →
Execution

A development workflow where engineers stop writing code manually and start acting as 'Agent Managers'. The focus shifts from syntax to architecture, requirements gathering, and code review.

Core Principles

  • 1.Prompt-Driven Architecture: Engineers spend their time writing detailed PRDs and instructions in English rather than writing functions in Python/JS.
  • 2.Multi-Agent Deployment: Use specific agents for specific tasks (e.g., one instance of Claude Code for coding, an 'Agent Charlie' for GitHub PR reviews).
  • 3.Compounding Prompts: Build a library of prompts that turn rough notes into technical specs, ensuring that the setup for the agent gets faster every time.
  • +1 more...

"No one is manually coding anymore. Organizations like ours, people who are playing at the edge, we're doing things that, in three years, everybody else is going to be doing."

#agentic#engineering#execution
View Deep Dive →
👥 Team & Culture

A change management framework to transition a company from 'AI-curious' to 'AI-native' by leveraging leadership behavior and social proof.

Core Principles

  • 1.The CEO Benchmark: The CEO must visibly use AI daily. If the leader delegates AI usage, the team will view it as 'low status' work.
  • 2.The 'Tobi Memo' Strategy: Send a company-wide memo declaring the company AI-first, explicitly stating 'I wrote this email with ChatGPT, and you should too.'
  • 3.Weekly Prompt Shares: Host a weekly meeting dedicated solely to team members showing off a prompt that saved them time.
  • +1 more...

"If the CEO is in it all the time... everybody else is going to start doing it. If the CEO is like, 'I don't know, this is for someone else,' no one else is going to be able to lead that charge."

#ai-first#cultural#rollout
View Deep Dive →