Expansion Managers: Prepare a Customer Advisory Session That Produces Signal

An advisory session with customers can turn into your most valuable data source or your least reliable one, depending on how you run it. Expansion managers often walk into these sessions hoping to hear a customer say they want to buy more, and that hope shapes the questions they ask and the notes they take. The result is a summary that reports enthusiasm nobody actually expressed. A well run session produces something more useful, a record of what customers do, where they get stuck, and who is affected, that you can act on later without embarrassing yourself in front of the account team.

Why this conversation goes wrong

Most advisory sessions fail before anyone speaks, because the manager walks in with a list of features they want validated rather than a set of open questions about how the customer actually works. When a customer offers a vague comment like "we need more flexibility," an eager manager hears a sales signal and writes it down as demand. That single line then gets forwarded to product or sales as proof that customers want a specific capability, when in fact one person, describing one workflow, made an offhand remark.

The deeper problem is authority confusion. A customer in the room is not necessarily the person who experiences the problem, and their opinion is not the whole account's opinion. Treat a single comment as universal at your own risk, since your next commercial conversation might reference something the account never actually confirmed. When the customer later gets asked to expand, and the reasoning was built on a stretched note, they notice the mismatch and trust erodes.

How to prepare

Prepare specific, open questions before the session rather than a list of features to pitch. Ask customers to describe a task they perform regularly, not whether they like an idea. Questions such as "walk me through what happens when a request needs approval" or "tell me about the last time this process slowed your team down" produce concrete answers you can write down and check later, unlike a yes or no answer to "would you use this."

Review the account history first. Read the notes from the last planning conversation with this account, since prior priorities often explain why a customer raises a topic now. The post on Expansion Managers Use Annual Planning to Learn Customer Priorities covers how to extract durable priorities from an annual planning conversation, and those priorities give you a baseline to compare against what you hear in the advisory session.

Decide in advance what you will and will not promise. Write down the boundary before the meeting starts, not during it, because it is much harder to hold a line in the room when a customer is animated and hopeful. You cannot commit to a delivery date, a discount, or priority access, and saying so calmly is much easier when you rehearsed the line beforehand.

What to say

Picture a session with a treasury manager and two other participants from the same account. The treasury manager says, "Our approval process needs to be more flexible." That comment alone tells you nothing you can use, so you ask, "What specific step in the process becomes difficult, and who has to deal with it when that happens?"

The treasury manager explains that regional teams need a different order of approvals during periods when staff travel for seasonal work, because the usual first approver is often unavailable. A second participant, from a different region, says their team has never run into that problem because they hire seasonal backup approvers. You write down both statements as separate data points instead of writing that the account wants a new approval sequence.

Later in the session, the treasury manager pushes for a commitment. "So when will you build this?" You answer, "I cannot give you a delivery date. What I can do is write up exactly what happens today, who is affected, and what outcome you need, and get that in front of the right people." That answer respects the customer's time without inventing a promise you cannot keep.

Mistakes to avoid

Do not report a single comment as if the whole account said it. One person describing one problem is one data point, not a mandate, and writing it up as consensus sets up a future conversation you cannot defend.

Do not promise anything about roadmap timing, feature delivery, discounts, or priority access, even informally. A customer who hears "we can probably get that in soon" will remember it word for word months later when nothing has shipped, and the account team inherits that broken promise.

Do not skip permission before sharing a customer's specific example internally. Ask first, and strip out any detail that is not needed for whoever reviews the note next. A customer's willingness to speak openly in future sessions depends on knowing their words will not travel further than agreed.

Do not close the loop with silence. A customer who raised a real problem and never hears back again assumes you ignored them, and the next time you ask for their honest input, you get a shorter, guarded answer instead of the detail you actually need.

Do not let the conversation stay abstract. If a customer says something is difficult, ask for the specific step, the specific role, and the specific frequency, because "difficult" means something different to a compliance officer than it does to a branch operations lead, and the difference changes what you write down.

How to practice and score it

Run the treasury manager exchange as a role play before you sit in front of a real account, and score three things afterward. Score whether you separated a customer's opinion from the account's, since one participant's comment does not represent a whole team. Score whether you avoided a specific promise about timing, cost, or access, even under pressure from a direct question. Score whether your closing summary names the affected role, quotes the customer's own words, and flags whether the issue is urgent or something the customer mentioned in passing.

A written summary built this way is worth far more than a note that says a customer is interested. It gives the next person in the process, whether that is a product manager or an account executive, something they can actually verify and act on. DealSpeak's practice conversations let you run this exact scenario with an AI counterpart that pushes back the way a real customer does, so you catch a wandering answer or an accidental promise before it happens with an actual account. If you also handle branch level decisions with this account, the post on Expansion Managers Assess Branch Rollout Readiness With Customer Evidence covers how to gather that kind of evidence without overstating it.

Before the next session

Treat every advisory session as a chance to collect accurate information, not a chance to manufacture a signal for the pipeline. The discipline is not complicated, ask specific questions, record who said what, and hold your line on promises, but it takes practice to do it under real pressure from an eager customer. Rehearse it enough times and it becomes the way you naturally run these sessions. For more scenarios built around financial services accounts, see Financial Services practice conversations.