Sales & Customer Service/Intermediate
Create a mutual action plan after a B2B discovery call
Convert discovery notes into a proposed sequence of buyer and seller actions, dependencies, owners, and decision dates.
THE RESULT
What you’ll create
A buyer-shareable mutual action plan draft with open items and internal follow-up tasks.
HOW TO USE IT
Workflow steps
- 01Extract only customer-stated outcomes, commitments, and decision milestones from the notes.
- 02Separate agreed actions from suggested steps and unknown approval gates.
- 03Order tasks by dependency and assign owners only when notes identify them.
- 04Draft a neutral shared plan and an internal list of questions to confirm before sending.
COPY-READY INSTRUCTIONS
Start your workflow
Use the stages in order. Fill in the bracketed sections and add only source material you are permitted to share.
STAGE 1 — 1. Extract commitments When to use: Use immediately after the call. Prompt: Turn these anonymized discovery notes into a fact table: [paste notes]. Customer-stated desired outcome: [paste or “not clear”]. For each potential action, capture exact source phrase or note ID, action, owner if explicitly named, date if explicitly agreed, and status (agreed / proposed / unclear). Separate customer commitments from seller suggestions. Do not fill gaps from typical sales process assumptions. Expected return: A commitment and open-item table with source traceability. User check: Verify every owner, date, and commitment against the notes. STAGE 2 — 2. Sequence the plan When to use: Use after correcting Stage 1. Prompt: Using only confirmed actions and milestones above, arrange a proposed path in a table: step, outcome, customer owner, seller owner, target date, dependency, and status. Leave unknown owners/dates as TBD. Suggested steps must be labeled “proposed.” Identify the minimum questions to confirm the decision process, approval gates, and any implementation dependencies. Expected return: A sequenced draft action plan and a short confirmation-question list. User check: Check dependencies and ensure proposed dates are not presented as customer-agreed. STAGE 3 — 3. Prepare the shared handoff When to use: Use after the account team confirms the plan. Prompt: Draft a concise email and attached-plan text for [customer role], using this confirmed plan: [paste]. State the shared goal, confirmed actions, proposed items needing confirmation, and the next check-in. Do not imply agreement on unresolved steps or promise delivery dates not approved. Add internal-only follow-up tasks separately so they are not sent to the customer. Expected return: A customer-ready draft plus a separate internal task list. User check: Account owner must verify commitments, scope, dates, and permissions before sending.