A land-and-expand motion has two halves and only one of them is staffed. The land half gets a pipeline, a forecast, and a manager who reviews it every Monday. The expand half gets a renewal date and a hope that the champion picks up the phone.
Ask a strategic AE with forty accounts which one to expand next quarter and you will get a name in about four seconds. Ask which product to lead with inside that account, and why this quarter rather than next, and the answer turns into a shrug dressed up as intuition. That second question is where the motion actually breaks. It is not a relationship problem, so more lunches do not fix it. It is a research problem with a different right answer in every account.
The half of land and expand nobody staffs
The economics of expansion are not in dispute. Harvard Business Review's summary of the retention literature puts it plainly: acquiring a new customer is anywhere from five to 25 times more expensive than retaining an existing one, and increasing retention rates by 5% increases profits by 25% to 95%. Every board deck in B2B software has a version of that slide.
What the slide does not say is that expansion revenue has been getting harder, not easier. SaaS Capital's 2026 benchmarking survey of more than 1,000 private B2B SaaS companies puts median net revenue retention at 103% and median gross revenue retention at 91% for companies between $3M and $20M in ARR. Read those two numbers together. The median company loses nine points of revenue to churn and downgrade, then claws back twelve. Expansion is not a growth engine at that ratio. It is a patch over the leak.
The gap between the board slide and the benchmark is process. Landing has one: a defined ICP, a scoring model, a qualification bar, a sequence. Expanding usually has a spreadsheet of accounts sorted by ARR and a quarterly nudge to "find whitespace." Sorting by ARR tells you where the money could be. It says nothing about which account is ready, or what it is ready for.
Three levers, and only one of them is a research problem
Expansion inside an account happens through three mechanisms, and they are not equally hard. Treating them as one undifferentiated "grow the account" goal is the reason expansion plans read like wishes.
| Lever | What it needs | Where the answer lives |
|---|---|---|
| More seats | Proof the current team is getting value, plus headcount growth in that team | Your product usage data, plus their job postings |
| More usage | Adoption work, onboarding, removing friction in the existing workflow | Your product usage data |
| Another product | Evidence a different team has a problem your second product solves | Almost entirely outside your systems |
The first two are customer success problems and most teams are at least competent at them. Usage is visible, adoption is measurable, and the person who cares about the outcome is already a customer. If seats are flat you can see it in a dashboard.
The third one is a sales problem wearing a customer success badge, and it is where the money is. Cross-product expansion is what separates a company patching its leak from one genuinely growing inside its base. It is also the only one of the three whose answer is not in your systems, which is why it gets skipped in favor of the two that are.
Why your own data cannot answer the product question
Consider a company that sells three things: a core workflow product, a compliance module, and an analytics add-on. An account bought the core product two years ago for its operations team. Sixty seats, healthy usage, renewal in five months. Which of the other two do you lead with?
Your CRM knows what they bought. Your product database knows how often they log in. Neither knows whether this company just picked up a regulated customer segment, opened an office in a jurisdiction with different reporting rules, or hired a Director of Compliance in March. All three of those facts would decide the question instantly, and none of them are in a system you own.
This is the specific limitation of the whitespace approach that most account planning tools implement. A whitespace matrix is a grid of accounts against products with the empty cells highlighted. It is genuinely useful, and it answers exactly one question: what has this account not bought. It cannot answer the question that follows, which is why this account would buy it now. That reason is always external. It is in a hiring page, a funding announcement, an earnings call transcript, a regulatory filing, a new job title on a leadership page.
An empty cell in a matrix is a fact about your invoice history. A buying signal is a fact about their business. Only the second one is a reason to make a call, and the difference between them is the difference between a list of forty accounts and a list of six with an argument attached to each.
Where the evidence for a second product actually lives
The useful sources are public, boring, and mostly unread by sellers because reading them at the scale of a whole account list is tedious work.
- Job postings. The most reliable expansion signal in B2B. A company hiring three data engineers is building something. A company hiring its first compliance lead has a problem it did not have last year. The requirements section often names the tools they are standardizing on.
- Leadership changes. A new VP arriving in a function you do not currently sell to is a budget cycle and a mandate to change something. It is also a person with no loyalty to the incumbent vendor in that function.
- Funding and earnings language. Public companies say what they are investing in because they have to. Private ones say it in the funding announcement. The phrase "expanding into" in either is an expansion signal with a date on it.
- Regulatory and market events. A rule change that applies to your customer's industry creates identical pressure across a slice of your account list at the same time. That is a campaign, not a call.
- Product and partnership announcements. A new product line at your customer means a new team, new processes, and gaps in tooling that did not exist a quarter ago.
None of this is exotic. The problem has never been that the evidence is hidden. The problem is that reading forty accounts against three products, quarterly, is roughly a week of a person's time, and that week never gets funded. So the research collapses into whichever two accounts the rep happened to read about, and the other thirty-eight get a generic check-in email.
This is the work PitchSmart exists to do: read every account on your list against what you actually sell, and return the buying signals that say which product a given account needs now, each one with the source it came from. The whitespace matrix shows the empty cell. The signal tells you why to call it this quarter. If you want the manual version first, our guide to the account research process walks the same steps by hand.
A per-account expansion loop you can run monthly
The goal is not a perfect model. It is to replace "sorted by ARR" with a ranked list where every entry carries a reason. Five steps, and the first one is the one teams skip.
- Write down what each product is actually for. Not the positioning line. The specific problem, the function that owns it, and the two or three observable conditions that mean a company has it right now. If you cannot name the observable conditions for a product, you cannot research against it, and no tool will save you. Our note on value proposition development covers how to get from a feature list to a condition you can look for.
- Map the account past your own buying center. You sold to operations. The compliance module buys from legal or risk. List the functions that would own each product, then find out who runs them. Account mapping is the discipline here, and the output is names and functions, not an org chart for its own sake.
- Research each account against each product. For every account and every product they do not own, look for the observable conditions from step one in public sources. Record the finding and the URL. A signal without a source does not survive contact with a deal review.
- Rank by evidence, then by size. Sort the accounts that produced a real signal by how much the expansion is worth. An account with a hiring signal and a new function lead outranks a larger account with nothing but an empty cell, every time. If you already run a scoring model on new business, the same logic applies: our piece on how to score leads transfers directly, with signals in place of firmographics.
- Open with the finding, not the relationship. "I saw you posted for a Director of Compliance in March and opened the Frankfurt office" is a different conversation from "checking in on how things are going." The first one earns a meeting with a person who has never heard of you.
Expansion is a new buying group, not a warm intro
The most expensive assumption in land and expand is that your champion carries you into the next department. They usually cannot, and often will not.
Forrester's State of Business Buying research found that an average of 13 people inside an organization are involved in a buying decision, with 89% of purchases involving two or more departments. The same research puts the share of B2B purchases that stall during the process at 86%. An expansion deal into a function you have never sold to is a new purchase with a new committee, and it stalls for the same reasons any purchase stalls. Your existing relationship gets you one warm introduction and a small amount of credibility. It does not get you a budget owner in a department that has never seen your invoice.
Treat the second product as a new deal with a head start. Qualify it. Build the case. The head start is real, and it is worth a lot, but it is a head start on a race you still have to run. Teams that skip qualification because "they are already a customer" produce the forecast that slips every quarter for a year.
How to tell whether any of this is working
Net revenue retention is the scoreboard, but it moves too slowly to steer by and it mixes three different things together. Instrument the parts.
- Products per account, tracked as a distribution. The average hides everything. What you want to see is the count of accounts on two or more products going up, not the mean creeping because one large account bought everything.
- Signal coverage. What share of your account list has been researched against your full product line in the last 90 days? If it is under half, your expansion plan is a sample, not a plan.
- Meetings sourced by a signal. Count expansion meetings where the opener referenced a specific external finding, separately from meetings booked off a relationship. The ratio between them tells you whether the research is reaching the conversation or dying in a spreadsheet.
- Time from signal to first touch. A hiring signal is worth something for about a quarter. If your median is six weeks, you are researching on a cadence slower than your customers change.
Split net revenue retention into its parts as well. Seat growth, usage growth, and cross-product attach behave differently and respond to different work. A quarter where NRR held flat because seat expansion covered a cross-sell miss is not the same quarter as one where cross-sell carried a seat contraction, and only one of them tells you the research loop is working. For a fuller treatment of the signals themselves and what each one is worth, see our guide to buying signals in sales.
The version of this that works
Land and expand fails quietly. Nobody misses a number because of it in any single quarter. The accounts renew, seats tick up, and net revenue retention sits at 103% for three years while the deck keeps saying the expansion motion is a strategic priority.
The version that works is unglamorous. Someone writes down what each product is for in terms you can observe from the outside. Someone reads every account against every product on a schedule. The ranked output has a reason and a link next to each name, and a rep opens with the reason. That is the whole method. It is mostly reading, which is exactly why it does not get done, and exactly why the teams that do it pull away from the ones that sort by ARR and call it a plan.
