The Most Valuable Thing a Vendor Can Do Is Say No

A few years ago a man came to us wanting to build a betting portal. He had a clear vision, real capital behind him, and every intention of spending it with us. He was, on paper, the perfect client. The kind you don’t want to slow down.

I asked him one question before we discussed anything else.

Do you have a licence to run a betting business?

He told me he had a business licence. I explained, as gently as I could, that a business licence and a betting licence are two entirely different things, and that in a great many jurisdictions the second one is extraordinarily hard to get, and sometimes simply unavailable. He went quiet. He said he’d come back to us once he had it sorted.

That was nine years ago. I’m still waiting.

I could have taken his money. He was ready to pay. We could have built him a beautiful, well-architected betting platform that he would never have been legally allowed to switch on, and by the time he discovered that, the invoice would have been settled and the problem would have been entirely his. Nothing I did would have been illegal or even, by the loose standards of the industry, unusual. Plenty of firms would have built it.

I’ve never once regretted asking the question instead. And I want to explain why, because the reason is not that I’m a good person. The reason is a business argument, and it’s one I think most technology buyers have completely upside down.

The economics of saying no

Here is what actually happened when I turned that project away.

That man tells people about me. Not “Brainium built my thing,” because we never built anything. He tells them something far more valuable than that. He says “I went to these people ready to spend a fortune, and instead of taking it, they stopped me making an expensive mistake.”

Do you understand how rare that story is, and how far it travels? In an industry where the default assumption is that every vendor will tell you whatever it takes to win the contract, a firm that talked itself out of one becomes the firm people recommend without being asked. That reputation compounds, quietly, for years. It is worth more than the project would ever have been, and it costs nothing but the discipline to ask an uncomfortable question at the wrong moment.

This is the part buyers get upside down. You are trained to see a vendor’s eagerness as a good sign. It is usually the opposite. A vendor who says yes to everything is not being helpful. They are being a vendor who says yes to everything, and one day the thing they say yes to will be your bad idea, and they will build it perfectly, and you will pay for it.

The most valuable thing a technology partner can do for you is sometimes to tell you not to build.

Every expensive failure was knowable at the start

I’ve watched a lot of software projects fail expensively over twenty-seven years. Almost none of them failed for reasons nobody could have seen. They failed for reasons that were sitting in plain sight on day one, and that everybody in the room agreed, tacitly, not to look at.

A licence nobody checked. An integration everyone assumed would exist and nobody confirmed. A data source that turned out to be locked behind a contract, or a regulator, or a department that had no intention of cooperating. A key third party who was never actually consulted. A regulation that made the whole model illegal in the one market that mattered.

None of these are technical failures. Every one of them is a question that should have been asked before a line of code was written, and wasn’t, because asking it might have slowed down the fun part.

The betting-portal question is not really about betting. It is about the single assumption your entire project rests on, the one thing that has to be true for any of this to work, that nobody has actually confirmed is true. Every project has one. Usually the team can feel it. It’s the thing everyone talks around in the planning meeting. The assumption stated a little too confidently and a little too quickly, that nobody wants to be the person to poke, because poking it might mean the project doesn’t happen.

A good partner pokes it. On day one. Before you’ve spent anything. That is the single most useful thing they will ever do for you, and it will feel, in the moment, like an obstacle.

How to tell, before you sign, whether your vendor will ever say no

This is the practical part, and it’s the reason I wrote this down.

When you are choosing who to build with, you are not really evaluating whether they can build. Most competent firms can build. You are evaluating whether they will tell you the truth when the truth is inconvenient to them. And you can test for that before you sign a thing.

Ask them, directly: tell me about a time you talked a client out of a project, or out of a feature they wanted. A firm that has the instinct will have a story ready, because they’re a little proud of it. A firm that doesn’t will stall, or give you a vague non-answer, or quietly reveal that they’ve never once left money on the table for a client’s benefit.

Ask them what they think is riskiest about your idea. Not what’s exciting. What’s riskiest. Watch whether they’ve actually thought about it or whether they reach for reassurance. Reassurance this early is a warning, not a comfort.

Ask them what would have to be true for this to fail. A partner worth having will answer that question with something specific and slightly uncomfortable. A vendor who just wants the contract will tell you it won’t fail.

The answers will tell you almost everything the proposal won’t. A firm that can say no to you before you’re a client is a firm that will tell you the truth when you are one. A firm that agrees with everything in the sales process will agree with everything right up until the project is on fire, at which point they’ll agree that it’s on fire and hand you the invoice.

The uncomfortable version

I’ll be honest about my own position here, because it would be dishonest not to. I run a firm that makes its money by building software. Every project I talk a client out of is revenue I don’t earn. When I ask the betting-portal question, I am, in the short term, arguing against my own P&L.

I do it anyway, and not because I’m a saint. I do it because the alternative, a portfolio full of projects that should never have been built, clients who quietly resent the money they wasted, and a reputation as a firm that will build anything you pay for, is a far worse business than the one I actually want. The short-term revenue is real. The long-term cost of chasing it is much larger and much harder to see, which is exactly why so many firms chase it anyway.

So before you commission your next build, ask yourself one question, and then ask it of whoever wants to build it for you.

What is the one thing that has to be true for this to work, that nobody has actually checked?

If you can’t answer it, that’s not a green light. And if the firm you’re about to hire can’t answer it either, or won’t, you’ve learned the most important thing about them before signing a single page.

If you’d like a second pair of eyes on a build you’re weighing up, that’s a conversation I’m always happy to have, including the version where I tell you not to do it. Sometimes that’s the most useful hour we’ll spend.