Read a sample: 1. The Purchase Is a Group Decision
A promising sales conversation can end with a sentence that changes its meaning: “I need to take this back to the team.”
The person who said it may genuinely like the proposal. They may believe the problem is urgent, the solution is credible, and the price is worth discussing. None of that means they can commit the organization. Their colleagues may need to use the product, fund it, integrate it, review its terms, or explain the choice if it goes badly.
For a seller, this is not necessarily an objection to overcome. It is information about the decision.
A group purchase differs from a one-person sale because the person who feels the need is not always the person who defines the requirements, controls the budget, carries the operational burden, or gives final approval. Even when one executive has formal authority to sign, that executive may rely on several other people’s assessments. A decision can have one signature and still be a group decision.
The seller’s task is therefore broader than persuading an interested contact. It is to understand how the organization makes this kind of choice and to help the people involved evaluate it with a clear view of the benefits, costs, risks, and work involved. That does not require the seller to manage the buyer’s internal politics. It requires curiosity, accurate documentation, and respect for the fact that the buyer’s organization owns the decision.
This chapter introduces a working case that will return throughout the book. It also introduces a decision log: a simple record of what is known, what remains uncertain, and what needs to happen next. Both are designed to help you replace confident guesses with a more useful picture of the purchase.
Imagine a company considering a new customer-support platform. The support director wants better visibility into incoming requests. A team lead wants a system that does not slow down agents. An information technology manager wants to understand how the platform connects with existing tools and how access will be controlled. A finance reviewer wants to understand the full cost. An executive must decide whether this project deserves resources now.
They are looking at the same purchase, but they are not experiencing the same decision.
For the support director, the central question may be, “Will this help us manage service more effectively?” For the team lead, it may be, “Can my team do its work during and after the transition?” For the technology manager, it may be, “What will we be responsible for maintaining?” For finance, it may be, “What are we committing to beyond the initial fee?”
These questions are not competing merely because they differ. A platform that satisfies one concern while ignoring the others may create a new problem rather than solve the original one. A seller who hears only the director’s enthusiasm might present a proposal that looks attractive in the first meeting and incomplete in every meeting that follows.
Nor should the seller assume that a job title reveals everything. A finance reviewer may care deeply about implementation capacity; a team lead may be the strongest advocate for spending more. An executive may delegate the choice, or may retain an approval role that is not obvious at the start. Titles are useful clues for inquiry, not substitutes for it.
A group decision is also not the same as a unanimous decision. Some organizations consult widely and leave the final choice to one accountable person. Others require several formal approvals. Still others rely on informal agreement before anyone is willing to advance a proposal. The structure matters because a favorable response from one participant can mean anything from “I am interested” to “We are ready to proceed.” You cannot safely treat those statements as equivalent without asking.
Consider a hypothetical company called Northstar Services, a midsize provider that supports business clients. Its customer-support team uses a shared inbox and several spreadsheets to track requests. The arrangement is familiar and relatively inexpensive, but requests are sometimes difficult to trace across the team. Managers also struggle to see which issues are waiting for a response.
Maya, Northstar’s support director, begins exploring a customer-support platform. She speaks with Jordan, a seller at a software company. Maya likes what she sees in an initial demonstration and asks for a proposal.
At this moment, Jordan could reasonably conclude that Northstar has a real problem and an interested buyer. Jordan cannot yet conclude that Northstar has agreed on the problem’s priority, the requirements for a replacement, the budget, or the approval process. Maya may not know all those things herself.
Instead of treating the request for a proposal as evidence that the deal is nearly done, Jordan asks:
> “When you consider a change like this, who else needs to understand the proposal or take part in the decision?”
Maya explains that Luis, a support team lead, would help assess whether agents could use the system. Priya, the information technology manager, would need to review the proposed setup. Elena, a finance manager, would review the commercial commitment. Maya believes her executive sponsor would make the final decision, although she is not certain which review would happen first.
The answer is useful precisely because it is incomplete. Jordan now has names and possible responsibilities, but not a verified map of authority. Maya has identified people who may matter; Jordan still needs to learn what each person actually does in…