Cracking the Code on Profitable Service Contract Growth

Service contracts and extended warranties are growing as a share of the aftermarket revenue mix — and for good reason. They offer customers more predictable costs and service organizations a more reliable revenue stream. What the conversation at a recent Service Council™ IdeaShare™ made clear is that pricing those contracts profitably is the code that many have yet to crack.

According to Service Council’s research, growth has become the number one mandate for service leaders in 2026, displacing efficiency for the first time in years. Contracted service agreements are central to that ambition.

But ensuring that contracted revenue translates into profit relies on the ability to model cost and risk across the life of the agreement, from asset reliability and parts availability to customer behaviour and labor capacity. For most organizations, that picture is incomplete at best.

Without it, many contracts end up costing more to deliver than they earn.

What Works on Paper Doesn’t Work in Practice

Only one participant said they could consistently predict contract profitability before signing. For most, it was 'sometimes'. That’s no surprise.

When asked how much of their contract pricing remains spreadsheet-driven, the majority of participants said more than 50% — and nearly half said more than 75%. Spreadsheets work just fine at calculating historical averages, but what they can't do is model how factors such as parts cost volatility, customer usage patterns, and asset age shift and interact across a multi-year agreement.

As one participant shared, that means product family, and sometimes geography, end up being the primary basis for cost estimation, because the effort required to incorporate anything more granular is simply too high.

When Every Quote Becomes a Debate

Without that foundation, the gap gets filled by people — too many according to most of the participants. As one put it, “you end up getting paper-locked by trying to reach consensus.”

When there's no shared data foundation, that consensus becomes the substitute for confidence. It also takes time.

In one of the polls during the session, quoting speed came out as the top concern when it comes to service contracts. In many cases, that forces a choice between putting a deal at risk by taking too long to quote or pricing it on assumptions that haven’t been tested. It also creates the conditions for unwanted sales behavior such as discounting to close, or bundling extended warranties rather than pricing them properly. One participant described a sustained effort to stop their sales team using service as a concession on equipment deals.

Ultimately, speed and pricing confidence are both products of the same thing — having the right data, integrated and accessible at the moment a quote is being built.

How Contract Design Shapes Behavior

Customer behavior is one of the most significant variables in contract profitability, and one that the contract design itself can either manage or make worse.

All-in contracts carry higher earning potential, but the range of outcomes is wide. Removing the customer's financial exposure to consumption also removes their incentive to manage it. In some cases, that means that what looked profitable at signing starts to look very different in delivery.

A lighter model — one participant described a health-check approach in the machine tool space, where a technician visits, assesses the asset, flags what needs attention, and schedules follow-up work — trades some of that upside for more predictable margins. The customer retains some skin in the game, the service organization stays close to the asset, and problems get caught before they become expensive.

The choice between contract models is ultimately a risk/reward decision that depends on the customer, the asset, and the organization's appetite for risk. But that appetite is dependent on understanding the risk — and that requires data that most organizations aren't yet integrating into contract pricing.

Why History Doesn’t Help

Unsurprisingly, given the macroeconomic environment, parts cost volatility came through as the dominant source of contract risk. Most organizations are working from historical consumption trends, adjusted upward by some assumption about inflation. But static contract pricing models and dynamic cost environments are a bad combination.

Unlike production components, which sit within a deeper BOM that can absorb cost increases across multiple inputs, in service, the part itself is the product. That means there’s nowhere to hide.

Add in low and unpredictable demand volumes, growing obsolescence risk as assets age, and limited supplier leverage and the cost structure of a service contract can shift significantly over its lifetime.

Unless a service contract is designed from the start with the flexibility to accommodate parts cost changes, either through terms that allow for price adjustments or at renewal, that’s a margin risk that most companies currently have no way to mitigate.

Turning Delivery History into Better Pricing

With more delivery history, better asset data, and a clearer picture of how the customer actually uses the service, renewals should, in theory, be where contract pricing gets easier.

In practice, that only happens if what was learned during delivery makes it back into the next commercial decision. One participant described estimating the hours, setting the schedule, doing the due diligence — and then the technician arrives at the customer's plant to find a very different reality. The organization has real data on cost, usage, and which assumptions were optimistic, but if that data lives in field engineers' notes or disconnected service records, the renewal gets built on the same foundation as the original contract.

Another participant offered a practical response to this: on product lines where contract performance was variable, they increased visit frequency, accepting a small margin reduction in exchange for earlier visibility into problems. It worked, but it's a workaround for a data problem, not a solution to it.

The Risk Behind the Revenue

The poll on contract KPIs was perhaps the most revealing moment of the session. While revenue and margin dominate executive attention, risk exposure barely registers, and where it does, it gets addressed after a contract underperforms rather than being managed from the point of pricing.

One participant was candid about why: the pressure to grow top-line service revenue in their organization is so intense that risk and margin are effectively seen as problems to solve later. Although that’s an understandable response to the environment, it’s also how contracts end up driving the top line and simultaneously damaging the bottom one.

And if risk exposure isn't being tracked as a metric, the investment case for building the data foundation that would make pricing more accurate, more confident, and faster simply can’t be made.

From Uncertainty to Opportunity

Pricing service contracts well is ultimately a data problem. The inputs that determine whether a contract is profitable exist in most organizations — asset condition, parts cost trajectory, customer usage patterns, labor requirements — but they sit in separate systems, owned by separate teams, in a form that isn't accessible or integrated at the moment a quote is being built. Connecting those inputs is the operational shift that makes the commercial ambition achievable.

Gerardo Pelayo closed the session with the provocation that uncertainty isn't the enemy — it's where the opportunity lives. The organizations that crack the code can take on more risk with more confidence — extending contract durations, offering bolder service packages, and building the kind of profitable recurring revenue base that the growth mandate demands.