EXPERTISE · B2B SAAS
For a B2B SaaS vendor, the first reserve of growth is the portfolio already signed. Velista structures the Customer Success and Account Management function so it produces retention and expansion.
What the function has to produce in retention, adoption and expansion, and the way that gets measured.
Spotting risk signals and industrialising the response well before renewal.
Making the existing portfolio the first growth channel.
Key accounts, renewal preparation and negotiation.
Segmentation, sizing, roles, and the interfaces with Sales and Product.
Customer lifecycle, account reviews, escalations. Without that cadence nothing repeats.
Hiring, growing and leading a team across several markets.
Scaling, with a portfolio of accounts that matter.
A CS function that exists but is not yet equipped.
When renewal is endured rather than steered.
To build, to segment, or to take international.
METHOD
A successful engagement is recognised by the fact that it ends. The first three stages build the system, the fourth makes it self-sufficient.
At a pricing SaaS vendor serving Tier-1 retailers, the Customer Success and Account Management function was built from scratch and then led internationally. It became the company's first growth engine, with NRR going from 90% to 120% and ARR multiplied by ten in five years.
The same logic in an e-commerce scale-up operating across three European markets, with a team of more than fifteen. A reactive role became a structured growth model, and expansion revenue was multiplied by ten.
A pricing SaaS vendor serving Tier-1 retailers, with no established Customer Success or Account Management function.
The function was built from scratch, from portfolio segmentation to follow-up processes and expansion strategy, then led internationally. It became the company's first growth engine.
TOOLS
Velista publishes the calculators it uses on engagements: NRR, team sizing, health score, target buying price, price image, markdown. No form and no sign-up.
See the tools →FAQ
Three answers to three situations. A firm brings method and deliverables, rarely execution in front of customers. A hired Head of Customer Success brings lasting execution, provided the role is fundable and the trajectory legible enough to attract the right profile. An independent sits between the two and installs the function, carries the first renewals, writes down what needs writing, then hands it over. Where the model is already stable and the budget is there, hiring is the right call.
Below roughly thirty recurring accounts, NRR is not a readable metric, since a single departure moves it several points and no decision can rest on it; at that stage the issue sits with the product, the positioning or the quality of the accounts being signed far more often than with Customer Success. The question becomes relevant once the portfolio is wide enough for repeated patterns of churn and expansion to appear, and once more than one person has to apply the same logic.
No, and the reverse order costs more. A Customer Success platform freezes a process: health scores, alert sequences, onboarding stages. Where the process does not yet exist, it freezes a default no one arbitrated, and the team spends its time filling fields nobody reads. A properly maintained CRM, a renewal tracker and a weekly portfolio review are enough to reveal what deserves tooling. The tool confirms a practice, it does not create one.
The timeline depends on the renewal cycle far more than on method. A quantified effect on NRR only reads once a full cohort of renewal dates has passed, often twelve months. Before that, leading signals appear within weeks: actual portfolio coverage, time to detect an at-risk account, share of accounts with an identified decision maker, proportion of renewals engaged ahead of term. Those signals do not replace the outcome, they only indicate whether it is being built.
On a narrow, documented perimeter. Analysis covers account-level data, meaning aggregated usage, contract history and stated reasons for leaving, and not personal data belonging to end users, which Velista does not access. Account names are anonymised wherever the analysis does not depend on them, and a confidentiality undertaking covers the engagement. Customer conversations are read in raw form only to find recurring patterns, and in a volume limited to that need.
Yes, provided what standardises is separated from what does not. Definitions, segmentation, alert thresholds, review cadence and the way a risk is qualified all standardise. Buying-cycle rhythm, the seniority of the contact actually reachable, service expectations and the weight a contract carries in the relationship do not. Velista works in French, English, German and Spanish, which allows local reporting to be read without an intermediary.
Format first, since a short diagnostic, a structuring engagement over several months, delegated operational leadership one to two days a week, or training and mentoring do not involve the same volume. Then duration, perimeter, which runs from one team in one market to several entities, and the number of stakeholders involved on the product, sales and executive side, which drives alignment time far more than the analysis itself. Costing follows a framing conversation.
A question that is not here can be settled in a thirty-minute conversation.
THE OTHER SIDE
Part of churn is decided at the moment of pricing. Velista works on pricing strategy for retail and e-commerce companies too.
Explore the Pricing expertise →CONTACT
A retention, expansion or pricing challenge? Thirty minutes is enough to frame it and to find out whether there is something worth working on together.