Buying process discovery

Buying process discovery maps the path a prospect will follow from recognizing a problem through approval, purchase, and implementation. Ask about that path while discussing the problem, then check whether your proposed next step fits it. Interest can exist without an active evaluation. A prospect may be learning, comparing providers, building an internal case, or preparing for approval, and each state needs a different question. Find the state before spending time on pricing or implementation details so the next question matches the prospect's actual motion.

Start with the buying motion

Start by finding out how this prospect normally buys, after the problem has enough shape to make the process relevant. Ask process questions after identifying the problem.¹ During initial discovery, ask how people buy software,² and widen the lens to understand how the company evaluates and purchases software.³

Use, "How do you guys make decisions on this type of stuff?".⁴ Listen for the actions, people, and approvals in the sequence. If the prospect can describe only interest in the solution, keep asking how decisions are made before discussing the solution in detail.

Map evaluation and timing

Separate an active evaluation from general learning by asking what has started, what remains, and what event will force a decision.

Ask, "What's the typical process for buying software in your business?"⁵ Ask when they need to be live. The answer can show where the prospect is in the evaluation process, whether an evaluation is underway, and what role the contact plays in buying.⁶

Ask for the decision timeline. Asking when they will sign can be too aggressive.⁷ For a complex product, ask what causes an opportunity to close.⁸ Continue when the prospect can describe the evaluation path and the event that turns interest into a decision. A vague date without a process behind it needs another question.

Map people and approval

A contact may explain a problem without owning approval. Map who participates and where the decision leaves that person's hands.

Ask, "Is there anyone else that needs to kind of sign off?"⁹ Understand how the person you are speaking with touches the process,¹⁰ and get as much insight into the approval process as possible before investing further in the deal.¹¹

Then ask, "What is their signing process like, who signs this?".¹² This exposes the final handoff and helps you check whether the person on the call can move the purchase forward. Continue when you know who approves, who signs, and what the contact owns. Missing answers leave the internal path untested.

Trace the purchase path

Trace the route from a preferred option to a purchase. The provider set, prior buying habits, budget, and procurement process can each change that path.

Ask, "Who else are you guys looking at? I'd love to learn more."¹³ Also ask how the prospect bought previous pieces of technology¹⁴ and when the budgeting process begins so you do not miss the buying opportunity.¹⁵

Check whether procurement is involved and whether the route is familiar. A buyer's current purchase may be going through procurement for the first time.¹⁶ Discovery should give you a general feel for how the prospect approaches price.¹⁷ Listen for gaps between the stated purchasing process and what this purchase will require. Continue once the prospect can explain the alternatives, budget timing, procurement route, and price discussion.

Test the implementation path

Approval is only part of discovery. Find the work that must happen before the solution can be adopted, and find the work the prospect has not started.

Identify the steps required for your solution and which of those steps the prospect has not taken.¹⁸ Ask what must be true for adoption and what success will look like. Success criteria can show whether the prospect has considered what it would take to buy and can help you avoid wasting time.¹⁹

A request for pricing or an implementation plan on the first call signals a different process from a prospect who is only learning.²⁰ Treat it as a cue to ask about the purchase path and implementation requirements immediately.

After the discovery call, buyers may do more research, visit review platforms, and present the solution to their boss and team.²¹ Prepare for those internal steps by asking what the prospect will need to explain or confirm after the conversation.

Make the process mutual

After mapping the prospect's process, make your own process visible and check whether the next step fits. This gives the prospect something concrete to accept, change, or reject.

Before asking about the prospect's process, explain your own process.²² Then ask, "Does that fit the way you're buying and what you're looking for?"²³ The answer tells you whether your proposed meeting, proof, or approval step belongs in the sequence.

Putting next steps in the prospect's hands often reveals information about the buying process.²⁴ When the answer is vague, ask difficult questions about next steps and the process to buy.²⁵ Agree on the next action only after the prospect can describe what happens, who participates, and what must be true for the action to matter.

What not to do

These errors make a deal look further along than it is. Keep them visible when reviewing discovery notes.

• Leave the prospect's decision process unexplored. This creates risks for the seller.²⁶
• Wait until late in the first meeting to ask process questions. Asking the right questions early reduces the chance of risky scenarios.²⁷
• Treat interest as proof of purchase intent. A prospect without an internal business case is still window shopping.²⁸
• Assume your process and the prospect's process will naturally match. These processes are frequently at odds.²⁹

Take these questions into discovery and write the answers as a path: how the prospect evaluates, who approves, how the purchase moves, and what implementation requires. Use the gaps to choose the people to include, the proof to prepare, and the next action to agree before the conversation ends.