Operators said

Topics

Retention & customer success

Where they agree

  1. Customer success should start from the customer's own definition of business outcomes and work back to the product, rather than from usage metrics. 9 independent voices · 2 shows3 new this month

    On [Un]Churned, Adnan Rahman says Paycor's value framework starts from outcomes like reducing time to hire, rolled out to 28 enterprise and 17 mid-market CSMs.

    12 sources
    Each customer has a shared Slack channel, and the CSM works toward the customer's own goals Listen

    Dan Lee said Nooks keeps a Slack channel with every customer and regularly checks how each is doing against its goals, such as sales productivity targets, and how Nooks can help. He said the CSM is effectively working for the customer, checking things like whether reps are performing well on calls, whether call scripts are good and whether the data is correct.

    “So we have a slack channel with every customer.”
    The value customers need proven is sometimes just reduced friction between teams, not hours saved. Listen

    Ariel Risman said CS at Notion acts as a thought leader in helping customers define what value looks like, and it depends on the team's biggest issue at the moment. For some it is cutting time spent on administrative tasks. For others it is reducing friction between teams that didn't work well together, so they can move with the velocity AI demands. He said to identify those issues, improve them, then iterate.

    “value could be just reducing friction between teams”
    Nerad draws on long-tenured CSMs from the acquired company to learn what drives its customers before judging retention risk. Listen

    After Advantive's most recent acquisition, Nerad spent a couple of months working with a senior CSM who had been at the acquired company for 15 years and knows its customers well. Together they worked through what drives those customers and what outcomes they intended when they bought the software. Nerad said the understanding of risk and retention follows from that customer understanding.

    “I have a senior CSM who's part of my team who she's been with this company 15 years. She knows the customers really well.”
    Anchoring value to the customer's company and board-level priorities protects you when your individual contact leaves or changes roles. Listen

    London says CSMs should try to stay tied to what the customer describes as company priorities, up to board level if possible. His reasoning is that this shows how your value aligns with the customer's business, not just with the person you happen to be speaking with, who may leave or change roles.

    “so you can see how your value aligns not just with the person with whom you're speaking, the customer contact who may leave or change, but their business.”
    Churn diagnoses, sometimes done as autopsies after the fact, show that the team didn't understand value the way the customer defines it. Listen

    Asked how a leader knows the team struggles with above-the-line conversations, London says the first thing that comes to mind is unhealthy customers or predicted churn. He attributes this to CS and sales teams being trained to push what they offer and to define value the way internal training told them to. In his view, that training leaves no room for customers to say how they define value on their own terms.

    “the diagnosis of that, which sometimes is an autopsy after the fact, is that we just simply didn't understand value the way the customer defines value.”
    Customers without a vision for how they will use a product become a vendor problem at renewal, so vendors should help build that vision. Listen

    At Microsoft, Brian says customers who had not planned how they would use the product did not consume what they had committed to, which affected later commitments. He recommends a function that helps customers set a vision of the value they will create, with the vendor's product built into that plan.

    “The fact that our customers didn't have a vision for how they're going to use our product and how it was going to benefit them was a problem.”
    LinkSquares starts value realization in pre-sales by identifying each customer's business outcomes, then checks onboarding and implementation against those outcomes. Listen

    Kellie said the company ties the customer's business outcomes through the whole relationship with checkpoints, starting in pre-sales. For existing customers, the team revisits outcomes because they shift over time and should not be assumed to be the same. She said these outcomes guide the initial scope and where the team starts with a customer. The team still does the typical things like customer satisfaction pulsing.

    “So we really try to start in the pre -sales and identifying what the customer's business outcomes are.”
    The first step to building a value framework is to ask the top reasons customers buy, then group the answers into three to five broad categories. Listen

    Adnan says the categories should be about challenges and outcomes, not features, and should start high level without boiling the ocean. He recommends interviewing best customers, top-performing CSMs, solutions engineers, account executives and the learning team, with categories emerging from the patterns in those conversations.

    “Yeah, the first step is You got to start by asking what are the top reasons customers buy our product, right?”
    The value framework makes CSMs start from the customer's desired business outcome and work back to the product, rather than starting from product usage. Listen

    At Paycor, Adnan says CSMs without a framework default to product usage, feature adoption and support cases, which he calls means rather than an end. The framework starts with outcomes such as reducing time to hire, cutting errors or improving employee retention in HCM, then works backwards to the product. He presents this as the core of the approach, which has been rolled out to 28 enterprise CSMs and expanded to 17 mid-market CSMs.

    “And so the value framework forces The CSM to start with the customer's desired business outcome whether that's reducing their time to hire”
    Companies should agree with customers each year on how value will be measured. Listen

    He says the company should make sure it knows how customers will measure value each year and that customers understand and agree on that measurement. He notes that the measure changes each year, so it has to be re-agreed at the start of each year to deliver incremental value.

    “Make sure you know how your customers are going to measure value each year and then growth is going to come organically from that.”
    Christine is rolling out SMART goals with customers to turn vague value into measurable outcomes. Listen

    SMART stands for specific, measurable, attainable, relevant and time-bound, and Christine introduced it to the team a few months before the episode. She says the framework lets the team define the goals that matter to a customer and then say whether they were met, which removes vagueness about whether the customer got value. She calls it a leading behavior and indicator and one of her two big priorities for 2026.

    “It takes the vagueness out of did I get value from Conga's products? Well, we defined that these particular goals were really important to you and we absolutely nailed it on these three or we didn't.”
    Christine's team is shifting customer conversations from product features to outcome-driven, business-level value conversations. Listen

    She says her team recently ran a training session on what value looks like to the customer and how to have conversations that let them measure outcomes. The aim is to connect Conga to the customer's root business goals rather than describing it as a product that does things. She describes this as a leading behavior that she expects to lead to better retention.

    “we focused on learning and talking about what does value look like to our customer and how do we have the right conversations with that customer so we can ultimately measure their outcomes.”
  2. Over-automating customer interactions creates disconnection and churn risk, because customers still want human contact. 5 independent voices · 2 shows

    On [Un]Churned, Jean de Villiers says Unit4's high-touch customers show about a 50-point higher NPS than self-serve customers, in an ERP market where NPS typically sits between zero and plus 15.

    5 sources
    Deltek must balance faster AI-driven support against customers' wish to talk to people. Listen

    She said Deltek could automate support with AI agents, but she doesn't think customers would love that. She asked where the balance is between going faster and the point at which customers simply want to talk to someone. She also mentioned that usage data can show why a customer's usage dropped.

    “I don't think our customers are going to love that right?”
    Jason Goldsmith warns that a touchless implementation can speed time to value but still create churn risk at renewal if the customer loses connection with the company. Listen

    He said Deltek's AI work is aimed at accelerating time to value and enhancing customer stickiness, and that the two have to be balanced. A touchless implementation that doesn't give customers what they want could create churn risk at their next renewal, because they feel disconnected from Deltek people. He said the company still needs to work out where AI should apply.

    “we could develop something that is a touchless implementation that doesn't actually give the customer what they want or provide them a great experience and then there are immediately a churn risk at their next renewal”
    High-touch customers show about a 50-point higher net promoter score than self-serve customers. Listen

    He said there is about a 50-point difference in net promotion between customers on the high-touch professional model and those on self-serve. He said ERP NPS typically sits between zero and plus 15, so a 50-point gap is very large. He linked the gap to customers being led, challenged and shown value realisation.

    “there is about a 50 -point difference in net promotion.”
    LinkSquares over-rotated toward digital-first engagement and is now bringing human engagement back, with the customer deciding how much contact they want. Listen

    She said some customers do not want to talk to the company, renew, and are happy as long as they get what they need, and that choice is up to them. She described the over-rotation as going in the wrong direction a little bit, mainly with the long-tail group of customers. She said the new platform is being used to re-create the engagement that had fallen by the wayside, and that it has taken a while but results are starting to show.

    “we over -rotated it in the wrong direction a little bit”
    Older customer demographics are more likely to prefer human or in-person interaction, while younger customers are more open to chatbots. Listen

    He presented customer demographics as the third factor limiting automation. He said this affects how much conversation can be contained, because some customers in airline and healthcare insurance segments simply prefer humans.

    “if you're dealing with the young demographics, they're probably more open to digital channel interaction, chatbot, talking to chatbot, versus much older demographics, they will potentially will really prefer in -person interactions.”
  3. At scale, churn risk has to be detected from data and AI signals rather than CSM calls. 5 independent voices · 2 shows

    On [Un]Churned, Eric Gilpin said G2 pings account owners in Slack daily when their customer is shopping a competitor, naming the competitor being viewed.

    5 sources
    Digital engagement data can show when a customer needs a human to step in, such as to remove a blocker or take a next step. Listen

    Kellie said the team cannot engage every customer all the time, so it uses data and digital engagement to identify when a CSM should step in. Once the blocker is removed or the next step is taken, the customer goes back to working on their own. This is how she describes the balance between digital and human engagement.

    “you can use the data, the digital engagement and all the things that you're doing to then identify, hey, now it's time we should, you know, step in”
    Okta's long-tail digital motion uses data signals to find customers who are not adopting. Listen

    Chael says Lawrence, who runs the long-tail digital motion, looks at data signals in the install base by customer to find where they are not adopting, where they are adopted, and where they are stalled. Early-career staff are deployed to have conversations about why and how to help. Chael says this began a couple of years ago and that AI now helps these staff get smarter faster.

    “look for data signals in that install base and by customer, where are they not adopting?”
    AI analysis of customer words and actions can flag accounts worth about ten times more than others, so teams can ignore the rest. Listen

    Jordan says his nightly runs identify the accounts flagging the most issues, and that with an understanding of why customers stay or churn, some accounts are worth 10 times more than others. He says the other 90% are ones intervention will not save, while accounts that say a priority will come in six to 12 months are worth engaging.

    “And so ignore this 90%. These 90%. These are the ones where actually intervention can help.”
    G2 sends account owners a daily Slack ping when a customer is shopping a competitor, naming the competitor being viewed. Listen

    Eric described a churn-signal integration with Slack: if you own an account at G2, you are pinged every day when your customer is shopping on someone else, and told who they are looking at. He said account owners prioritize this in their own time, and G2 teaches customers to do the same.

    “we will ping you every day. If your customer is shopping on someone else, we'll tell you who they're looking at”
    Risk detection at the scale of thousands of customers cannot rely on jumping on a call to judge sentiment. Listen

    Carsten says that with thousands of customers, teams cannot simply call each customer and try to judge sentiment. He argues that risk management and detection need to come from data, using AI.

    “So we, we can't just jump on a call and and and try to figure out whether with a sentiment, OK, how's the customer doing.”
  4. Customer feedback should flow directly to product teams so root causes get fixed, rather than being handled downstream by CS or support. 4 independent voices · 3 shows

    On Grit, Ping Wu said some contact center conversations should not exist, and that United Airlines uses Cresta to find their root causes and fix them.

    4 sources
    Roberge describes HubSpot splitting customers into six representative cohorts so it could run a monthly NPS study while surveying each customer only twice a year. Listen

    He said this worked in HubSpot's first ten years because it was transactional with thousands of customers. Each cohort mirrored the whole base for size, industry and region, so monthly scores reflected new patterns of promoters and detractors. The top detractor reasons went straight to the roadmap, and the team could see whether they moved.

    “We split the customers into six cohorts, all of which were representative of the entire base”
    Linear connects customer feedback to its product team via a customer requests feature and a Salesforce integration. Listen

    Karri Saarinen says that in many companies product and customer teams are isolated, and Linear has a customer feature and a customer request feature so that product teams can see customer problems, blockers and deal issues. He says a Salesforce integration lets customer requests be pulled into Linear, where anyone can view what a customer or segment is saying, and that sales and customer teams can then tell customers when a fix ships.

    “we have also like a Salesforce integration now to help with this like those those nodes can be like captured from Salesforce and then like you can pull them into linear”
    A product that requires users to configure settings or workflow rules can turn friction into requests that reach a CSM and may reach the product months later. Listen

    He describes a user who has to change personal settings, configuration or workflow rules, and says the frustration gets logged as a request or heard by a CSM. He says it may show up in the product nine months later. He offers this as an example of how feedback travels in the old model.

    “what that gets logged as a request or CSM hears it. Maybe it shows up in a product nine months later”
    Some contact center conversations should not exist and are best removed by fixing their root cause rather than by automating or augmenting them. Listen

    Ping Wu said these conversations arise from failed processes, broken products or confusing statements. He said AI's role here is to give full observability across channels, find the root cause and fix it, and gave United Airlines as an example of doing this with Cresta.

    “The first bucket are the conversation that shouldn't even be automated or augmented. They should not even exist.”

