Phase 2 of 10 · Decide

The business case

Why should the board approve this, and why now?

The big picture

GCC proposals rarely die because the economics are wrong. They die because the case speaks the wrong language. Executives approve investments that fit where the business is going, presented by people they trust, with risks named rather than hidden.

The decisions that matter

  • The business problem the GCC solves, in the CEO’s language
  • The single primary value thesis: cost, capability, speed or scale
  • How honestly to model the transition dip and the ramp to steady state
  • What exactly you ask for now, and what you ask for later

What good looks like at the end

  • A five-layer business case
  • A three-year financial model with sensitivity at 80% and 60% of projected savings
  • Three to five named risks with owners and mitigations
  • A specific, staged decision request with a date and budget

Who owns it

The sponsor, with Finance and the programme lead

When

After the mandate. The first approval is usually to proceed to detailed design, not to the full programme.

The five-layer business case

  1. Strategic fitWhy this investment fits the business’s three-year direction. Written in the CEO’s language, not the CFO’s.
  2. Value thesisOne primary driver (cost, capability, speed or scale), supported by secondary benefits. Do not lead with all four.
  3. Financial modelThree-year impact including set-up costs, the transition dip, the productivity ramp and steady-state savings, with sensitivity at 80% and 60% of projected savings.
  4. Risk and mitigationThree to five named risks (execution, talent, adoption) with explicit mitigations, owners and the residual risk.
  5. Decision requestA specific ask with a specific timeline: approval to proceed to detailed design, not approval of the final operating model.

What specialist advisers say

Curated from published work by Everest Group and HFS Research. Summarised in our own words; follow the link for the full piece.

In detail

The approach

  1. Answer three plain-language questions first

    What business problem does the GCC solve? Why now? What does success look like in three years, and how will we know?

  2. Build the model with the dip in it

    The first year rarely runs at full productivity while work is transferred and teams are trained. Show the dip, show the ramp, and show the case still works. It strengthens credibility.

  3. Price the hard-to-quantify value

    Treat talent access, speed to scale and continuous improvement as labelled upsides with conditions, priced as avoided delay or the cost of the alternative.

  4. Price the risks

    Cover execution risk, talent risk and adoption risk. Each gets a named mitigation and an owner, not a dismissive sentence.

  5. Pre-sell before you submit

    Hold one-to-one conversations with each decision-maker and the business unit leaders who fear losing control. Nobody should first hear the proposal in the committee room.

  6. Present in twenty minutes

    Recommendation and decision first, then the three strongest reasons, the headline numbers, the risks, and the ask. Everything else goes in the appendix.

Readiness signals

The signs that need attention before a centre moves on from this phase.

  • The strategic problem can be stated in two sentences without mentioning cost
  • The model includes the transition dip and still works at 60% of projected savings
  • Each named risk has a mitigation and an owner
  • The likeliest opponent’s concern is addressed in the main presentation
  • The ask is staged, with a budget, a date and the next decision point

Where organisations go wrong

  • Leading with labour arbitrage numbers

    What works: Lead with the business problem; savings are the proof, not the proposition.

  • Linear productivity from day one

    What works: Model the dip honestly. Anyone who has run a transition will spot its absence.

  • Asking for everything at once

    What works: Ask for approval to proceed to the next stage, with a stage-gate review.

  • Treating the people impact as a footnote

    What works: Tell the onshore story deliberately; it shapes both approval and execution.

Questions for leadership teams

  • Can the problem this GCC solves be described in the CEO’s language, without mentioning cost?
  • Who in the approval chain is most likely to resist, and has their concern been addressed directly?
  • Is the request for final approval, or for approval to proceed to the next stage?

Read more