The sale I didn’t make

Not every useful sales conversation ends in a deal.

I spoke with a legal-tech founder who was considering a custom software build. I could have taken the brief, assembled a proposal and waited to see whether the budget stretched far enough. But there was a question underneath the request: had the founder learned enough about the idea to justify that investment yet?

I suggested a lower-cost, low-code MVP to validate the idea first. That was not the answer that produced a custom development project for us that day. It was the answer I thought would help the founder decide what to do next with more confidence.

There is a real tension here. A sales team has a commercial goal. An early-stage customer has limited time, money and room for error. Pretending those interests never diverge does not build trust. I would rather name what I know, what I am assuming and what must be learned before recommending a large commitment.

When a founder brings me an idea, I ask: What part of the problem have you seen with your own eyes? What would the first group of users need to do? What can be tested without building the whole product? Who will make the decision to invest again when that test is over? The answers determine whether the next step is discovery, a scoped build, an existing product or a smaller experiment.

This is not a clever way of promising that a rejected deal will become future revenue. I cannot know that. Nor is ‘cheap’ always kind: a low-code experiment can also mislead if it cannot test the real risk. My job is to explain which uncertainty the option resolves and which ones remain.

A good sales conversation should leave someone clearer than when they arrived—even if the best answer today is not to buy from us. If that sounds unusual, perhaps we have made the sales conversation too much about the seller.

Read related: Helping customers decide sooner