Ranked by how many independent voices make each point and how specific their evidence is. Co-hosts of a show count as one voice, and a point needs at least two shows to appear here.

Where they split

With AI, a single post-sale owner can increasingly cover work that used to be split across specialist teams, such as onboarding, support, renewal and expansion.

said Margo Martin ([Un]Churned), Ghazi Masood ([Un]Churned), Amanda Kahlow (Revenue Builders), Abbas Haider Ali ([Un]Churned)

4 sources
Margo Martin expects that AI may eventually let one person onboard, implement, support and renew an ERP customer. Listen

She said the roles are blending with AI, and that at some point a single person could handle onboarding, implementation, support and renewal for an ERP customer. That raised the question of how to move from three separate organizations to one coherent customer experience. She uses the term convergence for this blending.

“like you may at some point with an ERP system have the same person onboard you, implement you, support you, and maybe even do your renewal”
Replit assigns each new customer a product advocate at the moment they become a customer, and that advocate combines the classic CSM, renewal and expansion roles. Listen

Internally the role is called account manager and externally product advocate. The advocate onboards the customer and works with the field engineering organisation to keep bringing new things to build on Replit. Ghazi describes it as designed with an AI-first mindset rather than the classic CSM and renewal structure.

“And basically you, you will get assigned A Replit product advocate the moment you become a customer.”
One AI should span every go-to-market role, because the buyer stays the same across the whole journey. Listen

