After this lesson you will be able to
- Judge whether an account is ready to expand or needs its current investment fixed first
- Build a whitespace map by department and business process, not by product list
- Run an executive business review that ends with an agreed next problem to solve
- Plan expansion timing so it does not collide with the renewal negotiation
Start with adoption, because expansion on a weak base backfires
Before you look for the next product, look hard at the current one. A customer that logs in rarely, keeps forecasts in spreadsheets, or has a backlog of admin requests will hear any expansion pitch as more of the thing that is not working. Your credibility drops, and the renewal gets harder.
You do not need a perfect dashboard to read adoption. You need a few honest answers. Ask the admin or the sales ops lead what people do in Salesforce every day, what they still do outside it, and what they would turn off tomorrow if they could. Ask the executive sponsor which report they open on Monday morning. If the answer is none, you have learned something important.
Sort the account into one of three states. Healthy means core processes run in Salesforce and leaders trust the data. Stalled means the system works but people route around it. Struggling means the customer questions the value of what they bought. Only healthy accounts are ready for a new product conversation. Stalled and struggling accounts need a fix first, and that fix is often the best expansion opener you have.
- Healthy: core process in Salesforce, leaders use the reports, a backlog of new requests
- Stalled: data exists but spreadsheets and side tools fill the gaps
- Struggling: low logins, an unhappy sponsor, talk of replacing or reducing licenses
Map whitespace by team and process, not by product catalog
A product list tells you what you could sell. A process map tells you what the customer needs. Draw the account as departments down the side and core processes across the top: lead to opportunity, quote to cash, case to resolution, onboarding, renewals, field work, partner management, reporting. Mark each cell with what runs it today. Salesforce, another system, spreadsheets, email, or nothing.
The gaps worth chasing have three things in common. Someone owns the pain, the process touches data already in Salesforce, and the current workaround costs time or money the customer can describe. For example, a 300-person equipment distributor may run sales in Sales Cloud while service tickets live in a shared inbox. The service team is a whitespace cell with a named owner, a data link to existing accounts, and an obvious cost in slow responses.
Keep the map in the account plan and update it after every meaningful call. Over a quarter it becomes the most useful document you have on the customer, and it keeps you from pitching the product of the month.
Read the signals that mean a new conversation is welcome
Expansion signals usually show up in ordinary conversations. The trick is to write them down and act on them. A new executive joins and wants visibility. A team asks to be added to Salesforce. The customer buys a company. Support volume jumps. Someone asks whether Salesforce can talk to the ERP. Each of these is an opening to ask a discovery question, not a cue to send a quote.
Our expansion finder at /salesforce-account-executives/expansion-finder/ turns this into a checklist. Tick what the customer owns and what you are hearing, and it suggests expansion paths with the signals behind them, discovery questions and a value hypothesis to test. Use it before your account review so you walk in with questions instead of a pitch.
- Leadership change or a new executive asking for visibility
- A department asking for access or building its own tracker
- Acquisition, new region, or new product line
- Rising case volume, slower response times, or a new service promise
- Questions about connecting Salesforce to ERP, billing or a data warehouse
- Interest in AI agents from a leader who has not yet defined a use case
Run an executive business review the customer wants to attend
Most executive business reviews fail because they are vendor reports. Thirty slides of usage charts and a roadmap tease will not get an executive to the next meeting. A good review is about the customer's business and takes 45 minutes or less.
Build it in four parts. First, the goals they told you at the start of the year, in their words. Second, what changed, using numbers they recognize from their own reports. Third, what is still in the way, which you gather by interviewing two or three people before the meeting. Fourth, one or two problems worth solving next, framed as questions for the executive to react to. End by asking which problem they want to explore and who should own it.
Send a short pre-read three business days ahead and ask the sponsor to add one item. That single step turns the meeting into their agenda. Afterward, send a one-page recap within a day with the agreed next problem, the owner and the date of the next conversation.
Time expansion around the renewal, not inside it
Expansion that arrives in the same email as a renewal quote feels like a price increase with extra steps. The customer bundles both into one negotiation, procurement takes over, and the value conversation disappears.
Work backward from the renewal date. Six to nine months out, run the business review and agree the next problem. Four to six months out, finish discovery and build the business case with the customer's numbers, using the ROI calculator at /salesforce-account-executives/roi-calculator/. Inside three months, keep the renewal clean and separate unless the customer asks to combine them. If they do want one agreement, make sure the expansion case stands on its own so it survives a line-by-line review.
Your company's renewal and co-termination rules vary, so check them with your deal desk early. What matters for this lesson is sequencing: value first, scope second, paperwork last.
Turn a whitespace cell into a qualified opportunity
Once a problem is agreed, qualify it like a new logo deal. Confirm the owner, the measure, the budget path and the people who will be affected. Expansion buyers are often a different department from your original champion, so do not assume the first buyer can sign for the second team.
Make the scope credible early. A customer who has lived through one implementation will ask how long the next one takes and who does the work. Bring a delivery partner into discovery so the timeline and effort are written by someone who has done the work, and use the deal desk at /salesforce-account-executives/deal-desk/ when you want that input on a specific deal. If adoption is the issue, a health check on the current org is a low-risk first step that often surfaces the next project on its own.
Talk tracks
Opening an account review with your executive sponsor
“Before we talk about anything new, I want to know what is working and what is not in what you already have. What does your team still do outside Salesforce that you wish they didn't?”
It shows you care about their return first and surfaces the real whitespace.
When usage looks low and the sponsor seems frustrated
“It sounds like you are not getting what you paid for yet. I would rather fix that than sell you anything else. Can we look at the two processes causing the most friction and agree what good looks like?”
Leading with a fix protects the renewal and earns the right to expand later.
A new department asks for Salesforce access
“That's a good sign. Before we add licenses, can we spend 30 minutes on how that team works today? I want to make sure they get a setup that fits them, not a copy of sales.”
It turns a license request into a discovery conversation and a properly scoped opportunity.
Inviting an executive to a business review
“I'd like 40 minutes to review what changed against the goals you set this year and agree one problem worth solving next. I'll send a one-page pre-read, and I'd value one item you want on the agenda.”
A clear purpose and an invitation to shape the agenda make the meeting worth their time.
The customer wants to fold expansion into the renewal negotiation
“We can do that. I'd suggest we agree the business case for the new work first, so it stands on its own in your review. Then we can decide together whether one agreement or two is simpler for you.”
It keeps the value case intact if procurement reviews every line.
A leader says they want AI but has no use case
“Let's start from the work, not the technology. Which high-volume, repetitive task does your team handle every day where speed or consistency matters most?”
It grounds the conversation in a measurable process instead of a demo.
Account expansion review (run once a quarter per strategic account)
Use it on a live deal. Tick items off as you go; nothing you tick leaves this page.
Common mistakes
Pitching expansion to an account that is struggling
The customer hears more of what is not working. Fix adoption first and let the fix open the next conversation.
Mapping whitespace by SKU
A product list hides who owns the pain. Map departments and processes so every opportunity has a named owner.
Turning the business review into a vendor report
Usage charts and roadmap slides do not move executives. Talk about their goals, their numbers and their next problem.
Bundling expansion into the renewal quote by default
It invites a pure price negotiation. Agree the value case months earlier and keep the renewal clean unless the customer asks otherwise.
Assuming your first champion can buy for a new department
Different teams often have different budget owners and different stakeholders. Qualify the expansion as its own deal.
How you will know it is working
- Your executive sponsor adds their own item to the business review agenda
- Expansion opportunities have a named customer owner and a baseline measure before you send pricing
- Expansion discovery finishes months before the renewal window instead of inside it
- Customers start bringing you new problems without being asked
Questions
How often should I run an executive business review?
For strategic accounts, two a year is a practical rhythm, with one placed six to nine months before renewal. Smaller accounts may need one lighter review a year. What matters more than frequency is that each review ends with an agreed next problem and an owner.
What if the customer has low adoption but wants to buy more?
Say what you see. Explain that adding products on a weak base usually makes adoption worse, and propose fixing the top two friction points first. Customers rarely object to an AE who protects their investment, and the fix often reveals a better expansion path.
Who should I interview before a business review?
Talk to two or three people who use the system daily, such as a team lead, an admin and an operations analyst. Ask what they still do outside Salesforce and what slows them down. Their answers give you concrete material that executives recognize.
How do I find whitespace in an account I just inherited?
Start with the admin and the sponsor. Ask them to walk you through how a deal, a case or an order moves through the business today. Fill in the whitespace grid as they talk, then run the expansion finder with what you learned.