account-planlisted

# Account Plan Most account plans are written once, for a review, and never opened again. They are a document produced to prove planning happened rather than an instrument anyone uses. The test that fixes this: **could someone inheriting this account in month four read it and know what was promised, by whom, and what is supposed to be true by when.** If not, it is a status report with an ambitious heading. The failure this exists to prevent: **the plan full of activity.** Twelve initiatives, no measure, no owners on the customer side, and no way to be wrong. It cannot be failed, so it is never achieved. --- ## What this needs **Shared context.** If an `account-context` document exists, read it first for the value metric and the segment norms. This plan expresses one account's version of what that document defines generally. Where it is absent, carry on and name the assumption. **Minimum: the account, its contract, and what you know about their goals.** Enough for a plan with honest gaps marked. **Better with** the original business case, the current outcome data and a stakeholder picture, which between them give the objective, the measure and the owners. **Best with** the customer's own stated goals, agreed with them rather than inferred. A plan written about a customer is weaker than one written with them, and the difference shows at the renewal. --- ## Which plan is this Three objects in this library carry the word plan and they are not interchangeable. - **`ac