She said roles exist because humans have limits on time, capacity and recall, but the buyer does not change roles. HubSpot began its superhuman in qualification and closing for SMB, then found customers needed support answers, and it kept the same superhuman rather than switching. She said the superhuman picks up where earlier conversations left off, so customers don't start over.

“But our superhumans supersede across all of the roles because your buyer is the same buyer across that whole journey.”
Abbas is testing a specialized generalist CSM who covers the breadth of post-sales and is specialized in using AI tools. Listen

He said he tested the idea with teams at an event in New York. The person covers support, services consulting and technical CSM questions, so the customer is not handed off to many people. He said the specialists who previously handled these questions stop dealing with repeated problems and move up the value chain. He described this as one of the newer ideas he is testing.

“They're generalists in the concept of post sales and they can apply them across all these disciplines.”
As a company grows or moves upmarket, customer success must split into specialized roles rather than relying on generalist CSMs.

said Carsten Schütz ([Un]Churned), Jim Richmond ([Un]Churned)

3 sources
As the company grew, CS needed team hierarchy and specialist roles because not everyone can be a generalist CSM. Listen

Carsten describes how his previous company, once it had more customers, moved from one pool of generalist CSMs to team leads and specialist roles. He says customer success engineers were there from the beginning, and CS Ops was added later, which helped develop and mature the organisation.

