A Practical Approach to Sizing Installed Base Revenue

The industry no longer needs convincing that installed base is a real revenue driver. For any OEM, service contracts, parts, upgrades, and lifecycle services sitting inside their existing customer base are broadly accepted as one of the highest-margin, lowest-acquisition-cost opportunities available. What’s far less discussed is a credible approach to sizing installed base revenue in a way that holds up once someone scrutinizes it. A number built on the wrong assumptions can cost an OEM credibility with the leadership team they’re trying to convince.

Installed base revenue draws from a consistent set of sources, whether an organization tracks them deliberately or not:

What Sizing the Opportunity Actually Requires

Most first attempts at sizing installed base revenue apply one serviceable addressable market (SAM) model uniformly with a single calculation per business type, extended across the whole portfolio. This works fine when a business genuinely operates as one uniform unit. It breaks down the moment a “business type” turns out to contain several distinct businesses inside it, each with its own customer profile, contract structure, and service economics.

Getting this right isn’t about finding a smarter formula. It’s about being willing to segment further than the org chart initially suggests and using the most granular data available even when that means redoing the calculation more than once.

What’s at Stake When the Number Is Off

An inflated estimate rarely survives contact with execution. It sets expectations leadership will hold the service organization to, and when the real, addressable number turns out to be a fraction of what was first presented, the credibility cost lands on whoever owns the number, not on the model that produced it.

A deflated estimate carries a quieter but equally real cost: genuine opportunity gets under-resourced or deprioritized because the business case looked too small to act on. Both failure modes trace back to the same root cause: a sizing exercise that didn’t go granular enough before the number left the room.

A Case in Sizing

I worked on a project with a diversified manufacturer spanning several distinct business units such as industrial automation, building solutions, and energy and sustainability among them. Like most organizations at that scale, each unit had its own service records, warranty databases, and sales histories, with no single consolidated view of the installed base.

The first sizing pass used an Addressable Market model built by business type that had one calculation for process automation, another for building automation, and so on. It produced a striking headline number.

However, the number did not survive scrutiny. Process automation wasn’t one business, it was three, each with a different customer profile and service economics that a single calculation couldn’t represent.. Splitting the model down to that level closed the first gap. Then came a second correction: several of the more mature business units had service-line level data available, and recalculating at that granularity revealed that a portion of what had been counted as opportunity was already covered or overstated at the coarser level.

By the time both corrections were made, the number had come down substantially from where it started.

A Practical Approach to Sizing It Right

Once the segmentation problem is solved, the actual sizing work comes down to systematically checking a handful of categories against real data, rather than assuming coverage or opportunity uniformly across the whole base. Installed Base Coverage itself is worth tracking as its own ongoing metric, not just a one-time sizing input.

Category	What to Check	Data Needed
Service contracts	Which assets are under-covered or approaching renewal	Contract records tied to asset ID
Parts & consumables	Usage patterns against installed base size	Parts sales history by asset/segment
Upgrades & retrofits	Assets nearing end-of-life or eligible for upgrade	Asset age, lifecycle stage
Obsolescence & replacement	Assets with discontinued support	Product lifecycle status
Remanufacturing	Assets suitable for refurbishment programs	Condition/usage data
Data-driven services	Assets with usage data enabling new service models	Telemetry or usage logs, where available

None of these categories require perfect data to start. They require honesty about which ones you can size with real data today, and which ones you’re still estimating, and being clear about that difference when you present the number.

Where This Fits: From Visibility to Revenue to Execution

Sizing the opportunity accurately assumes you can see your installed base clearly in the first place, which for many manufacturers is its own unresolved problem. For more details on this, see Why Installed Base Management Still Fails in Manufacturing.

And a well-sized number is only the beginning. Even accurately identified opportunities routinely stall once they’re handed to a sales organization built for large, infrequent deals rather than the higher-volume, lower-value transactions lifecycle revenue often looks like as covered in The $10M Junk Folder: Why Installed Base Revenue Is Lost.

Sizing the opportunity, seeing the installed base clearly, and building the commercial mechanism to act on it are three distinct problems. Solving only one rarely moves the needle on its own.