Deal Strategy: Buying Committee → Champion → Mutual Plan

What this chain helps you accomplish

Build a source-traceable deal strategy an account executive can actually use: identify the buying functions involved in an opportunity, evaluate whether a potential Champion has demonstrated internal influence, prepare a credible executive decision brief, and draft a buyer-centered mutual action plan.

Each prompt produces a named artifact and uses approved evidence from the previous step. The final package shows stakeholder coverage, a behavior-based Champion development plan, an executive-ready draft with a factual-claim audit, and proposed milestones, owners and risks for buyer validation.

The chain distinguishes observed customer behavior from seller assumptions. A plan is not described as mutual until the buyer has agreed to it. Promptifi supplies the reusable instructions; the seller runs them in an approved AI assistant, reviews outputs and decides what to share.

When to use it

• When an AE is progressing an active multi-stakeholder B2B opportunity and needs to establish who actually influences, evaluates and approves a purchase.
• After substantive discovery but before relying on a friendly contact as a Champion or asking them to advocate internally.
• Before preparing a short value-oriented brief for a CFO, COO, CIO, VP or another possible economic decision-maker, especially when multiple functions have different concerns.
• When a qualified opportunity requires agreement on proof of value, technical/security review, approval, contracting, onboarding or a buyer-defined go-live milestone.
• During a late-stage deal review where a seller-entered close date, unverified approval path or missing buyer commitment could conceal a delivery risk.

Do not use it to invent a buying committee, pressure someone into internal advocacy, estimate ROI from unvalidated metrics, or treat a seller close plan as buyer-approved. For very small, single-decision-maker purchases, a compact two-party plan may be more appropriate. Without sourced customer data, the chain can still produce validation questions and a draft, but not a confirmed Champion or buyer-agreed timeline.

Before you begin

Required and optional tools

Required: an employer-approved text-based AI assistant (ChatGPT, Claude, Gemini, Microsoft Copilot or a comparable tool) and the seller's authorized, preferably dated account notes. A paid tier, live web search, CRM connector, meeting scheduler or email integration is NOT required. Optional: permitted public company research and authenticated CRM information, but a pasted URL or account name does not grant access. All final deliverables are drafts until reviewed by people.

Work with sanitized notes unless your organization's AI/data policy expressly permits identifiable customer records. Avoid uploading confidential deal values, private emails, security assessments, contact details or call transcripts to an unapproved system.

Prepare these exact inputs

• {{ACCOUNT_NAME}} — Required. Official customer/account name from CRM or account notes; e.g., Harborview Logistics (fictional). If uncertain, verify before sharing externally.
• {{OPPORTUNITY_AND_STAGE}} — Required. Actual opportunity name and seller-reported stage; e.g., 'Operations Visibility, Evaluation'. If CRM stage is unavailable, write 'unverified' and do not assert it.
• {{WHAT_WE_SELL}} — Required. Accurate two- or three-sentence description of the seller's solution, buyers helped and factual capabilities, from approved collateral; never fill gaps with model guesses.
• {{CUSTOMER_PROBLEM_AND_OUTCOMES}} — Required if known; otherwise 'unknown'. Buyer-stated pain, intended outcomes and the source, e.g. 'operations lead described delayed reporting, call note L14'. Distinguish seller hypothesis.
• {{KNOWN_STAKEHOLDERS_WITH_SOURCES}} — Required, but 'none verified' is acceptable. For each known person/role include how known, last actual activity, sources/dates; example 'Jordan Lee, Operations Director (fictional), attended discovery, L05'. Missing names remain ROLE TBD.
• {{CHAMPION_CANDIDATE_AND_BEHAVIORS}} — Optional. Candidate and exact observed internal advocacy behaviors, with source and date; e.g. 'sent intro to IT lead (email 2026-10-20)'. If only enthusiastic talk, state that clearly; no self-appointed Champion.
• {{ECONOMIC_BUYER_EVIDENCE}} — Optional. Who actually has final economic approval and how established; e.g. 'finance VP alleged by operations contact; not confirmed'. If unknown, do not infer from senior title.
• {{BUYER_DECISION_AND_APPROVAL_PROCESS}} — Optional. Dated customer statements about evaluation criteria, committee steps, security/legal/procurement/signature; if missing, 'unknown' not 'not required'.
• {{CUSTOMER_METRICS_AND_VALUE_EVIDENCE}} — Optional. Customer-confirmed baseline, source, units, measurement period and any evidence for impact; e.g. 'seller notes: buyer estimates 3 hours/week', not verified savings. If missing, omit ROI and ask how to measure.
• {{BUYER_MOTIVATION_AND_DATES}} — Optional. Specific buyer-stated priority/event, business milestone, date/time zone and source; if none, write 'no buyer deadline confirmed'.
• {{TARGET_CLOSE_DATE_AND_BASIS}} — Optional. Seller-entered close target distinguished from buyer-committed milestone; e.g. '2027-01-31 seller planning date, not buyer confirmed'. If absent, TBD.
• {{BUYER_REQUIREMENTS_AND_COMMITMENTS}} — Optional. Only actually buyer-confirmed tasks, owners and dates; list possible security/procurement stages separately as not yet verified. If no commitments, 'none confirmed'.
• {{SELLER_DELIVERABLES_AND_LIMITS}} — Required. Seller-approved next steps, resources, delivery times and limits, e.g. 'technical walkthrough possible after scope review; no guarantee on POC dates'. No fabricated legal/security promises.
• {{APPROVED_PROOF_AND_SHARING_RULES}} — Required. Approved outcome proof, current capabilities, source links and who is authorized to receive documents; use 'no proof approved / no external share approval' where applicable. Never invent case studies or financial value.
• {{SOURCE_AND_DATA_HANDLING_RULES}} — Required. Employer-approved AI/data permissions, confidentiality restrictions, and which materials may be shared with buyers. Example: 'sanitized call notes only; no customer security artifacts'. If policy unclear, stop uploading sensitive text.
• {{AS_OF_DATE_AND_TIMEZONE}} — Required for interpreting date language; example '2026-11-05 America/Chicago'. If omitted, leave relative dates unresolved and ask for confirmation.

