AI Prompts for Mutual Action Plans

A mutual action plan is a shared timeline of everything that must happen — on both sides — between now and the buyer getting value. It works because it is built backward from a date the buyer cares about (go-live, budget cycle, a business event) and because it makes the buyer's own steps visible: security review, legal, procurement, internal approvals, the things sellers forget and buyers underestimate. A plan the buyer helps write is a forecast instrument; a plan the seller writes alone is a wish.

These prompts build the plan from the process discovery revealed, draft the shareable version, and use it in reviews to spot the milestones that are slipping. They depend on knowing the buyer's process; where it is unknown, the plan should say so and make finding out the first milestone.

Before you use these

Have these ready to replace the highlighted [variables]:

• The buyer's target date and why it matters to them
• Their decision and procurement process as far as known (steps, owners, durations)
• Your delivery steps (contracting, implementation, onboarding)
• Stakeholders on both sides

The prompts

• 1. Build the plan backward from their date
• 2. Draft the shareable version for the buyer
• 3. Use the plan to find slippage before the forecast does

1. Build the plan backward from their date

Act as a deal strategist building a mutual action plan for [opportunity] at [prospect].

Their target date and why: [date, business reason]
Their process as known: [evaluation steps, security/IT review, legal, procurement, budget approval, signature authority — with owners and typical durations where known; mark unknowns]
Our steps: [proposal, technical validation, contracting, implementation, onboarding, time to first value]
Stakeholders: [both sides]

1. Work backward from the value date: list every milestone on both sides with owner, duration, dependency and the latest start date. Include the buyer-side steps sellers usually omit (security questionnaire, legal redlines, procurement onboarding, internal change approval).
2. Critical path: the chain that determines whether the date holds.
3. Unknowns: steps whose duration or owner we do not know; make confirming each one a milestone with a date.
4. Feasibility: does the plan fit? If not, the options — earlier signature, parallel steps, phased go-live, or a different target date — and what to say to the buyer.
5. Risk points: the milestones most likely to slip (from typical experience and the deal's specifics) and the early warning for each.
6. The signature date implied by the plan — this is the close date, derived rather than guessed.

Present as a table. If more than a third of the steps are unknown, say the plan is provisional and prioritize the discovery to fix it.

2. Draft the shareable version for the buyer

You are drafting the buyer-facing version of a mutual action plan for [prospect].

Internal plan: [milestones, owners, dates]
Champion: [name, role, what they are trying to achieve and by when]
Their language: [how they describe the outcome and the project]

1. Framing paragraph: the outcome and date in their words; why a shared plan helps them (visibility for their stakeholders, fewer surprises), not why it helps us.
2. Milestone table: their steps and ours interleaved by date, with owner names, and with the steps only they can do clearly marked.
3. Roles: who on each side does what; who resolves blockers.
4. Open questions: the steps we need them to confirm (owner, duration), phrased as questions.
5. Cover note to the champion (under 120 words): what it is, the ask to review and correct, and the suggestion to share it with the stakeholders who own steps.
6. What not to include: our internal close date, forecast category, or anything that reads as pressure.

Tone: collaborative and specific. Remove any sales language.

3. Use the plan to find slippage before the forecast does

Act as a sales manager reviewing a mutual action plan for slippage on [opportunity].

Plan with status: [milestone, planned date, actual/current status, owner]
History: [milestones already late and by how much]
Forecast: [close date, category]

1. Status by milestone: on track, late (days), unowned, unconfirmed.
2. Drift: total slip so far and the pattern (buyer-side steps slipping? unknowns not resolved? our steps late?).
3. The earliest milestone whose slip makes the forecast close date impossible, and the arithmetic.
4. Signals in the slips: which suggest normal friction, and which suggest loss of priority or a competing process.
5. Actions: for each late or unowned milestone, the specific action, who takes it (rep, champion, executive), and by when.
6. Forecast recommendation: keep, move the date (to what, derived from the plan), or downgrade the category — with the reason in one sentence.
7. The question to ask the champion this week.

Be specific about dates. A plan that has slipped three times without a re-baseline is not a plan.

A backward plan, illustrated

Six of the milestones from a plan built back from a 1 March go-live. Buyer-side steps are the ones sellers usually omit.

Related prompts

• Stalled Deals
• Sales Forecasting
• Deal Reviews
• Sales Proposal Development
• Sales Negotiation and Discount Pushback
• Buyer and Buying Committee Mapping

Logical next step

After this, most sales teams move on to Stalled Deals.

All Sales prompts · Search the full library