“So not everyone can be a CSM. Not everyone can be the generalist.”
Small scrappy companies need CSMs who do everything, but enterprise-stage operations require specialization. Listen

Richmond described a CSM at a small company doing an annual business review, then a deep technical troubleshooting call, then an onboarding conversation, because people are still proving themselves in the market. He said that as Smartling moved to an enterprise localization play, that model had to give way to specialized roles.

“you got to be willing to do everything right.”
Enterprise-stage customer success gets operational leverage by splitting CSM work into onboarding, technical and value roles rather than generalists. Listen

Richmond said he does not want CSMs to be generalists and wants them to be excellent at what directly affects core metrics. Smartling's model has an onboarding team focused on getting customers to value quickly, a tech team that knows the platform and resolves issues, and a value team focused on commercials, renewals and economic buyers.

“the only real way to get operational leverage is is to specialize those roles.”

The generalist view assumes AI tooling absorbs breadth, while the specialist view reflects pre-AI scaling of complex enterprise products where depth drives core metrics.

From one operator's experience

What one named guest described doing or seeing. Each is a single account, not a point several operators agree on.

What to do

3 more
  • Replace red-yellow-green scores with AI-generated risk narratives and recommended next steps, and auto-generate success plans quarterly for accounts that lack one. Mark Roberge Vovsi does both at Proofpoint.
    2 sources
    AI can give each account a risk narrative with key issues and recommended next steps, not just a red, yellow or green score. Listen

    He described the early warning output as a helpful narrative: a risk summary for each account, its key issues, and recommendations for the next steps the CSM should take. He said this helps teams focus their attention on which accounts need it and what to do for each. He contrasted this with the traditional red, yellow and green health score.

    “With AI, you can also create a helpful narrative.”
    Proofpoint automatically generates success plans for customers that lack one and refreshes them every quarter. Listen

    Mark Vovsi said the AI reviews conversational data, support cases and risk signals to draft plans with tight objectives and milestones, rather than bullet points. Plans load directly into the CSP, and for large customers with many products, each product gets its own adoption and risk focus. He said the goal is to create objectives people would not otherwise have thought of, and that it saves hours.

    “we want to automatically load success plans for every single customer if they don't have one, or based on certain criteria, every quarter refresh it.”
  • Tie sales incentives and ICP discipline to retention, for example by requiring IT involvement in CPQ deals. Mark Roberge Roberge says this roughly triples the chance of a high-LTV account. Cassie Young adds that boards split NRR into current-ICP and legacy cohorts.
    3 sources
    Most retention problems Mark Roberge has been brought in to fix were sales problems, not product or onboarding problems. Listen

    He says the cause is usually a lack of structure keeping sellers disciplined on ICP customers, setting good expectations and setting up customer success properly. His example for Roadrunner's context: a rep who closes a CPQ deal without involving IT leaves CS facing an IT team that may politically try to kill the project. He said involving IT probably triples the likelihood of a high-LTV account, but reps paid only on quarterly revenue aren't incentivized to do it.

    “instinctively, most people think the retention causes product deficiencies or customer onboarding deficiencies. That's the minority in my experience. It's mostly a sales issue”
    Investors scrutinise early gross and net retention because early customers often turn out not to be the ideal customer profile. Listen

    Cassie Young says that even early on, investors look at gross and net retention because founders are asserting an ICP and need evidence that they can protect the base. She notes that later-stage boards often split net retention into current ICP and legacy customers, since early customers usually take time to show they were the wrong fit.

    “usually what happens is people sign up as early customers and it takes a little while for them to learn that they weren't the right customers.”
    QuotaPath is testing whether redesigned incentives plus AI-native service guidance can lift a customer's GRR, for example from 70% to 80%. Listen

    AJ Bruno says sales incentives are typically not aligned to company objectives, so a company targeting 80% GRR should ask what its incentives would need to look like to get there. QuotaPath's thesis is that building and aligning those incentives, with month-over-month and quarter-over-quarter strategic guidance from an AI-native service, could close a gap such as 70% to 80% GRR. He frames this as an unproven question rather than a result: 'the $100 billion question.'

    “can we actually help an organization go from 70 % GRR to 80 % GRR by building the right incentive structure and using an AI native service backing to help strategically guide that month over month, quarter over quarter. That's the $100 billion question”
  • When a customer announces it is leaving, offer a stay-alive contract, and give CSMs a time-bound win-back window in which a return doesn't count against GRR. Eleanora White says nine times out of ten Supermetrics' stay-alive customers keep the system live at lower spend.
    2 sources
    Eleanora White described a stay-alive contract for customers who plan to leave for a competitor, and said it often keeps the system live at a lower spend. Listen

    She said that when a customer says it is going to a competitor, Supermetrics offers an offboarding plan. She said that nine times out of ten, once the customer is on a stay-alive contract, it sees that implementation takes longer than expected and that the product over-promised and under-delivered, so it cannot switch off and keeps the system live at a lower spend. She described this as managing the relationship to the end.

    “nine times out of 10, when we have a stay alive contract is what we kind of call them, they'll see that they actually can't”
    Supermetrics runs a time-bound win-back window in which a returning churned customer does not hit GRR but does count toward retention. Listen

    Eleanora White said that when a customer is turned, the company sets a time period in which a return to the business does not affect team GRR but does affect retention. She said the window has to be time-bound, because otherwise CSMs might stop doing renewals on time.

    “we have a set time period that if that customer comes back to the business, it doesn't impact GRR numbers for the team, but it does impact that retention”
