How I Find Upsell and Cross-Sell Moments Without Pushing

An expansion trigger is an event that shows an existing customer may need more from you, such as hitting a seat limit or asking support about a premium feature. I turn triggers into a small system: score each signal, flag the account once the total crosses a threshold, and hand it to one person with the full context. This replaces the luck of someone spotting the opportunity in a QBR.

What counts as an expansion trigger?

I sort triggers into four groups:

• Usage: close to a seat limit, an API threshold or a storage cap.
• Behavior: heavy use of features that are stronger on a higher plan, or repeated visits to the pricing or add-ons page.
• Direct signals: "Can your tool do X?" in a ticket, or "we need better reporting" in a survey comment.
• Organizational change: a team hiring, a merger, a new market.

Why do teams miss these signals?

The signals live in different tools. Usage is in product analytics, contracts are in the CRM, and feature questions are in the help desk. Each signal looks small on its own and only makes sense when they all sit on the same account record.

On one team I worked with, partners often asked support whether we could handle a new region or booking type. Agents answered politely and closed the ticket, and the account managers never saw the question. We added an "expansion interest" tag and a weekly report for the account managers. Within a few weeks, several of those tickets had turned into real conversations. Nothing about the product had changed. The question just reached the right person.

How do I score triggers?

Account score = sum of points for each trigger seen in the last 30 days
Flag the account when the score is at or above the threshold

Example points: usage limit = 10, direct feature request = 5,
clicks on a locked feature = 5. Threshold = 15

An illustrative case: a customer pays $4,000 a month ($48,000 a year) for a reporting tool on a 20-seat plan. In one month:

1. They add their 19th user (10 points).
2. Finance users click a locked advanced analytics module several times (5 points).
3. Their operations lead asks support about an integration that only comes with the Enterprise plan (5 points).

The total is 20, which is above the threshold of 15, so the CSM gets one alert listing all three signals. The CSM writes: "Your team is growing and exploring advanced analytics, and support mentioned the integration you asked about. Do you have 15 minutes to talk about what you need?" Once the need is confirmed, the account manager takes it from there with full context. In this example, the move to Enterprise takes the account from $48,000 to $85,000 a year. Run that through the NRR calculator to see what a few of these do to retention, and track the monthly effect with the MRR calculator.

What should a trigger never replace?

The data tells you when to call. It doesn't tell you whether the customer is happy, short on budget or in the middle of a reorganization. I never open with "our system flagged you". I open with the problem I noticed. If the customer says no, I lower that trigger's points for them and move on.

To measure what the system produces, the expansion revenue article shows how to split expansion by source.

Try this this week

• Pick two triggers, for example seat limits and requests for one premium feature.
• Add a tag in your help desk for "can you do X?" questions.
• Send flagged accounts to one named owner, not a shared channel.
• Count the conversations the triggers create for a month before adding new ones.