WHY SERVICES DIE WHEN THEY'RE MEASURED LIKE A COST CENTRE

It’s rare for those in services delivery to fail loudly.

There’s no dramatic collapse, no single moment where everything breaks. Instead, the decline is gradual, a slow erosion of influence, innovation, and perceived value. The team is busy (maybe too busy) yet they are still viewed internally as an island or necessary but not strategic.

If that sounds familiar, the root cause is rarely capability. It’s measurement.

The KPIs of Services tend to determine how they behave or how they are seen and in many organizations, services are still being wrongly treated like a cost center.

So what does that look like? On any given day a VP of Services will look likely look at their Services dashboard. Utilization is on target, the team is booked as they should be for the next quarter and so revenue is predictable. Good times right?

And yet, in the last leadership meeting, services barely came up. Product is driving the roadmap, Sales is driving growth, Customer Success is driving retention. Services? That’s just “execution.”

There are signposts that you are in this place:

• Services is brought in late in the sales cycle

• Projects are delivered, but outcomes aren’t clearly tracked

• The same delivery challenges repeat across customers

• Leadership conversations focus on cost and capacity, not impact

• Services leaders struggle to articulate their contribution to ARR

  
  

Essentially you’re being set-up, direct from the top; you’re being optimized for the wrong things.

The Cost Centre Trap

Treating services as a cost center doesn’t usually happen by accident. It’s often an inherited thought, especially in product-led organisations where the “main offering”, whatever it may be, is seen as the engine of value; services only exist to support it. In many cases that is by design, as SaaS is valued on tangible ARR, so when Services ARR grows as a proportion of total revenue, it can dilute the overall “quality” of revenue in the eyes of investors. Services valuation multipliers aren’t as strong as product so success in growth terms can weaken a VP of Services position - if services becomes a large percentage of total revenue, the company’s overall valuation multiple gets pulled down. This is problematic.

Companies may respond by trying to minimize services revenue, push delivery to partners too early or underinvest in services capability. This tends to create bigger problems in the form of slower time-to-value, poor adoption and lower retention and expansion.

So in this model, one where Services is treated as a cost center, success is defined by efficiency:

• Maximize utilization

• Minimize delivery cost

• Protect margin

  
  

On the surface, these are sensible goals; in fact they are key to that holy grail of Services ARR. But they carry an implicit and potentially dangerous assumption: services are there to execute, not to create value, even ​​the idea that the product doesn’t deliver value quickly on its own.

And once that assumption takes hold, it shapes everything.

Example:

At the start of the quarter, services leadership is asked to submit their plan. The questions are familiar:

• How many billable hours can you deliver?

• What utilization rate are you targeting?

• Where can you reduce delivery cost?

In speaking to senior members in the Services Delivery Alliance, there is still little tangible measurement around customer outcomes, despite extensive thought leadership pertaining to its importance. These questions don’t ground the conversation on how services might accelerate adoption or influence expansion. Then the plan is approved, not because of the value it is creating, but because of the efficiency it demonstrates.

This shows that the mindset is embedded in how the business asks questions, not just how Services answer them. Then comes the dreaded follow-ups:

“We need to keep services lean”

“Let’s not let delivery slow down the sale”

“Services should just enable the product”

“Can we reduce the cost of implementation?”

None of these are unreasonable on their own. But together, they frame services as something to control, not something to invest in. It’s a signpost to a cost center mindset hidden in the language.

Over time, this way of thinking shapes how services teams operate. Hiring decisions prioritize cost efficiency over capability. Delivery models favour custom work that maximizes billable time, rather than repeatable approaches that reduce it. Investment in tooling, enablement, or productization is hard to justify, because it doesn’t immediately improve utilization or margin.

The result is a team that is optimized to deliver work, but not to evolve how that work is delivered.

The Metrics That Quietly Kill Value

Metrics are not neutral, they don’t just…measure. They drive behaviour, often in ways that aren’t immediately obvious.

Take utilization. It’s one of the most common metrics in services functions, for good reason. It tells the levels at which the team is being used (how effectively they’re being used is another question). But when utilization becomes the primary measure of success, something shifts.

Teams optimize for being busy, but not necessarily for being impactful.

The same is true for billable hours. When time becomes the unit of value, the incentive is to spend more of it. Efficiency, paradoxically, can start to look like underperformance.

Even margin, when viewed in isolation, can be misleading. A relentless focus on cost control often leads to standardization at the expense of customer experience, or underinvestment in innovation and enablement.

Individually, these metrics are useful. Collectively, when over-weighted, they optimize for efficiency over effectiveness.

And that’s where the problems begin.

The Downward Spiral

Once services are measured solely through a cost lens, a predictable pattern emerges.

First, teams optimize for utilization and efficiency. Schedules fill up. Billable hours increase. On paper, performance looks strong.

But beneath the surface, something is lost. There’s less room for innovation. Less focus on outcomes. Less incentive to improve how services are delivered, because improvement often means doing things faster, and billing less. Over time, customer impact starts to suffer with time-to-value stretching, experiences become inconsistent and Services feeling transactional rather than transformative. Then comes the real inflection point: the business begins to see services as low-value.

Budgets tighten. Headcount is scrutinized. Strategic influence diminishes.