All 34 positions best supported first

Actions written 10 Oct 2026 from the most useful of 362 recent insights and checked against them.

What was said 114 insights matching

Gainsight is running the full renewal process for customers' long-tail accounts with AI and humans in the loop, and selling on renewals achieved rather than activities. Listen

Josh Schachter says Gainsight's pitch is that customers sign and Gainsight owns their end-to-end renewal, running the renewal playbook through Gainsight with AI and humans in the loop. For the long tail it promises to take GRR from X to Y, which he calls low-hanging fruit because unassigned accounts can be given 'AI human in a loop' coverage. It will not sell on calls made or plays run, but on outcomes like 'we renewed this guy.'

“You sign on the dotted line, we are owning your end -to -end renewal.”
Mashrabov estimates AI can handle over 60% of first-line customer support but says it does not work for B2B, and high product velocity makes support agents harder to maintain. Listen

He says expecting legal and customer support to be mostly replaced, and so not ramping those teams quickly, was one of Higgsfield's main operational mistakes. Higgsfield now has over 10 people in legal and over 40 in customer success, all heavy AI users, and he sees no elimination in those roles. Because the company launches products roughly weekly, agents' context and rules change about twice a week, which makes a smart, coordinated human team important.

“It's true that probably over 60 % of customer support requests, especially the first line of defense, can be handled with AI. But when it especially comes to B2B, like, AI just doesn't work.”
Business customers make up slightly over 50% of Higgsfield's revenue, pure consumer use is around 10%, and mobile is under 10%. Listen

