Get your free personalized podcast brief

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

Rob Ferguson says features are far too easy to copy, so management must restructure teams to engage customers directly. He warns against sitting in the design pantheon and says the durable thing is the relationship on the other side, even with seasonal businesses. Forward-deployed teams are the management response.

Related Insights

Embed engineers directly with customers to hear feedback and ship solutions, often on the same day. This radical structure eliminates layers of communication (Product Managers, Customer Success) and scales the 'founder energy' of talking to users and immediately building what they need.

Instead of a traditional product roadmap, give engineers ownership of a broad "problem space." This high-agency model pushes them to get "forward deployed" with customers, uncover real needs, and build solutions directly. This ensures product development is tied to actual pain points and fosters a strong sense of ownership.

To build a cohesive, fast-adapting organization, infrastructure teams must be as connected to the end customer as product teams are. This isn't optional. When the entire stack understands the 'why,' it builds purpose and dramatically reduces the delay in responding to market shifts.

Most startups focus on product or technology innovation, but Gamma's CEO argues that innovating on organizational design is an equally powerful lever. This means rethinking hiring, management, and team composition to create a competitive advantage.

Unlike companies viewing field teams as a cost center, Peregrine considers its 'Forward Deployed' strategists its core R&D engine. 'Hacky,' unscalable solutions they build on-site to solve immediate customer problems provide the best signal for what the core platform needs, creating a rapid, customer-driven prototyping loop.

Rippling structures teams into business units led by GMs who oversee product, sales, and implementation. This is driven by the belief that a unified team focused on a specific customer problem (e.g., IT) delivers a superior end-to-end experience compared to a traditional matrixed organization.

The debate between being product-led vs. sales-led is a false dichotomy that creates friction. Instead, frame all functions as fundamentally 'customer-driven.' This reframing encourages product teams to view sales requests not as distractions, but as valuable, direct insights into customer needs.

Serval hires 'future founder' types as Forward Deployed Engineers (FDEs). Their primary function isn't just implementation but to replicate the early-stage founder motion: directly interacting with customers, identifying pain points, and channeling that feedback immediately into product improvements, thus scaling the founder-led feedback loop.

Siphoning off cutting-edge work to a separate 'labs' group demotivates core teams and disconnects innovation from those who own the customer. Instead, foster 'innovating teams' by making innovation the responsibility of the core product teams themselves.

To maximize their value, forward deployed engineers (FDEs) should not be a separate services team. Integrating them directly into the product organization ensures faster, higher-fidelity customer feedback and context capture, which directly shapes the core product.