An expansion signal is a change in a customer account that makes it more likely the customer will buy more: more users, a new team logging in, a funding round, a new leader. Spotting one is the account manager's job, it takes about 20 minutes per account once a month, and it ends in a conversation with the customer.
A common mistake is treating the signal as the answer. A signal tells you which account to look at. The customer's own words tell you whether it is ready. This piece covers both, and it belongs to our account expansion guide, which covers the whole motion from signal to renewal.
What an expansion signal is
An expansion signal is any observable change that makes one of three conditions more likely to be true: the customer is getting value, they have a new need, and someone can pay for it. It is a reason to start a conversation.
- 01Check value firstCan you quote the sponsor? If not, stop
- 02Scan the four signal groups
- 03Read the shape of the curveA spike then a drop is a project that ended
- 04Turn each signal into a question
- 05Have the conversation
- 06Decide: grow, wait or protect
Gong makes the business case for looking: "When three teams depend on you instead of one, churn becomes a lot less likely." We agree. Expansion and retention are the same work seen from two sides.
The three conditions
An account is ready to grow when all three hold at once.
- Value: the sponsor can name a result from what they already own.
- Demand: a named person has a problem the current contract does not cover.
- Capacity: someone with budget and authority knows about that problem and wants it solved this year.
Healthy and ready are different states. A green health score says the first condition is probably true and says nothing about the other two. An expansion read off the health score alone is the kind that stalls in a buying committee the account manager never met.
How to read an account, step by step
Read an account in six steps: check value first, scan the signals, read the trend, turn each signal into a question, have the conversation, then decide whether to grow, wait or protect.
1. Check value first
Before looking for growth, ask whether the sponsor could state a result from the current product in one sentence, today. Good looks like: you can quote the sponsor. If you cannot, stop here. The account needs an adoption or value conversation, and an expansion pitch would make it worse.
2. Scan the four signal groups
Use the table below. Mark each signal you see, and the date you saw it.
| Group | Signal | What it suggests | What confirms it | Question to ask |
|---|---|---|---|---|
| Product | Existing users using it more over 90 days | Value is deepening | The sponsor names a result tied to the extra use | "What has the team been using it for lately?" |
| Product | New users or a new team logging in | Demand beyond the original team | Someone in the new team describes a problem | "Who are the new people, and what are they trying to do?" |
| Product | Account hitting a plan limit (seats, usage, storage) | Demand inside the current team | The admin says the limit is getting in the way | "Is the cap slowing anyone down?" |
| Commercial | Funding round or new budget cycle | Capacity | A budget owner says money is allocated to the problem area | "What are the priorities for the new budget?" |
| Commercial | Hiring in the team you serve | More seats needed | The manager confirms the headcount plan | "How many people are you bringing on, and when?" |
| Relationship | New leader in the function | Opening or risk | The new leader has met you and said what they want to change | "What is the new leader trying to fix first?" |
| Relationship | Sponsor asks how another team could use it | Demand, with a champion | The sponsor introduces you to that team | "Would you introduce me to them?" |
| External | Acquisition, new region or new market | New business units with budget | Someone in the new unit describes a problem | "Who runs the new unit, and how do they handle this today?" |
Good looks like: at least one signal in Product or Relationship. Commercial and External signals alone show capacity with no proven demand.
3. Read the shape of the curve
Look at product signals over 90 days. A steady climb is a signal. A spike followed by a drop is a project that ended. Good looks like: you can describe the trend in one sentence.
4. Turn each signal into a question
For every signal you marked, write down the question from the table and who you will ask. Signals from a press release or a usage report have to be confirmed by a person. Good looks like: a short list of named people, each with one question.
5. Have the conversation
Ask the questions in your next scheduled touchpoint, ideally the QBR, or book a short call. Write down what the customer says in their words. Good looks like: a quote for each condition, or a clear "no".
6. Decide: grow, wait or protect
- Grow: all three conditions have customer evidence. Open the expansion as its own deal.
- Wait: value is confirmed, and demand or capacity is missing. Plan the conversation that finds it.
- Protect: value is not confirmed, or the sponsor has gone quiet. Fix adoption first, and keep any expansion out of the renewal.
Good looks like: one word per account, with the reason.
A worked example
This example is illustrative. Halden Freight is a fictional 900-person carrier with 150 seats on the routing team. Jordan is the account manager.
Value. At the last QBR the routing director, Rafael Moreno, said planners were saving most of a morning each week and gave his team's figure. Confirmed.
Signals. Two look strong. Halden announced a $40 million funding round last month. And usage on the account is up sharply over the quarter.
Shape. Jordan pulls the 90-day curve. Usage spiked in weeks 3 to 6, during a one-off network re-plan, and has since dropped back to normal. That signal is a project that ended. The funding round is real, but it shows capacity and nothing about demand.
A third signal Jordan almost missed. Eleven new logins in the last month came from the customer service team, which does not own a license. Someone there is using a colleague's account.
Questions. Jordan asks Rafael: "I noticed some of the customer service team have been logging in. Do you know what they're using it for?" Rafael: "They're answering delivery-time questions from customers. Their lead, Sana, has been complaining that they can't see route changes."
Decision. Wait, with a clear next step: demand is now named (Sana, delivery-time questions), capacity may exist (the funding round) and nobody has spoken to Sana yet. Jordan asks Rafael for an introduction.
The signal that looked strongest turned out to be noise, and the one that mattered was eleven logins from a team with no license.
Where it goes wrong
Most misreads start with one strong signal.
One reading treated as the diagnosis. Usage up does not mean ready. Read all three conditions before you move.
Spikes read as growth. A project, a migration or a seasonal peak looks like expansion on a dashboard for six weeks. Check the curve before you act.
Press releases treated as demand. A funding round or an acquisition shows the customer has money or new units. It does not show anyone there has a problem you solve. Find the person.
Expansion raised in the renewal window. If the renewal is close, keep the two apart. Raising expansion as a renewal add-on hands both decisions to procurement. See how to run a renewal call.
The signal never becomes a conversation. A list of flagged accounts with no named person and no question is a report. Every flagged account needs a next conversation with a date.
Reading signals across every account
A signal list scales with software. Usage data, CRM fields and call recordings can flag accounts automatically, and tools that read past conversations do this well. The part that does not scale is the step after the flag: an account manager working out what the signal means, who to ask and what to say. That is where expansion is won or lost, and it is coaching work that a manager with eight account managers and a few hundred accounts cannot cover.
On Replicate Labs the account manager brings the flagged account to Caty on a call, talks through what they have seen and turns it into a planned conversation with Caty's help: who, the opening line and what they want to leave with. Typing works when a call does not. Caty remembers the account, so next month's review starts from what the customer said. The manager sees the read across the team through Bryce.
The coaching procedure is in how to coach account managers, and the QBR where many of these questions get asked is in how to run a customer QBR. More on the approach: drive deal execution. To work through the accounts your dashboard flagged this month, talk to us.
FAQ
What are expansion signals?
Expansion signals are observable changes in a customer account that suggest the customer may buy more. They include more active users, new teams logging in, an account hitting a plan limit, a funding round, hiring in the team you serve, a new leader and an acquisition. Each one is a reason to talk to the customer.
What is the strongest signal that a customer is ready to upsell?
In our view the strongest signal is a named person at the customer describing a problem their current contract does not cover. Product signals such as hitting a plan limit come close, because they show demand inside the account. Funding rounds and acquisitions are weaker on their own, because they show money and say nothing about need.
How do you know when a customer is ready to expand?
A customer is ready to expand when three things hold at once. The sponsor can name a result from what they already own, someone has a new problem with an owner, and a person with budget wants it solved this year. If any one is missing, plan the conversation that finds it before raising expansion.
What is the difference between an upsell signal and a churn signal?
Some signals cut both ways. A new leader in the function can open a bigger deal or start a vendor review. Falling usage, a sponsor who stops attending QBRs or a new person on the buying committee are churn signals. Read every signal against the value condition first.
How often should account managers review expansion signals?
Monthly for each account, and before every QBR. A monthly scan catches signals while they are fresh without turning the account manager's week into a dashboard review. Funding rounds and leadership changes are time sensitive, so act on those within a few weeks.