Customers say they want it, but won't pay. Should I build more?
People keep asking for the next feature and don't buy it when you ship it. 'I'd use that' is not demand, and there's a cheap way to tell the two apart.
The story you’re telling yourself“They'd buy if I added the feature, service, or option they keep asking for, I need to build more.”
What you’re really afraid ofI keep building what people ask for, they still don't buy, and I can't tell if the product is the problem or something I can't see.
They told you. Clearly, more than once: "I'd definitely use this if it did X." So you built X. You shipped it, proud, and told them it was ready.
And they didn't buy.
So now there's a new X. Another feature, another option, another thing on the roadmap someone swore would tip them over. And a quiet dread that you could build forever and never reach the version they finally pay for.
"I'd use that" is not a sale
Here is the sentence that costs founders years: people are far more generous with their *wishes* than with their *wallets.*
"I'd use that" costs the person nothing to say. It's encouragement, politeness, a genuine-but-cheap opinion about a hypothetical. It feels like a sale because it sounds like enthusiasm. It is not one. The only signal that means anything is someone moving money before the thing is perfect.
When people ask for a feature and then don't buy once it exists, the feature was almost never the reason. It was the polite version of "not yet", and you took it literally, and spent months on it.
Building more is where you hide from selling
Building is comfortable. It's concrete, it's in your control, and it *feels* like progress. Selling — asking someone to pay, and hearing why they won't — is exposing and uncomfortable. So the roadmap becomes a place to hide from the harder question.
And the harder question is rarely "what's missing from the product?" It's usually one of these: Are the people asking actually buyers, or just interested browsers? Do they have the problem badly enough to pay to solve it? And have you asked for the money plainly, or kept sweetening the thing to avoid the ask?
More product adds cost, delay, and complexity to a business that hasn't yet proven the demand it already has. If the current version doesn't sell to anyone, a better version usually sells to the same nobody.
Find out whether it's a product gap or a buyer-and-price problem · a Daytalens verdict, $5,000
Sell what you have before you build what you don't
The cheap test costs you nothing but nerve: take what you have right now and ask ten of the "I'd use that" people to actually buy it, today, at a real price. Not pre-orders of a dream: the thing as it is.
Their answers will teach you more than another quarter of building. If some buy, you had a selling problem, not a product one, and now you know who your real buyer is. If none do, you just saved yourself months of building the wrong thing for people who were never going to pay, and the real work is figuring out who would.
Either way, the money is in the conversation you've been avoiding, not the feature you were about to start. If the people showing up aren't the ones who buy, start with the gap between who you built for and who actually pays.
Questions people ask
- Customers say they want a feature but won't buy, should I build it?
- Be careful: 'I'd use that' costs nothing to say and rarely predicts a purchase. When people ask for something and don't buy once it exists, the feature usually wasn't the real reason. Before building, test whether the people asking are actual buyers with the problem badly enough to pay: the answer is often no.
- Why won't customers pay for my product even though they like it?
- Liking and paying are different thresholds. Enthusiasm is cheap; money is the only real signal of demand. 'Likes it but won't pay' usually means the problem isn't painful enough for that person, they aren't your real buyer, or you haven't asked for the sale plainly. It's rarely a missing feature.
- Should I add more features to increase sales?
- Not until the current version sells to someone. If what you have converts nobody, a bigger version tends to sell to the same nobody, later and at more cost. Prove demand for what already exists — sell it, at a real price, today — before you build more.