What it takes for CS and Product teams to collaborate successfully

Published in November
29 November 2022
Published in November

29 November 2022

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:

  1. Why a strong product/CS relationship matters
  2. How to cultivate a strong Product/CS relationship
  3. How to align on visions and bring teams together

Key takeaways from the session

Customer Success <> Product: A key relationship

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 strategic advantage of having a strong Product-CS relationship

1. You can delivery transformative value to your customers

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.

2. You can accelerate operational efficiency

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.

3. You get to reduce customer churn and throwaway work

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:

  1. More effective solutions
  2. Better expectation-setting
  3. Reduced likelihood of preventable fires

Five principles to help cultivate a strong CS-Product relationship

  • Share the same customer narratives: E.g. get on the same page on how the customer should use the product.
  • Communicate using a shared language: Understand each other’s processes, decision-making frameworks, priorities, etc.
  • Eliminate barriers to collaboration: Don’t just collaborate when it’s convenient. Simplify your communication and collaboration—eliminate complicated processes and information silos, for instance.
  • Hold each other accountable: Leaders from both organizations need joint accountability. They need to commit to high deliverability, shared metrics, common goals, working sessions, open communication channels, etc.
  • Build empathy for each another: At the end of the day, communication is most effective when people have empathy for each other and trust each other. Use team building activities, informal coffee chats, etc. to build both.

More resources

  1. Implementation Stories from Preflight
  2. Customer onboarding resources from Rocketlane
  3. The Launch Station - a podcast for all things customer onboarding

FAQs

“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

Sebastian
Intercom

AI that executes your delivery work (Add to any plan)

Most popular

Standard

Ideal for expanding organizations needing more in-depth capabilities and integration for scaling.

$49

per team member/
month billed annually

*minimum of 5 team members

  • Full partner ecosystem support
  • Dynamic templates for any project
  • Milestone CSAT for customer pulse
  • Docs, forms, projects in one place
  • Docs, forms, projects in one place
  • Approval-governed time tracking
  • 200 Automations/user/month
  • Native HubSpot, Jira, Slack Integration

Most popular

Premium

Great for teams desiring tailored workflows with comprehensive reporting capabilities.

$69

per team member/month billed annually

*minimum of 5 team members

  • Real-time project profitability
  • AI resourcing and capacity planning
  • All revenue recognition models
  • Centralized rate cards and budgets
  • Portfolio reporting for leaders
  • Bill faster & improve cash flow
  • Native Salesforce integration

Most popular

Enterprise

Tailored for large enterprises requiring a fully customizable, comprehensive delivery engine.

Custom Pricing

*minimum of 5 team members

  • SAML SSO and role-based access
  • Unlimited, hands-off automations
  • Soft-allocate pipeline deals early
  • Skills matrix for smarter staffing
  • Staff global teams ahead of demand
  • Multi-currency global delivery
  • Snowflake data + custom reports

Full reviews for all 11 tools below

<TL;DR>

Best all-in-one Certinia alternative for B2B SaaS and technology PS teams with 25 to 150 consultants. Delivery, resource management, project financials, client portal, and agentic AI in one PSA, with no Salesforce dependency. From $49/user/mo (full PSA from $69) · 4.7/5 on G2 · 4 to 12 week go-live

<TL;DR>

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.

Trusted by top companies

One platform does what the entire table above tries
to split across tools.

One platform does what the entire table above tries
to split across tools.

One platform does what the entire table above tries
to split across tools.

Myth

Enterprise implementations fail because customers don’t follow the process or provide clean data on time. Most delays are purely “customer-side” issues.

Fact

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

Did you Know?

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.

Sebastian mathew

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.