Recognize a Real Expansion Opportunity

A current customer mentioning another department deserves curiosity, not an expansion forecast. “Our other team might like this” often reflects goodwill toward a current relationship. A real opening starts when a new group has a problem, an owner, and a reason to spend attention on change. Without those details, record interest without treating future work as expected.

Treat every department as a fresh discovery effort. Customer history still matters because you know how one team started, what language helped during early conversations, and which people shaped their choice. None of this proves a second team faces similar conditions. Different systems, handoffs, deadlines, leaders, and risks produce a separate decision process.

Begin with the trigger. Ask, “What happened recently which brought this group to mind?” A useful reply names an event or recurring friction. One team might share reports with a regional group, while regional staff rebuild similar reports in another process. A department leader might have watched a colleague’s routine during an internal meeting. General praise is a weaker signal. Look for a reason tied to work.

Then locate the affected workflow. Ask who begins work, who receives an output, where delays arise, and who feels pressure when a step fails. Request one recent situation rather than a broad description. You will hear the difference between casual curiosity and a problem someone wants solved. The details also help you avoid repeating a current customer story when a new group needs a different conversation.

Suppose an operations team says support has asked about their reporting process. Ask, “Which support task created this interest?” If Jordan says, “They spend Friday morning combining updates for a manager,” ask who combines updates, what sources they use, and what happens when one update arrives late. If Jordan says, “They heard our team likes the process,” you have an introduction opportunity, not a qualified expansion discussion.

An owner gives an opening shape. Ask who would lead an evaluation from the new team and who feels the problem day to day. An executive sponsor might support a conversation, while a manager owns workflow details. Do not assume your present contact has access to both people. Ask for an introduction after you understand why each person belongs in a further discussion.

Learn how the new team decides. Ask whether they face a date, a service issue, a planning cycle, or an internal request. Keep your language neutral. You are learning their process, not pressing for commitment. Mark interest without an owner or shared concern clearly, so a pleasant comment does not become a misleading forecast.

Carry history with care. Say, “Your team began with manual report assembly. Does support face a similar task, or does their work differ?” An honest reply often reveals an important contrast. Support might need handoff visibility rather than report assembly. Their discussion then needs a different example and a separate evaluation path.

Ask for permission before sharing detail from the current team. A contact might welcome a high level description of their process but prefer no discussion of internal routines. Explain what you plan to say in an introduction. For example, “I will say your team has developed a reporting routine and support expressed interest. I will not describe your internal steps.” This respects the relationship and avoids an awkward first conversation with the new group.

Fictional practice situation: Priya manages success for a technology customer. During a monthly review, Jordan from operations says, “Support has been asking about our reports.” Priya asks what changed. Jordan explains support staff spend several hours each Friday collecting case updates from different people before a manager meeting. Priya asks who leads support operations. Jordan names Sam and says Sam raised this problem during two recent staff meetings.

Priya does not promise a solution or label this an expansion. She asks whether Sam would welcome a 25 minute discovery conversation. Jordan agrees to send an introduction. Priya offers Jordan two sentences for the message: “Sam leads support operations. The team spends Friday mornings collecting updates for a manager review. Priya would like to understand how this process differs from ours.” Sam receives a reason to accept or decline without pressure.

On the call, Priya starts with Sam’s workflow rather than a customer success story. She asks what arrives late, who chases updates, and which manager uses the combined view. Sam says supervisors send notes through several channels, then an analyst gathers them. Priya asks what a better Friday morning would look like. Sam says the analyst should spend less time locating notes and more time checking unusual cases. Priya repeats this goal in Sam’s words and asks Sam to correct any part which feels wrong.

Priya next asks what other people need to agree before a change receives attention. Sam says the support director wants a clear picture of present work, and an analyst needs to explain current data sources. Priya proposes a further session with Sam and the analyst. The purpose is narrow: map one Friday update process and identify which source creates the largest delay. A product review does not belong yet because the group lacks a shared picture of present work.

Keep records separate from the original account story. In your notes, label the new team, primary problem, named owner, trigger, people involved, and open question. Include the contact who supplied each detail. Avoid phrases such as “same use case” unless a new participant has confirmed them. Clear records reduce the risk of an account team bringing assumptions from one department into another department’s meeting.

Adoption history still supplies useful prompts. Ask the original team which early obstacles appeared, which internal language helped, and who supported routine changes. Do not treat answers as rules for the new group. Use them to prepare better questions. A former obstacle might lead you to ask whether support staff have time during a busy Friday morning, rather than assuming an operations schedule fits them.

Watch for weak signals. A contact might say another leader is interested yet decline to name a workflow or introduce an owner. Another group might ask for pricing before anyone describes their problem. A leader might attend a review, praise current work, then leave without a next action. None of these events need a forecast. Record what happened, agree on a gentle follow up point if one exists, and return attention to customer work already underway.

Use a simple test before you open an expansion record. Write one sentence with the team, problem, owner, and trigger. “Support operations, Friday update collection, Sam, repeated manager meeting delays” passes because each part has evidence. “Finance noticed our work” does not pass because no problem or owner appears. This test protects your forecast from goodwill being mistaken for active work.

In Priya’s fictional situation, Sam accepts the mapping session for Wednesday morning. Priya sends an invitation naming Sam and the analyst, then places one opening prompt in the description: “Bring a fictional late case update so we trace where handoffs slow down.” At 9:00 Wednesday, she asks the analyst to place the update at the first step where someone waits, then writes Sam’s answer beside the source name.