Account Plan

Use this skill to run Account Plan as a practical consulting method, not as a generic framework explanation.

Method Notes

• Map decision rights, relationship strength, competitor position, proof gaps, and next ask.
• Do not treat a friendly contact as the account plan.

Required Inputs

Collect or infer these inputs before execution:

• account background
• opportunity
• stakeholders
• competitors
• relationship evidence

If an input is missing, do not block automatically. Mark it as missing, state the assumption used, and add a validation action.

When Not To Use

Do not use without a named account, a defined business need, relevant stakeholders, a value hypothesis, and a next customer decision. It is not a generic market or campaign plan.

Adjacent Methods

• stakeholder-power-map: diagnose power, stance, and hidden vetoes around one decision.
• deal-strategy-map: plan the buying path and next commercial commitment for one opportunity.

Step-by-Step Execution

Output Template

### 1. Account Objective And Evidence
Account objective:
Decision deadline:
Confirmed facts:
Assumptions to test:

### 2. Stakeholders And Buying Path
| Stakeholder | Role / power | Current stance | Evidence / confidence | Needed movement | Next ask |
|---|---|---|---|---|---|
|  |  |  |  |  |  |

### 3. Value, Competition, And Risk
| Buyer need | Proposed value | Proof | Competitor / alternative | Risk |
|---|---|---|---|---|
|  |  |  |  |  |

### 4. 30-Day Action Plan
| Action | Owner | Timing | Expected commitment / signal | Fallback |
|---|---|---|---|---|
|  |  |  |  |  |

### Evidence And Next Decision
- Confirmed facts:
- Assumptions:
- Missing evidence:
- Next action, owner, and timing:
- Expected signal and decision threshold:

Quality Gate

• Produce the method-specific outputs for Account Objective And Evidence, Stakeholders And Buying Path, Value, Competition, And Risk; do not substitute a generic framework summary.
• Tie every material score, causal claim, or stakeholder judgment to evidence or label it as an assumption.
• Include at least one disconfirming check, sensitivity, alternative explanation, or failure condition appropriate to the method.
• Convert the result into a named action or decision with an owner or stakeholder, timing, and observable signal.
• State missing inputs and the smallest validation action instead of inventing precision.
• Keep wording professional and plain enough that a smart non-specialist can use the output directly.