Mashrabov says the remainder of non-business revenue comes largely from aspiring creators and freelancers learning video AI to earn money. He describes them as 'a little churny' but says most come back within a year. Higgsfield invests in Higgsfield Academy and a YouTube channel to educate them as a future AI-native workforce. The West accounts for well over 70% of revenue; Seoul is the largest city by usage and the US the largest country.

“It's true that their behavior is a little churny. Within a year, most of them actually come back to try again.”
Kellie Woodin manages a 90-account commercial book by sorting it into renewing, onboarding and mid-implementation buckets and giving the rest async and self-serve resources. Listen

Kellie Woodin said Notion moved from a 'scaled' segment to 'commercial', which she described as less scaled and more hyper-prioritized. Because the team now owns renewals, she buckets accounts by who is renewing this quarter or next, who is onboarding, and who is in an active workflow implementation, and gives those high-touch attention. The team relies on agents and operational rigor for velocity and leans on async and self-serve resources for everyone else. Workshops, onsites and office visits are reserved for selected accounts.

“who's renewing, who's onboarding and who we're in any workflow implementations with, and those become our prioritization buckets.”
Notion turned success plans into 'AI transformation plans' that diagnose maturity, set a mutual action plan, and prescribe workflows from a library of best-in-class customer builds. Listen

The plans keep the usual success-plan elements: business objectives, pain points and success metrics. They add a walkthrough of the AI maturity model to diagnose where the customer is and where they want to go. That feeds a mutual action plan listing the workflows to build together, plus recommended workflows based on the customer's objectives. The speaker said the growing library of best-in-class customer workflows lets the team be prescriptive, which customers are asking for. Some customers still get them labelled as success plans.

“We diagnose where they are and we have a conversation about like where do you want to go and how can we help you get there. And so then we pull together a mutual action plan.”
Notion merged its relationship/renewal manager motion into CS, and is now folding in technical building as well. Listen

Christina Parra described a first 'CS Evolution' that merged relationship managers and renewal managers with CSMs to bring the commercial piece into CS. The next evolution adds the technical piece. Her reasoning is that adoption, consumption, commercials and value are inextricably tied, so one team can be a consultative partner across all of them.

“we launched CS Evolution where we actually merged our relationship manager renewal manager motion with our CSM motion. So we brought together the commercial piece. And then this next evolution is bringing the technical piece in.”
Notion's CS team reframed its job from selling software to selling work, building end-to-end workflows with customers instead of setting up use cases. Listen

Kellie Woodin said Notion's role shifted from developing use cases to developing workflows, because Notion is a blank canvas once tools, AI and agents are connected. The team now runs workshop-style co-build sessions rather than one-to-many trainings, so customers get end-to-end workflows running and start saving time right away. That is why the title changed from customer success manager to 'outcomes architect'.

“Now we're not selling software, we're selling work.”
Nerad finds long-tail engagement the hardest part to standardize across acquisitions, and says it still needs work. Listen

Nerad said acquired companies engaged their small customers in very different ways, which is hard to fold into one model. Advantive is moving the long tail to one-to-many outreach in partnership with product marketing, segmenting by customer tier rather than by line of business. She credits marketing with strong general outreach. What has been tougher is the next level: tailoring to each customer's products and what is meaningful to them.

“Less about it being one LOB versus the other and more about how do we segment to be able to serve those customers appropriately.”
Nerad still finds value in QBRs for top-tier customers, despite the debate over them in customer success. Listen

Nerad said that, whatever they are called, structured reviews to engage and listen to the largest customers remain valuable at Advantive. She said that is a different motion from how the long tail should be served.

“yes, we still do find value in QBRs. I know that's hotly debated in customer success”
Advantive standardized one simple at-risk ticket that anyone in the company can log, with reason codes for routing and spotting trends across business lines. Listen

Nerad said themes such as cancellation, at-risk and downsell are common across companies, so Advantive developed a standard process for them across acquisitions. The at-risk ticket is intentionally simple so that anyone, not only CS, can log something they heard from a customer. It captures product specifics and reason codes, which route it to the right team and allow trend analysis across lines of business. Advantive also built save plays that apply across all lines of business.

“So it's intentionally simple and being able to log an at -risk ticket. This is where a human is actually saying, hey, I heard a customer say this”
Nerad coaches empathy by challenging the 'so what', framing work in the customer's metrics, teaching personas and coaching on real emails. Listen

Nerad pushes CSMs to think about moving the customer's numbers, not just internal numbers like retention. She teaches them to consider the persona and experience of the person complaining, and to listen for what the customer isn't saying. She does this at a CS-only day attached to sales kickoff and in day-to-day moments, such as reviewing an email response that missed a customer's frustration.

