Shared Services Operations
Shared services consolidates support functions that historically lived inside business units (finance, HR, procurement, IT, legal ops, customer service) into a single internal entity that serves all BUs at lower unit cost via scale, standardization, and specialization. The model emerged in the late 1980s — Ford and Baxter were early adopters, but General Electric's GE Capital Services in the early 1990s and Shell's pioneering finance shared services centers in the late 1990s established the playbook. The economic logic is clear: 8 mid-size BUs each running their own 5-person AP team (40 FTEs total) can be replaced by a single 22-FTE center that serves all 8, with better controls and consistent reporting. By 2024, ~80% of Fortune 500 companies operate some form of shared services or 'Global Business Services' (GBS) model, and the global GBS market exceeds $200B in addressable spend (Hackett Group). The mature evolution is the 'Tower' model: each function (Finance, HR, IT, Procurement) operates as a distinct tower with its own SLAs, leadership, and chargeback model.
The Trap
Treating shared services as a cost-cutting exercise, not an operating-model redesign. The classic failed implementation: pull AP, AR, payroll, and procurement out of 6 BUs, dump them in a low-cost city, and announce a 25% headcount reduction. Six months in, BU CFOs complain that 'shared services doesn't understand our business,' BU controllers maintain shadow teams to do the work the SSC was supposed to do, and total cost goes UP because you now have central + shadow capacity. The mechanism: shared services only delivers savings when work is actually standardized BEFORE consolidation. If each BU has different invoicing rules, different approval workflows, different vendor master data, the SSC inherits all the variation and can't extract scale. Second trap: governance collapse. Without a clear chargeback model and SLA framework, BUs treat the SSC as a free internal vendor and over-consume. Third: location strategy mistakes — picking a low-cost city without a deep enough talent pool means 60% attrition and constant rework.
What to Do
Run shared services in three sequenced phases: (1) STANDARDIZE — before any consolidation, redesign the process to a single 'best-of' standard across all participating BUs. Resolve 80% of the variation BEFORE moving any FTEs. (2) CONSOLIDATE — move the standardized work into the SSC location with a deliberate location strategy (talent depth + cost + timezone overlap). Use 'lift and shift' only for the final transition step, never for the redesign step. (3) OPTIMIZE — once consolidated, layer in automation, self-service portals, and continuous improvement. Set up a Service Level Agreement (SLA) per service line with quarterly reviews; install a chargeback model so BUs see the cost of consumption (and have skin in the game on demand reduction). Govern with a 'BU Council' that has actual authority — not advisory only.
Formula
In Practice
Shell's finance shared services journey (begun 1999) is the textbook case. Pre-SSC: ~5,500 finance FTEs distributed across 90+ countries, each with bespoke processes. By 2010 Shell had consolidated to ~3,500 FTEs in five global SSCs (Krakow, Manila, Chennai, Glasgow, Kuala Lumpur), with cost-per-transaction down 40%+ and substantially improved controls. Critically, Shell did the standardization work first — three years of process simplification before the major consolidation moves. General Electric's GE Capital Services pioneered shared services in the early 1990s, and Jack Welch credited the SSC model with hundreds of millions in annual savings during the GE conglomerate era. By contrast, when companies skip the standardization step, results are predictably bad: a 2015 Hackett study found that 35-40% of first-generation shared services implementations failed to deliver promised savings, primarily due to insufficient standardization and shadow-team persistence in BUs.
Pro Tips
- 01
Set the BU 'shadow team' metric explicitly: track post-consolidation what the BU still spends on the function that was supposedly moved. Healthy ratio: shadow cost < 5% of SSC cost. If shadows exceed 15%, you didn't actually consolidate; you created a redundant layer.
- 02
Use the 'Three Curves' framework for SSC business case: (a) lift-and-shift labor arbitrage gives you the first 15-25% savings in year 1-2, (b) standardization + process redesign delivers the next 15-25% in year 2-4, (c) automation and self-service portals deliver the final 15-25% in year 3-6. If your business case promises 50% in year 1, it's wrong.
- 03
Pick SSC locations based on 5-year talent depth, not year-1 cost. Krakow, Manila, Chennai, Mexico City, Costa Rica all became saturated talent markets after early movers — late entrants face wage inflation and attrition. Tier-2 cities (Lodz, Cebu, Coimbatore, Bogota) often offer better long-term economics.
Myth vs Reality
Myth
“Shared services is the same as outsourcing”
Reality
Shared services keeps the work in-house under your direct management, just consolidated to one location. Outsourcing transfers the work to a third party. The economics differ: SSCs preserve institutional knowledge and control, outsourcing prioritizes labor arbitrage. Many mature operators run a hybrid: captive SSC for core/sensitive work, BPO for true commodity work.
Myth
“All transactional work should be in shared services”
Reality
Some 'transactional' work is actually deeply business-context-dependent. AP for a manufacturing BU with thousands of small vendors is genuinely different from AP for a SaaS BU with 50 enterprise vendors. Forcing both into a single SSC process produces either generic processes that serve neither well, or 'standard with exceptions' that recreates the variation you tried to eliminate.
Try it
Run the numbers.
Pressure-test the concept against your own knowledge — answer the challenge or try the live scenario.
Knowledge Check
Your CFO mandates a shared services center for finance — promising 30% cost reduction in year 1 by lift-and-shifting AP, AR, GL, and payroll from 7 BUs to a single low-cost city center. What's your highest-priority concern?
Industry benchmarks
Is your number good?
Calibrate against real-world tiers. Use these ranges as targets — not absolutes.
Shared Services Cost Reduction (vs. distributed baseline)
Finance, HR, Procurement shared services centers — Fortune 1000 benchmarksBest in Class (mature SSC)
40-60%
Good (year 3-4)
25-40%
Average (year 1-2)
10-25%
Underperforming
< 10%
Source: Hackett Group / Deloitte Global Shared Services Survey 2023
Real-world cases
Companies that lived this.
Verified narratives with the numbers that prove (or break) the concept.
Shell
1999-2010+
Shell consolidated finance from ~5,500 distributed FTEs across 90+ countries into five global shared services centers (Krakow, Manila, Chennai, Glasgow, Kuala Lumpur). Critically, the standardization phase ran for ~3 years before major consolidation moves — Shell rebuilt processes onto a single 'best-of' standard before relocating work. The result by 2010+: ~3,500 finance FTEs (a 36% reduction), cost-per-transaction down 40%+, dramatically tighter controls, and reporting that produced a single global view of financial performance for the first time in Shell's history. Shell's SSC playbook became a template studied by other supermajors and is referenced in most major consulting SSC methodologies.
Pre-SSC Finance FTEs
~5,500
Post-SSC Finance FTEs
~3,500
Cost-per-transaction Reduction
40%+
Standardization Phase
~3 years before consolidation
Shell's success is the standardization-first sequence. Most failed SSC implementations skip this step. The savings curve is real but back-loaded — years 1-2 are about the structural move, years 3-5 are when the productivity and automation gains compound.
GE Capital Services
1990s
Under Jack Welch, GE pioneered the shared services model in the early 1990s. GE Capital Services consolidated finance, HR, and procurement support across the conglomerate's many businesses (aviation, healthcare, energy, financial services, plastics) into central centers. The savings ran into hundreds of millions annually. More importantly, GE used SSCs as a strategic platform for Six Sigma rollouts — once processes were consolidated, they could be measured and improved with statistical rigor that was impossible across distributed BU operations. GE's success made shared services a default operating-model recommendation in McKinsey, Bain, and BCG playbooks for the next two decades.
Annual Savings (peak GE Capital era)
Hundreds of millions
Functions in Scope
Finance, HR, Procurement, IT
Industry Influence
Defined the SSC playbook adopted by F500
Shared services compounds with other operating-model investments. GE didn't just save money — they used the consolidated platform as the foundation for Six Sigma, which is where the real strategic value emerged. SSCs without continuous improvement become stagnant cost centers; SSCs with CI become engines of compounding productivity.
Related concepts
Keep connecting.
The concepts that orbit this one — each one sharpens the others.
Beyond the concept
Turn Shared Services Operations into a live operating decision.
Use this concept as the framing layer, then move into a diagnostic if it maps directly to a current bottleneck.
Typical response time: 24h · No retainer required
Turn Shared Services Operations into a live operating decision.
Use Shared Services Operations as the framing layer, then move into diagnostics or advisory if this maps directly to a current business bottleneck.