Sep 8, 2025 · 50m · y-combinator
The FDE Playbook for AI Startups with Bob McGrew · Y Combinator
0:00 / 0:00
▶ Watch on YouTube →
gold bands on the timeline = statements, start to end. Hover to read, click to jump. CC turns on captions
Former OpenAI CRO and Palantir executive Bob McGrew joins the Lightcone Podcast to unpack the Forward Deployed Engineer (FDE) strategy and explain why AI agent startups are reviving this hands-on model to bridge the gap between frontier AI models and enterprise adoption.
How this conversation actually went
Every chapter scored 0–10 on four independent dynamics. Hover any point for the reasoning behind the score. The partners hold 20.5% of the talking time here. How this is scored →
The partners as informed peer 4.9 Guest teaching 5.5 Guest disagreement 0.7 The partners pushing back 0.5
speaking balance: gold is the partners, purple is the guest (3 minute bins)
Sharpest disagreement ▶ 14:35 Bob rejects glib dismissal of the consulting critique
Rather than reassuring Jared that calling FDE consulting is just a misconception, Bob firmly counters that it is a very real existential failure mode for startups.
Hardest push from the partners ▶ 20:26 Harj challenges the structural friction of FDE cultureHarj presses Bob on the inevitable cultural tension between rogue field engineers optimizing for single clients and central engineers building maintainable abstractions.
Biggest teaching moment ▶ 36:17 Bob reframes PMF efficiency versus FDE contract growthBob directly educates Harj on the core metric difference between standard SaaS (reducing work per customer) and FDE (driving contract value up to justify ongoing custom work).
The partners hold their own ▶ 31:25 Diana provides concrete YC case studies on outcome pricingDiana demonstrates deep operating expertise by citing YC startups Castle and Happy Robot, explaining their specific metric-based ramp structures with enterprise clients.
the scores for every segment, with the reasoning behind each
| Chapter | Topic | The partners as informed peer | Guest teaching | Guest disagreement | The partners pushing back | Why |
|---|---|---|---|---|---|---|
| Defining Forward Deployed Engineering (FDE) | 4 | 3 | 0 | 0 | Jared sets the stage by citing data from the YC job board regarding the surge in FDE hiring among AI startups. Bob collaboratively provides the foundational definition of forward deployed engineering. | |
| The Origins of Palantir's FDE Strategy | 3 | 6 | 1 | 0 | Bob educates the hosts on Palantir's early history building software for intelligence agencies. He contrasts traditional Crossing the Chasm scaling with Palantir's platform and gravel road approach. | |
| FDE vs. Traditional Enterprise Sales | 5 | 5 | 1 | 1 | Harj and Jared probe why Palantir avoided hiring seasoned defense sales executives. Bob explains why outside-in enterprise sales failed and why engineers solving problems from the inside proved superior. | |
| Core FDE Team Structure: Echo and Delta Teams | 5 | 6 | 0 | 0 | Bob details the roles of Echo teams (domain rebels) and Delta teams (rapid prototypers willing to eat pain). Diana and Jared connect these archetypes to startup founding teams. | |
| Debunking the 'Consulting' Criticism | 6 | 6 | 2 | 2 | Jared raises the common criticism that FDE is merely glorified consulting. Bob counters the premise by arguing it is a legitimate failure risk before explaining how Palantir built generalized ontologies to generate software margins. | |
| Cultural Dynamics and Internal Tension | 5 | 6 | 1 | 1 | Harj questions the internal cultural friction between customer-focused field engineers and central product teams. Bob outlines how misaligned incentives are reconciled through joint product reviews. | |
| Why AI Agent Startups are Embracing FDE | 5 | 7 | 1 | 0 | Diana and Harj ask why AI startups are adopting FDE. Bob delivers an in-depth explanation showing that AI agents, like Palantir's early products, lack incumbent categories and require deep internal discovery. | |
| Y Combinator Application Announcement | 6 | 4 | 0 | 0 | After the mid-roll announcement, Bob explains outcome-based pricing. Diana demonstrates strong domain familiarity by citing YC portfolio companies Castle and Happy Robot using similar pricing models. | |
| Overcoming Enterprise Risk and IT Barriers | 5 | 5 | 0 | 0 | Bob explains the asymmetry of enterprise risk and strategies for navigating resistant IT gatekeepers by attaching to top executive priorities. | |
| Evaluating FDE Performance and Product Leverage | 6 | 7 | 2 | 1 | Harj asks how founders know when to abstract custom work into core product. Bob corrects the standard SaaS mindset by showing that FDE success means scaling contract value while maintaining high-touch customization. | |
| Demo-Driven Development and Building a Learning Culture | 5 | 6 | 1 | 1 | Diana asks about the stigma surrounding demo-driven development. Bob defends demo-driven roadmaps as essential for generating customer desire and maintaining a learning culture. | |
| Applying FDE Principles to the U.S. Army Reserve | 3 | 5 | 0 | 0 | Bob shares his transition to serving as a Lieutenant Colonel in the U.S. Army Reserve, explaining how FDE principles apply to institutional military modernization. | |
| AI Capabilities vs. Adoption: Advice for Founders | 6 | 5 | 0 | 0 | Bob analyzes the widening gap between fast model capabilities and slow enterprise adoption. Jared synthesizes the episode with an analogy comparing OpenAI to a core product team and startups to deployed FDEs. |
Statements from this episode (31)
Friedman: FDE model is the dominant structure for AI agent startups
“It's actually become, I think the dominant way that the AI agent startups are organizing themselves.”
Friedman: Over 100 YC startups hiring forward deployed engineers
“I was looking earlier today, and if you look at the YC job board, there's over a hundred YC startups that are hiring for a job with the title for deployed engineer and up from basically zero, three years ago”
McGrew: Forward deployed engineers bridge the gap at customer sites
“A forward deployed engineer is someone typically technical and engineer who sits at the customer site and fills the gap between what the product does and what the customer needs.”
McGrew: Startups that can scale with identical customer setups should avoid FDEs
“If you're in a business where this is working for you, That's great. Don't do the FDE strategy. You have been given an amazing gift. If you have the opportunity to just scale, treat all the customers the same, go ahead and do that.”
McGrew: Palantir CTO Shyam Sankar invented the FDE strategy
“And I think this is where Shamsankar, who's very early employee, you know, now that I think the president and CTO of Palantir, he really invented the FDE strategy.”
McGrew: FDEs function as product discovery linking client needs to platforms
“What he realized we needed was for the FTEs to act as product discovery. So they would go to the site, they would take the product as it was, and they would fill the gap between what the product did and what the users needed. So, you know, the FDE goes and bui…”
McGrew: FDE-led product discovery beats traditional sales-led discovery
“Sales-led product discovery, you're talking to people from the outside. And again, this is important very early on, but it's not as effective as the FDE-led product discovery, where you're solving these problems from the inside.”
McGrew: Enterprise implementations fail unless addressing CEO's top five priorities
“If you're not solving one of the top five priorities for the CEO, it's probably not going to work. They probably won't have the energy to persist through the much more challenging route of getting effectively a new piece of the product built in a way that work…”
McGrew: Palantir's FDE model relied on Echo analysts and Delta engineers
“The two key roles are those of what we call the echo team and the Delta team. The echo team were Embedded analysts. So they would go to the customer site. They would speak to the users. They would try to figure out what demo or what use case really made sense …”
McGrew: Forward-deployed domain experts must be 'heretics' rejecting existing workflows
“So the echo team, you know, a classic Profile for someone to join your echo team would be someone from the domain you're working in. So, you know, possibly a former army officer or someone who worked deeply in healthcare. So they have deep domain knowledge, bu…”
McGrew: Forward deployed engineers must be rapid prototypers, not code craftsmen
“And then for your deltas you want someone who's really good at prototyping. So the wrong profile for a Delta would be someone who's a craftsman who really loves, you know, making sure the abstractions are exactly right. That, you know, they're building softwar…”
McGrew: Forward deployed engineering is ideal training for startup founders
“What you're doing you know, in each of these new environments at each of these customer sites, Is a little bit like being a startup founder, but you're a startup founder where you have access to some very powerful piece of product leverage that makes your job …”
McGrew: FDE deployments start at negative margins before becoming profitable
“From a business model perspective, one of the key things that you will see, that you should see, is that it may be the case that you're, when you go into, you do a new deployment at a customer, that you're actually losing money early on. As the longer you're a…”
McGrew: Bringing one-off FDE solutions directly into core products causes over-specialization
“There's a classic failure mode here where, you know, the FD implements something for one customer and you say, great, well, that's how you should do it. And you bring it directly into the product. And it turns out if you do that, you're building something that…”
McGrew: Palantir avoided hiring traditional PMs who lacked abstraction skills
“We didn't hire product managers for a long time. And when it did come time for me to hire product managers, I would interview people who were amazing product managers at, you know, other companies. And I would ask them to think at this level of abstraction. Th…”
McGrew: Building what customers ask for turns startups into consulting firms
“I think one of the other failures, by the way, that's even prior to that, and more, the easier failure to become a consulting firm, it's where you build the product in the field that the customers are asking for, rather than the one that's actually valuable to…”
McGrew: Startups should avoid FDE strategy unless no alternative works
“My first, second, and third pieces of advice to people who are thinking about trying an FDU strategy is like, don't,
Don't do this at home.
If you can avoid it, like it's probably bad for you.
Probably you're going to end up doing services.
And then only if yo…”
McGrew: In five years, AI agents won't be a single category
“Probably in five years, we'll look back, we'll be like, well, AI agents, there wasn't even a thing at all, right?
We were actually doing all these different things.”
McGrew: The FDE model is doing things that don't scale, at scale
“Well, that's the advice that you give to an early stage founder, and the FDE model effectively is doing things that don't scale at scale.”
McGrew: Most successful FDE startups have Palantir alumni leading the model
“I think the startups, the most successful startups doing the FTE model have people from Palantir running the FTE model.”
McGrew: The FDE model sells business outcomes, not software installation
“Fundamentally what you're selling with the FDE model is that you're not selling the installation of software. You're selling an outcome.”
McGrew: FDE model pushes startups toward larger, flexible customer contracts
“With the FD model, you're going to get pushed towards larger and larger contracts. Like we talked about, you're going to be growing contracts per customer over time. The contracts, because they're complex are going to be more flexible.”
McGrew: Early startups should take on execution risk with outcome-based pricing
“Early on, it makes sense for the startup to just take on all the risk and say, we're going to just believe in our own execution. And, you know, we're going to take on the risk and you pay us if it works or you pay us when, you know, we're actually able to expa…”
McGrew: FDE strategy succeeds by growing contract sizes rather than cutting customization
“In the product market fit strategy, you want to be doing less work for every customer, you want to be driving down costs, you want to keep the contract size the same. In the FTE strategy, you want to drive the contract size up. So you're doing more and more va…”
McGrew: Platform teams must treat internal FDEs as their key customers
“You want to focus on, on the user experience and you have to do that, but you also have to remember your other key customer is the FDE. Your product should be, you know, ultimately delivering a good thing to the user after FDE customization, but it should be d…”
McGrew: Demo-driven development forces teams to focus on customer pain points
“What the demo does is it changes the locus of what you're thinking about from thinking about what can I build to what is it that the customer wants? And am I solving that pain point for the customer?”
McGrew: Joining a fast-growing young company best prepares future founders
“My advice to people, if they're thinking about where to join a company is I tell them to join a young company, not necessarily a small company. Right. But a young company, because a young company is still figuring things out. It's still learning. It hasn't suc…”
McGrew: Palantir spawned many startups because its culture prioritizes continuous learning
“This is why Palantir has birthed so many other startups is because even as a very large company, it is still a company where everybody all the time is learning, focused on learning and, you know, always doing that same grinding motion that it is to be a new st…”
McGrew: Army tech transformation mirrors the FDE playbook
“In many ways it does feel a lot like running the FDA strategy, you know, on the army. We get to see, you know, what is the, what are the CEOs? What are the leadership's top five priorities? Can we make progress against those? But also in a world where you see …”