How is this different from the renewal play?

The renewal play runs one moment — securing and expanding at a renewal. The strategic account plan runs the whole relationship: a stakeholder and whitespace map, a multi-quarter expansion sequence, and a multi-threaded value story across several buyers. Use the account plan to run a flagship account year-round; it then feeds the renewal play when a renewal comes up, sharing one source of truth.

Do I need a huge account for this to be worth it?

It's built for your highest-value, most complex accounts — the ones with multiple buyers, real whitespace, and a renewal big enough that losing it would hurt. For smaller or single-product accounts, the pre-call brief and renewal play are enough; reserve the full half-day campaign for the accounts where deliberate, multi-threaded planning actually changes the outcome.

What does 'multi-threaded' mean and why does it matter?

Single-threaded means the account rests on one relationship — usually a champion who could change roles or leave, taking the deal's momentum with them. Multi-threaded means you've built value cases and relationships across several stakeholders (the champion, the economic buyer, the blocker), each hearing the version that moves them. The plan flags every single point of failure precisely because a strategic account carried by one person is fragile.

How do I keep a strategic account plan's data safe?

It concentrates contract terms, internal politics, and named individuals' roles and relationships — among the most sensitive data you hold. Keep all of it in a workspace your company has approved, never paste a customer's private details into a tool you don't control, and scrub to [account] or [stakeholder] if you share a prompt for help.

The strategic account plan, end to end

when to reach for this

A strategic account is too big to run on instinct and single-threaded relationships — yet most get "managed" as a series of disconnected deals, with one champion who might leave, whitespace nobody mapped, and an expansion that only comes up at renewal. This is the orchestration play: pull everything you know into a stakeholder map, find the whitespace, build a value story that lands across multiple buyers, sequence the expansion over quarters, and assemble an account plan with named owners and approval gates. It pulls every other Sales playbook into one campaign — so a flagship account is run deliberately, by a team, not improvised by one rep.

gather this first

Everything on the account: the notes folder, the email threads, the CRM export, usage/adoption data, the org chart or LinkedIn map, and the current contract terms.
Your value-prop.md, icp.md, battlecards.md, and any discovery captures — the foundations this campaign orchestrates, not rebuilds.
The commercial picture: current contract value, the products they have vs. don't, known expansion opportunities, and the internal account team (who owns what relationship).

the workflow

Map the stakeholders and the whitespace

In Claude Desktop, open the account folder and ask in the chat — no terminal needed. Single-threaded accounts are fragile accounts. Before any plan, map who matters and where the unsold opportunity is — that's the terrain the whole campaign plays on.

you ask

Read the account notes, threads, CRM export, org map, and usage data. Build two things: (1) a stakeholder map — each key person, their role in decisions (champion, economic buyer, blocker, influencer), what they care about, and how strong our relationship is; and (2) a whitespace map — which products/teams/regions have us vs. don't, and where the biggest unsold opportunity sits. Flag every single point of failure (a deal resting on one champion).

what you get back A stakeholder map with relationship strength and gaps ("strong with the VP Ops champion; no relationship with the economic buyer in Finance — a single point of failure") and a whitespace map ranking the real expansion opportunities. The foundation everything downstream inherits.

The single-points-of-failure flag is the most valuable output here — a strategic account carried by one relationship is one job change away from churning.
Build the multi-threaded value story

Different stakeholders buy on different value. Turn the one value narrative into the specific case each key buyer needs to hear, so the account is sold across threads, not through one person.

you ask

Using value-prop.md, the usage data, and the stakeholder map, build the value story for this account: the concrete results delivered so far (with real numbers), then the specific value case re-pointed for each key stakeholder — what the champion, the economic buyer, and the blocker each need to believe. Name the proof point that lands for each.

what you get back A multi-threaded value story — the shared results plus a per-stakeholder case ("Finance needs the cost-per-seat trend; the champion needs the team-time saved") — so the campaign gives every buyer the version that moves them, not one generic pitch.
Sequence the expansion as a plan, not a wish

Turn the whitespace into an ordered play: which opportunity first, what has to be true to win it, and how each land sets up the next. This is the strategy the account plan executes.

you ask

From the whitespace map, sequence the expansion over the next 2–4 quarters: which opportunity to pursue first and why, the entry point and stakeholder for each, what has to be proven to win it, and how landing each one sets up the next. Call out the risks and dependencies — where one slip stalls the sequence.

what you get back An ordered expansion plan — "Q1: land the second region via the Ops champion using the onboarding proof; Q2: that adoption opens the Finance conversation for the enterprise tier" — with the dependencies and risks named, so growth is a sequence you drive, not a hope you wait on.
Pre-handle the account-level risks and objections

A campaign this size has predictable failure modes — a champion leaving, a budget cycle, a competitor in another division. Get ahead of them now, the way the renewal play pre-handles a single call.

you ask

