A New Stakeholder Enters Late in the Deal

A late addition can reset an evaluation you thought was nearly done. The new person may be protecting a risk the group has not addressed.

Read the signal

Treating the stakeholder as a blocker usually leads to a defensive feature pitch. Their concerns may be legitimate, and the deal’s earlier consensus may have excluded a required decision owner. You need to learn their criteria without forcing them through every previous meeting.

Make the next move

Ask the champion why the stakeholder joined and what decision they influence. Send a short summary of what has been tested and invite the newcomer to identify gaps. Offer a focused conversation on their domain rather than replaying the full sales cycle.

Language you can adapt

Illustrative wording:

We have confirmed the workflow with operations, but I understand you are reviewing implementation risk. Which requirements should we test with you before the team makes a decision?

The wording is a starting point. Replace the problem, evidence, and request with details the buyer actually gave you. If those details are missing, ask a question before sending a polished message. Specificity makes it easier for the buyer to correct your understanding and easier for you to see whether the opportunity is moving.

Decide what happens next

Update the decision map after the conversation. A new requirement may change scope, price, or timing. Do not preserve an old close date just because it was already in the forecast.

Write the result in your deal notes as an observable fact: who responded, what they agreed to do, and when. A friendly reply is useful, but a decision, a named owner, or a scheduled review tells you more. If the next step remains vague, treat that as information about the deal rather than a reason to send the same follow-up again.

Use these examples responsibly. Describe your product, pricing, and customer results accurately, and adapt every suggestion to the buyer’s stated process.