Build an Expansion Conversation From Adoption Evidence

Expansion managers earn trust when they understand how the existing service is used before suggesting an adjacent workflow.

Ask for an example of a team using the current service in its regular work. What action follows the report, alert, or workflow? Who depends on it? This is stronger than an internal activity metric because the customer can verify it. If a gap appears, describe it as a question for discovery, then invite the operational owner to explain whether an additional capability would actually help.

A fictional merchant uses a reporting capability each morning to decide which refunds need attention. The expansion manager can ask the operations lead to describe that decision and the evidence they rely on. If another team still researches exceptions manually, ask that team to describe the work and the need it creates before discussing additional capability. Coach the manager to distinguish observed use from assumed value. A strong follow-up invites the team doing the manual work to explain its process before any commercial discussion.

Ask what teams rely on the current capability, what result they value, and where their process still has friction. A fictional merchant may use payment reporting daily but still rely on manual work for refunds and customer support.

Do not treat login counts as proof of value or present a feature as included when it is not contracted. Practice the question, “What would you want to improve next, based on what your team sees today?”

Schedule a review of evidence with the operational owner before introducing a commercial proposal.