Shared Services Is a Strategy, Not a Cost Centre

The framing that kills shared services teams isn’t a reorganisation or a budget cut. It’s a label. “Cost centre” is a category of accounting, but it functions as a category of perception — and once leadership thinks of your team as overhead, every conversation about resources, headcount, and investment starts from the wrong baseline.

I’ve led shared services functions serving seven internal business lines. The question I get most often from peers in similar roles isn’t about technology or process — it’s about positioning. How do you make the case for investment in a team whose outputs are largely invisible when everything is working? How do you compete for budget against Sales, which can show a revenue number, or Engineering, which can show a shipped feature?

The answer isn’t to rebrand the function or produce a glossy internal pitch deck. It’s to change what you measure and how you report it. A shared services team that reports on activity — tickets closed, BRDs written, dashboards built — looks like overhead. A shared services team that reports on outcomes — revenue decisions enabled, process time reduced, data quality improved — looks like infrastructure. Infrastructure gets invested in. Overhead gets cut.

“Shared services teams that report on activity look like overhead. Teams that report on outcomes look like infrastructure. Infrastructure gets invested in.”

The Positioning Problem Is a Measurement Problem

The root cause of the cost-centre perception is almost always measurement. Shared services teams default to reporting what’s easy to count: volume metrics. Tickets closed. Projects completed. Dashboards delivered. These are real outputs, but they don’t tell the story of impact — and in a resource allocation conversation, impact is the only story that matters.

The shift requires identifying the business outcomes that your team’s work enables, and then building the reporting layer that makes those outcomes visible. This isn’t spin. It’s accuracy. If your BI team built the dashboard that Sales uses to identify at-risk accounts, the revenue retained through those interventions is a downstream outcome of your team’s work. If your BA team wrote the BRD for the automation that eliminated 15 hours of manual Finance reconciliation per week, that efficiency gain is an outcome of your team’s work. The connection is real — it just requires deliberate measurement to make it legible to leadership.

The maturity model for shared services organisations, as described in Harvard Business Review, moves through three stages: from transactional (execute requests), to advisory (shape requirements), to strategic (drive capability). The positioning challenge is almost always about moving from transactional to advisory — and the measurement layer is what makes that transition visible to the business.

Four Things to Start Measuring

The Executive Reporting Layer

Changing what you measure only matters if you change how you report it. The mistake most shared services leaders make is reporting to their own manager, in their manager’s format, using operational language that doesn’t translate to C-suite conversations.

The executive-level shared services report has three components. First, outcomes delivered this period — in business language, not operational language. Not “seven dashboards completed” but “Sales now has live pipeline visibility they were previously building manually, estimated at 12 hours per week.” Second, current capacity and commitments — what the team is working on, what’s committed for next quarter, and what’s in the backlog waiting. Third, the ask — what investment, decision, or removal of blocker would increase the team’s impact in the next period.

The ask is the part most shared services leaders leave out. A team that reports outcomes without making an ask is providing information. A team that reports outcomes and then makes a specific, evidence-based request for resources, tools, or access is behaving like a strategic function. That distinction matters more than the content of the report itself. You can see this framing in how the M&A integration workstream at AudienceView was positioned — outcomes first, then the resource requirement those outcomes justified.

When the Reframe Doesn’t Stick

Sometimes the cost-centre framing is structural, not perceptual. If shared services reports through Finance as a support function rather than through Operations or Technology as a capability function, the budgeting model will keep producing the same pressure regardless of how well you report outcomes. That’s a harder problem — it requires a conversation about reporting lines, not just measurement frameworks.

But even in structurally challenging situations, the measurement and reporting shift creates the evidence base for that conversation. It’s difficult to argue for a reporting line change without a track record of strategic contribution. It’s much easier once you have four quarters of documented outcome data showing that the team’s work enabled revenue, reduced cost, and supported strategic priorities.

The teams that prove shared services is a strategy get the budget to act like one. The teams that don’t — that stay in the transactional, ticket-closing, activity-reporting posture — get outsourced or restructured the next time the business needs to find savings. The measurement framework is the strategic choice. For more on what this looks like from a customer-facing operations perspective, CXMaster.biz covers the same strategic positioning challenge for CX leaders.