AMA: Confluent Senior Director of CS & Account Management, Conor Holmes on Customer Success / Sales Alignment

While the ideal is to involve Customer Success as early as possible, doing it universally burns out the CS team. To help frame decisions to map CS involvement strictly based on deal complexity, segment, and post-sale resource requirements, below is an example framework; Enterprise / High-Complexity Segment (Involved Pre-Sale: 3/4's way through the deal cycle) The Trigger: Deals requiring custom Professional Services, heavy integrations, or where the AE hands over full relationship ownership post ...Read More

This strategy is highly nuanced depending on the product complexity, customer segment, and total addressable market. However, to keep it simple, operationalise quickly, and avoid internal friction, I use a framework built on clear definitions and hard triggers.Split definitions - CS / Account Management owns Upsells (organic growth: adding more seats, upgrading tiers, or driving usage of the existing product). They are closest to the daily user and can expand accounts naturally. Sales owns Cross ...Read More

This should be captured structurally in a CRM with a hard requirement for any churn or downgrade to be categorised via standardised reason codes. Once captured, this data feeds into a monthly cross-functional review with the executive team (including Product, Engineering, Sales, and CS) to address root causes and mitigate product/service gaps. To influence qualification, these insights should be leveraged by sales to continually define the target customer selling to who could best who can benefi ...Read More

Honestly, I’ve rarely seen a traditional, rigid RACI matrix actually work. My preference is to map out responsibilities visually against the customer journey. The simpler, the better. A who owns what framework is better IMO Sales owns commercial alignment and relationship continuity. Solutions Engineering (SE) owns technical validation and scopes the technical blueprint pre-sale. CS / Implementation owns the actual post-sale execution against that blueprint and is responsible for the renewal Bec ...Read More

A clean handoff is one where the customer never has to re-explain their goals, pain points, or timeline to a new team. It should feel like a single, continuous thread moving them toward the value of their investment. The Required Artifacts: To ensure this happens efficiently without creating administrative burden, we require four things: AI-Generated Deal Summary: Automated transcripts and summaries of pre-sale discovery and demo calls so CS can review the raw context. The Account Plan: A centra ...Read More

The success of running joint renewal reviews comes down to having a aligned methodology but distinct inputs. Here is the framework I use: Aligned Forecast Categories: Ensure both teams use the exact same definitions for forecast stages (e.g., Commit, Best Case, Pipeline, At Risk) so we are speaking the same language. Dual Input Submissions: Both CS and Sales submit distinct forecasts in the CRM. Sales forecasts based on commercial view; CS forecasts based on product adoption, health scores, and ...Read More