Services, having been measured as a cost center, become one. Language used internally often highlights this inflection point. Think “How do we make sure services doesn’t slow this deal down?” instead of “How do we use services to accelerate this customer?”.

​​At the individual level, this shows up in small, everyday decisions.

1. Choosing to extend a piece of work rather than simplify it, because billable time is #1

2. Skipping an internal improvement initiative, because there’s no capacity

3. Repeating a familiar approach, because there’s no incentive to change it

   
   

Over time, these decisions compound. Not because people don’t care, just the system doesn’t reward anything else. Efficiency, without a connection to outcomes, doesn’t elevate services - it erodes them.

What High-Performing Services Teams Do Differently

The most effective services organizations don’t ignore efficiency, but instead treat it as a milestone of a larger picture. They recognize that services sit at a critical intersection: product, customer, and revenue.

And they measure accordingly.

Instead of asking, “How efficiently are we delivering?” they also ask:

• How quickly are customers realizing value?

• How effectively are we driving adoption?

• What role are we playing in retention and expansion?

• How repeatable and scalable are our offerings?

  
  

These teams understand that services are not just a delivery function. They are a lever for growth.

Time-to-value becomes as important as utilization. Customer outcomes matter as much as margin. Repeatability and productization are seen as strategic priorities, not operational nice-to-haves.

Take a SaaS company rolling out a new enterprise customer.

In a cost-center model, Services are brought in post-sale to deliver the implementation as efficiently as possible = on time, on budget, fully utilized.

In a high-performing model, Services are involved earlier. They help shape the scope, define what success looks like, and align delivery to measurable outcomes/adoption milestones, time-to-value, and expansion potential.

The work may look similar on the surface. But the intent, and the impact, is completely different.

Some questions to consider/add to your monthly dashboards:

1. How long does it take new customers to reach first value?

2. What are the adoption levels within the first 30, 60, 90 days?

3. What is the correlation between services engagement and renewal or expansion?

   
   

A good route to “cleaning” this up is productization. We have a playbook on this here.

From Delivery Function to Strategic Lever

When services are measured differently, they behave differently.

They start to accelerate product adoption, not just implement it. They de-risk customer outcomes, reducing churn and increasing lifetime value. They create new revenue opportunities through packaged, repeatable offerings. And increasingly, they enable partner ecosystems to scale delivery beyond the limits of internal teams.

In this model, services are no longer separate from ARR, they are integral to it. But this shift doesn’t happen through intent alone. It requires a change in how success is defined.

Area	Delivery Function (Cost Centre)	Strategic Lever (Growth Driver)
Role in lifecycle	Brought in post-sale	Engaged pre-sale and through expansion
Success definition	Delivered on time, on budget	Customer achieves measurable outcomes
Commercial model	Selling time (hours, days)	Selling outcomes (packages, milestones)
Relationship to product	Implements what’s sold	Shapes how the product is adopted
Impact on revenue	Neutral or cost to recover	Drives retention, expansion, ARR
Scaling model	Add more people	Increase repeatability + partner leverage

From The Services Delivery Alliance (SDA) - The Modern Services Portfolio is moving away from the traditional

A Better Way to Measure Services

The goal isn’t to abandon traditional metrics. Utilization and margin still matter, but they need context.

A more balanced approach looks something like this:

• EfficiencyAre we using our resources well? (Utilization, margin)

• EffectivenessAre we delivering meaningful outcomes? (Time-to-value, adoption, customer impact)

• ScalabilityCan we grow without linear increases in effort? (Repeatability, productization, partner leverage)

  
  

When these dimensions are measured together, services organizations are incentivized not just to deliver, but to evolve.

---

You Get the Services You Measure

Services don’t become strategic by accident.

If you measure them like a cost center, you will get a cost center: efficient, busy, and ultimately undervalued.

But if you measure them as a driver of outcomes, adoption, and growth, they become something else entirely, a critical lever in how your business scales.

The question isn’t whether your services team is performing.

It’s what you’re asking them to optimize for.

If you’re not sure whether your services team is operating as a cost center or a growth lever, use this prompt to find out, and what to do next.

AI Prompt (Copy & Paste)

Act as an expert advisor in professional services strategy for SaaS and technology companies.

I want you to assess whether my services organization is operating as a cost center or a strategic growth lever, and help me reframe it.

First, ask me 8–10 targeted questions to understand:

• How services is measured (metrics, KPIs)

• When services is involved in the customer lifecycle

• How success is defined internally

• The relationship between services, sales, customer success, and product

• How services contributes (or doesn’t) to retention and expansion

• The level of repeatability vs custom delivery

• How leadership talks about services (language used)

Then:

1. Diagnose whether the organisation is operating as:

   • Cost center

   • Value enabler

   • Strategic growth lever

2. Explain the key gaps holding it back, based on my answers

3. Show me how these gaps are connected to how services is currently being measured

4. Recommend a new measurement model across:

   • Efficiency (e.g. utilisation, margin)

   • Effectiveness (e.g. time-to-value, adoption)

   • Scalability (e.g. repeatability, productisation, partner leverage)

5. Give 3–5 practical changes I can make in the next 90 days to move toward a strategic model

6. Suggest how I should reframe the role of services in internal leadership conversations (including example language I can use)

   
   

Be specific, practical, and grounded in real-world SaaS services organisations. Avoid generic advice.