Your services team shapes renewals. Why aren’t they measured on NRR?

Your services teams help shape renewals. Why aren’t they measured on NRR?

If you ask a software company who owns net revenue retention, you'll usually hear the same answers: the CRO, the CCO, Customer Success, maybe account management. Rarely does anyone say professional services.

The numbers back that up. According to the 2026 Global Services Dynamic Report only 45% of services and delivery teams have defined NRR goals, the lowest of any function and 17 points behind executive leadership. Yet in software, delivery is where the customer first experiences what they bought. It's where adoption starts, where value gets proven, and where the earliest signs of renewal risk and expansion potential appear. This creates a structural blindspot, meaning a team with some of the most direct influence on whether customers stay and grow is often the one least connected to the number that measures it. 

Closing that gap starts with a simple shift: tie delivery health to account health, so the signals services teams see every day reach the people deciding what happens at renewal.

Renewals are decided long before the renewal conversation

In most software businesses, the renewal is treated as an event. A CSM opens a renewal opportunity 90 or 120 days out, pulls a health score and starts preparing the business review. By then, the outcome is largely set.

The real decision happens months earlier, during implementation and onboarding. That's when the customer learns whether the product does what sales promised, whether their team actually uses it and whether the vendor understands their business. A rocky go-live or a key workflow that never got configured can quietly sink an account that looked healthy on paper.

Services teams know which customers are hitting milestones and which are stalling. They hear the offhand comment about a new business unit that wants the same rollout. They notice when the executive sponsor stops showing up to steering meetings. Those are some of the most reliable leading indicators of renewal and expansion a software company has and they rarely travel past the project team.

The problem with measuring delivery on utilization alone

If services shape renewals, why is it so rarely measured on them? Most of it comes down to historical operations and procedures. Delivery teams have long been run as cost centers or margin centers, with utilization, billable hours and project margin as the scorecard. Those metrics still matter, but on their own, they can often reward the wrong things. A team measured only on utilization is incentivized to keep consultants billable, not to flag that a customer is drifting toward churn while a project can come in on time and on budget while the customer walks away unconvinced. When delivery isn't accountable for what happens after go-live, the handoff to Customer Success becomes a wall instead of a bridge. 

The pricing shift transforming software right now makes this gap harder to ignore. As more vendors move from seat-based to outcome-based models, revenue depends on customers actually achieving results and servicesdelivery is where those results start. A services organization that isn't measured on outcomes is disconnected from the very thing the business now sells.

Connecting delivery health to account health

Giving services a stake in NRR doesn't mean handing delivery leaders a renewal quota. It means making delivery data part of how the business understands every account.

Today, most account health scores are built on product usage, support tickets and CSM sentiment. Delivery data, when it's included at all, is usually a lagging field someone updates by hand. 

A more complete picture brings project and engagement signals directly into the account record, alongside adoption, support and financial data. These signals include:

• Milestone and time-to-value progress showing whether the customer is reaching first value on schedule
• Scope and change-order patterns revealing whether what's being delivered still matches what was sold
• Stakeholder engagement tracking whether sponsors and end users are showing up and participating
• Budget burn and margin flagging projects under strain before the customer feels it
• Delivery sentiment and risk logs capturing what the project team is hearing and worried about

When these signals live on the same record that Sales, Services and Success all work from, delivery health stops being a private project metric. It becomes an early read on account health that everyone can see and act on.

Surfacing expansion before anyone has to ask

Risk gets most of the attention, but the bigger upside of connecting delivery and account health is expansion. Service teams are often the first to spot it.

A customer who finishes phase one ahead of schedule is a strong candidate for phase two. A new region or business unit requesting the same rollout is an expansion opportunity hiding in a status update. When that context stays inside a project plan, it surfaces late (if at all) and usually occurs when sales starts digging ahead of renewal.

When delivery signals feed the account record in real time, the picture changes. Customer Success can see which accounts are expansion-ready months earlier and sales gets a warm, well-documented handoff instead of a cold call. Even more, Services gets credit for the revenue its work made possible, with a clear record of the value it delivered.

How can software companies give services a real stake in NRR?

Moving services from utilization-only to shared retention accountability is as much an operating change as a technology one. A few practical places to start:

1. Add outcome metrics to the delivery scorecard. Keep utilization and margin, but add time-to-value, adoption at go-live and post-project account health. Measure what happens to the customer, not just the project.
2. Put delivery data on the customer record. If project health lives in a separate system or spreadsheet, it will never inform renewal decisions. Delivery, success and financial data should sit on one shared record.
3. Redesign the handoff. Make the transition from services to Customer Success a structured exchange of goals, risks and expansion signals, not a ticket closure. Include delivery leads in early account reviews.
4. Give services credit for the revenue it influences. Track renewals and expansions that trace back to delivery work. What gets attributed gets prioritized.

AI can help here too. When routine work like status reports, RAID logs and project summaries is automated, delivery leaders get time back to focus on the customer relationships that actually move retention. In Certinia's experience, that can mean 20+ hours a month reclaimed per project manager.

NRR is a team number and services belongs on that team

NRR has always been a shared outcome. Sales sets expectations, Services delivers on them, and Customer Success sustains and grows the relationship. The problem is that most software companies only measure part of that chain against the number.

When delivery health is connected to account health, the whole picture comes into focus. Risk shows up while there's still time to act. Expansion surfaces before Sales has to go looking for it. And services gets recognized as what it already is: one of the biggest drivers of whether customers stay and grow.

Certinia brings professional services and customer services together on Salesforce, powered by Veda AI, so Sales, Services, and Success work from a single customer record. Every team sees the same signals, and NRR becomes a number you can actually prove.