Given the stakeholder and whitespace maps and our battlecards.md, name the 4 biggest risks to growing this account over the next year (champion change, budget freeze, a competitor in another division, stalled adoption) and the account-level objections each expansion will raise. For each, draft the honest mitigation or response, grounded in the value story — and what early signal would warn us it's happening.

what you get back A risk-and-objection plan — each major threat with a mitigation, an honest response, and the early-warning signal to watch — so the campaign reacts to a champion change or a budget freeze with a plan, not a panic.
Assemble the account plan and red-team it

Pull all of it into one living account plan with named owners, gates, and dates — then have Claude attack it. A skeptical pass now is far cheaper than discovering the gap two quarters in. Review the assembled file as a diff before it's saved.

you ask

Assemble a one-to-two-page account-plan.md: the stakeholder map, whitespace and expansion sequence, the multi-threaded value story, the risk plan, and a quarter-by-quarter action list with a named owner and any approval gate (pricing, legal, exec sponsor) for each move. Then red-team it as a skeptical VP: where is it single-threaded, which expansion assumes adoption we haven't hit, and what's the weakest link in the sequence? Show me the file before you save it.

what you get back A living account-plan.md shown as a visual diff to accept — owners, gates, and dates on every move — plus a red-team pass that names the weak link ("the Q2 expansion assumes a Finance relationship you haven't built yet"), so the team runs the account from one honest plan.

When Claude writes the plan, Desktop shows it as an accept/reject diff — review the whole campaign in one place, and make sure every commercial move has a named owner and a gate before it's saved.

make it your own

Spotted by the review: The weekly pipeline review and the renewal play surface which accounts deserve this full treatment — run the strategic plan on your flagship accounts, a lighter brief on the rest.
Feeds the renewal play: a strategic account heading into renewal hands its stakeholder map, value story, and risk plan straight to The renewal play — the campaign and the renewal share one source of truth.
Quarterly business review: the value story and results section drop straight into a customer-facing QBR deck — the same proof, pointed outward.
Keep it living (Power Track): save the assembly as an /account-plan command and let a scheduled agent refresh the stakeholder and whitespace maps each quarter off fresh data, so the plan never goes stale (see the Features tab).

watch out for

Put the approval gates on the plan. A strategic account touches pricing, legal, exec sponsorship, and multi-quarter commitments — none of which one rep owns. Name who signs off on each commercial move as a step in the plan, with deadlines, so expansion isn't held up by an unsecured approval at the worst moment.
A strategic account plan concentrates the most sensitive data you hold — contract terms, internal politics, individual stakeholders' roles and relationships. Keep all of it in your approved workspace, never paste a customer's private details into a tool you don't control, and scrub to [account]/[stakeholder] if you share a prompt.
Every number and relationship claim gets verified. A wrong usage figure, an overstated relationship strength, or an invented org detail steers a quarter of strategy wrong. Fact-check the data and sanity-check the stakeholder reads against what your team actually knows — the map is only as honest as its inputs.
Claude maps, sequences, and red-teams; the team owns the account. The plan is a living strategy to adapt as the account moves, not a script — relationships shift, priorities change, and a human makes the call on every commercial move and what to actually say to each stakeholder.

you'll end up with A living `account-plan.md` for a flagship account: a stakeholder and whitespace map, a multi-threaded value story, a quarter-by-quarter expansion sequence, a risk plan, and named owners and gates on every move — so a key account is run as a deliberate campaign by a team, not improvised deal by deal.

Questions people ask

How is this different from the renewal play?: The renewal play runs one moment — securing and expanding at a renewal. The strategic account plan runs the whole *relationship*: a stakeholder and whitespace map, a multi-quarter expansion sequence, and a multi-threaded value story across several buyers. Use the account plan to run a flagship account year-round; it then feeds the renewal play when a renewal comes up, sharing one source of truth.
Do I need a huge account for this to be worth it?: It's built for your highest-value, most complex accounts — the ones with multiple buyers, real whitespace, and a renewal big enough that losing it would hurt. For smaller or single-product accounts, the pre-call brief and renewal play are enough; reserve the full half-day campaign for the accounts where deliberate, multi-threaded planning actually changes the outcome.
What does 'multi-threaded' mean and why does it matter?: Single-threaded means the account rests on one relationship — usually a champion who could change roles or leave, taking the deal's momentum with them. Multi-threaded means you've built value cases and relationships across several stakeholders (the champion, the economic buyer, the blocker), each hearing the version that moves them. The plan flags every single point of failure precisely because a strategic account carried by one person is fragile.
How do I keep a strategic account plan's data safe?: It concentrates contract terms, internal politics, and named individuals' roles and relationships — among the most sensitive data you hold. Keep all of it in a workspace your company has approved, never paste a customer's private details into a tool you don't control, and scrub to `[account]` or `[stakeholder]` if you share a prompt for help.