“some of it's just challenging the so what? Right? Making sure that we are thinking of things through the customer's metrics, right? Moving the customer's number, not just our number like retention”
Nerad assigns CSMs by line of business, covering roughly three to six products each, because no CSM can advise credibly across the whole portfolio. Listen

Nerad said Advantive has too many products for CSMs to advise on solutions and outcomes across very different ones. Within a product family there is enough overlap that CSMs must be able to tell products apart and cross-reference them; a ProPlanner manufacturing customer may also be interested in Pinpoint, for example. Advantive's enablement covers both CS skills and product knowledge. Josh suggested three to six products per line of business and Nerad agreed.

“there are too many products for the CSMs to really be able to advise on the solutions and the outcomes across very different products.”
Nerad draws on long-tenured CSMs from the acquired company to learn what drives its customers before judging retention risk. Listen

After Advantive's most recent acquisition, Nerad spent a couple of months working with a senior CSM who had been at the acquired company for 15 years and knows its customers well. Together they worked through what drives those customers and what outcomes they intended when they bought the software. Nerad said the understanding of risk and retention follows from that customer understanding.

“I have a senior CSM who's part of my team who she's been with this company 15 years. She knows the customers really well.”
Advantive organizes into four lines of business, each with a GM over sales, support and services, while one VP of CS owns renewals and retention across all four. Listen

Nerad said Advantive restructured by line of business once it reached a certain size, because the way to serve customers differs a lot between them. Each GM oversees sales, support and professional services. Nerad owns the entire renewal and CS function and partners with the GMs. She owns overall retention, ARR renewal rates and uplift.

“We have four LOBs here, yet at the same time, I own the entire renewal CS function, and so I partner with those GMs on how to serve them.”
Lauren Hughes' next priorities are a customer 360 analytical layer and customer support automation. Listen

She wants to stitch every customer's touchpoints across marketing, sales, support calls and quarterly success reviews, which currently exist only in pockets. She also plans to bring the same friction-removal focus to post-sales support, where Justworks is an early adopter of an AI tool and has made deflection gains. She noted the AI-native support platform market is moving fast.

“I'm excited about this concept of customer 360.”
Lauren Hughes dropped the instructional designer role because classroom-style training was not landing with remote reps, and moved to bite-sized learning. Listen

She said instructional designers spent time turning launches into classroom experiences, but people now learn from LinkedIn, podcasts and peers, and reps on Zoom training often do not pay attention. Justworks shifted to learning reps can consume on the go that connects to what is happening in the market.

“So we really needed to move towards like bite-sized learning.”
Maintaining content is not enablement's job, and moved Confluence upkeep to product, PMM and customer education with AI staleness alerts. Listen

Previously only revenue enablement updated Confluence, which she said required 32 people. Product, product marketing and customer education now update content directly. AI measures how recently content was updated, alerts owners when it goes stale and suggests refreshes.

“We needed 32 people to keep Confluence updated.”
Garrett expects Brex to need changes in post-sale work, such as broader ecosystem conversations, to raise NRR by a further 10 to 30 points over the next couple of years. Listen

He said Brex has increased NRR a lot in the last couple of years, but that what it did before probably will not get it to a further increase. He presented the changes he described as examples of what would be needed. The figure is his stated ambition, not a forecast of results.

“if we want to go increase NRR by another 10, 20, 30 points in the next couple of years”
Brex increased the share of customers closing their books on the platform by about 20 percent in twelve months by changing how its customer success team talks to customers. Listen

Garrett said the gain came not from product changes but from reorienting the customer success team toward the business process of closing the books and how it fits with ERP and other tools. He said the reason someone does or doesn't adopt is often not whether the tool works, but unease about changing a process they cannot afford to get wrong. He said the team needs to get better at doing the same for other cross-functional workflows.

“we actually basically changed the way that our customer success team was oriented and talking to people about it”
Proofpoint gives the success plan template and rules work a dedicated owner. Listen

Mark Vovsi said one person reports to the head of customer success and has a foot partly in his team, focused on process, templates by customer segment and product ownership. Feedback from CSMs flows to her, and similar owners exist for other customer teams and for renewals. Josh likened her role to a product manager working through a backlog of iterations.

“It's almost like she's the product manager now with a backlog of iterations to make, I would suppose, on the success plan.”
Proofpoint automatically generates success plans for customers that lack one and refreshes them every quarter. Listen

