The account plan as most organizations practice it is a document that exists to demonstrate to management that the account team has a plan. It is reviewed at the beginning of the year, updated at mid-year, and referenced again during QBR season. It contains the right sections: whitespace analysis, organizational map, strategic objectives, opportunity list, competitive positioning. It is usually accurate at the point it is written and increasingly fictional by the time it is reviewed.
The account team that works from this document is not working from a plan. They are working from a historical record of what the plan used to be. The customer’s organization has changed since the plan was written. The priorities have shifted. The stakeholders have moved. The document has not.
What an account plan is for
An account plan that is useful for the account team answers a specific set of questions that the account team needs to answer to do their job well.
Who in the customer organization is shaping the decisions that matter to us? Not the org chart, which is a record of reporting lines, but the actual influence map: who talks to whom, whose opinion shifts other people’s thinking, who needs to be aligned before a recommendation can move forward. The org chart and the influence map overlap but are not the same. The account plan needs the influence map.
What does the customer care about in the next two quarters? Not what they cared about when we wrote the plan, but now. What is on the agenda at their leadership meetings. What is the strategic initiative that has absorbed organizational attention. What has changed in their market or their competitive environment that is reshaping their internal priorities. The account plan that answers this question requires the account team to have conversations with the customer regularly, not to rely on what was written down six months ago.
Where is the account headed over the next two years, and where are we in that trajectory? A customer that is expanding the relationship has a different profile than a customer that is stabilizing at current spend. A customer that is in a period of internal organizational change behaves differently than one that is in steady state. The account plan that helps the account team understand the trajectory helps them make better decisions about where to invest attention.
What does the customer believe is true about us that is wrong, and what is missing from their understanding of what we can do? Most customers have an incomplete or slightly inaccurate mental model of their technology partners. The account team that knows which specific gaps and inaccuracies exist in the customer’s view of them is the one that can do something about it. The account plan that answers this question requires the account team to be honest about what they have not managed to communicate.
What makes most account plans useless
Most account plans fail to answer these questions because they were designed to answer different ones.
The questions that account plans are typically designed to answer are the questions management needs answered to forecast revenue: what is the total opportunity, what is the likely spend this year, what is the pipeline, what are the risks to the number. These are legitimate questions and management has legitimate reasons to need the answers.
But they are not the questions that help the account team serve the account. They are reporting questions, not planning questions. An account plan built around reporting questions is a useful management tool that masquerades as a strategic document. The account team that confuses the two ends up with a plan that serves the forecast call and a head full of relationship context that was never written down because the plan template did not have a place for it.
What happens when the plan is wrong
An account plan that has not been updated since the customer’s priorities changed is not just unhelpful. It is actively misleading.
The AE who approaches a conversation with a customer using last quarter’s account plan as their frame of reference is working from the wrong map. They are asking about an initiative that has been deprioritized. They are not aware of the new organizational structure that changed who makes decisions in the account. They are pitching the expansion path that made sense when the plan was written and that now runs into an internal political situation that the plan does not reflect.
Customers notice when a vendor’s mental model of their organization is out of date. It signals that the vendor is not paying close attention. In enterprise accounts where the relationship is the primary competitive differentiator, not paying close attention is a serious problem.
What good account planning looks like
The account plans that help account teams are living documents with a short update cycle. Not because the template requires quarterly updates, but because the account team uses the plan actively and finds errors in it as they work.
They are written in the language of the account team’s understanding, not in the language of the management template. The stakeholder section describes how decisions actually get made, not what the org chart says. The objectives section describes what the customer is trying to accomplish, not what the account team is trying to sell. The risks section describes real risks that the account team is actively managing, not a generic list of competitive threats.
They are updated when the account changes. When a new executive joins the customer’s leadership team, the account plan is updated. When a strategic initiative is announced that affects the account team’s relationship, the account plan is updated. When a competitive vendor makes a significant move in the account, the account plan is updated. Not at the end of the quarter.
And they are distinct from the management reporting documents that exist to satisfy the forecast process. The account team that understands this distinction can maintain both: the living account intelligence document that helps them do their job, and the reporting document that satisfies the organizational process. Both are necessary. Conflating them produces a plan that does neither job well.
The underlying question
The account plan exists to help the account team answer one underlying question: what do we need to do in the next three months to move this account in the right direction?
Everything in the plan that helps answer that question is useful. Everything that does not is documentation.
Most account plans contain a lot of documentation and not enough of what helps. The fix is straightforward: start with the question, add only what helps answer it, remove the sections that exist for the template and not for the account team, and update the plan when the account changes, not when the process requires it.
The account teams that do this have a competitive advantage that does not show up in any system of record. They know their accounts. Their plans reflect what is actually true right now, not what was true when the year began. And when the customer’s organization changes, they are the ones who already knew it was coming.