The sales meeting that changed the question.

What we pitched.

The presentation led with measurement accuracy, turnaround and references. The buyer’s concern was different: whether the inventory number could be explained, checked and used in the company’s own review process. A polished technical pitch had arrived before a proper understanding of the purchase decision.

What she asked.

She wanted to know whether the methodology could stand up to review, how the inventory record would connect with plant movements, and what evidence the internal-controls team would have if a number was challenged. The presentation had not answered those questions.

She thanked us and stood up. We lost the meeting, in the sense that she didn't sign anything that day.

What we learned.

The ICP wasn't "someone who wants accurate stockpile volumes." The ICP was "a CFO who has signed off on a stockpile number in the last twelve months and is now worried about doing it again next year." Accuracy was a feature, not the purchase driver. The purchase driver was defensibility.

What we changed.

Three useful changes follow from that conversation.

Lead with the evidence chain. Explain how the data is collected, checked, identified and connected to the deliverable. Make the measurement basis available for review.

Scope the reconciliation. Ask what movement, density and book records exist, and agree how they can be compared with the measurement record. Do not promise a completed reconciliation without those inputs.

Design for the reviewer. Find out who will examine the result, what their acceptance requirements are and how exceptions should be documented. Put that review into the delivery process.

The follow-up.

The useful lesson is bigger than a single sales meeting. A buyer does not purchase an accuracy claim in isolation. They purchase a way to answer a question, make a decision or defend a process. The technical method should support that outcome and remain open to examination.