How to Write a One-Page Account Plan (7-Section Template)

A one-page account plan is the artifact that decides whether a tier-1 account gets a real ABM motion or a generic outbound cadence. Per Forrester research, the median B2B sales team has account plans for fewer than 30 percent of its named tier-1 accounts in 2026, and the plans that exist are 12-page slide decks nobody reads. This is the format that fits on one page, gets used weekly, and travels well across reps when an account changes hands.

Full disclosure: Abmatic AI ships an account-graph layer that automates a chunk of the data inputs to an account plan, so we have a financial interest in good account planning. The format below is platform-agnostic. Use it in Salesforce, HubSpot, Google Docs, Notion, or whatever the team will actually open.

The 30-second answer

A one-page account plan has seven sections: account snapshot (firmographic plus current relationship), buying committee map, business problem hypothesis, prior interactions log, recommended next actions, internal coordination plan, and a 90-day milestone. Together, those seven sections fit on one printed page or one Notion page that loads in three seconds. Per public customer reports, teams that switch from 12-page plans to one-pagers see plan adoption rise from below 30 percent of tier-1 accounts to above 80 percent inside one quarter.

See an ABM platform that auto-populates account plan inputs from the account graph, book a demo.

Why 12-page account plans fail in production

The standard failure mode: the company adopts an enterprise account-planning template, reps spend three hours filling it in for the first plan, the plan goes into a folder, nobody opens it again, the next quarter someone notices the plans are stale, the company adopts a new template. Per public customer reports, this loop runs at most under-100M-ARR sales teams every 18 to 24 months.

The structural reasons:

• Length kills usage. A 12-page plan takes 90 minutes to update. Reps with 50 named accounts will not invest 75 hours per quarter on plan maintenance.
• No load-bearing fields. Long plans have many fields that no decision rests on. Reps quickly learn which fields nobody reads, fill those with placeholder text, and the plan becomes performative.
• No data integration. Plans that require manual data entry of CRM data are duplicates of CRM with extra steps. Reps drop the plan in favour of CRM.
• No 90-day milestone. Without a near-term outcome to anchor the plan, it becomes a permanent description of the account, not a forward-looking commitment.

The seven-section one-pager addresses each leak directly.

The seven sections

Section 1: Account snapshot

Five lines, all auto-populated. Industry, employee band, geo, ARR (estimated or actual), current deal stage. Pulls from CRM plus enrichment. The rep does not type any of this.

Section 2: Buying committee map

The committee map lists named contacts in the buying committee, by role: champion, economic buyer, technical buyer, end user, blocker. Each entry has a relationship status: cold, engaged, advocate, dormant. Auto-populates from CRM contact records, augmented by LinkedIn lookups and rep-side annotations. See buying committee and buying committee mapping.

Section 3: Business problem hypothesis

Two to four sentences. The rep's working theory of why this account would buy now: what business problem the product solves for them, what trigger event might activate the buying process, what their alternatives look like. This is the section that drives the rest of the plan; weak hypotheses produce weak plans.

Section 4: Prior interactions log

The last six meaningful touches across the buying committee. Auto-populated from the CRM activity log, filtered to meaningful touches (meetings, calls, replied emails, demo attendances), excluding noise (email opens, automated nurture). The rep glances at this before any new outreach.

Section 5: Recommended next actions

The top three actions for the next 30 days, prioritised. Each action has an owner (AE, BDR, marketing), a target date, and a success criterion. Examples: send a CFO-targeted ROI brief to the economic buyer by week 2, request a 30-minute discovery with the champion by week 3, queue a programmatic ad sequence to the broader committee for the month.

Section 6: Internal coordination plan

Who owns what across roles. AE owns the relationship arc. BDR owns prospecting net-new contacts. Marketing owns the campaign and content support. Customer success (if a customer) owns the renewal or expansion arc. The plan names the owner for each function for this account specifically; defaults are fine if explicit.

Section 7: 90-day milestone

The single outcome the plan is committing to in the next 90 days. Examples: secure a discovery meeting with the economic buyer by end of quarter, advance the open opportunity from stage-2 to stage-4, expand the buying committee from three known contacts to seven. The milestone is testable, has a date, and gets reviewed at the end of the period.

