Expansion Managers: Use Annual Planning to Learn Customer Priorities

Annual planning conversations put you in front of a customer who is already thinking about next year, before you ask a single question about your own renewal or expansion. Use that timing well. The purpose of this conversation is to learn what the customer intends to do, not to steer them toward a decision on your roadmap.

Why This Conversation Goes Wrong

Expansion managers often walk into annual planning with an outcome already in mind. They hear "we are opening two new branches" and start building a case for additional licenses before the customer finishes the sentence. That instinct comes from good intentions, quota pressure, a real desire to help, but it turns a discovery conversation into a pitch before the facts are in. The customer notices. Their answers get vaguer, because they sense the meeting has a target behind it. Once that trust drops, the account note you write afterward will not hold up when someone reviews it months later and asks why a training question got logged as a signed opportunity.

The other common failure is treating every mention of growth as validated. A customer executive says something big, "we are growing fast," and the manager writes it down as a tailwind for the account. But growing fast could mean five new employees or five hundred. It could mean growth in a business line the customer plans to run on a different vendor entirely. Enthusiasm is not evidence. Your job in this conversation is to turn vague statements into specific, dated, owned facts, or to record honestly that the specifics are not decided yet.

How to Prepare

Before the call, write down what you already know about the account and separate it from what you are guessing. If the customer mentioned branch openings in a prior call, that is known. If you assume those branches will need new reporting tools, that is a guess, and it belongs in your list of questions, not your list of facts.

Prepare three or four open questions tied to the customer's business, not your product. Ask where operations will change, who owns budget for new initiatives, and when decisions get made internally. Avoid questions that only make sense if the customer already wants to buy something from you. A question like "which workflow changes when the branches open" invites a real answer. A question like "how many more licenses will you need" assumes an outcome nobody has decided yet.

Decide in advance how you will record uncertainty. If you walk in planning to write a clean, confident account plan, you will unconsciously edit the answers to fit that plan. Decide instead, before the call, that your notes will separate confirmed facts from open questions in two distinct columns.

What to Say

Start with the customer's plans, not yours. Ask something like, "I saw you are opening two new offices next year. Where does that first change the work your teams do today." That question is specific and lets the customer answer with whatever is actually true for them, instead of what they think you want to hear.

The operations leader answers, "Honestly, the first thing on my mind is training. We need every new branch staffed and ready within a few weeks of opening, and we do not have a plan for that yet. Finance is still deciding how it wants reporting organized across the new locations, that part has not been settled." Two separate facts just arrived. One is a training need with a rough timeline and an obvious owner, the operations leader. The other is an open question inside finance with no owner confirmed and no decision made.

Resist the pitch. Separate the two threads instead. Ask, "On training, is there a date by which staff need to be ready, and who owns that project." Then ask about the second thread, "On reporting, who inside finance is deciding that, and when do you expect they will settle it." Neither question offers a solution. Both find out who owns each thread and when it moves.

If the customer asks directly whether your product can handle branch level reporting, answer honestly. Say, "I do not know yet. Let me find out what is required and who on our side can confirm it. I will get back to you by early next week." That answer is truthful. Promising capability on the spot, before you check with your own team, creates a commitment you may not be able to keep.

Mistakes to Avoid

The first mistake is writing down enthusiasm as commitment. A customer saying they are excited about growth is not the same as a customer saying they have budget approved and a start date. Keep those two things separate in your notes and in your head.

The second mistake is letting a planning conversation quietly turn into a pricing or contract conversation. If the customer asks what an expansion would cost, that is a fair question, but answer it as a separate topic with its own process, not folded into notes labeled discovery. Mixing the two makes your account plan unreliable, because nobody can tell later which parts were fact finding and which parts were negotiation.

The third mistake is skipping the recap. Many managers leave the call satisfied they learned something and never write it down in a form the customer can check. Send a short summary that separates what the customer confirmed, what is still open, and what you agreed to do next. Give the customer a chance to correct it. Skip this step and the note in your system becomes your own interpretation instead of a shared record, which causes real problems when someone else on your team relies on it later.

The fourth mistake is asking your questions in an order that boxes the customer in. Ask about budget before you ask about the actual operational change, and the customer answers defensively. Ask what changes first, then who owns it, then when it gets decided. Money comes last, if it comes up at all.

How to Practice and Score It

This conversation is easy to describe and hard to run well under real pressure, especially when a customer says something that sounds like an opening and your instinct is to jump on it. Practicing it with a realistic counterpart, the kind DealSpeak provides, lets you rehearse the discipline of separating fact from hope before you are on a call where the customer is watching how you react.

Score yourself, or have a manager score you, on a few concrete points. Did you ask about the customer's operational change before asking about scope or budget. Did you keep confirmed plans separate from exploratory ones in your notes. Did you avoid promising capability, pricing, or availability that had not been checked with your own team. Did the recap you sent separate facts, open questions, and next steps clearly enough that the customer could correct it without an argument.

Managers coaching a team through this should watch for the moment an executive makes a broad claim like "we are growing fast" and see whether the rep asks for a specific example instead of accepting the claim at face value. That single habit, waiting for specifics before writing anything down, separates an account plan built on evidence from one built on guesswork. The same discipline shows up in other high stakes conversations expansion managers run, including how they assess a rollout in Expansion Managers Assess Branch Rollout Readiness With Customer Evidence and how they protect a plan when their main contact changes roles, covered in Expansion Managers Protecting a Customer Plan When the Champion Changes Roles.

Closing the Loop

Annual planning gives you a real reason to ask a customer what matters to them next year, and the answer is worth more than a manufactured pitch. Keep the conversation about their plans, write down facts and open questions separately, and let the customer confirm your notes before anyone treats them as a case for expansion. If you want more practice with conversations like this one, DealSpeak's Financial Services practice conversations cover this scenario and others specific to the industry.