The FDE Playbook for AI Startups with Bob McGrew
Y Combinator Startup PodcastFull Title
The FDE Playbook for AI Startups with Bob McGrew
Summary
This episode explores the Forward-Deployed Engineer (FDE) model, a strategy pioneered by Palantir for customer-centric product development and adoption, and its relevance to the current AI startup landscape.
The discussion highlights how the FDE model addresses the unique challenges of deploying novel AI technologies by embedding engineers with customers to drive product discovery and build tailored solutions, contrasting it with traditional SaaS scaling.
Key Points
- The FDE model involves technical engineers embedding with customers to bridge the gap between product capabilities and specific customer needs, often solving novel problems.
- Palantir's FDE strategy originated from the challenge of building software for the intelligence community, where direct user feedback was scarce and conventional sales approaches were ineffective.
- The FDE model prioritizes deep customer engagement and problem-solving over generalized scaling, allowing for the creation of platform-like solutions adaptable to diverse customer environments.
- The distinction between sales-led and FDE-led product discovery is crucial, with FDEs gaining insights from within the customer's operations, leading to more impactful solutions.
- Palantir's FDE team was structured with "Echo" (analyst/account management) and "Delta" (software engineering) roles, requiring unique profiles focused on domain expertise, critical thinking, and rapid prototyping.
- The FDE model can initially result in losses but becomes profitable as the product becomes better suited to customer needs and expands to address more significant problems, demonstrating a scalable approach to complex enterprise solutions.
- The inherent heterogeneity of markets, like government and defense, necessitates the FDE approach, where solutions are tailored to specific segments rather than a single, standardized product.
- The rise of AI agents is driving the adoption of the FDE model because there is no incumbent product, requiring extensive product discovery from within the customer's context.
- The FDE approach is effectively "doing things that don't scale at scale," leveraging deep customer engagement to drive adoption of novel technologies.
- Misconceptions about the FDE model often equate it to consulting; however, successful FDE implementation focuses on building repeatable value and driving product generalization.
- Pricing for FDEs shifts from usage-based SaaS models to outcome-based contracts, reflecting the value delivered to the customer and encouraging larger, more flexible agreements.
- Building a successful FDE strategy requires significant organizational discipline, a focus on delivering valuable outcomes, and a commitment to continuous learning and adaptation.
- The FDE model is well-suited for AI startups because the AI landscape is rapidly evolving with no established products, demanding intensive, customer-specific product discovery.
- Demo-driven development is critical for the FDE model, forcing a customer-centric perspective and driving the creation of integrated, valuable solutions that solve real pain points.
- The FDE model fosters a "learning company" culture, essential for adapting to rapidly evolving AI capabilities and ensuring product adoption.
Conclusion
The Forward-Deployed Engineer (FDE) model is crucial for the current AI landscape due to the lack of incumbent products and the need for deep customer engagement to drive adoption.
Building a successful FDE strategy requires significant organizational discipline, a focus on outcome-based pricing, and continuous learning, akin to operating as a startup.
The FDE approach embodies Y Combinator's ethos of "doing things that don't scale" but at a scale that is now feasible with large enterprise contracts, filling the gap between AI capabilities and their practical application.
Discussion Topics
- How can AI startups effectively balance the FDE model's need for customization with the long-term goal of scalable product generalization?
- What are the key indicators for a startup to transition from early-stage "doing things that don't scale" to a more systematic FDE approach?
- In what ways can the FDE model be adapted for different industries beyond enterprise software and government, particularly in emerging AI applications?
Key Terms
- Forward-Deployed Engineer (FDE)
- A technical engineer who works directly at a customer's site to understand their needs and customize or develop solutions.
- SaaS
- Software as a Service, a software distribution model where a third-party provider hosts applications and makes them available to customers over the internet.
- Ontology
- In the context of Palantir, a system for organizing and representing information, allowing for complex relationships between data objects to be understood and analyzed.
- Product Market Fit
- The degree to which a product satisfies strong market demand.
- Heterogeneity
- The quality or state of being diverse in character or content.
Timeline
Explanation of what a Forward Deployed Engineer (FDE) is and their role in bridging product gaps for customers.
The origin story of Palantir's FDE model, stemming from their initial work with the intelligence community.
The contrast between a scaling-focused approach and Palantir's FDE strategy, which embraces customer proximity.
How Palantir flipped the traditional view of services, making FDEs a valuable part of product discovery.
The decision to use engineers for product discovery instead of traditional sales roles, especially in government sectors.
The difference between sales-led and FDE-led product discovery.
The structural breakdown of Palantir's FDE team into "Echo" and "Delta" roles.
The ideal profiles for Echo team members (analysts) and Delta team members (engineers).
The comparison of FDE roles to startup founders and how this training is beneficial.
Addressing the misconception that the FDE model is just consulting.
The financial model of FDE engagements, where initial deployments may lose money but lead to long-term profitability.
The crucial role of the product team in supporting and generalizing the work of FDEs.
An example of how the Palantir ontology was developed through FDE insights.
The concept of generalizing objects and properties for the ontology versus specific customer needs.
The potential for cultural tension between FDEs focused on customer solutions and product teams focused on generalization.
The difference between a "gravel road" (FDE solution) and a "paved road" (generalized product).
The organizational discipline required to prevent the FDE model from becoming pure consulting.
Reasons for the current surge in AI companies adopting the FDE model.
Why Palantir needed the FDE model due to market heterogeneity.
How the FDE model is being applied to AI agents due to the lack of incumbent products and the need for extensive product discovery.
The connection between the FDE model and YC's "do things that don't scale" advice.
Common misconceptions and ways companies get the FDE model wrong.
The difficulty in choosing and pricing FDE engagements, which focus on outcomes, not just software installation.
Examples of AI startups (Castle, Happy Robot) successfully using FDEs for large enterprise clients.
The challenges of deploying on-premise solutions and navigating internal IT departments.
How Palantir secured executive buy-in for their FDE model and its relation to leadership's top priorities.
The FDE model as a discipline and skill that requires strong leadership and learning.
The similarity between Palantir's FDE model and classic YC advice on manual, high-touch customer engagement.
The key difference between product market fit strategy (driving down cost) and FDE strategy (driving up contract size).
Measuring contract size and the value of delivered outcomes.
The role of the product team in providing leverage to FDEs and facilitating easier customer deployments.
The FDEs' potential to find new uses for abstracted product features.
The painful but necessary process of FDEs adopting and using new product features.
The judgment calls involved in product vision and generalization within the FDE model.
How demo-driven development is crucial for FDEs in creating desire and solving customer pain points.
The FDE model as a means of building a learning company.
Bob McGrew's new role in the U.S. Army Reserve and applying Palantir's lessons.
The best opportunities for startup founders, relating back to AI agents and the FDE strategy.
The gap between rapid AI capability improvements and slow adoption rates.
An analogy of OpenAI as the "home product team" and startups as FDEs for AI adoption.
Episode Details
- Podcast
- Y Combinator Startup Podcast
- Episode
- The FDE Playbook for AI Startups with Bob McGrew
- Official Link
- https://www.ycombinator.com/
- Published
- September 8, 2025