The framework: snapshot, committee, hypothesis, log, actions, owners, milestone

1. Snapshot populates automatically from CRM. No rep typing.
2. Committee map blends auto-populated CRM data with rep-side relationship annotations.
3. Hypothesis is the rep's load-bearing two-paragraph thesis on why now.
4. Interactions log auto-populates and stays current without rep effort.
5. Recommended actions are three named actions with owners and dates.
6. Coordination plan names cross-functional owners explicitly.
7. Milestone is the testable 90-day commitment.

The plan fits on a page, updates in 15 minutes monthly, and reads in 60 seconds.

How to roll this out without rep revolt

Three principles that determine whether reps adopt the plan:

• Auto-populate as much as possible. Sections 1, 2, and 4 should require zero rep typing on the first version. The rep edits, does not author.
• One template, one location. Pick Salesforce or HubSpot or Notion. Stick. Reps will not maintain three account-plan templates.
• Treat the milestone as a forecasting input. If reps see the milestones rolling up to the forecast, the plan becomes a tool, not a paperwork exercise.

Per public customer reports, the rollout pattern that works is to start with 10 to 20 tier-1 accounts, refine the template based on rep feedback, then expand to the full tier-1 list over one quarter.

Common traps

Trap 1: Adding a SWOT section

SWOT analyses sound thorough and produce no decisions. Drop them in favour of the business-problem hypothesis, which is shorter and more actionable.

Trap 2: No 90-day milestone

Without a milestone, the plan becomes a description, not a commitment. The milestone is the section that gets reviewed at quarter-end.

Trap 3: Recommending more than three actions

Five-action lists become zero-action lists. Three is the practical ceiling for a 30-day window.

Trap 4: Plan stored offline

Plans in Google Docs that nobody opens are worse than no plan. Plans in CRM that everyone sees during deal review get used.

Trap 5: Updating quarterly only

Quarterly updates produce stale plans. Sections 4 and 5 (interactions log and recommended actions) need monthly refreshes; the rest can update quarterly.

How this connects to the rest of the stack

The account plan is the rep-side artifact that the rest of the ABM stack feeds into. Tiering decides which accounts get plans. Prioritisation decides which plans get attention this week. Routing decides which signals update which plans. Influence reporting closes the loop on which plans produced pipeline.

For related frameworks, see account tiering, prioritising accounts with mixed signals, running 1:1 ABM for top 50 accounts, and target account list.

FAQ

How long should a one-pager actually be?

One printed page or one screen of a typical laptop without scrolling. Around 400 to 600 words plus the buying-committee table. Anything longer is a different artifact.

What template tooling is best?

Salesforce custom objects or HubSpot custom records keep the plan inside the rep workflow, which drives adoption. Standalone Notion or Google Doc templates require switching tools, which depresses usage. Pick the format that lives where the rep already works.

How often should the plan be updated?

Sections 4 and 5 (interactions log, recommended actions) update monthly. Sections 2, 3, 6, 7 (committee, hypothesis, coordination, milestone) update quarterly. Section 1 (snapshot) updates whenever CRM enrichment refreshes.

Who owns the account plan?

The AE on the account, with input from the BDR, the marketing partner, and customer success if applicable. The plan is reviewed in the regular deal-review meeting; ownership is single, input is plural.

How does this differ for tier-2 versus tier-1 accounts?

Tier-1 accounts get the full one-pager. Tier-2 accounts get a lighter version: snapshot plus committee plus three-action list, no separate hypothesis or milestone section. Tier-3 accounts do not get plans; they get programmatic motions only. See account tiering.

How does the plan interact with the forecast?

The 90-day milestone is the input. If the milestone is to advance an opportunity to stage-4, that becomes a forecast assumption. Roll milestones up to the team forecast at quarter start; review hit-rate at quarter close.

A one-page account plan is the smallest artifact that produces the largest behavioural change in tier-1 selling. Seven sections, fifteen minutes a month, one printed page. The teams that adopt it run tighter ABM motions and lose fewer named accounts to drift. The teams that stick with 12-page templates lose them to non-use.

See an account-plan workflow with auto-populated CRM data and committee mapping, book a demo.