Daniel Saks
Chief Executive Officer
Expansion signals are the changes inside a current customer that make a bigger contract likely: the team using your product is growing, a new office opens, a new leader arrives with a budget, or the account adds a tool that works next to yours. Account managers often hear about these changes late, after the budget is set. This playbook finds them early, starting from the customer list you already have.
The build runs on your own data first. You upload your customer list, Landbase matches each account to its company record and appends headcount, location, hiring, funding, leadership and tech fields, and a simple comparison step flags the accounts where something changed. For finding new logos instead of growing existing ones, use the buying signals prospecting playbook.
An expansion signal is an observable change at a customer account that raises the odds of an upsell (more seats or a higher tier), a cross-sell (another product) or a wider deployment (another team, region or business unit). Unlike a new-logo signal, you already know the account's contract, usage and owner, so it is easier to interpret and cheaper to act on.
The money involved is large. SaaS Capital's 2025 B2B SaaS retention benchmarks, based on a survey of more than 1,000 private B2B SaaS companies, put median net revenue retention at 101% and median gross retention at 91%. In the same survey, companies with net retention of 110% to 120% reported a median growth rate of 30%, against 21% for companies at 100% to 110%. Net retention includes upsells, cross-sells and price increases, so the gap between those two bands is largely expansion selling.
Retention economics point the same way. Writing in Harvard Business Review in 2014, Amy Gallo cited research by Frederick Reichheld of Bain & Company finding that a 5% increase in customer retention increases profits by 25% to 95%. Expansion signals tell the account team where to spend that effort this quarter.
Expansion signals come from two places, and a good list uses both.
Each signal below lists what it means, the field that carries it and a decay window. The windows are starting points to test against your own sales cycle and renewal calendar, not fixed rules. For the general method, see how to apply signal decay windows.
If you sell per seat to sales teams, the sales department growing is the signal; total company headcount is only a proxy. Compare the department headcount today with the count you recorded at signing. Window: 60 to 90 days, then re-check every quarter, because team growth is a state that persists rather than a one-day event.
A new office means new teams, new regional leaders and often a separate budget line. Compare the account's current location count and addresses with what your CRM holds, and confirm announcements with a news lookup. Window: 60 to 90 days from the announcement, while the site is being staffed and equipped.
Open roles for the people who would use your product (or the people who run it, such as an operations or admin hire) show that the team is about to grow before headcount data shows it. Check the number and titles of the account's open job postings. For the prospecting version of this signal, see hiring signals. Window: 30 to 60 days from the posting date.
New capital at a customer usually funds hiring and new initiatives, and the account team that already has a relationship gets the first look. Use the latest round's name and announcement date. The funding signals playbook covers the new-logo side. Window: 60 to 90 days from the announcement.
Leadership change cuts both ways. A champion promoted to a bigger role can carry your product into more teams; a new executive in the buying function will review the stack and either expand or replace what is there. Check recent executive arrivals at the company level, and the current title, internal promotions and time in role for your known contacts. Window: 30 to 45 days for the first conversation, since new leaders tend to set priorities in their first quarter.
When a customer adds a tool that integrates with yours, or one that signals a new use case, an integration or add-on conversation follows. Use the date each tool was detected so you look at what was added recently rather than the whole stack. Technographic data is broad: a free Landbase count run in November 2026 found 4,647 of 7,713 US software companies with 50-500 employees recorded as using both Salesforce and Gong, so "uses tool X" alone separates very little. Recent additions do. Window: 45 to 60 days.
If your customer acquires a company, the acquired team may be consolidated onto your platform, which is an expansion. If your customer is acquired, the parent may consolidate away from you, which is a risk. Check the account's acquisition history and parent company, and confirm with news. Window: 90 days for the first conversation, then revisit at each integration milestone.
The steps use one example throughout: a company that sells a sales software product per seat to US B2B software companies, with a customer list of a few hundred accounts. You can describe each step in plain language in the Landbase app, or have Claude Code run it for you through the Landbase CLI. Three kinds of steps use credits: research queries, AI qualification and contact enrichment (emails and phones). Those steps are marked below; nothing else in this build uses credits.
Export one row per customer account from your CRM with the website, account name, account owner, ARR, seats purchased, renewal date, health score and the headcount you recorded at signing. A second file can hold your champions: name, email, LinkedIn URL and company website.
Upload the customer file to Landbase and give it a clear name, such as "Customer base Nov 2026". Landbase turns it into a dataset that the later steps build on.
Landbase first maps your columns into its own schema, keeping your CRM fields such as seats purchased and account owner alongside its own. It then links each row to its Landbase company record. Each step produces a new version of the dataset that feeds the next one.
Ask Landbase to add the expansion fields to every matched customer: total and department headcount, headcount change by department, location count and addresses, open job postings and their titles, latest funding round and date, recent executive arrivals, tools in use with detection dates and acquisition history.
This appends the current value of each field to every account. Preview a few rows afterwards to confirm the new columns hold values. A field Landbase does not recognize, or has no data for, does not stop the step; it just comes back blank.
Next, compare the new values with what your CRM recorded and add one true/false column per signal, keeping the account owner on every row. For example, flag accounts whose headcount is at least 20% above the count at signing, accounts that announced funding in the last 90 days, and accounts with five or more open roles.
The result is a new dataset ready to score. Add a column for each signal you track, for example a location count above the CRM value or a tool detected recently. Repeat steps 3 and 4 monthly on the same matched dataset to catch new changes.
Upload, onboard and match the champions file the same way, then enrich it with each person's current title, time in role, internal promotions and any recent job start.
This shows each champion's current title and employer. A higher title at the same company is a promotion signal. A different employer means the champion left: the customer account needs a new relationship, and the champion's new company becomes a new-logo lead. People move often (the US Bureau of Labor Statistics put median tenure with the current employer at 4.1 years in January 2026), so check this list at least quarterly. More data is in the job change frequency statistics.
To see who now leads the buying function at each customer, limit a contact search to your matched accounts. Ask for sales, revenue operations and revenue leaders at your customer companies only.
The search returns current leaders at your customers only. Names that are not in your CRM are new relationships to build, and a new name in the top seat is a leadership-change signal.
If the hiring or headcount columns came back empty for many accounts, a research query can join your customer list to job-posting data, for example recent sales and revenue operations postings at each account. It uses credits and quotes the estimate before anything runs.
For a single account where you suspect an office opening or an acquisition, a standard search for recent news on that company is enough.
To find net-new accounts that look like your best expanders, the lookalikes playbook starts from the same list.
The four layers used for new-logo lists change meaning when the list is your customer base.
Score the flagged accounts into tiers:
Inside a tier, sort by ARR. For tiering mechanics, see how to prioritize audiences by signal strength and recency.
Expansion signals belong to whoever owns the customer relationship. Because the flagged list keeps the account owner on every row, routing is a filter, not a research task.
The first touch should reference the change and offer something useful, not a quote. For example: "You added two regional sales teams this quarter. Teams that size usually hit a reporting gap in month two; worth 20 minutes to plan rollout for the new teams?"
Measure the flagged accounts against a control group of similar customers with no signal, over at least two quarters.
Drop or re-window any signal that does not beat the control after two quarters.
Expansion signals are changes at an existing customer that make an upsell, cross-sell or wider deployment more likely. Common ones are team headcount growth, a new office, related hiring, funding, a new leader or promoted champion, an adjacent tool and an acquisition. They differ from new-logo buying signals because you already know the account's contract and health.
For seat-based products, headcount growth in the team that uses your product is usually the most direct, because it shows a gap between seats owned and people who need them. A promoted champion is often the strongest for cross-sell, since that person can sponsor your product in new teams. Two independent signals at a healthy account beat any single signal, so test combinations against a control group.
No. Usage, seat utilization, support tickets and health scores live in your own product analytics and CRM. Landbase adds what happens outside your product: headcount, locations, hiring, funding, leadership, tech stack and acquisitions. Upload your customer list with usage and health columns and both sources sit in one dataset.
A prospecting list starts from the whole market and looks for accounts you do not sell to yet. An expansion list starts from your customer list and looks for change inside accounts you already serve, then routes it to the account owner. The buying signals playbook covers the new-logo side.
Re-run the enrich and flagging steps monthly on your matched customer dataset, and re-check champions at least quarterly. Monthly fits windows of 30 to 90 days, and accounts near renewal can be checked more often.
Three kinds of steps use credits: research queries, AI qualification and contact enrichment for emails and phones. Each quotes or reports its cost. Uploading, matching, enriching with company and person fields, flagging changes and standard searches do not. If you are new to Landbase, the free trial includes 1,000 free credits.
Tool and strategies modern teams need to help their companies grow.