Shared services are the most powerful and most misunderstood part of organizational finance. Every organization of meaningful size has them. Finance, HR, IT, compliance, facilities, legal, executive leadership, board governance. They exist because consolidating these functions is more efficient than duplicating them across programs and departments. They consume a significant portion of the operating budget, often thirty to fifty percent in mature organizations. And the way their costs flow into program-level financials determines whether your strategic decisions are being made on accurate intelligence or on systematic distortion.

In most organizations, the distortion wins. Not because anyone is doing anything wrong, but because shared services consumption is genuinely hard to measure, and the methodologies used to allocate their costs are almost always proxies that don't reflect actual consumption. The distortion is invisible from the financial reports. It's only visible when you trace specific decisions back to the cost data they were made on, and ask whether the cost data was true.

Here's the structural dynamic. Shared services produce value across the organization, but the consumption patterns are dramatically uneven. The CFO's attention isn't distributed evenly across programs. It concentrates on programs with complex funding requirements, regulatory exposure, or active strategic decisions. The compliance function doesn't allocate equally across programs. It concentrates on programs with the highest regulatory complexity. The IT function doesn't serve all departments equivalently. It directs more capacity toward departments running specialized systems, undergoing major implementations, or generating the most support tickets. HR doesn't distribute uniformly. It concentrates on departments with high turnover, complex compensation structures, or active hiring cycles. Every shared service has consumption patterns that are measurably uneven, and the allocation methodology has to capture that unevenness to produce accurate cost intelligence.

Most allocation methodologies don't capture it. They use proxies. Headcount. Square footage. Percentage of direct cost. These proxies are administratively clean and operationally inaccurate. They distribute shared service costs across programs in patterns that have only loose correlation to actual consumption. The resulting program-level cost numbers look authoritative and are systematically wrong, in directions that vary by program and by shared service.

The decisions made on top of this distorted intelligence are where the damage shows up.

Pricing decisions go wrong because the cost basis underneath them is wrong. A fee-for-service program priced based on a cost calculation that under-allocates shared service consumption produces margin that's smaller than it appears. A program priced on cost data that over-allocates shared service consumption either prices itself out of the market or generates margin the organization doesn't realize it's earning. Either way, the pricing strategy is built on a foundation that doesn't reflect the actual cost of delivery.

Investment decisions go wrong because program profitability analysis is distorted. Leadership looks at program-level financials, identifies the strongest performers, and directs investment accordingly. The strongest performers on the financial reports may not be the strongest performers operationally. They may be programs that are absorbing under-allocated shared service consumption, which makes them look more profitable than they are. The investment goes to the wrong place. The organization expands programs that aren't structurally as strong as they appear, while underinvesting in programs that are bearing more shared service load than the allocation reflects.

Strategic decisions about scaling, contracting, or restructuring go wrong because the cost intelligence underneath them is wrong. An organization considering whether to expand a program needs to know what it actually costs to deliver. An organization considering whether to consolidate or eliminate a program needs to know what shared service capacity will be released, and whether that capacity translates to actual cost reduction. Most allocation methodologies can't answer these questions cleanly, because the methodologies don't track shared service consumption at the level of operational detail the decisions require. The strategic analysis gets done on cost data that's directionally suggestive and structurally unreliable.

Indirect cost recovery goes wrong because the rate calculation rolls up from the same allocation methodology. A rate built on cost data that doesn't reflect actual shared service consumption produces recovery that doesn't match what the organization actually spends. The recovery either understates the cost (more common) or overstates it (creates audit risk). In either case, the rate isn't doing what it's supposed to do, which is reimburse the organization for the actual cost of administering the funded programs.

Negotiations with funders go wrong because the cost defense is weak. Funders increasingly request detailed cost analysis, especially for large or strategic awards. An organization that can't defend its cost structure with operational specificity loses leverage in those negotiations. It accepts rate caps, cost limitations, and budget structures that wouldn't hold up if the organization could clearly demonstrate the actual cost of delivery. The negotiating disadvantage compounds across the funding portfolio.

The cumulative effect of shared services distortion is that the organization is operating on cost intelligence that's wrong in ways no one can fully see, and making strategic decisions on that intelligence as if it were accurate. The decisions that result aren't catastrophic. They're suboptimal. The organization loses ground at the margins, year after year, in pricing, investment allocation, strategic positioning, and cost recovery. The losses don't show up as a line item. They show up as performance that's slightly below what the organization should be capable of, with no clear cause.

The fix requires treating shared services consumption as something to be measured, not estimated. Activity-based methodologies that track actual consumption of shared services by the programs and departments they support. Service-level frameworks that define what shared services produce and allocate based on documented delivery. Effort tracking for the personnel-intensive shared services like finance, HR, and compliance. Cost driver analysis for the asset-intensive shared services like IT and facilities. The infrastructure required to do this is more demanding than headcount allocation. It produces cost intelligence that survives operational scrutiny, supports defensible negotiations, and allows leadership to make strategic decisions on data that reflects reality.

Most organizations won't do this work because the existing allocation passes audit, the existing methodology produces numbers, and the cost of building better infrastructure feels disproportionate to the visible benefit. The visible benefit is small because the cost of bad allocation is invisible. The invisible cost is enormous, and it compounds across every decision made on top of the distorted cost data. The organizations that recognize this stop treating shared services allocation as an accounting question and start treating it as a strategic discipline.

If your shared services are consuming thirty percent or more of your operating budget, and you can't tell me with operational confidence which programs are consuming what proportion of which services, your strategic decisions are being made on cost intelligence that's structurally compromised. The decisions still get made. They just get made worse than they should.