Key Takeaways

  • Palantir CTO Shyam Sankar created the forward deployed engineering model, while Bob McGrew spent a decade turning field deployments into standardized software products.
  • Enterprise sales stall when founders sell only to executives; products succeed when engineers partner with a frontline user willing to test buggy code.
  • McGrew refused to build roadmap features without a committed client waiting to run them immediately.
  • Custom field code must flow back into the core platform, or headcount scales linearly with client contracts.
  • Founders can adopt this cycle through McGrew's Forward Deployed Engineering (FDE) Product Development Method.

Most enterprise startups face a brutal choice: build an unvetted roadmap that nobody uses, or turn into a custom IT consultancy. Bob McGrew encountered this problem during his decade directing product and engineering at Palantir. The company solved it by creating forward deployed engineering.

McGrew credits Palantir CTO Shyam Sankar with the core design: “The outcome of that process was the forward deployed engineering model, which I think mostly Shyam Sankar, who's the CTO at Palantir, deserves the most credit for. But my job was to figure out how to build products for it.” (play from 45:57)

The model treats field engineers as product researchers instead of billable staff. Enterprise software founders usually pitch senior executives. McGrew found that executive buy-in is incomplete: “Classically, that visionary is a sponsor, and you do need that sponsor, but what the book doesn't talk about is you actually also need a user, someone who's actually willing to use your software to go accomplish an outcome.” (play from 48:48)

With a user committed, roadmap development changes. “I would not develop a feature unless I had a customer that was ready to use that feature,” (play from 46:17) McGrew explains. “And so when I think about the product roadmap, a lot of the beginning point for the product roadmap is not, 'Okay, I'm gonna go build this feature,' it's, 'How do I find a customer that needs this feature so I can go build it?'” (play from 46:23)

The danger is getting trapped writing bespoke patches. McGrew insists startups must turn field work into platform features: “The FDE strategy is a product strategy that teaches you how to build products. The FDEs are filling the gap between the product and the user, and if they have to keep filling the gap, you get no leverage. Instead, you have to productize what they're seeing and bake that back into what you're doing.” (play from 50:56)

McGrew's Forward Deployed Engineering (FDE) Product Development Method

  • Step 1: Secure Both an Executive Sponsor and a Dedicated Power User: Identify not just a high-level executive visionary sponsor who buys into the contract, but an actual frontline power user who has a critical workflow pain point and is willing to suffer through buggy early iterations alongside you.
  • Step 2: Embed Engineers Directly into Customer Workflows: Place product engineers directly on-site to partner on achieving concrete operational outcomes. Never build a roadmap feature in isolation; anchor every feature build to a specific customer waiting to run it immediately.
  • Step 3: Productize Learnings to Gain Leverage: Treat FDEs as temporary bridges filling the gap between the nascent software and the user. Systematically extract their custom scripts, workflows, and edge-case fixes and engineer them back into the core platform so that manual engineering hours do not scale linearly with customer count.
  • Step 4: Snowball Demonstrated Outcomes to Earn Broader Scope: After delivering a clear operational victory on a small-scale component, leverage that trust to expand problem-by-problem and team-by-team across adjacent product divisions and larger revenue opportunities.

When This Works (and When It Doesn't)

This method works when building enterprise software for complex, high-value domains with sensitive IP or unique operating requirements. It fails if the company treats FDEs merely as billable professional service consultants without actively feeding user feedback back into the core codebase.

The strategy also breaks when contract values are too small. Placing engineers on-site eats capital. Without six-figure or seven-figure annual contracts, engineering travel and salaries will destroy your margins. It also fails if internal politics divide field engineers from core engineers. If platform teams view field staff as second-tier support, bespoke scripts never merge into the main codebase, leaving you with an expensive services shop.

What to Do With This

If you are selling industrial software this week, stop writing speculative Jira tickets. Pick one customer account and secure both the vice president funding the pilot and the plant technician entering the data.

Send an engineer to their facility for three days. Find where their current workflow stalls, and script a fix directly on-site. When the sprint ends, review those scripts with your platform team. Refuse to close the ticket until the underlying data logic merges into your main software release. As McGrew notes, “once you achieve that outcome, you can then look around at all the other outcomes, and you've earned the right to work on something bigger.” (play from 49:45)