Scale Strategy with Territory Business Plans

Learning Objectives

After completing this unit, you’ll be able to:

Explain how a Territory Business Plan extends the connected planning model from a single account to a region.
Describe the similarities and differences between territory-level planning and account-level objects.
Explain how a shared Goal Definition keeps account and territory progress aligned and comparable.
Describe how progress rolls up from field tasks to the Territory Business Plan.

Scale the Plan Beyond One Account

In the previous unit, you explored running a single Account Plan from import to live execution. Such a plan captures one customer relationship completely. It also captures only one.

A regional leader works at a different level. A field director is often accountable for a product push across dozens of health systems at once. Each one has its own pharmacy and therapeutics (P&T) committee, its own timeline, and its own competitive picture. Reading that whole region from Account Plans opened one at a time is slow and uneven. The pattern that matters most, which territories are advancing and which have stalled, stays out of view.

The Territory Business Plan answers that need. It applies the connected model you built for one account to an entire region. Because it runs on the same blueprint, a regional leader gains portfolio-wide visibility without learning a new tool or vocabulary. In this unit, you follow a regional leader at Cumulus as they build a Territory Business Plan and coordinate the launch across the accounts in their territory.

Understand the Parallel Structure

Before building anything, it helps to see how territory planning maps onto the account planning data structure you already know. The two mirror each other, with a single deliberate difference at the goal level.

Plan Level	Parent Plan	Goal Instance	Execution Layer
Account	Account Plan	Account Plan Objective	Action Plan and Assessment Tasks
Territory	Territory Business Plan	Goal Assignment	Action Plan and Assessment Tasks.

A Goal Definition sits above both levels as the shared organizational blueprint. Import it into an Account Plan and the system creates an Account Plan Objective. Import the same goal into a Territory Business Plan and it creates a Goal Assignment, the territory-level counterpart, carrying the same strategic intent across a wider scope. Beneath that goal instance, the execution layer is identical.

That symmetry is the point. A regional leader plans in the same language the field teams use, so work done on one account and work coordinated across a region stay comparable. The shared blueprint, not a separate reporting system, is what keeps regional strategy and account execution aligned.

Build the Territory Business Plan

Creating a Territory Business Plan follows the same workflow as account planning. Open Territory Business Plans, select New, then name the plan, associate it with a territory, set the planning period, and add a description.

Two settings enable this layer.

Territory Foundation: Configure territory status values, completion mappings in Key Account Management settings, and territory trigger handlers.
Template Target Object: Create an Action Plan Template with its Target Object set to Goal Assignment so imported tactics attach to the territory hierarchy.

With the plan saved, open the Goal Assignments tab, the territory equivalent of the Account Plan Objectives tab, and click Import Template. The modal presents the same Goal Definitions that the field teams see. The difference is what the import creates: a Goal Assignment rather than an Account Plan Objective. The Goal Assignment is populated with the territory-targeted action plan and its assessment tasks.

At Cumulus, the regional leader builds the Immunexis Regional Market Access Plan for the San Francisco North territory and imports the formulary goal. Because the template was authored for regional coordination, the tactics it deploys read at the level of the whole territory rather than a single account. They consolidate evidence needs across the region, or analyze review cycles across every integrated delivery network (IDN) within it.

In a few steps, the regional leader has a structured plan for the entire territory, built from the same blueprint that a key account manager draws on for a single account. Same strategy, wider scope.

Monitor Progress Across the Region

With the plan in place and the work underway, the regional leader's job turns to coordination and visibility. As field teams complete the regional assessment tasks under each Goal Assignment, the territory trigger handlers recalculate progress automatically. Completion climbs from each assessment task, through the action plan, through the Goal Assignment, and up to the Territory Business Plan, just as it does for accounts.

From a single screen, the regional leader reads how the new launch strategy is progressing across the territory, without aggregating reports by hand or waiting on updates from individual accounts. Because account plans and territory plans draw on the same Goal Definitions, the two views line up for comparison. The leader can monitor which territories are advancing and which accounts need support, then shifts attention there. It all comes from one connected view, built on the same frameworks the field already uses.

This is the return on a decision made back at the blueprint stage, to share one strategic foundation across both scopes. That choice is what brings a regional pattern and an account detail into the same picture.

Wrap Up

The Immunexis launch now runs on one connected system. A regional leader coordinates the strategy across the territory while key account managers run it account by account. Every closed task, profiled stakeholder, and completed sprint rolls into a single, current picture of where the launch stands. Strategy and execution are no longer separate documents. They are part of the same living plan.

Viewed as a whole, Key Account Management connects every layer of the commercial organization. An admin builds the reusable blueprint of approved goals, governed templates, and the assignments that bind them. A key account manager imports that blueprint into a live account plan, profiles the stakeholders, aligns the team, and works the plan to completion. A regional leader applies the same frameworks across a territory and reads progress from one connected view. At every level the same blueprint, the same vocabulary, and the same roll-up logic keep strategy and execution aligned, from one field task to a national objective.

Because each layer holds connected, structured data rather than scattered notes, the plan keeps leadership current. It also gives Agentforce the context to summarize an account or recommend the next move. That is what turns key account planning from a static record into a system that grows more useful the more the team works it.

Tempo estimado

Tópicos

Procurando ajuda?