What does cost to serve mean in shared services?

It is the full cost of supporting one business unit, every transaction, exception, urgent request and ticket it generates, on top of standard processing. A flat per-unit charge ignores most of it.

How do you calculate cost to serve per business unit?

Build a capacity cost rate for each resource group and time equations for each activity, then assign by the actual volume and complexity each business unit generates, not by a flat average.

Why do two business units of the same size cost different amounts to serve?

Because exceptions, urgency and service mix are uneven. A clean, on-cycle unit costs far less than one that generates exceptions, corrections and off-cycle requests.

How can a shared services centre lower cost to serve?

Surface the cost-to-serve spread, fix the upstream behaviour driving exceptions and urgency, promote self-service, and re-price the work that breaks capacity planning.

Shared Services · Go deeper

Shared services cost to serve: two business units, same size, very different cost.

A shared services centre serves internal customers, the business units, the same way an external provider serves clients. And just like external clients, two internal units of identical size can cost wildly different amounts to serve. One sends clean, batched, on-cycle work; the other sends a constant trickle of exceptions, urgent requests and corrections. A flat per-unit cost flattens that difference completely. Cost to serve, built activity by activity, rebuilds it.

Take the Profit Check Book a scoping call

Cost and Profitability Consulting · 150+ models since 2010 · TDABC

In short

Shared services cost to serve is the full cost of supporting one business unit, every transaction, exception, ticket and ad-hoc request it generates, not a flat per-unit charge. It can vary two to three times between units of the same size because complexity, exception rates and service mix land unevenly. TDABC assigns each activity to the internal customer that consumed it, so the centre sees which business units are genuinely cheap to serve and which absorb disproportionate capacity.

2-3x

spread in cost to serve between units of the same size

Exceptions

cost several times a clean transaction, and cluster on a few units

Self-service

adopters cost less, and a flat charge never credits them

01The cost pain points

A flat per-unit cost hides a two-to-three-times spread.

Two units of the same revenue or headcount can cost very different amounts to serve once exceptions, urgency and service mix are counted. The average tells the centre nothing useful, and worse, it rewards the units that are expensive to serve and penalises the ones that behave.

The flat cost hides the spread

Same size, very different cost once exceptions, urgency and service mix are counted. The average is no basis for a decision.

Exceptions are the silent cost

A clean invoice costs little; an exception that needs investigation, escalation and a correction costs several times more. Exception-heavy units are expensive even at modest volume.

Urgent work breaks capacity planning

A unit that routinely demands rush or off-cycle runs consumes standby capacity and interrupts batched work, raising real cost to serve well above its transaction count.

Self-service adopters cost less

Units that adopt portals, standard templates and on-cycle submission are genuinely cheaper to serve. Without a cost-to-serve view, that good behaviour is invisible and unrewarded.

The same pattern plays out with external clients in IT services, where the account that calls constantly is cheap to bill and expensive to keep, and in professional services, where a demanding client can cost several times more to serve at the identical rate.

COST TO SERVE: TWO UNITS, SAME SIZE

Illustrative. Same size, two to three times the cost to serve, with the whole difference sitting in the exception and urgency tail, not the standard volume.

02How TDABC applies

Cost to serve a unit is the sum of what it generates.

Each activity a business unit generates, times the capacity cost rate, plus its fair share of standby capacity. Run the same logic per unit and the real cost-to-serve spread appears, often two to three times between units the chargeback had treated as equal.

Cost to serve a business unit =
    (standard transactions x cost per standard transaction)
  + (exceptions           x cost per exception, typically several x a standard one)
  + (urgent / off-cycle    x premium handling cost)
  + (tickets and queries   x cost per interaction)
  + (onboarding / offboarding events x cost per event)
  + allocated share of true standby / fixed capacity

Illustrative. The exception term carries several times the cost of a standard transaction, which is why exception-heavy units pull away.

03Where the cost hides

In the exception and urgency tail, not the headline volume.

As an illustrative sector pattern, a GBS organisation that built cost to serve per business unit found a cluster of units whose transaction counts looked average but whose exception and rush-request rates made them the most expensive to serve in the group. The answer was rarely to cut service, it was to fix the upstream behaviour, standardise the submissions and re-price the urgent work, so the cost to serve fell where it was being created.

For the full method, see our guide to cost to serve.

Frequently asked questions

What does cost to serve mean in shared services?: It is the full cost of supporting one business unit, every transaction, exception, urgent request and ticket it generates, on top of standard processing. A flat per-unit charge ignores most of it.
How do you calculate cost to serve per business unit?: Build a capacity cost rate for each resource group and time equations for each activity, then assign by the actual volume and complexity each business unit generates, not by a flat average.
Why do two business units of the same size cost different amounts to serve?: Because exceptions, urgency and service mix are uneven. A clean, on-cycle unit costs far less than one that generates exceptions, corrections and off-cycle requests.
How can a shared services centre lower cost to serve?: Surface the cost-to-serve spread, fix the upstream behaviour driving exceptions and urgency, promote self-service, and re-price the work that breaks capacity planning.

Go deeper

Start here

See which units are cheap to serve, and which absorb your capacity.

The Profit Check takes 12 to 15 minutes and no data upload. It points to where your cost-to-serve spread is most likely hiding, and what fixing it upstream is worth.

Fee: Fixed, agreed before we start
Duration: 3 to 5 weeks
Your time: 2 to 4 hours in total
Access: No ERP access, no lock-in

Start with ProfitAudit 360 Take the Profit Check

Proof

A distributor in New Zealand. €1.335M of cost-to-serve made visible, then halved, and 830 loss-making customers brought down to 295.

Read the case study →

Who you would be talking to

Miguel Guimarães, Founding Partner

Cost and profitability practitioner for 25+ years. Presented the Damco cost-to-serve case at Managing for Profit (Amsterdam RAI, December 2009), on the same programme as Robert S. Kaplan.

Call +351 910 313 731

Shared services cost to serve: two business units, same size, very different cost.

A flat per-unit cost hides a two-to-three-times spread.

The flat cost hides the spread

Exceptions are the silent cost

Urgent work breaks capacity planning

Self-service adopters cost less

Cost to serve a unit is the sum of what it generates.

In the exception and urgency tail, not the headline volume.

Frequently asked questions

Stop billing by headcount, start billing by use

One cost rate, a time equation per transaction

Cost to serve, the core method

See which units are cheap to serve, and which absorb your capacity.

Keep exploring

Whale Curve Analysis

Cost-to-Serve

Case Study: NZ Distributor

Not sure where you fit?