A promising conversation can stall because the person interested in the work is not the only person who must agree. Financial approval, operational adoption and technical access may belong to different people. The next step is to understand those decisions and their order, with the buyer’s cooperation. Adding more contacts to a deal does not by itself make the buying process clearer.
Map Decisions Before Job Titles
Ask which decisions remain before the organization can commit. A budget holder may approve expenditure, an operations leader may accept the delivery burden and a systems owner may approve access. One person can hold several roles, or a role may belong to a committee. Record the actual decision rather than assuming authority from a title.
For each decision, identify the evidence needed, its owner and any prerequisite. Keep unknowns explicit. “Finance needs to review” is incomplete until the team knows what finance is reviewing and when the required material will be available. Do not invent a deadline merely to populate a close-date field.
Help The Sponsor Explain The Work Internally
The person who introduced the opportunity may need to explain it to colleagues who never attended the sales conversation. Give them an accurate, concise description of the problem, proposed scope, customer responsibilities and unresolved questions. Avoid loading the document with claims that the sponsor cannot defend.
Ask the sponsor which parts are likely to be challenged. A technical owner may need a data flow explanation while an operational manager needs a staffing plan. Those are different information needs. Reusing the same sales presentation for every stakeholder can leave both unresolved, even if the presentation is persuasive in the original meeting.
Use A Decision Map For A Complex Opportunity
Illustrative scenario: a business wants to introduce a shared customer onboarding process. The commercial director supports it, operations must supply staff, and the systems team must confirm integration access. The seller’s map identifies three open decisions and one dependency: operations cannot agree on staffing until the pilot scope is fixed.
The next action is therefore a scope review with the sponsor and operations owner, followed by a technical access review. Asking all three people to approve a broad proposal at once would obscure the dependency. The map should show who owns each action on the buyer’s side and what the seller has promised to provide.
Treat Disagreement As Information
If stakeholders describe different problems, pause before negotiating terms. One may want a diagnostic report while another expects a working system. That is a scope conflict, not necessarily resistance. Document the alternatives and help the sponsor resolve which outcome the organization is buying.
Do not bypass a concerned stakeholder or portray them as an obstacle to overcome. Their concern may reveal a real dependency or risk. With the buyer’s permission, clarify the objection directly and record what would resolve it. If the organization cannot agree on the problem, a smaller investigation may be more appropriate than a full implementation proposal.
Advance Only When The Buyer Has A Next Decision
A useful mutual next step names the decision, participants, required information and target timing. Confirm it in language the buyer recognizes. “Send another proposal” is weak if nobody has agreed what question the revision answers. “Review the two staffing options before choosing pilot scope” describes progress that can be observed.
Keep the opportunity’s stage tied to that evidence. A larger buying group can make an opportunity look more engaged while adding unresolved dependencies. If the sponsor cannot secure the next conversation, revisit priority and timing rather than escalating contact volume. The goal is a workable buying decision, including a clear decision not to proceed.
Common Questions
Do We Need Contact With Every Stakeholder?
Not always. Work through the buyer’s agreed process and respect their preferences. You do need a credible understanding of the decisions and dependencies, including where your information is secondhand.
What If The Sponsor Says Everyone Is On Board?
Ask what decisions have been completed and what remains. A simple written confirmation of scope, responsibilities and the next step is more useful than assuming informal support equals approval.