Sponsor Change Plan
When To Use
The person who hired you is leaving, or you realise only one person there knows why you matter. A part-time seat has few witnesses. When the sponsor goes, their successor inherits a line in the budget and a name they do not know. This answers: how do I meet the new sponsor on their goals, and who else should be able to say what the seat does?
When Not To Use
If no one is leaving and you want the whole picture of who the work depends on, run Stakeholder Map. If the contract date is what worries you, run Renewal Review.
Inputs
- Who is leaving, when, and who takes over, if known
- What the new sponsor has said about their priorities, with where and when they said it
- Your monthly reports, decision records and stakeholder map for this client
If you have none of this, I start from the date of the change and what the engagement has delivered so far, mark the new sponsor's goals "unknown" and mark the plan as a first draft.
Approach
Five steps for a change of sponsor from customer success practice (ask for an introduction, hold a knowledge transfer, make contact, learn the new person's goals, revise the plan), joined to a roles table from key account planning, described generically: people by their role in the work and what they have said they need. The source is old and was written for account managers, so it is used as a checklist, not as evidence about fractional work. The failure this prevents is the single thread.
Workflow
- Ask at most three questions: who is leaving and on what date; do you know the successor; who besides the sponsor has seen the results of your work?
- Ask for the introduction while the sponsor is still there. I draft the request for you to send: a short note, with the two things the successor should hear from the person who hired you.
- Prepare the three-way handover call: why the seat exists, what was agreed (statement of work, charter), what has been delivered against it, what is open, what the sponsor would do next.
- Write what the new sponsor has said about their goals, with the source. Anything they have not said is "unknown" and becomes a question for your first meeting. I do not guess their view of you, of the seat or of part-time roles.
- Run the single-thread check: for each result, who else at the client can describe it? List the relationships to build, by role, and what each person needs from your function.
- Revise the next 90 days against the new sponsor's stated goals, marking what continues, what waits for their decision and what you propose to stop.
Output Format
# Sponsor Change Plan
Client: [name] · Leaving: [role, name] on [date] · Taking over: [role, name, or not yet known]
## Introduction and handover call
Introduction asked of [sponsor] by [date] · Call agenda: why the seat exists · what was agreed · delivered against it · open items · what [sponsor] would do next
## The new sponsor's goals
| Goal or priority | In their words? (source, date) | If unknown: question to ask |
|---|---|---|
| [goal] | [stated, where] or unknown | [open question] |
## Who else knows what the seat does
| Result or piece of work | Who can describe it today (role) | Relationship to build | What they need from the function |
|---|---|---|---|
| [result] | [role, or only the sponsor] | [role] | [stated need, or unknown] |
## Revised next 90 days
| Work | Continues / waits for their decision / propose to stop |
|---|---|
| [work] | [status] |
## Decision
[You] ask [sponsor] for the introduction by [date]; [new sponsor] confirms or changes the priorities at the first meeting.
Done When
- The introduction is asked for before the sponsor's last day
- Every goal of the new sponsor is sourced or reads "unknown" with a question
- Each result has at least one other person who can describe it, or a relationship to build
- The revised plan marks what waits for the new sponsor's decision
Quality Bar
- People appear by role and stated need; nobody is rated as ally, risk or obstacle
- No guess about the new sponsor's opinion or intentions
- The handover call reports what was delivered from your reports, with nothing rounded up
- The plan is not a campaign to keep the contract; it tells the new sponsor what they need to decide
- Only this client's records are used, nothing is invented, and you make the introduction request and hold the meetings yourself
Next
Run frac-renewal-review (Renewal Review) to put results and options in front of the new or current sponsor before the contract date.
About the makers
This pack is made by 90n (90n.ai): AI-native ways of working and tools for Product, Marketing and HR teams, built by ex-McKinsey founders. We map where time and money leak, redesign the work around AI and stay until your people run it themselves, and we run our own company on Claude. If your team has outgrown the self-serve version, message Pauline (linkedin.com/in/paulinebertry).
1---2name: frac-sponsor-change-plan3description: Builds a plan for a change of sponsor in a fractional engagement, with who is leaving and when, the introduction to ask for, a handover call agenda, what the new sponsor has said about their goals (or "unknown", turned into questions), the other relationships to build so the role does not hang on one person, and the revised plan for the next 90 days. Use for "run frac-sponsor-change-plan", "my sponsor is leaving", "the person who hired me is leaving", "executive sponsor change", "new CEO at my client", "the engagement depends on one person", "who else knows why I am here", part of the Claude for Fractional Leaders Pack by 90n.4metadata:5 source: https://skillmd.com/skills/polar-bear-org/frac-sponsor-change-plan6---78# Sponsor Change Plan910## When To Use11The person who hired you is leaving, or you realise only one person there knows why you matter. A part-time seat has few witnesses. When the sponsor goes, their successor inherits a line in the budget and a name they do not know. This answers: how do I meet the new sponsor on their goals, and who else should be able to say what the seat does?1213## When Not To Use14If no one is leaving and you want the whole picture of who the work depends on, run Stakeholder Map. If the contract date is what worries you, run Renewal Review.1516## Inputs17- Who is leaving, when, and who takes over, if known18- What the new sponsor has said about their priorities, with where and when they said it19- Your monthly reports, decision records and stakeholder map for this client20If you have none of this, I start from the date of the change and what the engagement has delivered so far, mark the new sponsor's goals "unknown" and mark the plan as a first draft.2122## Approach23Five steps for a change of sponsor from customer success practice (ask for an introduction, hold a knowledge transfer, make contact, learn the new person's goals, revise the plan), joined to a roles table from key account planning, described generically: people by their role in the work and what they have said they need. The source is old and was written for account managers, so it is used as a checklist, not as evidence about fractional work. The failure this prevents is the single thread.2425## Workflow261. Ask at most three questions: who is leaving and on what date; do you know the successor; who besides the sponsor has seen the results of your work?272. Ask for the introduction while the sponsor is still there. I draft the request for you to send: a short note, with the two things the successor should hear from the person who hired you.283. Prepare the three-way handover call: why the seat exists, what was agreed (statement of work, charter), what has been delivered against it, what is open, what the sponsor would do next.294. Write what the new sponsor has said about their goals, with the source. Anything they have not said is "unknown" and becomes a question for your first meeting. I do not guess their view of you, of the seat or of part-time roles.305. Run the single-thread check: for each result, who else at the client can describe it? List the relationships to build, by role, and what each person needs from your function.316. Revise the next 90 days against the new sponsor's stated goals, marking what continues, what waits for their decision and what you propose to stop.3233## Output Format34```markdown35# Sponsor Change Plan36Client: [name] · Leaving: [role, name] on [date] · Taking over: [role, name, or not yet known]37## Introduction and handover call38Introduction asked of [sponsor] by [date] · Call agenda: why the seat exists · what was agreed · delivered against it · open items · what [sponsor] would do next39## The new sponsor's goals40| Goal or priority | In their words? (source, date) | If unknown: question to ask |41|---|---|---|42| [goal] | [stated, where] or unknown | [open question] |43## Who else knows what the seat does44| Result or piece of work | Who can describe it today (role) | Relationship to build | What they need from the function |45|---|---|---|---|46| [result] | [role, or only the sponsor] | [role] | [stated need, or unknown] |47## Revised next 90 days48| Work | Continues / waits for their decision / propose to stop |49|---|---|50| [work] | [status] |51## Decision52[You] ask [sponsor] for the introduction by [date]; [new sponsor] confirms or changes the priorities at the first meeting.53```5455## Done When56- The introduction is asked for before the sponsor's last day57- Every goal of the new sponsor is sourced or reads "unknown" with a question58- Each result has at least one other person who can describe it, or a relationship to build59- The revised plan marks what waits for the new sponsor's decision6061## Quality Bar62- People appear by role and stated need; nobody is rated as ally, risk or obstacle63- No guess about the new sponsor's opinion or intentions64- The handover call reports what was delivered from your reports, with nothing rounded up65- The plan is not a campaign to keep the contract; it tells the new sponsor what they need to decide66- Only this client's records are used, nothing is invented, and you make the introduction request and hold the meetings yourself6768## Next69Run frac-renewal-review (Renewal Review) to put results and options in front of the new or current sponsor before the contract date.7071## About the makers7273This pack is made by 90n ([90n.ai](https://90n.ai)): AI-native ways of working and tools for Product, Marketing and HR teams, built by ex-McKinsey founders. We map where time and money leak, redesign the work around AI and stay until your people run it themselves, and we run our own company on Claude. If your team has outgrown the self-serve version, message Pauline (linkedin.com/in/paulinebertry).