Enterprises agree to be design partners for three main reasons: they are innovators who want to see technology early, they want their specific needs built into the product, and they want to be part of building a significant new company. It's about influence and access, not just a free trial.

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.

To successfully automate complex workflows with AI, product teams must go beyond traditional discovery. A "forward-deployed PM" works on-site with customers, directly observing workflows and tweaking AI parameters like context windows and embeddings in real-time to achieve flawless automation.

Tock rejected traditional focus groups and instead embedded its software engineers directly into restaurants to work shifts as hosts. This forced immersion gave the engineering team firsthand experience with the end-user's pain points, leading to a far more intuitive and effective product than surveys could produce.

Harvey's Forward Deployed Engineering team isn't just for building custom solutions. It's a strategic product discovery tool. By embedding engineers with large clients who have undefined GenAI needs, Harvey identifies and builds the next set of platform features, effectively using customer problems to pave its future roadmap.

To break through industry blindness, Pella created a two-person research team with opposing perspectives: a long-tenured internal engineer and an industrial designer with experience from other top companies. This "oil and water" dynamic was key to their success.

To truly understand the industry, Qualia's team, including the first 25 hires, rotated through living in their first customer's basement. This unparalleled access provided deep domain knowledge and ensured they built what was actually needed, a strategy the founder credits for their success.

Stripe's Experimental Projects Team discovered that embedding its members directly within existing product and infrastructure teams leads to higher success rates. These "embedded projects" are more likely to reach escape velocity and be successfully adopted by the business, contrasting with the common model of an isolated R&D or innovation lab.

By embedding product teams directly within the research organization, Google creates a tight feedback loop. Instead of receiving models "over the wall," product and research teams co-develop them, aligning technical capabilities with customer needs from the start.