Lesson 6 of 6
Winning sponsorship
9 min
Listen to this lesson
A good case can still fail if it reaches the wrong people in the wrong order. Sponsorship is built before the meeting, not in it. This lesson covers who to win, how to structure the pitch, the objections you will hear, and the success measures that keep the sponsor on your side after the money is approved.
Who has to say yes
| Stakeholder | What they care about | What to show them |
|---|---|---|
| CIO (sponsor) | Stable releases, predictable cost, credibility with the business | Demand forecast, cost of quality, the release rule |
| CFO | Return, risk and budget treatment | Three cases, payback, funding model, capitalization answers |
| Process owners (Dan for finance, plus order to cash) | No surprises in close or billing; their people's time | Escaped-defect costs in their area; key-user hours released |
| PMO lead (Grace) | Projects delivered on time | Engagement model, catalog rates, lead times |
| Release manager (Luis) | Clear readiness evidence on time | Service levels and the readiness assessment format |
| System integrator and AMS partner | Their scope and revenue | Contract obligations, call-off model, shared tools |
A stakeholder map for Contoso's TCoE case. Win the process owners before the CFO meeting.
CTAL-TM v3.0 suggests sorting stakeholders by power and interest into four groups: promoters, latents, defenders and apathetics. The grid tells you where to spend your time. The CFO is usually a latent: powerful, but not interested in testing until a number makes it interesting. Key users are often defenders: very interested, because their time is at stake, but with little power to approve anything. Turn defenders into your evidence and latents into promoters.
The one-page pitch
Executives read one page. Structure it in five parts, each with one number:
- The problem. "Our SAP cost of quality is $1.29 million a year; 26% of it is defects that escaped to production."
- The demand. "Next year brings two feature pack stack updates, about 120 enhancements, monthly patches and the Monterrey roll-out."
- The proposal. "A core TCoE of five, a business test network of twelve named key users and a partner call-off, chartered to own standards, the regression pack and data."
- The economics. "One-time investment $229,000 in three milestone tranches; expected net benefit $208,800 a year from year 2; conservative case breaks even."
- The ask. "Approve the charter and release tranche 1."
Objections you will hear
| Objection | What it usually means | A good answer |
|---|---|---|
| "Our system integrator already does testing." | Why pay twice? | The integrator tests its own deliverables; the TCoE owns standards and independently judges evidence. Contracts will require the integrator to use our tools and standards. |
| "SAP Cloud ALM is free, so why do we need more?" | Tools should be enough | Cloud ALM is the system of record, not the capability. Someone must keep the regression pack, data and evidence current. |
| "Just automate everything." | Automation is the whole answer | Automation pays only for stable, frequent, high-risk processes, and it needs maintenance and data. The roadmap automates in that order. |
| "A permanent team will become a bottleneck." | Loss of control and speed | The hybrid model keeps functional testing in teams; the service levels are published and measured. |
| "The numbers are too optimistic." | Trust | Here is the conservative case, which breaks even, and the assumptions the pilot will measure. |
| "Why now?" | Priority | The next feature pack stack update is on the calendar, and Solution Manager 7.2 assets must be triaged before the end of 2027. |
Common objections and answers that address what is really being asked.
Success measures the sponsor will watch
Agree a small set of measures before funding, each with a baseline from lesson 2 and a dated target. They connect directly to the scorecard in sap-tst-401; the difference here is that the sponsor signs them. Contoso agreed four: escaped defects of severity 1 and 2 per release (baseline 10 a year), regression hours per release event (baseline 1,400), key-user testing hours in close weeks (target zero), and evidence for an audit request delivered within five working days.
- Month 0Charter signed, tranche 1 releasedCore team named; baseline published
- Month 3First release under the TCoEReadiness assessment format used; first showback
- Month 6Tranche 2 decisionOrder-to-cash regression automated and stable for one release
- Month 12First annual reviewScorecard against baseline; charter reviewed; tranche 3 decision
What would you do?
In the steering meeting, the CFO says: "Your expected case assumes escaped-defect costs fall by 55%. I don't believe it." How should Priya respond?
- Build sponsorship in order: process owners, PMO and release, finance, then the CIO and the steering decision.
- Pitch on one page: problem, demand, proposal, economics, ask, each with one number.
- Answer the real concern behind each objection: duplication, tools, automation, control, trust, timing.
- Agree a few success measures with baselines and dated targets, and release funding by milestone.
Check your understanding · not graded
Lesson check
1. Whom should Priya win over first when building sponsorship?
2. An executive says, "SAP Cloud ALM is free, so we don't need a TCoE." What is the best answer?
3. What makes a TCoE success measure useful to a sponsor?
4. The CFO is powerful but not yet interested in testing. Where does the CTAL-TM grid place the CFO, and what should Priya do?