Prepare a source-labeled deal packet

1. Collect approved CRM notes, discovery excerpts and known stakeholder interactions. Label each input with its original source, date and speaker when possible. Keep buyer statements, sales hypotheses and seller-entered forecasting details separate.
2. Ask yourself which key facts are actually known: final budget authority, decision criteria and sequence, any security/contracting gates, desired business outcome, and whether anyone has really advocated internally. Missing evidence is acceptable.
3. Record what proof can legitimately be shared externally. An executive brief must not expose internal opportunity strategy or unsupported commercial outcomes.
4. Do not assume a mutual action plan means every listed owner or date is confirmed. Have a separate way to ask the buyer to validate proposed milestones.

Methodology references that informed this chain: MEDDICC on behavioral Champion qualification (https://meddicc.com/what-is-meddpicc/champion); Gartner's 2025 findings on buying-group consensus (https://www.gartner.com/en/newsroom/press-releases/2025-05-07-gartner-sales-survey-finds-74-percent-of-b2b-buyer-teams-demonstrate-unhealthy-conflict-during-the-decision-process); and Clari on buyer-centered mutual action plans (https://www.clari.com/blog/mutual-action-plan-best-practices/). These references explain the approach; no external playbook or separate paid prompt is required.

How to run the chain

1. Start a new conversation in an approved AI assistant. Fill out the STARTING CONTEXT in the Chain Steps section, including dated notes and explicit unknowns; paste it into the conversation. Do not assume the model accessed URLs or CRM records on its own.
2. Run Prompt 1. Review every stakeholder's source ID, exact known role and all inferred priorities or missing functions. Correct any invented person or presumed authority; then explicitly approve STAKEHOLDER_EVIDENCE_MAP_v1.
3. Run Prompt 2 in the same chat with the approved map and real behavior evidence. Check the published 0–3/U rubric. Approval of a nice relationship is not a behavioral Champion test; revise if necessary. Approve CHAMPION_PROOF_PLAN_v1.
4. Run Prompt 3 with both approved artifacts. Read the executive brief as if you were the buyer. Check metrics, why-now claims, buyer wording and confidentiality. If the Champion or sharing permission is unconfirmed, keep it labeled NOT FOR FORWARDING. Approve EXECUTIVE_DECISION_BRIEF_v1 only after editorial review, not on behalf of the buyer.
5. Run Prompt 4 with all three approved artifacts. Examine the proposed milestone table, dependencies, owners, buyer-confirmed versus seller-proposed dates, and review email. The final output is PROPOSED_MUTUAL_SUCCESS_PLAN_v1; it becomes 'mutual' only when an actual buyer reviewer confirms the relevant milestones.
6. Where a prompt needs repair, supply the exact inaccurate statement, source and corrected value; request a complete replacement artifact with the next version. Re-run dependent downstream steps if upstream evidence changes.
7. If starting a new chat, paste the completed Starting Context plus the FULL latest approved artifacts needed for that step. Never rely on memory from another conversation, and provide only information permitted by your organization's data policy.
8. Seller approves any external sharing or actual follow-up separately. Send no buyer messages, schedule nothing and update no CRM field unless separately authorized through the seller's ordinary process.

Explicit approval and version control

Approve the exact artifact by saying 'APPROVED — STAKEHOLDER_EVIDENCE_MAP — v1' and analogously for CHAMPION_PROOF_PLAN and EXECUTIVE_DECISION_BRIEF. A revised v2 supersedes v1 only after approval. The model cannot approve itself. Seller approval does NOT mean an internal buyer has endorsed the plan or accepted any task.

What completed work looks like

An evidence-labeled buying committee map, a defensible Champion scorecard with tests, an executive brief appropriate for verification, and a proposed customer-success-oriented MAP with specific questions needed for mutual agreement. Unknowns, dates and owners remain explicit. No external actions occur merely by running the chain.