Mark Vovsi said the AI reviews conversational data, support cases and risk signals to draft plans with tight objectives and milestones, rather than bullet points. Plans load directly into the CSP, and for large customers with many products, each product gets its own adoption and risk focus. He said the goal is to create objectives people would not otherwise have thought of, and that it saves hours.

“we want to automatically load success plans for every single customer if they don't have one, or based on certain criteria, every quarter refresh it.”
Proofpoint's CS organisation began with no assigned accounts, no digital motion, and an account manager acting as quarterback when questions about risk or adoption arose. Listen

Mark Vovsi said CSMs at Proofpoint were product experts but were not focused on success plans, QBRs or renewal outcomes. Before the rebuild, the account manager led each account and a CSM was brought in only when risk, health or adoption questions came up. Proofpoint brought in a new CS leader to stand up the organisation, then launched a CSP, high-touch playbooks and digital campaigns.

“We didn't even have assigned, you know, accounts for our CSMs.”
During a breach crisis, putting legal, product and sales on every customer call kept the explanation accurate. Listen

Mark said RSA converted inside sellers into people who talked to customers about the attack and trained tech support staff to have customer conversations. Every call needed someone from legal, product and sales to make sure the company was positioning and explaining exactly what had happened. He said the effort ran for about a year, and some EMC leaders worked from the RSA offices for weeks.

“You had to have legal, someone from product and someone from sales on every call to make sure you were positioning and explaining exactly what took place.”
Freshworks is trialling a combined account-management and customer-success role in parts of its long tail, but Ian Tickle says he has no answer yet on the future of those roles. Listen

Ian raises the open question of what account management and customer success should look like going forward, including a role combining the two. He says he is very happy with his current account management and CS teams. A few long-tail segments are trialling the combined model and testing whether technology can make it more effective.

“And we don't have an answer for that at the moment I'm very happy with my account management and customer success team”
Lifecycle programs at Bloomreach ran separately in customer marketing and CS, and AI may connect them. Listen

Simon said lifecycle programs have been somewhat disconnected between customer marketing and CS, with well-intended programs run by his team and by customer marketing that were quite different. He is excited about combining them, saying AI makes the connection more possible, which should help the team act faster on intent and stay aligned in how it communicates with customers.

“right now, lifecycle programs have been somewhat disconnected between customer marketing and CS.”
Bloomreach's small-customer efficiency play is less about a digital-only tier and more about making CSMs effective across more accounts. Listen

Simon said Bloomreach does not have a traditional long tail, and its smallest customers are really important and are not customers paying $2,000 a year. The efficiency approach isn't just about building a digital-only tier but about making CSMs more effective and valuable across more accounts, with agentic AI extending the team to smaller customers.

“it isn't about just building a digital only tier, it's about making sure that CSMs can be more effective and more valuable across more accounts.”
Bloomreach is experimenting with forward deployed engineers, starting with its largest enterprise customers. Listen

Simon said Bloomreach is not quite there yet but is experimenting with the FDE role, which he expects to grow into. The plan is to start with the largest enterprise customers and prove the value before scaling from there.

“we're going to start with our largest enterprise customers.”
The comp change suits some CSMs but not all, and the team must keep its focus on value from what customers already bought. Listen

Simon said some CSMs were already more commercially expansion-focused, which suited them, while others come from a neutral position of making sure the customer gets every ounce out of what they already purchased. He said he does not want the team to lose that focus and that it is more important than ever, while linking new product features to what fits each customer.

“make sure the customer get every single ounce out of what they've already purchased.”
Braze treats Gainsight as a system of interaction where CSMs spend their day, with data pulled in from other systems as needed Listen

Saumyo deliberately calls Gainsight a system of interaction rather than a system of record, because he wants CSMs to spend their day in that platform. If data needed by CSMs is not in Gainsight, his team fetches it from places such as Snowflake or external AI tools like Staircase AI, and surfaces it on that platform. He says he would almost never want CSMs to not have a platform.

“I very carefully call it System Of Interaction, not a System Of Record because I want the user group which is CSM in this example, CSMs to basically spend their day within that platform”
Saumyo prefers in-app intelligence so CSMs can work in one platform instead of switching between tools Listen

Saumyo's ideal is that a CSM logs into one platform in the morning and logs off at the end of the day without going anywhere else. Reps need some outside research, but he says the goal is to avoid swivel-chair work, where people copy and paste between apps, which he sees as context switching that makes CSMs less happy. He says this ideal is not going to happen anytime soon, but he believes in-app intelligence will be a significant efficiency booster.

“if I have to kind of swivel chair go to a different app and launch something and do something and copy paste something and come back here.”

Show all 114