A prospect once came to me with a project fully formed in his head. He knew what he wanted built, he had a budget for it, and he wanted to start soon. It was, on paper, the easiest sale I could ask for. He was ready to hand me money to do a thing I could do.
I told him not to.
What was actually in front of me
The thing he wanted built was real and it would have worked. But when I asked him to walk me through how the work flowed today, before we touched any of it, the build he had in mind was solving the second problem, not the first. Upstream of it was a much simpler mess that was quietly causing the thing he wanted to fix. Automate the second problem and he would have a faster version of a process that was broken one step earlier.
So the honest thing to say was: do not pay me to build this yet. Fix the step before it, which costs you almost nothing, and then let us see if you still need the build at all.
Why that was hard to say
It was hard because I wanted the work. I still want the work. Nobody running a young business enjoys turning down a ready buyer, and there is a voice that says take it, deliver it well, he will be happy, everyone wins.
Except he would not have won as much as he thought, and eventually he would have worked that out. A client who later realises he paid for the wrong thing does not come back, and he tells people. A client you talk out of the wrong thing remembers that you did.
What actually happened
He fixed the cheap upstream step. It helped more than he expected. And then he came back, because now he could see clearly which build was worth doing, and he trusted the person who had told him the truth the first time to be the one to do it.
I did not lose the sale. I moved it three weeks later and made it the right one. But I did not know that would happen when I said no, and I have to be honest that it does not always happen. Sometimes you tell someone the truth and they go and buy the shiny wrong thing from somebody else. That is a real cost and I am not going to pretend it away.
What it changed in how I sell
It moved the whole first conversation. I stopped opening with what I can build and started opening with what is actually happening in the business. The build, if there is one, falls out of that naturally, and it is nearly always a better build than the one the client walked in describing, because it is aimed at the real problem instead of the visible one.
It also made me calmer in the room. When you are willing to say "not this, or not yet", you stop performing certainty you do not have. You can think out loud. Clients feel that difference immediately, and it turns out to be more persuasive than confidence ever was.
The thing I keep coming back to
The most useful thing I do for most people who contact me is not the build. It is the half hour of mapping that tells them whether the build is even the right move. I used to think of that as the free part before the real work. I now think it is the real work, and the build is what happens when it points there.
This is the same lesson from the other side of the desk. I have written about why every SA SME needs an ops autopsy before buying AI, and about what a four-hour business autopsy actually looks like. Telling a client not to hire me is just that principle applied honestly to my own invoice.
Frequently Asked Questions
Did you really lose money doing this? On that deal, no. I moved it later and it became the right build. But the honest answer is that saying no sometimes does cost you the sale, and I would be lying if I said every one comes back. I do it anyway because the ones that stay are worth more than the ones you win by staying quiet.
Is this not just a sales tactic dressed up as honesty? It would be if I did it hoping for the return. The test is whether you still say no when you are fairly sure the client will walk. If you only tell the truth when it pays, clients can smell it. It has to be real to work, which is the inconvenient part.
How do you know when to say no to a build? When mapping the work shows the requested build sits downstream of a cheaper, simpler fix. Solve the upstream problem first. If the build is still needed afterwards, it will be a better-aimed build. If it is not, you just saved someone real money.
What do you open a first meeting with now? Questions about how the business actually runs, not a description of what I can build. The build comes out of understanding the work. Leading with the work instead of the tool is the whole change.
More of the build, and the mistakes, at heinoux.nexbdm.co.za.