When several people must approve a service purchase, track their roles and decision needs alongside the proposal. Your main contact can be helpful and enthusiastic while still needing budget approval, technical input, or agreement from the people who will use the service. A simple stakeholder map makes those dependencies visible.
The map should support your contact’s buying process. Ask who needs to be involved and how they prefer to coordinate. Do not turn the exercise into an excuse to contact colleagues behind their back or gather personal information unrelated to the work.
Map roles before names
Begin with four questions: Who experiences the problem? Who will work with the provider? Who approves spending? Who can prevent implementation from proceeding? In a small company, one person may hold several roles. Another person may influence the purchase without signing anything.
Salesforce’s high-ticket sales guide describes the multiple stakeholders and approval steps that can accompany a significant purchase. A service business does not need an enterprise-sized organization chart to apply the underlying idea. Even a purchase involving an owner, office manager, and outside adviser has different questions to answer.
| Role | Typical question to clarify | Useful evidence |
|---|---|---|
| Problem owner | What needs to improve? | Current situation and desired outcome |
| Day-to-day contact | What will our team need to do? | Schedule, responsibilities, support route |
| Spending approver | What commitment are we making? | Scope, price structure, timing |
| Specialist reviewer | What requirements must be satisfied? | Relevant documentation and explicit unknowns |
Ask without challenging your contact’s authority
Use questions that make coordination easier: “Who else will need to be comfortable with the rollout?” and “What information would help you discuss this internally?” These invite the buyer to explain their process. Asking whether someone is the “real decision-maker” can turn a practical question into an unnecessary status contest.
Record confirmed roles separately from assumptions. If your contact says the owner usually approves purchases, write that as information supplied by the contact. Do not mark approval complete until the relevant step actually happens. Include the date you learned the information, because people and responsibilities can change during a longer evaluation.
Give each concern a place
Salesforce’s stakeholder-alignment training stresses understanding the assumptions and evidence behind decisions. For a small provider, the practical application is a shared requirements list. Capture each concern, why it matters, the evidence needed, and who can confirm that the answer is sufficient.
In an illustrative commercial cleaning purchase, the owner may care about total commitment, the site manager about access, and employees about disruption. The proposal might satisfy the owner but still fail because no one has arranged keys or agreed on service hours. A short joint discussion about access could resolve more than another general sales presentation.
Avoid producing a different promise for each participant. Keep one current scope and one shared list of open questions. Tailor the explanation to each person’s responsibilities while keeping the underlying facts consistent. If two requirements conflict, show the conflict openly and ask the buyer to prioritize it.
Choose a coordination method
Some buyers want one meeting with everyone present. Others prefer their main contact to collect questions and circulate answers. Ask which method fits. Supply a concise summary that can be forwarded without requiring the contact to reconstruct your conversation from memory.
The summary should explain the problem, recommended work, customer responsibilities, outstanding decisions, and next step. Avoid speculative return calculations unless the buyer has provided defensible inputs and understands the assumptions. Clear boundaries often help an internal discussion more than an aggressive projection.
Keep the map current through the decision
At each meaningful checkpoint, verify who is involved, which questions remain, and what has changed. A new operations manager may need context; a departing sponsor may leave the purchase without an owner. Treat those as changes to the buying process rather than evidence that your main contact has become uncooperative.
Before forecasting the sale, check that the necessary roles have been consulted and the actual approval process is understood. “Everyone liked the proposal” is different from “the owner approved the scope and purchasing has issued the required order.” Your map is useful when it explains the next dependency in plain language.
