A technically correct solution can answer every question and still leave the commercial decision unresolved.

There is a pattern in technical sales conversations that is easy to miss: at some point, the questions stop being about whether the solution works and start being about what happens after the organization relies on it.

Weeks of evaluation go well. Specifications are confirmed, performance requirements are met, the proposed configuration is demonstrated. Then, without anything changing in the solution, the customer asks about previous installations. About spare parts and service availability. About what happens if the component fails unexpectedly.

These may appear to be routine due diligence questions, but they can also reveal a shift in what the customer is trying to establish. The customer is no longer asking whether the solution works.

They are asking what relying on it will mean for their organization.

Two kinds of confidence

A solution that meets every technical requirement can still leave a customer uncertain — not about performance, but about adoption.

Can maintenance support it? Does the organization have experience with this technology? What happens if a replacement component is not immediately available? These are technical questions too — but they concern operational adoption rather than technical performance. Technical evidence helps answer them; it rarely answers them alone.

Consider a manufacturer evaluating two suitable solutions. One uses equipment their maintenance department has operated for years: limitations understood, spares in stock, procedures in place. The other performs better and costs less to run — but introduces unfamiliar components and a different maintenance approach.

Engineering prefers the second solution. Operations sees a harder decision, because the expected improvement has to be weighed against the consequences of change.

Technical confidence and organizational confidence are not the same thing, and the customer needs both before they can say yes.

What the new questions are really about

The distinction is often visible in what customers ask about:

• Questions about capacity and performance concern what the solution will do. They point forward.

• Questions about references, track record, and failure behavior concern what happened to others. They are still questions about the future — about the customer's own operational risk, asked indirectly.

A shift from the first kind to the second does not prove concern about implementation; these may be routine purchasing questions. But it is a reason to check which uncertainty is actually on the table.

If the remaining uncertainty concerns implementation, another technically perfect explanation will accomplish very little.

The more useful contribution is addressing what adopting the solution means for the organization that has to live with it.

From the book

Technical confidence, organizational confidence and the questions that reveal which one is still missing are explored in more depth in Chapters 6 and 10 of Sales Between the Lines, including how the specificity of customer questions can signal a shift from curiosity to genuine evaluation.