The one-page account plan

Why account plans die at eleven sections

Every enterprise team has met the official account plan: eleven sections, a SWOT grid, a relationship heat map, three pages of fields. It gets written once — the week it’s mandated — read never, and quietly abandoned by exactly the reps who plan best, because a document that costs an evening to update loses to the quota every Tuesday.

The fix isn’t a better template. It’s a smaller claim: a plan’s only job is to hold what the team currently knows and currently believes about one account, in a form cheap enough to update after every conversation. That’s four sections, one page, every line dated. Anything more is a report wearing a plan’s name.

---

The new rep opens the account. Instead of forty tabs, there’s a page — written by the last owner, dated three weeks ago, ending with a sentence that says exactly what to test next.

The four sections

What does each section hold, and what is it for?

1 · Live problems, in their words. What this account is trying to change, quoted from its own announcements, hiring, and leaders — with a source and date per claim. This section is the output of the research hour, and its discipline is the same: change-in-motion only, no trivia.

2 · The people (the seat map). Who owns each problem, who decides, who pays, who can veto, who lives with it — names, engagement status, last-verified dates. The compact form of the full seat map; on the one-pager it’s five lines, not a diagram.

3 · Why we fit. The falsifiable line between what they’re changing and what you demonstrably fix — which of your best customers’ problems this account rhymes with, and the proof. If this section is generic, the account shouldn’t be on the list.

4 · The working hypothesis. One sentence: what you believe earns the next meeting, what the last conversation changed, and what would prove the whole pursuit wrong. This is the plan’s living edge — the only section that should change weekly.

The template

The one-page account plan

The whole artifact, rendered. Copy the structure; the values show one illustrative account.

1 · Live problems — their words, with receipts

• Throughput stall"Output has flatlined while orders grew" — COO, trade interview · Sep 4
• Systems consolidationTwo integration-engineer postings · careers page · Sep 18

2 · The people — seats, status, freshness

• Owns · Dir. of OperationsEngaged, two conversations · verified Sep 24
• Decides · VP OperationsIdentified — intro in motion via Director
• Pays · CFONever met — the plan's named risk
• Veto · Security leadIdentified — surface the review early
• Lives with it · team leadsNames unknown — ask the Director

3 · Why we fit

• The rhymeSame stall-plus-consolidation shape as our three best manufacturing customers at purchase

4 · Working hypothesis — the living edge

• We believeThe consolidation forces a tooling decision this FY; the Director will champion if the VP hears a defensible number · updated Sep 24
• Killed ifThe initiative loses its budget line, or the VP owns a competing in-house build
• Next testVP conversation — the Director offers the intro this week

The plan in motion

When does it get touched?

Three rhythms make the page worth more than the eleven-section binder it replaces:

After every meaningful conversation — two minutes: what changed, which claims got verified or killed, what the hypothesis says now. This is the update cost that makes the habit survivable.

Before every conversation — one minute: read the page, walk in current. The plan pays for itself here, daily.

At handoff — the whole point. Territory carve, promotion, attrition: the next owner starts from the page instead of from zero, and the company stops re-buying the same understanding every quarter. The handoff test is the plan’s quality bar: could a stranger read this page and know what to do Monday?

Keeping forty of them alive

One page per account works beautifully at ten accounts and starts failing at forty — not because the format breaks, but because the inputs rot: problems shift, people move, verified-on dates age, and refreshing them by hand is a research job wearing a maintenance costume.

Systematize the page’s inputs, keep its beliefs human. Narrative AI maintains sections one through three continuously — problems, people, and fit, sourced and dated as evidence moves — and proposes updates instead of waiting for the evening that never comes; the hypothesis stays the seller’s, every message stays rep-initiated, and every AI-suggested CRM change waits for the rep’s approval.

Four sections, one page, dated. The plan that survives is the one cheap enough to keep true.