Read a sample: 1. Why Considered Purchases Take Time
A promising first meeting can create a misleading sense of momentum. The buyer describes a frustrating problem. Your solution appears to fit. The conversation is warm, the questions are specific, and someone says they would like to move quickly.
Then the work begins.
Your contact needs to explain the problem to colleagues who experience it differently. An operations manager wants to know what would change for the people doing the work. A technical reviewer needs to understand how a new system would connect with existing ones. A financial approver asks what the organization would stop doing to make room for the expense. Someone else wonders whether the problem is important enough to solve now.
None of these conversations necessarily means the buyer has lost interest. They are part of deciding whether the organization can make, support, and live with a change.
This chapter is about recognizing that work. When you understand what a considered purchase asks of a buying organization, a long cycle becomes less mysterious. You can distinguish a genuinely advancing evaluation from a busy sequence of seller activities. More importantly, you can choose actions that help people make a sound decision instead of simply asking them to make one faster.
Consider a hypothetical company called Harbor Ridge Services. Its operations team uses several disconnected tools to manage customer requests. Information is copied between systems, handoffs are inconsistent, and managers have difficulty seeing where requests are delayed.
Maya, the operations director, begins looking at workflow software. She meets Daniel, a seller whose product appears to address several of her concerns. After a demonstration, Maya says, “This looks promising. I need to discuss it internally.”
Daniel could hear that as the beginning of a delay. A more useful interpretation is that Maya’s evaluation has entered a different setting. The question is no longer just whether she likes the product. It is whether the organization understands the problem well enough to make a change, agrees on what that change should accomplish, and has the capacity and authorization to proceed.
Maya may need to answer questions that did not arise in the demonstration:
- Which parts of the current process are causing the most trouble?
- Do the people doing the work agree with her assessment?
- What would the new workflow require them to do differently?
- Which existing tools would remain in use?
- Who would handle implementation and ongoing administration?
- How would the purchase compete with other priorities?
- What concerns must be resolved before approval?
Daniel cannot answer all of these questions for her. He can, however, help her see which questions remain open and provide information that makes the answers easier to develop.
That is a significant shift in perspective. In a considered purchase, you are not merely presenting an offer to a buyer. You are participating, from the outside, in an organizational decision. Your influence is real but limited. The people inside the organization carry responsibilities, relationships, and constraints that may not be visible to you.
Buying processes vary. Some organizations have formal review stages; others rely on conversation and informal agreement. Some begin with a clearly defined need, while others explore possible solutions before they understand the problem. The work rarely unfolds in a neat sequence, and participants may revisit earlier questions when new information appears.
Even so, several kinds of work commonly need attention.
Defining the need. A buyer may start with a symptom rather than an agreed problem. At Harbor Ridge, Maya sees delays in customer requests. Her colleagues may see separate issues: unclear ownership, inconsistent data, insufficient staffing, or a system that does not support the way they work.
A purchase can stall if the proposed solution addresses a problem that only one person believes is important. Before pressing for a decision, help your contact describe the current situation in language others can recognize. Ask what happens today, where the difficulties appear, and who is affected. Avoid treating every frustration as proof that your product is needed.
Establishing priority. A real problem does not automatically become an active project. Harbor Ridge may agree that its workflow is awkward while also facing a more urgent service issue or an internal reorganization. The choice may not be between your product and doing nothing. It may be between improving this workflow and spending limited attention on another worthwhile initiative.
A respectful seller makes room for that comparison. “How is this issue being weighed against other work?” is often more revealing than “When can you sign?”
Exploring approaches. Buyers may compare suppliers, consider modifying an existing tool, investigate an internal solution, or decide to change the process without buying anything. They may also discover that different approaches solve different parts of the problem.
You do not need to pretend all options are equally suitable. You do need to understand what the buyer is comparing and why. A product demonstration that highlights features may be less useful than a discussion of what each approach would require from the people responsible for implementation.
Evaluating consequences. A purchase can affect people who did not initiate the search. A team may need training. A manager may need to change reporting routines. A technical group may inherit support responsibilities. A financial reviewer may need a clearer view of the full commitment, not just the initial price.
These concerns are not distractions from the sale. They are part of the decision.…