The prompt
Score 10 of 10, Excellent
Use it when A deal has several people and steps on the buyer's side, and you want a shared plan of who does what by when, from today to go-live.
- {{buyer_company}}
- {{buyer_contact}}
- {{target_outcome}}
- {{buying_process}}
- {{people}}
- {{key_dates}}
- {{current_status}}
Full prompt and why it works
Prompt
Draft a mutual action plan for the deal with {{buyer_company}}, to share with {{buyer_contact}} and agree together. It lists every step both sides need to take to get from today to {{target_outcome}}, so that nothing stalls because nobody owned it. The buyer will read it, so it must be accurate, neutral and free of sales language. What we know about their buying process (steps, approvals, legal, security, procurement, budget timing): """ {{buying_process}} """ People involved on both sides, with roles: {{people}} Dates already agreed or required: {{key_dates}} Where things stand today: {{current_status}} Produce: 1. A one-sentence goal at the top, in the buyer's terms, for example "Have the new scheduling system live for the March intake". 2. A table with the columns Step, Owner (name and side), Due date, Status (done, in progress, not started), Notes. Work backward from the target date, and include the steps people often forget: security review, legal redlines, supplier setup in procurement, budget sign-off, the signer's availability, and the kickoff. 3. Dependencies: which steps must finish before others can start. 4. Risks to the date, up to 4, each with what would help. 5. Questions to confirm with the buyer on our next call. Use only the steps, people and dates I gave. Where a step is likely but I have not confirmed it happens at this company, include it with the owner "[to confirm]" and add it to the questions. Do not set dates the buyer has not agreed; mark any date you suggest as "proposed". If the target date looks impossible once the steps are laid out, say so plainly with the arithmetic rather than squeezing the steps to fit, and date the table forward from today to show the earliest realistic date.
Variables
- {{buyer_company}}
- The buyer's company name.
- {{buyer_contact}}
- Your main contact there and their role.
- {{target_outcome}}
- What the plan leads to, with its date, for example "live by April 1 for the new financial year".
- {{buying_process}}
- What you know about their process: approvals, legal, security review, procurement, budget timing.
- {{people}}
- Everyone involved on both sides, with their roles.
- {{key_dates}}
- Dates already agreed or fixed, or "none yet".
- {{current_status}}
- Where the deal stands today, in a sentence or two.
Why it works
- Who it's for. It is written to share with the buyer, so it stays neutral and factual, which is what makes a buyer willing to own their half of the steps.
- Background facts. It adds the steps that most often stall deals late, such as security review and supplier setup, but marks each as to confirm instead of assuming it.
- If unsure. Unagreed dates are marked proposed, and an impossible target date is called out with the arithmetic rather than hidden by squeezing the plan.