Strategic Account Planning for Corporate Groups: One Plan Across Parent and Subsidiaries

What strategic account planning should decide

Strategic account planning is the repeated process of choosing how to protect and grow an important customer relationship. The plan is its dated decision record. It should explain the customer outcome the team wants to support, the part of the corporate group covered by the plan, the current commercial position, the few opportunities worth testing, the people who influence the next decision and the actions the team accepts.

A company profile is useful research but is not a plan. Neither is a contact list, a relationship diagram or a collection of open opportunities. Those artefacts describe parts of the account. Planning requires choices and exclusions. A reviewer should be able to see why one subsidiary is a priority, why another is outside scope and what evidence could change either decision.

Start with a customer-centred objective. “Grow the account” is too vague to guide action. “Help the group standardise a verified workflow across the three operating entities that have the same requirement” is testable, provided the requirement and entities are actually confirmed. The commercial outcome may follow, but the plan should not invent customer value merely to support an internal target.

Define a time horizon and the decision to be made by its end. A 90-day planning cycle might aim to confirm agreement coverage, establish whether two subsidiaries share the same need and decide whether to qualify one expansion motion. It should not imply that an enterprise procurement cycle will close on the same timetable. The horizon governs learning and team action, not the customer’s calendar.

Write stopping rules. If the local entity is already covered, lacks the relevant use case or asks the team not to pursue the idea, close the hypothesis. A plan without a way to say no becomes a repository of permanent optimism. A smaller plan with current evidence is more useful than a comprehensive document that cannot be challenged.

Plan the relevant group, not the logo

Choose a planning anchor and an inclusion rule before collecting information. The anchor could be the contracting entity, a regional operator or the ultimate parent. It is a navigation point, not automatically the buyer. Record the stable entity identifier and the definition used so the group can be reconstructed when names or ownership change.

Include legal entities that are commercially relevant to the objective. That may mean operating subsidiaries in selected markets with a plausible use case, plus the parent or shared-service company that influences the decision. Exclude passive holding companies, dissolved entities, unrelated minority investments and out-of-scope jurisdictions, while retaining the reason for each exclusion.

Separate ownership from buying organisation. The ultimate-parent and immediate-parent guide explains the legal chain. The buying path can cut across it. A local subsidiary can have its own budget while a central team sets standards; a shared-service company can influence deployment without owning the operating companies. The plan should link these facts rather than replacing one with the other.

Give each included entity a status: active customer, confirmed covered, coverage unknown, candidate for research, explicitly excluded or structural context only. This prevents a group member count from becoming an opportunity count. It also makes missing evidence visible. “Unknown” should open a question, while “candidate” should require a fit reason and a named next step.

For very large groups, split the operating view while preserving one coordination layer. Regional or business-unit subplans can carry their own buyers, agreements and actions. The group plan should state the shared objective, cross-entity dependencies, executive relationships and conflict rules. This keeps local detail manageable without creating isolated teams that approach sister companies with inconsistent assumptions.

Use four linked layers instead of one long document

The first layer is the group objective. Record the customer outcome, planning horizon, owner and success evidence. Keep one primary objective. Supporting objectives can exist, but competing priorities make it hard to tell which actions matter. If the team cannot agree on the objective, the account is not ready for a detailed action plan.

The second layer is the entity position. For each in-scope company, record identity, relationship to the group, customer status, agreement coverage, adoption or service context, accountable commercial owner and current work. Keep sources and dates. A field that says “customer” without naming the entity or agreement cannot safely support expansion.

The third layer is the buying path. Identify the relevant business unit and buying roles for the specific problem, then connect people only when the relationship is supported. Avoid building a giant organisation chart. The relationship-mapping guide shows how to distinguish decision roles, access and verified introduction paths.

The fourth layer is the action register. Every open question or hypothesis needs an owner, due date, next decision and evidence standard. “Research Germany” is not a sufficient action. “Agreement owner confirms whether Northstar GmbH is covered before 7 November; if covered, close the local expansion hypothesis” is clear enough to execute and review.

Keep structured facts near their systems of record and render a concise review view. Copying CRM, contract and support data into a slide deck creates another place for it to decay. The plan can link or summarise governed records while retaining the evidence date and accountable source owner.

