Expansion readiness

A confirmed customer goal, a relevant limit in the current arrangement, a proposed addition that could address it, and a willingness to explore the change may signal expansion readiness. Increased usage or a positive relationship may prompt investigation. Neither establishes a need to buy.

Assess the need before the opportunity

Start with the customer's work: what are they trying to do, what has changed, and where does the current arrangement fall short? Ask the people who own and perform the workflow.

A request for “more capability” may mean additional seats, a different feature, help with configuration or a process change. Establish which it is before choosing a commercial response.

Ask what the customer would be able to do after a change that it cannot do reliably now. Record the answer in the customer's terms. If nobody can describe that difference, the opportunity needs more discovery.

Read signals in context

Expansion clues can appear in customer conversations and product activity. Check relevant interactions—email, meetings, support tickets and product usage—for mentions of growth, an additional product or a new use case. A signal is a reason to ask a question, not proof that the customer is ready to buy.

Note where customers do the work and where they ask to learn. A request for education or a discussion of a new use case can point to an unmet need. Confirm what the customer is trying to achieve and whether the current arrangement limits it before acting.

Check current value and the proposed fit

Look at use of the relevant workflows by the relevant roles over a period that matches how often the work occurs. Check access, actual use, completion of important tasks and the customer's account of results.

A login count alone cannot establish value. Low activity may be normal for an occasional task; ask before drawing a conclusion.

Test the proposed addition against the gap. Could existing entitlements, configuration or training solve it? Does the extra capability address the affected workflow? What implementation effort would the customer need to provide? An upgrade that leaves the original obstacle in place is a poor fit.

Key Metrics for Expansion Readiness

Test practical readiness

A relevant need may still be difficult to address immediately. Clarify who owns the decision, whether budget is available and whether the customer has the technical capacity to use the proposed addition. These conditions help distinguish a useful conversation now from a valid need that requires a later revisit.

Weigh the likely impact against those constraints. Identify what would change for the affected workflow and what the customer would need to contribute. If readiness depends on resolving a technical or service issue, agree who will address it before treating the expansion as the next step.

Decide what to do with the signal

These are decision prompts, not a scoring formula. A healthy account may have no reason to expand. A customer with an urgent new need may still need a service issue resolved before it can evaluate another purchase.

Give the customer control of the next step

Ask whether it would be useful to assess how the additional capability supports the new workflow. Agree what the customer wants to see, who should take part and what would count as a successful evaluation. Keep unverified benefits as hypotheses. Attendance at a review or training session does not imply buying intent.

If a commercial discussion is appropriate, pass sales the confirmed need, current arrangement, adoption context, open risks, stakeholders, timing and agreed next step. Include what remains unknown so the customer does not have to repeat the whole story.

When several teams need to contribute, make ownership explicit. Customer Success may need to coordinate with Sales, Product or Support so the customer gets a consistent account of the need, the proposed change and any dependencies.

Revisit readiness as conditions change

Record why an account was advanced, deferred or ruled out. For a deferred case, record the agreed revisit condition and responsible owner. Review it when the customer's goal, usage, service situation or timetable changes. Close a case that no longer has a customer need.

Expansion revenue shows that an existing customer bought more. It does not, by itself, show that the change was suitable or valuable. Review customer outcomes and unresolved problems alongside commercial results.