Negotiation Chain: Strategy → Mutual Action Plan → Close

What this chain helps you accomplish

Prepare for late-stage B2B commercial negotiations without improvising discounts, overpromising terms, or treating a seller's desired close date as a buyer commitment.

Five connected AI prompts turn actual deal evidence into a Deal Readiness & Evidence Register, a private Negotiation Strategy Brief, a verified Negotiation Outcome Record, a Buyer-Reviewable Mutual Action Plan, and a Stage-Appropriate Follow-Up & Close Readiness Pack. Each step depends on a seller-approved prior artifact, with a pause for the real negotiation conversation.

The chain helps you identify what is genuinely agreed, protect approval boundaries, explore conditional give-and-get options, reveal unresolved procurement and legal dependencies, and propose an honest next buyer decision. A joint action plan becomes mutual only when the buyer reviews and accepts its relevant milestones, owners, and timing.

Promptifi provides instructions for your own AI tool. It does not negotiate for you, grant pricing authority, co-sign a plan, send closing emails, amend contracts, schedule meetings, or update your CRM. No deal outcome or time savings are guaranteed.

When to use it

• Before a commercial negotiation: A buyer is discussing price, scope, payment terms, service commitments, or a proposed agreement and you need an approved, evidence-based negotiation plan.
• After a substantive negotiation conversation: You need to separate what the buyer requested, what you proposed, what each side actually accepted, and what requires legal or management approval.
• When a deal involves multiple decision steps: Procurement, finance, legal, security, technical validation, signature authority, or implementation dependencies could prevent the buyer's desired outcome.
• When a prospect asks for a mutual plan: You want a buyer-centered draft that invites correction and agreement, rather than a close-date checklist imposed by the seller.
• When preparing a closing or next-step email: You need accurate wording that reflects the actual stage, buyer's outcome, unresolved approvals, and any legitimate timeline.

Do not use this to create artificial urgency, invent a procurement commitment, claim an unapproved discount, or pressure a buyer to sign on a seller-only timeline. If the buyer is not ready to negotiate or has not accepted any joint plan, the correct deliverable may be a discovery/approval-gap plan or a request to review a draft MAP—not a closing email.

An internal negotiation brief is confidential seller material. Never copy the concession limits, reservation point, approval thresholds, or internal alternatives into a document intended for the customer.

Before you begin

Minimum tool: A text-capable conversational AI application such as ChatGPT, Claude, Gemini, or another organization-approved model. No premium feature, CRM connector, calendar integration, browsing, document automation, or email sending is required. Paste permitted information directly. Links alone are not proof an AI opened or verified the documents.

Prepare the following fields. Replace the double-brace placeholders with real seller-controlled or buyer-supplied information. The inputs and outputs use E# for pre-negotiation evidence and N# for notes from an actual negotiation discussion.

• {{ACCOUNT_AND_OPPORTUNITY}} — Required. Named account, actual product/service, deal stage, and deal purpose from CRM or a current opportunity record. Example: Harborline Equipment, enterprise subscription evaluation. If unknown, identify the opportunity before proceeding.
• {{BUYER_DESIRED_OUTCOME}} — Required as a field; may be unconfirmed. The customer's stated operational goal and intended timing, with E# speaker/date. Example: E1 — Operations Director, Nov. 4, 2026 — wants initial team ready by March 2027. If inferred rather than stated, label HYPOTHESIS and do not invent a buyer deadline.
• {{CURRENT_PROPOSAL_AND_SCOPE}} — Required. Current company-approved offer, term, amount/currency, quote date/version, implementation scope, dependencies, exclusions, and what remains to be approved. Example: annual subscription $72,000; onboarding $8,000; pricing sheet approved Nov. 2, 2026. If price is only an estimate, label UNAPPROVED ESTIMATE.
• {{SELLER_NEGOTIATION_AUTHORITY}} — Required, PRIVATE. Documented discount, term, scope, service and exception authority, approvers, conditions, and expiration of approvals. Source: sales policy/manager. Example: seller may discuss but cannot approve any discount; manager review required. If unclear, enter NONE VERIFIED—do not invent a concession ladder or share this field with the buyer.
• {{NONNEGOTIABLES_AND_BATNA}} — Optional, PRIVATE. Verified company deal limits, unacceptable risks, best alternative to a negotiated agreement (BATNA), target/reservation boundaries, and management decision rights. Example: legal cannot accept a specified data obligation without counsel review; no validated reservation price. If absent, enter UNKNOWN; do not compute a fictional walk-away position.
• {{BUYER_POSITION_EVIDENCE}} — Required as a field; may be incomplete. Dated, attributable buyer requests, comments and objections, labeled E1, E2, etc., including what was actually said. Example: E2 — Procurement Manager, Nov. 3, 2026 — asked whether payment terms are flexible, without naming an acceptable term. If absent, enter NONE and use a discovery/qualification plan.
• {{STAKEHOLDERS_AND_APPROVALS}} — Optional. Verified buyer/seller participants, economic and signature authority, decision criteria, legal/procurement/security steps, and evidence source/date. Example: finance review stated by buyer; signatory unknown. If absent, enter UNKNOWN; never create names or promise approvals.
• {{BUYER_TIMING_AND_DEPENDENCIES}} — Optional. Buyer-confirmed target outcome dates, renewal dates, contract/process requirements, and reasons timing matters. Example: procurement needs a vendor record before legal sign-off; dates unknown. If absent, enter UNKNOWN. A seller forecast close date is not a buyer deadline.
• {{COMMERCIAL_AND_PROOF_LIMITS}} — Optional. Company-approved collateral, allowed statements, contract review restrictions, and product delivery obligations. Example: only approved security package may be shared; onboarding timetable must be confirmed by services. Enter NONE PROVIDED when absent.
• {{NEGOTIATION_CONVERSATION_RECORD}} — Required only after a real negotiation for Prompt 3. Authorized post-call transcript or seller notes labeled N1, N2 etc., with actual speaker/date/time when available, verbatim versus paraphrase, exact requests and responses. Example: N1 — Procurement Manager — Nov. 5, 2026 — requested net-45 terms; seller did not accept. If no meeting occurred, enter NOT YET AVAILABLE; stop after pre-call preparation.
• {{MAP_REVIEW_STATUS}} — Required as a status field for final buyer-facing use. State whether a real buyer reviewed and accepted the specific MAP version, owners, milestones and dates. Example: draft not yet shared; no buyer sign-off. If unknown, mark NOT MUTUAL. Do not infer acceptance from a positive meeting.
• {{SENDER_AND_COMMUNICATION_GUARDRAILS}} — Optional. Verified email sender/recipients, communications history, opt-outs or contact restrictions, and internal sign-off requirements. Example: AE will email only attendees after manager approves revised terms. If unknown, enter UNKNOWN; keep output DRAFT ONLY.

