Account Expansion Plan: 6-Month Template With a Worked Example
9 min read ยท 2026-10-25
An account expansion plan is a written plan for growing revenue inside an existing customer, by selling more seats, a higher tier, a new product or the same product to another team. It names the opportunity, the people you need to reach, the value you will prove and the steps, owners and dates that get you to a signed order.
The template below covers six months for one strategic account. It starts with a health check, because you cannot expand an account that is not getting value, and it ends with adoption of what was sold, because expansion that does not get used turns into churn at renewal. Account executives, account managers and customer success managers can use it alone or as a shared plan.
The roadmap at a glance
Goal: One expansion deal signed in a healthy account, with the new users or teams live and using the product before the next renewal conversation starts. Duration: 6 months (26 weeks)
Health check (Weeks 1-2)
Confirm the account is getting value today and is ready for a growth conversation.
- Pull usage data for the last two quarters: active users, features used and trends by team.
- List open support tickets, escalations and any promises from the original sale that were not delivered.
- Ask your main contact and the executive sponsor how they rate the results so far against the goals they bought for.
- Fix or plan fixes for anything blocking value before you talk about buying more.
Milestone: A one-page health summary rated green, amber or red, agreed by the AE and the CSM. Only green or amber accounts move to the next phase.
Whitespace and opportunity map (Weeks 3-5)
Find where the account could use more of what you sell and rank the options.
- Map the customer's org: business units, regions and teams, and mark which ones use your product today.
- Build a whitespace grid with teams as rows and your products or tiers as columns, and mark each cell as owned, in use, possible or not a fit.
- Look for triggers such as new funding, a merger, a new executive, a hiring push or a project announced in an earnings call.
- Rank the top three opportunities by size, fit and how easy they are to reach through current contacts.
Milestone: A whitespace grid and a ranked list of three expansion opportunities, reviewed with your sales manager.
Stakeholder map and access (Weeks 4-8)
Reach the people who can say yes in the new team or for the new product.
- List the buying roles for the top opportunity: economic buyer, champion, users, IT or security, procurement.
- Rate each contact as supporter, neutral or blocker, and note who knows whom.
- Ask your current champion for introductions to the target team, with a short note they can forward.
- Book an executive sponsor meeting between your leadership and theirs if the deal is large enough.
Milestone: Meetings held with the economic buyer and at least one future user in the target team, logged in the CRM.
Discovery and joint business case (Weeks 7-12)
Build a business case the new buyer agrees with, based on their goals and your proof inside the account.
- Run discovery with the target team on their goals, current tools, pains and timing.
- Collect results from the teams already using the product, such as time saved or errors avoided, and get the customer to confirm them.
- Write a short business case with the problem, the proposed scope, the expected result and how it will be measured.
- Review the business case with your champion before it goes to the economic buyer.
Milestone: A business case the economic buyer has read and agreed to take forward, with a target decision date.
Proposal and close (Weeks 12-18)
Agree on scope, commercial terms and the steps to signature.
- Build a mutual action plan with dates for the proposal, security review, legal review and signature.
- Decide whether to add the expansion to the current contract or co-term it with the renewal, and agree this with deal desk.
- Present the proposal to the economic buyer and handle procurement questions.
- Plan the rollout with the CSM before signature, so the customer sees how the new team gets started.
Milestone: Expansion order form signed and booked in the CRM, with the rollout plan attached.
Rollout and adoption (Weeks 19-26)
Get the new users or product live and producing results before renewal.
- Run a kickoff with the new team, with named admins and a target go-live date.
- Run training and track weekly active users in the new team against the rollout plan.
- Hold a 60-day review with the economic buyer to check results against the business case.
- Record lessons and next whitespace opportunities in the account plan.
Milestone: The new team meets its adoption target at the 60-day review, and the account plan is updated with the next opportunity.
Account expansion plan vs account plan
An account plan covers everything about a customer: goals, relationships, risks, renewal and growth. An account expansion plan is the part of it that focuses on one growth opportunity, with its own steps, owners and dates. Many teams keep one account plan per strategic customer and attach an expansion plan for each major opportunity.
Keep the two linked. The health check and the stakeholder map live in the account plan and get updated all year. The expansion plan uses them and adds the work needed to close and roll out one deal.
Who owns what
Expansion fails most often in the gaps between sales and customer success. Settle ownership at the start and write it into the plan, especially who leads the commercial conversation and who owns adoption after signature.
Many companies split the work as below, but your comp plan and team structure decide the details. Agree on them with both managers before the first customer meeting.
- Account executive or account manager: owns the plan, the whitespace map, the business case, the proposal and the close.
- Customer success manager: owns the health check, the proof of value from current users and the rollout after signature.
- Solutions engineer: runs technical discovery and demos for the new team and supports the security review.
- Executive sponsor on your side: meets the customer's senior leaders when the deal is large or strategic.
- Sales manager: reviews the plan every month and approves discounts within deal desk rules.
- Customer champion: introduces you to the new team and confirms the results used in the business case.
Example: an expansion plan for a logistics customer
Picture a company that sells a field service scheduling platform. A logistics customer uses it in its North American operations team. The European operations team still uses spreadsheets, and the customer has just announced a project to standardize tools across regions. Here is how the plan could look.
Notice that the opportunity came from a trigger (the standardization project) and that the business case uses results from the current team, confirmed by the customer.
- Weeks 1-2 (owner: CSM): health check green, two open tickets fixed, sponsor confirms fewer missed appointments since launch. Milestone: health summary agreed.
- Weeks 3-5 (owner: AE): whitespace grid shows Europe operations and the premium analytics tier as the top options. Milestone: ranked list reviewed with the sales manager.
- Weeks 4-8 (owner: AE with champion): champion introduces the VP of European operations. Milestone: meeting held with the VP and two dispatch leads.
- Weeks 7-12 (owner: AE and CSM): business case built on North American results, confirmed by the customer's operations analyst. Milestone: VP agrees to take it to the regional budget review.
- Weeks 12-18 (owner: AE with deal desk): expansion co-termed with the main renewal, security review reuses last year's answers. Milestone: order form signed.
- Weeks 19-26 (owner: CSM): three European depots go live in waves. Milestone: adoption target met at the 60-day review.
How to build the whitespace map
The whitespace map is the core of the plan. In Excel or Google Sheets, put the customer's business units or teams in rows and your products, modules or tiers in columns. Fill each cell with one status: owned, in use, possible or not a fit. Color them consistently, for example green for in use, yellow for owned but not used, blue for possible and gray for not a fit.
Add three columns on the right: estimated size, main contact and next step. Yellow cells deserve attention first. A product that is owned but not used is a risk at renewal and an easy adoption win before any new sale. Blue cells are your expansion pipeline, and the ones with a contact and a trigger go to the top.
How to present the plan to sales leadership
Sales leaders usually review expansion plans in account reviews or quarterly business planning. Put the summary on one slide: account health rating, the top opportunity and its estimated size, the stakeholder map with gaps marked, the next three milestones with dates, and what you need from leadership, such as an executive sponsor meeting or a pricing exception.
Leave out the full org chart and the history of the account. Leaders want to see whether the opportunity is real, whether you can reach the buyer and what could stop it. Bring the whitespace grid as a backup slide in case they ask where the next opportunity comes from.
Metrics to track
Track the deal and the account together. A signed expansion in an unhappy account often comes back as a reduction at renewal, so a good plan reports both.
Pull the numbers from the CRM and your product analytics, and review them in the same monthly meeting where you update the plan.
- Expansion pipeline: value of open expansion opportunities in the account, by stage.
- Stakeholder coverage: number of buying roles with a supporter or neutral contact, against the full list for the deal.
- Health score: the customer success health rating before and after the expansion.
- Adoption in the new team: weekly active users or usage of the new product against the rollout plan.
- Net revenue retention for the account: revenue at the end of the year divided by revenue at the start, including expansion and any reductions.
Common mistakes to avoid
- Pitching an upsell to an account with open problems damages trust, so run the health check first and fix what blocks value.
- Relying on one friendly contact limits you to the team you already serve, so ask your champion for introductions and build a stakeholder map for the new team.
- Building the business case on generic claims makes it easy to reject, so use results from the customer's own teams and have them confirm the numbers.
- Leaving the CSM out until after signature creates a weak rollout, so plan adoption together before the order form goes out.
- Ignoring the renewal date leads to two separate negotiations, so decide early whether to co-term the expansion with deal desk.
- Counting the deal as done at signature hides adoption problems, so keep the plan open until the 60-day review.
Frequently asked questions
What should an account expansion plan include?
It should include an account health summary, a whitespace map, a ranked list of opportunities, a stakeholder map, a business case, a mutual action plan and a rollout plan. Each step needs an owner and a date. Add the metrics you will report so progress is visible.
Who should own account expansion, sales or customer success?
It depends on your company's structure and comp plan. A common split has sales owning the commercial conversation and close, and customer success owning health, proof of value and adoption. Write the split into the plan so nothing falls between the two teams.
How do you find expansion opportunities in an existing account?
Map the customer's teams against your products in a whitespace grid and look for gaps. Watch for triggers such as new leaders, funding, mergers or hiring plans. Ask your champion and current users which other teams face the same problems.
How long does an account expansion take?
It depends on deal size and how the customer buys. Adding seats in a team that already uses the product can take weeks. Selling a new product to a new business unit often takes as long as a new sale, because it involves new buyers, security reviews and budget cycles.