Mutual Action Plan
When To Use
Everyone agreed in the meeting. Then came supplier registration, a contract review, a data questionnaire and a budget code, each one news to you and each owned by someone you have never met. Run this the day after a yes, to lay out with your contact every step between agreement and the first day of work.
When Not To Use
With no yes so far, use Proposal Follow-Up Emails. If your contact still has people above them to persuade, use Client Decision Brief first; a plan cannot schedule a decision nobody has taken.
Inputs
- The start date the client wants, in their words, and why that date
- What you know of their process: approvals, legal, procurement, security or data checks, who signs
- The proposal or statement of work, and any dates already promised
If you have none of this beyond a start date, I work back from it and mark every step as an assumption to check with your contact.
Approach
A mutual action plan is a common selling practice, described generically: one shared list of what both sides must do to reach a start, each step with an owner and a date. The weight is on "mutual". A timetable you write alone and send over reads as pressure and is politely ignored. Built with your contact, it brings out the procurement step nobody mentioned until the fifth week.
Workflow
- Ask, in one go: what start date does the client want, and why? Who on their side has said what about the process? Which steps on your side could slow things (paperwork, your availability)?
- Work backwards from the start date and list every step in reverse: kickoff, signature, contract review, supplier set-up, security or data checks, internal approval, budget release. Add anything the client named. Leave nothing out because it is awkward to ask about.
- For each step record the owner as a role on either side, the date it must be finished for the start to hold, and what it needs from the other party. Roles only; never guess a person's name.
- Check that the time adds up. Where steps cannot fit before the start date, say so and show the earliest realistic start. A plan that is late on its first day teaches everyone to ignore it.
- Mark each step with no owner or no date as a risk, and turn each into one question for your contact. Those questions are often the most valuable part.
- Label the plan "proposed, to agree" and draft a short note inviting your contact to correct it on a call. Contract and data-protection steps carry "check with a qualified adviser".
Output Format
# Yes-to-Start Plan
Status: proposed, for agreement with [client contact role] on [date]
Start the client wants: [date], because [their reason]
## Steps from yes to day one
| # | Step | Owner (role, side) | Done by | Needs from the other side | Status |
|---|---|---|---|---|---|
| 1 | [step] | [role, client / consultant] | [date] | [input] | [not started / under way / done] |
## Risks and questions
- [Step with no owner or no date]: [question for your contact]
## Earliest realistic start
[The client's date holds / earliest is [date], because [steps that cannot fit]]
## Note to your contact
[A few lines asking them to correct the plan with you on a call; you send it]
## Decision
[Client contact role] and [you] agree the plan, or move the start date, on a call by [date].
Done When
- Every step from yes to day one is listed, worked back from the client's date
- Each step has an owner by role and a date, or sits under risks with a question
- Dates that cannot fit are shown as they are, with the earliest realistic start
- The plan reads "proposed" and is ready to settle in conversation
Quality Bar
- Steps on the client's side use their process words, not your sales stages
- An assumed step is marked "to confirm", never stated as fact
- Your own steps and dates are in the plan too
- Contract, procurement and data points end "check with a qualified adviser"
- Agreed together, never imposed; I invent no step, owner or date as fact, and you send the note and hold the call.
Next
Run firm-win-loss-review (Win/Loss Review) to review how this pursuit went while it is fresh.
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: firm-mutual-action-plan3description: Drafts a mutual action plan covering every step from the client's yes to the first day of work, worked back from their start date, with an owner by role and a date per step on both sides, steps with no owner turned into questions, and the whole plan marked proposed until agreed together. Use for "run firm-mutual-action-plan", "the client said yes and nothing is moving", "mutual action plan", "steps from yes to signature", "work back from the start date", "who handles procurement and legal", "plan the path to kickoff", part of the Claude for Consultants · Team in Claude Pack by 90n.4metadata:5 source: https://skillmd.com/skills/polar-bear-org/firm-mutual-action-plan6---78# Mutual Action Plan910## When To Use11Everyone agreed in the meeting. Then came supplier registration, a contract review, a data questionnaire and a budget code, each one news to you and each owned by someone you have never met. Run this the day after a yes, to lay out with your contact every step between agreement and the first day of work.1213## When Not To Use14With no yes so far, use Proposal Follow-Up Emails. If your contact still has people above them to persuade, use Client Decision Brief first; a plan cannot schedule a decision nobody has taken.1516## Inputs17- The start date the client wants, in their words, and why that date18- What you know of their process: approvals, legal, procurement, security or data checks, who signs19- The proposal or statement of work, and any dates already promised20If you have none of this beyond a start date, I work back from it and mark every step as an assumption to check with your contact.2122## Approach23A mutual action plan is a common selling practice, described generically: one shared list of what both sides must do to reach a start, each step with an owner and a date. The weight is on "mutual". A timetable you write alone and send over reads as pressure and is politely ignored. Built with your contact, it brings out the procurement step nobody mentioned until the fifth week.2425## Workflow261. Ask, in one go: what start date does the client want, and why? Who on their side has said what about the process? Which steps on your side could slow things (paperwork, your availability)?272. Work backwards from the start date and list every step in reverse: kickoff, signature, contract review, supplier set-up, security or data checks, internal approval, budget release. Add anything the client named. Leave nothing out because it is awkward to ask about.283. For each step record the owner as a role on either side, the date it must be finished for the start to hold, and what it needs from the other party. Roles only; never guess a person's name.294. Check that the time adds up. Where steps cannot fit before the start date, say so and show the earliest realistic start. A plan that is late on its first day teaches everyone to ignore it.305. Mark each step with no owner or no date as a risk, and turn each into one question for your contact. Those questions are often the most valuable part.316. Label the plan "proposed, to agree" and draft a short note inviting your contact to correct it on a call. Contract and data-protection steps carry "check with a qualified adviser".3233## Output Format34```markdown35# Yes-to-Start Plan36Status: proposed, for agreement with [client contact role] on [date]37Start the client wants: [date], because [their reason]38## Steps from yes to day one39| # | Step | Owner (role, side) | Done by | Needs from the other side | Status |40|---|---|---|---|---|---|41| 1 | [step] | [role, client / consultant] | [date] | [input] | [not started / under way / done] |42## Risks and questions43- [Step with no owner or no date]: [question for your contact]44## Earliest realistic start45[The client's date holds / earliest is [date], because [steps that cannot fit]]46## Note to your contact47[A few lines asking them to correct the plan with you on a call; you send it]48## Decision49[Client contact role] and [you] agree the plan, or move the start date, on a call by [date].50```5152## Done When53- Every step from yes to day one is listed, worked back from the client's date54- Each step has an owner by role and a date, or sits under risks with a question55- Dates that cannot fit are shown as they are, with the earliest realistic start56- The plan reads "proposed" and is ready to settle in conversation5758## Quality Bar59- Steps on the client's side use their process words, not your sales stages60- An assumed step is marked "to confirm", never stated as fact61- Your own steps and dates are in the plan too62- Contract, procurement and data points end "check with a qualified adviser"63- Agreed together, never imposed; I invent no step, owner or date as fact, and you send the note and hold the call.6465## Next66Run firm-win-loss-review (Win/Loss Review) to review how this pursuit went while it is fresh.6768## About the makers6970This 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).