Evidence and authority rules: E# means a pre-negotiation source and N# means an actual post-negotiation note. Include speaker/owner, date, direct quotation versus paraphrase, and scope. Mark FACT/BUYER-REPORTED, SELLER PROPOSAL, MUTUALLY CONFIRMED, APPROVAL PENDING, HYPOTHESIS, and UNKNOWN distinctly. Seller approval to use a draft inside this chain does not grant authority to change pricing or indicate customer agreement.

Private versus shareable: Keep company concession authority, BATNA, walk-away limits, margin assumptions, internal forecast and escalation strategy inside the PRIVATE Negotiation Strategy Brief. MAP and buyer emails must omit that information. All external terms must match an approved customer-visible quote or clearly be marked conditional and pending approval.

Data safety: Use only company-authorized AI tools. Redact sensitive contracts, personal data, internal pricing thresholds and privileged legal content when access is not approved. Do not rely on AI for legal contract approval or financial authorization.

How to run the chain

1. Open a new conversation in an approved text-capable AI tool. Complete the Starting Negotiation Context from Chain Steps, including E# sources and permissioned internal constraints. Keep this conversation and the private strategy output inside an authorized workspace.
2. Run Prompt 1. Audit the evidence, current deal/approval status and buyer's real negotiating position. Correct any assumption presented as a confirmed fact and explicitly approve the Deal Readiness & Evidence Register.
3. Run Prompt 2. Review the private negotiation boundaries, alternatives and conditional trade ideas with the responsible internal approver before the customer discussion. Approve the latest Negotiation Strategy Brief for internal preparation only.
4. Pause for the actual negotiation conversation. Do not let AI simulate accepted buyer concessions. After the discussion, paste the permitted N# notes under the heading Negotiation Conversation Record and run Prompt 3. Review exactly what each side requested, proposed or accepted. Approve the record.
5. Run Prompt 4 to draft a buyer-reviewable MAP with real milestones and explicit TBDs. The buyer must review and accept the relevant owners/dates before anyone calls it a mutual action plan. Seller approval alone never makes the MAP mutual.
6. Run Prompt 5 using all four approved artifacts and the true MAP review status. Review the email path—buyer MAP accepted, buyer MAP not accepted, pending approvals, or no legitimate close—and verify each claim. Save drafts, then obtain any separate management/legal approvals before sending or scheduling anything.

Approval convention: Use APPROVED — [Exact Artifact Name] — v1. Use only this version as input to subsequent prompts. If corrected, output the entire next version, approve it, and rerun any downstream prompts that depended on changed facts.

One conversation is preferred. For a new chat, paste the complete Starting Negotiation Context, actual N# notes, required complete approved artifact versions, and unresolved questions. Do not rely on cross-chat memory.

Failure/stop conditions: Missing documented negotiation authority means no authorized concession recommendation; missing actual negotiation notes means do not produce a made-up outcome; missing buyer acceptance means the MAP is DRAFT/PROPOSED, not agreed; missing legitimate urgency means the email must not create a deadline. An agreed next step is only agreed when attributable evidence supports acceptance.

Completion standard: A protected internal negotiation plan, an accurate outcome record, a buyer-centered MAP draft with verified versus proposed milestones, and an honest stage-appropriate email with a separate internal review checklist. No emails, calendar events, signature requests, contract revisions or CRM changes happen automatically.