Practice Reopening a Deal With a New Stakeholder

A new stakeholder in a late stage deal changes the conversation. Some sellers replay every earlier detail. Others rush into a pitch. Both choices leave the new person outside work already under way. An enablement consultant should coach a short reset. Acknowledge earlier work, ask about the new person’s responsibility, and identify what they need for their part of the decision. The seller does not need a fresh discovery meeting with every attendee. The seller needs a respectful entry point for each decision role.

Finance leaders often listen for different details than an operations champion or end user. Their attention often settles on approval paths, timing, budget ownership, or comparison with an existing process. A product tour assumes every person needs identical context. Coach sellers to arrive with a working record of earlier discovery. The record should hold observed goals, unresolved questions, named participants, and planned decisions. Leave assumptions out. An unfilled field becomes a question for the next conversation.

In a fictional workshop, Dana, a regional vice president, says her team loses momentum when finance joins an evaluation. Consultant Imani asks, “What does a seller usually say during the first two minutes?” Dana shares an opening full of product history. Imani stops her after one paragraph. “Where did finance enter?” Dana laughs and says, “Nowhere.” The group hears how an organized summary still fails to invite a new person into the decision.

Imani sets up a fictional roleplay. One participant plays a seller, one plays the operations champion, and one plays a finance leader who joined after earlier meetings. The seller opens, “I know the operations group has spent time on workflow. Before I recap earlier discussions, what does finance need to understand for your review?” The finance leader replies, “I need to see how a new purchase reaches approval.” Imani asks Dana what the seller should learn next. Dana chooses a question about the current approval path.

Coach precision in every next question. “Tell me more about finance” sounds polite yet produces an unfocused reply. A stronger question is, “Which step in your approval process changes when a new vendor reaches final review?” The finance leader might explain a budget owner needs a documented reason for the expense. The seller now has a useful direction. Earlier notes do not need a full replay. The seller needs to connect prior discovery with the finance leader’s responsibility.

Offer a short recap after one or two questions, rather than before any questions. In the fictional roleplay, the seller says, “The operations group wants managers to review selected calls during weekly coaching. You are looking at approval ownership and a documented reason for a new expense. Have I captured both roles accurately?” The champion corrects one detail. Managers review selected calls, not every call. The correction matters. A brief recap invites correction early and avoids a meeting built on a loose detail.

The recap should not sound like a verdict. Avoid language such as “You need our solution because finance needs approval.” A stakeholder has not made a commitment by naming a responsibility. Keep your words close to what they said. “You mentioned a budget owner and a documented reason” preserves accuracy and leaves room for explanation. This discipline keeps discovery notes from becoming proof of a business case.

Prepare stakeholder cards before a workshop. An operations champion card might read, “You want less time locating calls for coaching. You worry a new review will delay the group.” A finance leader card might read, “You joined because an expense needs a clear owner. Ask about approval timing.” These private details give participants reasons for different questions. Observers then see whether the seller changes direction after new information appears.

Ask the seller to open without slides. Slides tempt people to follow a prepared order instead of listening. Give the seller sixty seconds to welcome the new stakeholder, recognize earlier work, and ask a role question. Pause the exercise after sixty seconds. Each stakeholder states what they understood and what remains unclear. If finance says, “I heard product history but not why I was invited,” start again. Revise the opening instead of explaining away the feedback.

Add a second fictional scene where the operations champion grows defensive. The champion says, “We already covered all of this. We need to move.” The seller replies, “I hear your concern about momentum. Finance has a role in this decision, so I want to learn their review need and keep our next session focused.” This response respects the champion without excluding finance. Ask observers to point to exact words showing respect for both people. General praise offers little coaching value.

Use a decision map after each practice. Place the decision in the center and write each person’s role beside their stated concern. Include only statements heard during the roleplay. In this fictional example, operations wants a workable coaching review. Finance needs a budget owner. The seller needs a meeting with both people after gathering approved material. Do not fill empty spaces with guessed motives. A missing detail becomes the next question.

Managers should coach for evidence of listening. Listen for recognition of previous work, a question tied to the new stakeholder’s role, a recap open to correction, and a next meeting connected to a stated decision. Do not score energy, charm, or a polished pitch. Ask, “When finance said approval timing mattered, which question came next?”

In a later round, introduce an incomplete answer. The finance leader says, “I need more detail before I bring this forward.” The seller should not rush toward unsupported specifics. Ask, “Which detail would help you identify who needs to join the next review?” If finance asks about a technical or contractual subject outside approved material, record the exact question and name the route to an appropriate owner. The meeting stays useful without invented answers.

Follow up language needs a purpose. The seller might say, “I will send a brief record of today’s workflow and your approval questions by Wednesday. After you identify the budget owner, we will meet with you and the operations group to review those points.” Each sentence connects a person with a stated need. Do not schedule a vague next chat. A useful meeting has participants, a reason, and a question worth answering.

Before practice ends, review the decision map for loose ownership. “Finance team” does not name a person. “Send information” does not name an output. Replace vague entries with a person, a document or conversation, and a date. If the finance leader has not named the budget owner, record “finance leader will identify budget owner by Wednesday.” The seller does not need to guess a name in order to establish a next action.

For final practice, hand Dana the champion card and give another participant the finance card. Start a six minute meeting without slides. At minute four, ask the finance leader to name one missing detail. The seller writes the detail into the decision map, states who will provide an approved response, and names Wednesday for the recap. Before the timer ends, the seller sends a calendar hold for a meeting with Dana and finance, using the missing detail as the agenda line.