Home / Blog / In Berlin, Customer Success Confronts the Execution Gap

header for In Berlin, Customer Success Confronts the Execution Gap

In Berlin, Customer Success Confronts the Execution Gap

The tools are there. The frameworks exist. Customer Success teams across SaaS have invested in AI, CRM platforms, health scoring, and stakeholder engagement strategies. Teams have never articulated the strategy more clearly.

Eighty-five percent of companies are actively experimenting with AI in their post-sales functions. Five percent are seeing real returns.

That single statistic, surfaced inside the room at CS Snack Berlin, captures more precisely where the industry actually is than any trend report. The problem is not a lack of direction. It is the gap between having the right approach and making it work in practice.

At our latest Customer Success Snack session in Berlin, hosted at doinstruct and Superchat, post-sales professionals examined what customer success operations in 2026 actually demand, across nine roundtables covering AI adoption, customer attention, CRM strategy, value proof, executive engagement, and CS organisation design.


AI Has Moved From Experiment to Infrastructure Challenge

Six months ago, the AI conversation in Berlin’s CS community was largely about personal productivity. Better first drafts. Saved hours. The energy at this last session was different.

As participant Christiane Kaiser observed after the event: “Teams are starting to embed AI into their processes — risk detection, automated triggers, escalation logic that doesn’t depend on a CSM remembering to check a dashboard.” The shift from individual habit to operational system, she noted, is the one that actually moves retention numbers.

The sessions led by Inka Seidel, Head of Customer Success at Superchat, and Laura Espinel, Senior Consultant at Customer Obsessing Consulting, surfaced a failure mode that runs across customer success operations in 2026. Teams have AI access, budget, and tools. What they lack is the behavioral infrastructure to use them well. Laura named it directly: stop treating AI as a tool rollout instead of a behavior change. Expecting adoption without enablement is a structural error, not a motivation problem.

Three practices separated teams seeing returns from those still experimenting: defining success before deployment (what does “time saved” actually translate to in retention or expansion terms?), investing in internal knowledge bases before adding AI layers, and running structured adoption programs. The “AI buddy system,” pairing less confident users with experienced colleagues, is a practical lever teams are beginning to test.


Customer Attention Is a Positioning Problem, Not a Channel Problem

Inboxes are full. Calendars are saturated. CS teams are competing for the attention of stakeholders managing multiple vendors, renewals, and internal change initiatives simultaneously.

The sessions moderated by Leslie Boadum, Julian Janecke, and Rick Brink reached a consensus early: the primary attention killer is not the wrong outreach format. It is unclear positioning.

The 3×3 framework emerged as a structural baseline: maintaining active relationships across three levels (individual contributor, leadership, and C-Suite) before a renewal arrives, so that reaching those levels does not feel like a sales tactic when it matters most.

Leslie Boadum’s session introduced the concept of persona translation. The Buyer needs ROI and business impact framing. The Beneficiary wants high-level software outcomes. The User cares about daily workflows. CSMs who treat these three personas as interchangeable create noise. CSMs who tailor to each one create a signal.

One practical intervention received near-unanimous agreement across sessions: personalised Loom videos. Described as “super practical, easy to implement, and immediately testable,” they are traceable in ways standard emails are not, and capable of changing the register of an interaction in a way that subject-line optimisation cannot.

The Sales-CS handover also surfaced as a structural attention problem. Sales overpromising and then disappearing erodes trust before CS even starts. Mandatory handover notes and activated call recordings were the practical fixes with the most traction.


Proving ROI Under Pressure Is a Translation Problem, Not a Data Problem

ROI conversations are one of the clearest stress tests of customer success operations. They happen at the wrong moment. They are triggered when budgets are reviewed, when leadership changes, or when a renewal is ninety days out.

As Mônica Kochenburger, who moderated a session on proving value under pressure, put it: “Value conversations should not start when they are needed. They should already be happening from the beginning.”

The discussions moderated by Mônica Kochenburger and Johannes Delion of doinstruct identified the same challenge across very different industries. The problem is rarely missing data. It is that CS teams have activity data (logins, sessions, features used) while executives make budget decisions based on business impact. Converting one into the other is where value proof breaks down.

Giorgia Pedenzini‘s session named the structural root cause: without pre-purchase benchmarks or defined KPIs, proving value later is nearly impossible. The customer has no baseline to measure against. Onboarding and kickoff are the right moments to establish that foundation, asking what the customer is trying to improve, how success will be measured, and who internally needs to see the evidence.

End users, operational managers, and economic buyers each need a different value narrative built from the same underlying data. Most CS teams are currently telling one story to all three.


CS Leaders Are Building for a Function That Keeps Changing Shape

The leadership sessions opened with a recurring challenge: the catch-all problem. CS becoming the default owner of every post-sales issue (billing queries, support escalations, internal miscommunications) is one of the most persistent structural failures in the function. Every task that lands with a CSM and belongs elsewhere is strategic capacity lost.

CS must be defined by value ownership, not by the absence of another owner. As one participant in Kate Neal’s leadership session put it: “CS has become a catch-all function. Before we automate anything, we need to ask whether we should be doing this at all.”

Kate Neal‘s session made clear that AI leadership in CS is inseparable from knowledge management. Clean, centralised data is the precondition for reliable AI outputs. Leaders who have not resolved the data foundation have not resolved their AI strategy, regardless of which platform they have licensed.

Larger organisations are increasingly segmenting CS into specialised roles: dedicated onboarding, retention-focused CSMs, and expansion specialists with commercial mandates. Cross-functional rituals like a regular Customer Excellence Hour, involving Marketing, Sales, Product, and Finance, keep the broader organisation aligned rather than leaving CS to advocate alone.


What This Means for Customer Success Leaders

Three implications ran through the Berlin conversations about customer success operations in 2026:

  1. The data foundation is the AI strategy. AI access without clean, centralised, cross-functional data produces outputs that teams stop trusting. The highest-impact investment in 2026 is not the next AI feature. It is the CRM hygiene and data governance that make any AI layer viable.
  2. Value conversations need to be designed into the customer journey, not triggered by pressure. Kickoff is the right moment to establish baseline metrics, define success by stakeholder type, and begin the ROI conversation that will matter at renewal. Teams that skip this inherit a structural disadvantage that execution later cannot fix.
  3. The catch-all problem will not solve itself. CS leaders who have not defined what their function doesn’t own are watching strategic capacity disappear. Clarity about the CS mission, enforced through clear internal boundaries, is the precondition for everything else.

The Conversations That Keep This Moving

The sessions in Berlin were not theoretical. They were practitioners comparing what actually works, across different industries, company sizes, and tech stacks, in a closed-door format designed for exactly that kind of honest exchange.

The insights here came from 75 people who showed up at doinstruct and Superchat, sat across a table from someone wrestling with the same challenge, and said something true.

If you are building or leading a Customer Success team in Europe and want more of these conversations, we would love to have you at a future CS Snack. Events are peer-only, sponsor-free, and designed to produce the kind of thinking that actually changes how you work.

Subscribe to the newsletter to stay connected, and join us at the next session in a city near you.


Find your hyper-local community

Find your local community in Dublin, Amsterdam, Stockholm, Malmo, Copenhagen, Berlin, Munich, Hamburg, Ghent, Paris, Madrid, Zurich, Bucharest and more.

Get invited to Events, Job alerts & More. Straight to your inbox.

close-link