An ABM Account Plan Template for Sales and Marketing

TL;DR. Use this ABM account plan template to give sales and marketing one shared view of an account: its likely problem, what you know, who you need to reach, what proof to offer and what happens next. Keep verified facts separate from hypotheses, and give every next action an owner and a review point. The blank template and hypothetical example below show how to turn account research into a coordinated plan.

What should an ABM account plan help you decide?

Write the plan to answer a practical question: what should we do next for this account, and what evidence supports that choice?

A company profile alone does not answer it. Industry, size and product categories provide context, but your plan needs a specific problem worth investigating.

Start with account fit. Use your ideal customer profile to explain why this account deserves attention. Then write a problem hypothesis that someone at the account can confirm, correct or reject.

For example: “The operations team may struggle to approve supplier changes because requests move between disconnected queues.”

That is a starting question for discovery. It becomes a confirmed problem only when you have evidence from the account.

For the wider programme, use the account-based marketing playbook. Keep this document focused on decisions about one account.

What goes in the ABM account plan template?

Copy this table into a shared document. Keep answers short enough that sales and marketing can review them together.

Section	What to record	Completion check
Account and scope	Organisation, business unit and use case	Everyone knows which part of the account the plan covers
Reason to prioritise	Fit with your ICP and evidence of a relevant need	The reason goes beyond brand recognition
Verified facts	Evidence, source, when checked and limits	Another teammate can trace each fact
Problem hypothesis	Suspected problem, affected role and possible consequence	The statement is explicitly marked unconfirmed
Open questions	What would confirm or disprove the hypothesis	Each important unknown has a discovery question
Relationships	Known contacts, their involvement and missing perspectives	Interest is separate from authority
Relevant proof	Evidence suited to the problem, role and decision	Claims stay within what the evidence supports
Shared next outcome	An observable change in understanding or commitment	Completion can be checked
Coordinated actions	Action, owner, dependency and review point	Outreach has a clear sequence
Review decision	Continue, revise, pause or stop	The next investment follows from evidence

Leave a field marked “unknown” when necessary. Add an action to resolve an important unknown instead of filling it with a confident guess.

How do you separate verified facts from guesses?

Use three labels throughout the plan:

• Verified fact: directly supported by an identifiable source.
• Hypothesis: a plausible explanation that needs testing.
• Unknown: something you cannot yet assess.

Record the limits of each fact. A contact saying “our team uses spreadsheets” supports a statement about that team. It does not establish how the whole organisation works.

Likewise, a public announcement about expansion does not verify a budget, buying deadline or need for your product. Record the announcement as a fact and any commercial interpretation as a hypothesis.

For each important entry, capture the source and when it was checked. If sources conflict, retain both accounts and assign someone to resolve the difference. Avoid quietly replacing uncertain evidence with a cleaner story.

How should you map relationships and choose proof?

Map people by their involvement in the decision. Include these perspectives where relevant:

• The person experiencing the problem.
• The person responsible for the outcome.
• The person evaluating practical fit.
• The person approving spending.
• Anyone able to block implementation or purchase.

One person may cover several perspectives. Mark each role as confirmed or assumed, and record what access you actually have.

Replace “build an executive relationship” with a specific gap: “We have not spoken to whoever owns approval turnaround.” Then decide whether an existing contact can help arrange that conversation.

Choose proof against the question each person needs answered. A process owner may need to inspect the proposed workflow. A technical evaluator may need integration documentation. A spending approver may need an estimate built from inputs the account has validated.

Record what each asset demonstrates and what remains unproven. Use only customer evidence you have permission to share. Label demonstrations, assumptions and estimates clearly.

What does a filled account plan look like?

This is a hypothetical example, not a customer story. All account details, roles, interactions and evidence below are illustrative.

The seller offers approval workflow software. The target is an unnamed distributor’s purchasing team.

Field	Illustrative entry
Scope	Supplier-change approvals within the purchasing team
Reason to prioritise	The use case appears to fit the seller’s workflow capabilities; urgency and commercial fit remain unverified
Verified fact	In an illustrative discovery conversation, the purchasing lead described requests arriving through email and a shared sheet; this covers their team only
Problem hypothesis	Unclear ownership may be causing requests to wait between purchasing and finance
Unknowns	Frequency, business impact, finance’s perspective, spending authority and competing priorities
Shared next outcome	Purchasing and finance review a process map together and confirm whether the suspected handoff problem exists
Current relationship	Purchasing lead engaged; authority to approve spending unknown
Relationship gap	No contact with the finance colleague who handles these approvals
Relevant proof	A demonstration using sample requests, showing ownership and approval status; no claim of measured savings
Continue condition	Both teams recognise a problem and agree to evaluate a possible change
Pause condition	The problem is not material, or the account does not want to investigate it

The coordinated actions make the plan usable:

Sequence	Action	Owner	Dependency or review point
First	Ask the purchasing lead to correct the draft process map and identify the finance participant	Sales	Review the response before further outreach
Next	Prepare a walkthrough around the confirmed process	Marketing	Use the corrected map
Then	Hold a joint discovery conversation, if accepted	Sales	Confirm finance participation
After discovery	Revise the hypothesis and agree whether a demonstration is useful	Sales and marketing	Use the account’s stated problem

Marketing does not need a separate campaign to every possible contact. In this example, its immediate contribution is material that supports the agreed conversation.

If finance says approvals move quickly, revise the hypothesis. Do not preserve it simply because the walkthrough is ready.

How often should sales and marketing review the plan?

Use a weekly review as a starting point for active accounts. For accounts without a near-term action, choose a lighter cadence and record what would justify renewed attention.

In each review, answer:

1. What new evidence did we obtain?
2. Which hypothesis changed or was rejected?
3. Which relationship gap now matters most?
4. What happened after the last action?
5. Should we continue, revise, pause or stop?

Update the plan after a meaningful conversation, even if the scheduled review is later. Name one person to maintain it, while each action owner updates their own commitments.

Measure progress through observable changes: a problem confirmed, an introduction accepted, an evaluation question answered or a next step agreed. Keep content consumption separate from commitments made by the account.

What common mistakes should you avoid?

Writing a generic problem. “Improve efficiency” gives little direction. Specify the workflow, affected role and consequence you want to investigate.

Treating a contact as a champion. Record what they have done to advance the discussion before assigning that label.

Sending proof before understanding the question. Choose material that addresses an identified concern.

Running disconnected outreach. Give sales and marketing a shared sequence, including what must happen before the next message.

Keeping every account active. Use explicit pause conditions when fit, need or willingness to engage remains weak.

Overplanning a simple purchase. If one buyer can assess a standard offer directly, shorten the document to the problem, evidence and next action.

What else should you know about ABM account planning?

Related reading

• Account-Based Marketing B2B Playbook — place individual account plans within your wider programme.
• How to Build an ICP — define which accounts deserve focused attention.
• MQL to SQL Handoff — agree how marketing and sales accept responsibility for the next step.