Build the baseline before proposing growth

Begin with identity and structure. Reconcile CRM accounts to distinct legal entities, confirm parent-child links and flag unresolved matches. Shared domains, similar names and common addresses are clues rather than sufficient proof. The CRM data-quality guide describes why related subsidiaries should be linked rather than merged.

Next reconcile the commercial record. Which entity signed each agreement? Which products, services, territories or affiliates are covered? Who owns the renewal and service relationship? Where the answer requires interpretation, assign it to an authorised agreement owner. Sales assumptions should not substitute for a contractual reading.

Record current adoption and outcomes at the lowest useful grain. A parent-level revenue total can hide one successful subsidiary and several unrelated entities. Likewise, a global contact count can make relationship coverage look strong when all contacts sit in one business unit. Use entity, product and buying-unit dimensions where they affect the decision.

List active opportunities, commitments and service issues. Protect them from the planning exercise. A new group coordinator should not silently take ownership from a local seller, and a speculative expansion idea should not distract from an unresolved customer problem. The plan must show dependencies and accepted handoffs before it changes routing or outreach.

Date the baseline. Corporate structures, roles, agreements and priorities move. “As of” dates let reviewers distinguish a stale statement from a current unknown. Assign refresh responsibility to the field owner rather than asking the account lead to validate every source alone.

Turn white space into testable expansion hypotheses

A blank product-by-entity cell is a question, not pipeline. The entity may already be covered through a group agreement, may not have the use case, may buy through another route or may be unsuitable for the offer. Use the white-space analysis guide to classify covered, uncovered, unknown and excluded cells before prioritising them.

Write each hypothesis in a form the team can disprove: a named entity or buying unit, a specific problem, evidence that makes the problem plausible, the customer outcome the offer could support, the missing evidence and the next decision. Do not begin with the product and search the corporate tree for somewhere to place it.

Prioritise with separate dimensions. Consider fit, customer relevance, relationship access, timing evidence, agreement constraints and delivery capacity. Keep uncertainty visible instead of averaging it into a precise-looking score. A strong fit with no customer evidence remains a research hypothesis; an engaged contact without the relevant role remains an access clue.

Limit work in progress. A strategic account plan with fifteen open plays usually lacks a real priority. Select the smallest set that the account team can investigate well without harming current service. Put the remainder in a dated backlog with the condition that would bring each item back into review.

The funnel above is illustrative because no universal conversion rate applies. Its useful lesson is directional: each stage should narrow the field through better evidence. If every connected entity survives every gate, the inclusion criteria or review challenge is probably too weak.

A corporate-group strategic account plan example

Suppose the fictional Northstar group has one current UK customer, operating subsidiaries in Germany and France, and a recently acquired Dutch company. The group objective for the next 90 days is to protect the UK renewal and determine whether one verified cross-entity workflow merits a qualified expansion conversation.

Northstar UK Ltd holds the current relationship. Its renewal and customer outcomes stay first. Northstar GmbH appears to operate a comparable process, but the team has not verified local need or purchasing autonomy. The plan gives the local seller an investigation action rather than creating an opportunity.

Northstar France SAS appears uncovered in CRM. The agreement owner has not yet confirmed whether the UK contract includes the French affiliate, so the immediate action is coverage verification. Meridian Labs BV joined the group recently. Until legal completion, operating integration, permissions and ownership are confirmed, the plan holds commercial outreach.

The group view prevents four bad outcomes: treating every entity as open pipeline, contacting an affiliate already covered by contract, shifting the UK renewal owner without a handoff, and using an acquisition announcement as proof of customer demand. It also creates one valid research path for Germany without overstating the result.

At the review, the team might learn that France is covered, Germany buys independently and Meridian will remain operationally separate. The plan then closes the French hypothesis, keeps Meridian outside scope and decides whether the German need merits customer-led discovery. Progress is the quality of those decisions, not the number of boxes filled.

Connect people to the decision and the entity

