Protocol InstituteBusiness

Feed · thread · version 1 · updated 27 September 2026

Forward-Deployed Engineers (FDEs): Business Model, Role Evolution, and Market Implications

Session of 3 November 2025. Participants: rafa_0x, sachbenny, thewanderingeditor, timber1997, holajorge, mihir0k, stevebeans., oneiromancer2665.

The SIGPfB group discussed the emerging role of Forward-Deployed Engineers (FDEs) and its implications for software business models. The conversation revealed that FDEs primarily conduct information processing and context collection for customers rather than traditional implementation work, reversing the product-driven approach that has dominated Silicon Valley. Participants noted that this model represents a return to customer-driven business practices, exemplified by Palantir's Foundry platform, and functions as an extended, machine-augmented version of Waterfall development. The role requires significant in-person engagement and trust-building, making it difficult to scale with traditional staffing approaches.

Key points

  • FDE work is primarily information processing and context collection rather than interface customization, representing a shift from product-driven to customer-driven business models similar to Palantir's approach.
  • The FDE role resembles traditional service-based relationships (handymen, gardeners, consultants) and may evolve into a standalone consulting service comparable to Big Four consulting firms.
  • FDEs are uniquely positioned to 'break protocol' both internally and with clients, requiring significant in-person trust-building and contextual knowledge that creates high social barriers to scaling.
  • The rise of FDEs may indicate that Waterfall-style development could regain value in certain contexts, or represent an entirely new design space that challenges the Agile dominance of Silicon Valley.
  • AI models function as customer-driven collections of stable behavioral patterns rather than explicit problem-solving tools, enabling FDEs to bridge the gap between generalized AI capabilities and specific customer needs.

Source: Protocol Institute meeting archive · PI website commit f48390c. Summarized by c3po, the Protocol Institute's session pipeline, from the session's Discord thread.

Follow

Follow this blyg. Paste the feed into any RSS reader, or the blyg's address into Blygger Studio or another blyg client:

https://protocolsforbusiness.com/blyg/feed.xml

https://protocolsforbusiness.com/blyg/

To follow every member too, import blogroll.opml.

Join the conversation

This is a feed, not a forum. Two ways to answer a post:

  • Talk about it on Discord. The group meets in the Protocol Institute Discord, channel #protocols-for-business: join the Discord.
  • Respond from your own blyg. Quote this post in a thread, or publish a response to it (in Blygger Studio: follow this blyg, then use Respond or Quote on this post). Your blyg sends a Webmention; once it is verified, your post is listed under Responses here, usually within the hour.

    Blyg ID 0kpdm445aex86567menm3h4dbe

    Quote line ![[0kpdm445aex86567menm3h4dbe]]

    Respond to (stub_of) {"origin": "https://protocolsforbusiness.com/blyg/", "id": "0kpdm445aex86567menm3h4dbe", "version": 1}

    Webmention endpoint https://protocolsforbusiness.com/blyg/webmention

  • No blyg yet? Start one, or use any blog with an RSS feed, then ask to join the community so your posts appear in the Feed.

Machine-readable: item JSON · changelog 1 version