Get your free personalized podcast brief

We scan new podcasts and send you the top 5 insights daily.

Anthropic validates products internally before any external release. A feature is only considered ready for public launch once it achieves a critical mass of daily active users within the company. This rigorous dogfooding process ensures the tool provides real workflow value, moving beyond simple feedback to proven adoption.

Related Insights

Vercel's validation framework starts with "Customer Zero"—themselves, relying on internal taste and needs. They then move to "Customer One," a select group of close design partners for external pressure testing before a wider release. This balances internal conviction with external feedback.

Salesforce operates under a 'Customer Zero' philosophy, requiring its own global operations to run on new software before public release. This internal 'dogfooding' forces them to solve real-world enterprise challenges, ensuring their AI and data products are robust, scalable, and effective before reaching customers.

Instead of guessing when a new feature is ready for public launch, Ladder uses a beta group of 2,000 members. They repeatedly surveyed these users with the question, "How likely are you to switch from your existing app?" They only launched when the metric climbed from an initial 20% to 85%.

Anthropic's safety model has three layers: internal alignment, lab evaluations, and real-world observation. Releasing products like Co-work as “research previews” is a deliberate strategy to study agent behavior in unpredictable environments, a crucial step lab settings cannot replicate.

To ship features weekly, Anthropic PMs use a repeatable framework: 1) Set clear user goals to reduce ambiguity, 2) Brand launches as "research previews" to lower shipping commitment, and 3) Create tight, low-friction processes between engineering, marketing, and docs.

For core product changes, Granola eschews quantitative A/B testing in favor of qualitative gut feel from intensive internal use. By building prototypes and having the entire team use them in their own chaotic workdays, decisions are made based on collective intuition about what *feels* better.

Don't just assume a new AI workflow is better. Treat internal process changes with the same rigor as product features. Apply a hypothesis-driven framework to how your team operates, experimenting with new AI tools and methods, and validating whether they actually improve outcomes before committing to them.

Anthropic relies heavily on internal users for early feedback, finding them more honest and focused on crucial interaction design details. This "bleeding edge" internal signal on UI polish is often more valuable than external feedback on broader user flows.

The Codex team's core mandate was to create a tool they loved and used daily for their own development. This intense dogfooding—including building the app on itself—served as the ultimate validation and quality bar before they considered shipping it externally.

Anthropic has flipped the traditional development process. Instead of debating quality at the mock or discussion stage, they push teams to build a working version first. Quality decisions are then made based on hands-on usage of the live product, which provides much richer and more accurate feedback.