Ask a founder if anyone will pay for their idea, and almost all of them say yes. Ask them who, and the room gets quiet.

That gap is the whole problem. “Will anyone pay” isn’t a yes-or-no question at all – it’s a question about a specific person, in a specific moment, reaching for their wallet for a specific reason. Most founders answer a different, easier question instead: is this valuable? Would this help someone? Those are nice questions. They’re not the same question, and the difference is where a lot of good ideas quietly die a year in.

The substitution nobody notices they’re making

“Would this help someone?” is almost always true. Most ideas worth building would help somebody, somewhere, a little. That’s a low bar and it feels like a high one, because you’re the one who thought of it and you can feel how much it would’ve helped you six months ago.

The payment question asks something harder: whether the value is large enough, urgent enough, and clearly enough yours to solve that a stranger picks your solution over doing nothing, over a workaround, over their current tool, over just living with the problem.

The tell is in the shape of your answer. A feature list means you’re answering the helpfulness question. A name, a dollar figure and a reason means you’re answering the payment question.

The three things a real answer has

The build-or-don’t decision needs three things, and knowing who pays is the first. This is that one on its own, because it’s the one founders are surest they’ve already answered. I’ve never seen a founder answer “will anyone pay” without these three, and I’ve never seen one who thought they could answer it who actually had all three.

A named buyer – not a persona, an actual type of person you could describe meeting. What they’re doing today instead – because they’re doing something, even if it’s nothing, and nothing has its own comfort you’re competing against. And the number – what they’d pay, and why that number rather than half of it or double it.

“Small businesses would love this” isn’t an answer. “A solo bookkeeper running four client files in spreadsheets, currently paying nothing and losing two hours a week to it, who’d pay $30 a month to get the two hours back” is an answer.

Notice how much more nervous the second one makes you. That nervousness is worth naming, because you will feel it again every time you get close to the real question. Call it the flinch. It is what a specific answer costs, and it is the most reliable signal you have that you have stopped describing and started testing.

Interest is not the same currency as payment

Founders collect a great deal of real, honest interest before they collect a single dollar, and the interest quietly gets treated as though it were the same thing. It isn’t. Interest costs the other person nothing. Payment costs them something they’d rather keep.

Interest costs the other person nothing. Payment costs them something they’d rather keep.

A stranger saying “I’d definitely use that” has spent zero of anything. The same stranger being asked for a card number is a different conversation, testing a different thing, and it is the only version that tells you the truth. Everything before that point is market enthusiasm. Only the version with a price attached is market validation.

Why founders avoid asking the real version

Because the real version can say no, cleanly, in a way “would this help you” almost never does. Nobody wants to watch a stranger’s face while they name a price. It is far more comfortable to describe the feature and read the nod as a yes.

But the nod was never the information you needed. The price test is uncomfortable precisely because it is the only one that produces a fact instead of a feeling – and a fact bought with one awkward conversation is a great deal cheaper than the same fact arriving after you’ve built the thing.

Ask it the hard way

Skip the feature pitch. Name the buyer, name what they do today instead, name a number, and ask for it directly, before you’ve built anything they’d feel bad saying no to.

And watch for the flinch. If naming your number out loud makes you hesitate, you already know it’s the real test – the flinch is the answer arriving before the stranger has said a word. Everything you were doing before it was practice at not asking.

The flinch is the answer arriving before the stranger has said a word.

Want more like this? Rick writes about the go/no-go decision, founder counterintuitions, and the business of building ventures worth building.

All writing