Expansion Managers: Establishing an Operating Cadence With Customers

An operating cadence with a financial services customer either earns its place on the calendar or turns into a meeting everyone dreads and quietly stops attending. The difference comes down to whether the meeting maps to a decision the customer actually needs to make, or whether it survives out of habit because someone scheduled it eight months ago and nobody canceled it. Expansion managers who get this right treat the cadence as a structure built around specific recurring decisions, not as a relationship ritual. In financial services this matters even more, because compliance reviews, operational fixes, and product changes each move on a different timeline, and folding all three into one generic monthly call confuses everyone about what the meeting is for. The Financial Services practice conversations hub covers more of these recurring account conversations if you want the wider picture.

Why This Conversation Goes Wrong

Most cadence problems start with the manager, not the customer. A manager inherits an account, sees a standing monthly call already on the calendar, and keeps it running because canceling a meeting feels riskier than letting it continue out of inertia. Over time the agenda drifts. What began as a working session for the operations team turns into a mixed group that includes an executive sponsor who only needed to hear about a handful of decisions a year, now sitting through updates that do not concern them.

Attendance creeps up for the same reason. Nobody wants to be the one who removes a name from the invite, so the meeting grows until it serves no single person well. The customer notices before the manager does. People send a delegate, join late, or stop turning on their camera. The manager reads this as disengagement and starts worrying about the account, when the real problem is that the meeting has no decision attached to it anymore. A cadence that produces no action is worse than no cadence at all, because it burns time and trust while looking, on paper, like proactive account management.

How to Prepare Before You Propose a Cadence

Before you suggest any recurring meeting, write down the decisions that actually recur for this account and how often each one truly comes up. A financial services customer might resolve workflow and support handoff questions every few weeks, revisit product scope once a quarter, and reset priorities with an executive twice a year. Those are three different rhythms, not one meeting run at three different sizes.

For each recurring decision, name the person who owns it. The owner is not always the person who has attended in the past out of habit. An operations lead who resolves workflow questions daily is usually the right owner for a monthly working session, while an executive sponsor only needs a seat when the decision changes budget or direction. Write out, for every session, the decision on the table, the owner, the input required to make it, and the evidence that will tell you whether the last decision actually worked. A monthly review might need an update on an unresolved support handoff. A quarterly conversation might need a fresh look at a stated customer objective and which teams have to weigh in on it.

Separate current service issues from future scope before the meeting even starts. If a customer has an open complaint or a stalled ticket, resolve it and assign it on its own track first. Raising a future expansion topic in the same breath as an unresolved problem reads badly, and it teaches the customer that your review meetings are sales meetings wearing a different name.

What to Say in the Meeting

Open by naming the purpose you think the meeting should serve, and ask the customer to correct you. Picture an exchange with a financial services customer that currently runs one monthly meeting covering everything.

The manager asks, "What decision do you need this monthly meeting to support." The operations lead answers, "We need to close out open workflow questions between our team and yours before they pile up." The manager follows up, "Does your executive sponsor need to be in this one, or only when priorities shift." The operations lead says the sponsor only needs to join when something changes budget or direction, and otherwise prefers a short written summary.

The manager proposes splitting the two purposes, a monthly working session with the operations team focused on workflow questions, and a separate quarterly session with the sponsor focused on objectives and scope. The manager asks the customer to correct the attendee list rather than assuming it is right the first time.

Later in the relationship, the customer says, "Let us keep this lightweight going forward." Instead of agreeing in the abstract, the manager asks which single question is worth time at the next meeting, and who will bring the information needed to answer it. The customer names the outstanding handoff issue and says their support lead will have the details. The manager closes by repeating the decision, the owner, and the date back to the customer, then confirms it in writing right after the call.

Mistakes That Undermine a Cadence

A few habits quietly wreck an otherwise well built cadence.

1. Treating meeting frequency or attendance as a signal of account health. A well attended meeting with no decisions is not a healthy account, and a shorter meeting with a clear decision is not a warning sign.
2. Letting a session end without a named owner for whatever comes next. If nobody owns the follow up, it does not happen, and the next meeting opens by revisiting the same open item.
3. Mixing service problems with future scope in the same conversation. Fix the open issue first, on its own track, before introducing a topic that grows the relationship.
4. Adding people to the invite because it feels safer than asking whether they are needed. Every extra attendee with no stake in the decision dilutes the meeting for the people who do have one.
5. Running the same format for every account regardless of what that customer's decisions actually require. A cadence copied from another account often fits the wrong rhythm entirely.

How to Practice and Score It

Rehearse the moment when a customer tries to shrink the meeting to nothing, because that moment decides whether the cadence survives. Set up a role play where the customer says something like "let us keep this lightweight" or "we do not need to meet this month," and see how you respond. Score the response on three things, whether you named one specific decision worth the time, whether you named who owns the input for that decision, and whether you closed with an actual date rather than a vague promise to follow up.

Managers who are new to an account benefit from pairing this practice with related skills. If you inherited an account where the previous manager trained the customer's team directly, the piece on Expansion Managers Rebuilding Training Ownership After a Team Change covers how to reset that relationship without losing the customer's trust. If your cadence includes a periodic look at how the customer actually uses the product, the guide on Expansion Managers Running a Utilization Review That Produces Decisions walks through turning that review into a real decision instead of a status report. DealSpeak lets you rehearse these exact moments against an AI counterpart that pushes back the way a real customer would, so the first time you handle someone trying to cut a meeting short is not in front of the account.

A cadence earns its place on the calendar by producing decisions the customer can point to later, not by showing up reliably on a shared invite. Build it around what actually recurs for that account, write down the decision and the owner every time, and cut anything that stopped doing either. That discipline is what keeps a customer showing up to the meeting instead of quietly working around it.