
•
•

Summarize blog with








In this episode of Implementation Stories, Jennifer Chiang, Head of Customer Success at Seso, and author of The Startup’s Guide to Customer Success, shares with us what it takes for CS and product teams to work together successfully.
Jennifer discussed the following topics:
Think of some of the most successful product companies: Salesforce, Microsoft, Hubspot, Twilio, Atlassian, etc. They have something in common: their Product Management and Customer Success teams have a really strong relationship for a variety of initiatives, both strategic and tactical. They understand that if their product isn’t adopted successfully, the product isn’t valuable and therefore, the company will not meet its business goals.
The Product team can work with the CS team to gain complete visibility into what customers want. This will help ensure your products are actually addressing the key pain points of the customer, and learn how to communicate your value proposition to your ICP. The CS team can increase loyalty, decrease churn, etc, if they have full visibility into the product roadmap, which they can get from the Product team.
Both Product and CS teams have infinite workload, and its very easy for folks on both sides to burn out. When CSMs are overwhelmed or burnt out, they’re unable to create deep relationships with customers. Likewise, overwhelmed or burnt out PMs are unable to deliver on product roadmaps and visions. Ultimately, the business suffers.
A tight and empathetic partnership would mean understanding that both CS and Product are the same team, which in turn can lead increased transparency, improved shared context, lesser firefighting and internal friction. Ultimately, this improves the operational efficiency for both teams.
A strong relationship between CS and Product leads allows for quicker and more effective brainstorming and strategy planning for customers. Shared context (you don’t have to start from scratch each time) would mean the following for customer relationships:
“Speeds up CSV importing and saves me from having to get customers to use a template file or create mapped data exports. Quick to integrate and flexible outside the happy path. We found defining workbooks and templates confusing; at a prior job it was configured through code, which I preferred.”
Source: G2 review


AI that executes your delivery work (Add to any plan)
Most popular
Ideal for expanding organizations needing more in-depth capabilities and integration for scaling.
Most popular
Great for teams desiring tailored workflows with comprehensive reporting capabilities.
Most popular
Tailored for large enterprises requiring a fully customizable, comprehensive delivery engine.

A Forward Deployed Engineer (FDE) embeds in the customer environment to implement, customize, and operationalize complex products. They unblock integrations, fix data issues, adapt workflows, and bridge engineering gaps — accelerating onboarding, adoption, and customer value far beyond traditional post-sales roles.





70–85% utilization. 94% G2 rating.
One platform does what the entire table above tries
to split across tools.
70–85% utilization. 94% G2 rating.
One platform does what the entire table above tries
to split across tools.

70–85% utilization. 94% G2 rating.
One platform does what the entire table above tries
to split across tools.
Enterprise implementations fail because customers don’t follow the process or provide clean data on time. Most delays are purely “customer-side” issues.
Implementations fail because complex environments need real-time technical problem-solving. FDEs unblock workflows, integrations, and unknown constraints that traditional onboarding teams can’t resolve on their own.
Get a better all-in-one PSA
Get a better all-in-one PSA
Companies that embed engineers directly with customers see significantly higher enterprise retention compared to traditional post-sales models — because embedded engineers uncover “unknowns” that never surface in ticket queues.

VP Sales, Intercom

A Forward Deployed Engineer (FDE) embeds in the customer environment to implement, customize, and operationalize complex products. They unblock integrations, fix data issues, adapt workflows, and bridge engineering gaps — accelerating onboarding, adoption, and customer value far beyond traditional post-sales roles.






.webp)