Map roles for the specific hypothesis: problem owner, operational user, economic authority, technical or security reviewer, procurement, legal and executive sponsor where relevant. The same person may hold several roles, and some roles may sit at group level while others remain local. Record which entity and buying unit each role belongs to.

Distinguish known, inferred and missing roles. A senior title does not prove decision authority. An introduction path does not prove support. A contact who helped with one subsidiary may not be authorised to discuss another. The plan should show the claim, its basis and the next respectful way to verify it.

Coordinate outreach through the accountable account lead. Before contacting a sister company, check current relationships, customer preferences, agreements and local ownership. A warm introduction should have a customer-relevant reason. “You are in the same group” is context; it is not a value proposition.

Protect personal data and access boundaries. Store only the information needed for the business purpose under the organisation’s policies. A corporate link does not expand consent or permission across entities. Where a divestiture or restricted programme changes access, the plan should trigger a review before information is shared.

Give the plan one owner and many accountable contributors

Name one plan owner who convenes the review, resolves conflicts and accepts changes. This person does not perform every task. RevOps can own data rules and account relationships; customer success can own adoption evidence; agreement owners can confirm coverage; regional sellers can own local discovery. Each field and action needs the person best placed to maintain it.

Separate the group coordinator from entity execution owners. The coordinator maintains the shared objective and prevents conflict. Execution owners retain local customer context and accepted actions. Define when a decision requires consultation or approval, especially for reassignment, executive outreach, pricing, data access and cross-border coordination.

Use a decision log for disputed or material choices. Record the question, evidence, decision, owner, date and condition for reopening it. This stops the same debate from returning without new facts and makes handoffs easier. It also reveals whether a planning rule consistently creates exceptions that need a policy change.

Keep commercial credit rules outside the legal hierarchy. A parent-child link should not decide who receives pipeline credit, and a compensation rule should not rewrite the corporate structure. The sales-territory planning guide provides a separate method for group coordination, local execution and conflict resolution.

Review acquisitions, divestitures and reorganisations without rewriting history

Use material structural events to reopen the plan. Confirm the entity, relationship type, announcement date and effective date. Then assess commercial impact as separate questions: agreement scope, buying authority, service obligations, data access, opportunity ownership and customer communication. Ownership change is context, not automatic permission to update them all.

Preserve previous relationships and plan decisions. A divested subsidiary may leave the current group view while its historical activity remains attributed to the former structure for the period in which it occurred. Label the time basis of reporting so current and historical views do not silently contradict each other.

Distinguish a source correction from a real-world event. A provider may fix a duplicate, reveal an older relationship or change its classification. That update may improve the account map without creating a customer trigger. The corporate-change trigger guide shows how to route events through verification and commercial-impact review.

Monitor changes according to materiality. Prioritise events that could affect current agreements, active work, ownership or the plan boundary. Retain low-impact changes for reference without interrupting the account team. A high alert count is not a sign of better planning if the review queue hides the changes that matter.

Make the review a decision meeting

Send a concise pre-read that highlights changes since the last review: new evidence, closed questions, blocked actions, customer feedback, structural events and decisions required. Do not spend the meeting reading the company profile. Participants should arrive prepared to accept, reject, defer or reassign the decisions on the page.

Review the current customer first. Confirm service risks, commitments and renewal dependencies before discussing expansion. Then inspect the entity boundary, agreement coverage and buying path. Challenge each active hypothesis: what evidence improved, what remains missing, and what would cause the team to stop?

Close with an action register containing owners and due dates. Record decisions immediately and update the plan’s modification date only when the content genuinely changes. Archive superseded review snapshots when history matters. A continuously edited page without dated decisions makes it difficult to explain why the team acted.

Measure evidence resolved, customer-validated progress and commercial outcomes separately. Useful leading indicators include agreement questions answered, buying roles verified and customer actions completed. Qualified pipeline, retained revenue and expansion revenue are later outcomes. Meeting counts and contact volume can support diagnosis but should not be presented as proof that the plan works.

Start with one strategic group and one planning cycle. Use the current systems of record, add only the fields required for decisions and watch where ownership or evidence breaks down. After the pilot, standardise the smallest repeatable plan structure. The goal is not a perfect template; it is a trustworthy rhythm for making better account decisions.