The handoff quietly killing your NRR (that doesn't happen in customer success)

It’s often said that sustainable net revenue retention (NRR) requires the entire organization, not just the customer success (CS) team, to be incentivized by the customer’s ultimate success.

That’s what Certinia’s CCO Todd Kisaberth said in another recent blog post. But there’s one function that rarely comes up in that retention conversation, even though it sits at one of the most consequential moments in the entire SaaS customer relationship: professional services (PS).

In most software companies, professional services is treated as an implementation function. They show up after the contract gets signed, configure the product, hit the go-live milestone, and hand the account to CS. Then they move on to the next project. By the standard model, their job is done.

What that model misses is how professional services shapes the customer's first experience of value. And that first experience sets the trajectory for everything that follows: adoption, expansion, and renewal. (In other words, everything that CS is responsible for.)

Professional services is the most underleveraged function in the customer journey. The more interesting question is why CS leaders haven't spent more time improving this critical partnership.

Why professional services gets treated as invisible

The reasons professional services gets siloed from the CS conversation are mostly structural.

Professional services is typically measured on project economics: utilization rates, margin, on-time delivery and budget adherence. Customer success, on the other hand, is measured on retention and expansion. The metrics don't talk to each other, so the teams don't either.

But this creates a dynamic where professional services optimizes for a successful go-live, and CS inherits whatever that go-live actually produced – which is sometimes great, and sometimes a customer who went live on time but never really saw value (or even understood what they were supposed to do next).

The handoff between professional services and CS is one of the most consequential moments in the customer lifecycle, and in most organizations it's treated as an administrative formality. A close-out meeting. A transition email. A Salesforce record update that says "implementation complete."

What it should be is a deliberate transfer of everything PS learned about the customer during implementation: the stakeholders who are resistant, the use cases that aren't quite landing, the business outcomes the customer is actually trying to achieve. That intelligence exists. It just rarely makes it to CS in any structured way.

What professional services knows that customer success doesn't

Implementation teams develop a ground-level understanding of customers that almost no other function gets. They're in the weeds with the people who actually use the product – the practitioners who actually determine whether adoption succeeds or stalls.

They see which teams are engaged... and which are checked out. They know which parts of the configuration were compromises and which were exactly right. They hear the offhand comments that reveal whether the customer is genuinely excited or just managing an internal project they didn't fully choose.

This is exactly the kind of intelligence that would make a CS team dramatically more effective. A CSM who inherits an account with that context is starting from a real picture of where the customer actually is, with enough lead time to act on it.

When professional services and CS operate in separate systems with separate mandates, this intelligence evaporates at handoff. The CSM starts fresh. The customer re-explains their goals to someone new. And the trust deficit that Todd wrote about – the one that quietly seeds churn long before renewal – takes root right there.

The outcome continuity problem

Sales makes promises about business outcomes. Professional services delivers a technical implementation. CS is tasked with closing the gap between what was promised and what was built.

A large gap between what was promised and what was built is something relationship management alone can't close. The customer bought a result, and renewal conversations reflect that reality plainly.

Making professional services accountable for outcome continuity, alongside go-live, is the structural fix. That means PS builds project plans that trace directly back to the business outcomes documented in the sales cycle. It means CS has visibility into the PS project during implementation, so they can see when something is drifting from what was promised. And it means the metrics PS is evaluated on include leading indicators of customer health, alongside project economics.

This is a bigger organizational change than it sounds. It requires PS and CS leadership to agree on what success actually means, and to share accountability for it. But companies that have made this shift consistently report faster time-to-value, fewer stalled implementations, and CS teams that spend less time firefighting and more time driving expansion.

What this looks like in practice

Operationalizing this comes down to three things:

1. A shared definition of the customer's intended outcomes, documented in a way that sales, PS, and CS all contribute to and can all see. A living record of what this customer is trying to achieve, updated as PS learns more during implementation.

2. CS visibility into project plans and status.

The CSM who will take over the account needs to have visibility into the status of the implementation so that they can plan provisioning, education and adoption plays accordingly.  If they start too soon or too late (or not at all), the customer’s time to value starts to get longer, and the customer becomes a churn risk from the get-go.

3. A structured PS-to-CS transition.

This means CS gets involved before go-live (ideally 30 to 60 days prior) so the CSM has time to build context, meet the customer alongside PS, and understand the implementation before they own the account. The overlap gives CS a running start rather than a standing one.

4. Professional service metrics that include CS outcomes.

This is the change that makes everything else sustainable. If customer health at 90 days post-go-live is part of how professional service performance is evaluated, the entire incentive structure shifts. PS has a genuine reason to care about what happens after implementation, and the cross-functional collaboration that follows tends to be real rather than ceremonial.

The tension between sales and CS at the point of handoff, with each team operating under different definitions of success and incomplete visibility into each other's work, is something the CS community has been wrestling with in earnest.

Todd Kisaberth and I explored this recently with a group of CS practitioners in a session hosted with Customer Success Collective, and the conversation made clear that the PS dimension is the piece most organizations haven't fully accounted for yet. If business outcomes are still getting lost in the sales-to-CS handoff, the next chapter of that discussion picks up exactly there.

Why customer success “hero culture” is a churn red flag

Too often, we mistake heroic acts of account management for a customer-centric culture. We shouldn’t. Requiring a hero to save an account is only proof that your system has already failed.

Customer Success CollectiveTodd Kisaberth

The bigger picture

Todd’s earlier article ended with a call to build customer success on alignment, data integrity, and measurable value realization. I’ll take that a step further: that alignment has to include professional services, explicitly and structurally.

As long as professional services exits the customer relationship at go-live, organizations are leaving one of their most valuable sources of customer intelligence unused and surrendering one of the most direct levers available for improving net revenue retention.

The organizations getting this right are running CS and professional services as a continuous motion, with shared data, shared accountability, and a shared definition of what customer success means. That's a design problem, and it's one most CS leaders have more influence over than they realize.  Getting it right is a critical step in preventing eventual churn.