There is a specific moment in every SaaS customer relationship where the outcome of the next twelve months is quietly decided. It is not the renewal conversation. It is not the quarterly business review. It is the first 30 days after the contract is signed, when the customer still has momentum from the buying decision and the product has not yet proven it deserves to exist in their workflow. David Becerra, a customer success leader who has built CS organizations from startup through SAP enterprise, sat down with Thibaut de Lataillade to explain exactly how that window works, why most companies fumble it, and what his team did to stop the bleeding.
The Relay Race That Most Companies Lose
Becerra reaches for the same metaphor every time this topic comes up, and it is worth paying attention to because the precision of it reveals how deeply he has thought about the mechanics. Picture the Olympic relay race. The hundred meters. One runner is sprinting at full speed. The next runner is already accelerating before the baton arrives. The handoff happens mid-stride. Zero deceleration. The race continues without a breath of lost momentum.
That is what the sales-to-CS transition should feel like. That is not, in Becerra’s extensive experience, what it usually feels like.
What usually happens is something closer to the first runner stopping dead, fumbling the baton, dropping it on the track, picking it up, looking around for someone to hand it to, and then discovering that the second runner is still putting on their shoes in the tunnel. The customer, meanwhile, is standing in the bleachers watching all of this and wondering whether they made a terrible purchasing decision.
“When the momentum breaks and then the project stalls, you’re really setting yourself up for more work later on and really having to undo all of that.”
The best organizations, Becerra argues, have the CSM involved before the deal closes. Not in the room during negotiations, necessarily, but already briefed on use cases, key stakeholders, and the specific outcomes the customer expects. The customer should not feel a transition at all. Marketing leads to sales, sales leads to CS, and the whole thing feels like one continuous conversation rather than being passed between departments like a parcel nobody is entirely sure they want to accept.
The Roambi Experiment: Fixing Onboarding After Getting It Wrong
Becerra is disarmingly honest about the origin story. At Roambi, the mobile BI startup he co-founded, they did not arrive at their onboarding fix through strategic brilliance. They arrived at it through the panic of watching customers churn at rates that made their venture capital projections look like creative fiction.
The product itself was compelling – a visual, mobile-first data visualization tool that made executives want to pull out their phones in meetings and show things off. The problem was the gap between the sales demo, where everything looked gorgeous with sample data, and the actual deployment, where the customer had to get their own data into the system and build their first visualization. That gap was where excitement went to die.
They tracked how long it took customers to publish their first visualization. The correlation was brutal. The longer it took, the less likely the customer was to renew. Customers who had not built something tangible within 30 days were churning at rates that demanded intervention.
The fix was a mandatory activation package. Every deal included a product expert – consultant, services person, whatever you want to call them – who partnered with the customer to get that first visualization live within the first month. They even commissioned salespeople to sell the package, accepting a short-term hit on margin because the long-term math was obvious: a customer who sees value early stays. A customer who stalls in onboarding limbo does not.
“We saw a pretty big reduction in early churn. I would say 10 or 15% of churn went down after we were starting to sell those packages.”
Why “Time to Value” Is Not the Same as “Go-Live”
There is a subtle but critical distinction in how Becerra talks about time to value that is worth isolating, because most CS organizations conflate it with the full implementation timeline and then wonder why the metric feels unmanageable.
TTV is not the go-live date. It is not the complete deployment. It is not the moment when every feature is configured and every user is trained. It is the first point – the earliest possible point – where the customer can look at the product and say, “Yes, this is why we bought it.” That might be a single dashboard. A single report. A single workflow that works the way it was supposed to. The bar is deliberately low, because the purpose is not to finish the project. The purpose is to sustain momentum.
When companies define time to value as the complete implementation, they create a metric that stretches to months or quarters, and during that entire period, the customer is running on nothing but the memory of a good sales demo and the hope that things will eventually work out. Hope, as anyone who has watched a customer quietly disengage over six months can confirm, is not a retention strategy.
The activation package at Roambi worked precisely because it targeted that first moment of value, not the final one. Get the customer to a point where they have something real, something they built with their own data, something they can show to their boss. Everything else – the full rollout, the additional use cases, the expansion – follows naturally from that initial proof point. Without it, you are asking the customer to believe, and belief erodes at a rate directly proportional to the number of weeks since the last time they saw something work.
The Cultural Challenge of Selling Onboarding
Making the activation package mandatory was not purely a product decision. It was a cultural one, and Becerra is clear-eyed about the friction it created. The sales team had been incentivized to sell software. Selling a services package alongside the software felt like adding friction to the deal. It reduced the initial margin. It required explanation. It was, in the short-term calculus that salespeople are professionally optimized to perform, a complication.
The argument that won was the data. Customers without the activation package were churning. Customers with it were not – or at least, not at the same rate. The 10 to 15% reduction in early churn was not a hypothesis. It was a measured outcome. And the downstream revenue from retained customers who expanded their usage dwarfed the margin hit on the activation package.
Becerra also connects this to a broader pattern he observed during Roambi’s transition from on-premise to cloud. In the on-prem world, you could sell a large deal, attach a maintenance contract, and the revenue looked solid on paper regardless of whether the customer was actually getting value. SaaS stripped away that hiding place. Every year – or every month, depending on the billing cycle – the customer makes an active decision about whether the product is worth continuing. The transparency of subscription economics is unforgiving: if the customer is not getting value, you find out, and you find out fast.
That transparency is precisely why the first 30 days matter so much. In a subscription model, you do not get to hide a bad onboarding experience behind a multi-year contract. The customer’s willingness to renew starts forming the moment the ink dries, and every week of stalled implementation chips away at it.
For the full interview breakdown, see our complete Expert Insight with David Becerra.
Tools Mentioned in the Interview
The following tools and platforms were referenced during this conversation.
Related Content
Customer Success From Startup to Surf Camp: Expert Insights with David Becerra
David Becerra has built customer success organizations from startup to SAP enterprise to a surf retreat in Indonesia. He breaks down what actually drives retention, why your quietest customers are your biggest risk, and what hospitality teaches SaaS about onboarding.
How Data Signals Transformed a Low-Touch Customer Success Team
David Becerra built a low-touch CS organization at SAP that scaled from 10-20 accounts per CSM to 60-80, driven by Mixpanel usage data that reduced churn by 10%.
What Running a Surf Camp Taught a CS Leader About Onboarding
David Becerra left enterprise SaaS to manage a surf retreat in Indonesia and discovered that the principles of customer success -- onboarding activation, setting boundaries, and building advocacy -- transfer to hospitality with unsettling precision.
