Account plan

An account plan is a written plan for growing a specific customer relationship: what the account needs, who influences decisions, where the revenue could come from, and what the team will do about it over a defined period. It covers the account, not a single deal.

Why it matters in B2B sales

In accounts large enough to matter, the revenue that arrives next year is rarely the deal in front of you. It comes from a division nobody has spoken to, a renewal that needs defending, or a problem the customer has not yet framed as a purchase. None of that surfaces from working the current opportunity.

Account plans also survive people. A rep leaves and takes the relationship map, the political knowledge, and the reason a proposal was structured a particular way. Written down, that knowledge transfers in a week. Unwritten, it takes a new owner two quarters to rebuild, and the customer notices.

What goes in an account plan

The account's own situation first: their strategy, their pressures, their measures of success, in their words rather than yours. Then the map of who matters, which is where stakeholder mapping does the work, covering influence, priorities, and current disposition.

Then your position: what you sell them today, what the relationship health actually looks like, and where competitors sit. Then the opportunity: named expansion paths with a rough size and a trigger, plus the renewal and its risks. Finally the actions, dated and owned, and the review cadence, which is usually the QBR. A plan with no dated actions is a briefing document.

Account plan vs opportunity plan

An opportunity plan covers one deal: this requirement, this buying committee, this decision, this close date. An account plan covers the relationship over a year or more, and one account plan usually contains several opportunities at different stages.

The distinction matters because they fail differently. An opportunity plan goes stale when the deal closes and gets replaced. An account plan goes stale silently, and a plan written last January that nobody has touched is worse than none, because people trust it. The teams that get value from account planning review quarterly and delete what is no longer true.

A concrete example

A vendor with 200,000 of annual revenue in a manufacturing group maps four divisions, of which one is a customer. The plan identifies the group CIO as an unengaged sponsor, an upcoming ERP programme as a trigger, and two divisions with the same workflow problem the existing customer solved. Over four quarters the actions are unglamorous: an introduction through the existing sponsor, a site visit, a joint session with one division head. The second division signs eleven months later.

How it shows up in a modern proposal workflow

Account plans decay because they are separate from the work. The plan lives in one place and the actual deal material lives in another, so what the team learns during a bid never reaches the plan, and the plan never informs the next proposal. Cobl keeps the account's deals and documents in one workspace, so what was learned producing a proposal stays attached to the account it was about.

The test of a plan is whether someone new to the account could read it and know what to do on Monday. Most fail that test not because the thinking was wrong but because nobody updated it after the thinking changed.

Frequently asked questions

Which accounts need an account plan?

Accounts where the potential is larger than the current revenue and where several people are involved on the customer side. Planning a transactional account with one contact and no expansion path is overhead. A common cut is the top ten to twenty accounts by potential rather than by current spend.

How often should an account plan be updated?

Quarterly is the usual cadence, often anchored to the customer QBR so the review has real input. What matters more than frequency is that updates remove things that are no longer true, rather than only adding.

Who writes the account plan?

The account owner, with input from anyone who touches the customer: delivery, support, and any technical contact who hears things sales does not. Plans written by one person in isolation tend to record the relationship that person has rather than the one the company has.