How Do You Know If Anyone Will Pay Before Building?

Most founders build first and look for customers second. By the time they start asking "will anyone pay for this?" they've already spent six months and a significant chunk of runway on the answer.

This post is about reversing that sequence, and the specific traps that catch even experienced founders who think they're doing validation right.

The Real Problem Isn't Whether Your Problem Exists

Here's something that trips up almost every early-stage founder: the problem you're solving is probably real. People have it. They'll acknowledge it in a conversation. They might even get excited about your solution.

But a problem being real doesn't mean it's a priority.

Think about it this way. If you're building a fitness app and you talk to someone who goes to the gym once a week, they'll almost certainly agree that tracking workouts is a hassle. They're not lying. The problem exists. But someone who goes to the gym once a week is not going to pay for a fitness app, because the gym isn't a central enough part of their life to justify the investment.

This is what I call the problem ranking issue. Founders validate that a problem exists without ever validating where it ranks against everything else the customer is dealing with.

The question most founders ask: "Does this problem sound familiar to you?"

The question they should be asking: "What's your biggest challenge right now?"

That second question might have nothing to do with what you're building. And that's the point. If your problem doesn't come up unprompted, or if it comes up but ranks fifth on their list behind things you can't solve, you don't have a customer yet. You have a conversation partner.

"Day in the Life" Reveals More Than Any Direct Question

One of the most effective customer discovery techniques is deceptively simple: ask someone to walk you through a day in their life related to the area you're building in.

Not "do you have this problem?" Not "how often does this happen?" Just: "Walk me through what that actually looks like on a Tuesday."

What you're listening for isn't whether the problem comes up. It's how much time they spend on it, how much friction it causes, and how often it happens. Frequency is a proxy for priority. A problem someone encounters daily is categorically different from one they hit monthly, even if they describe both as "frustrating."

This approach also protects you from a common trap: founders who interview people who technically fit their ICP but are light users of the relevant context. If your product lives at the gym, talk to people for whom the gym is a serious part of their week, not someone who shows up occasionally and feels vaguely guilty about it.

Enthusiasm Is Not a Buying Signal

There's a specific kind of founder pain that doesn't get talked about enough: the launch that follows a great validation process. The interviews went well. People were engaged. One or two even said "I'd definitely pay for this."

And then launch day comes and nobody buys.

What happened?

Usually, one of two things. Either those people were being polite, saying what felt socially appropriate in the moment, or they were genuine but they weren't the right people. The first customers most founders talk to are people they already know: colleagues, former clients, people in their network. These people want you to succeed. They'll give you energy and encouragement. What they won't give you is an honest read on market demand.

Getting past your immediate circle is hard. It requires more networking, more outreach, and eventually a willingness to talk to complete strangers who have no emotional stake in your success. That's uncomfortable. But a stranger's "yes" is worth ten times a friend's "yes," because the stranger has no reason to spare your feelings.

The deeper issue is that most founders don't have a repeatable process for reaching their ICP at scale. They get customer one and customer two through connections, and then the well runs dry. The solution to this isn't more hustle. It's getting precise about who your ideal customer is, where they spend time online and offline, and building a consistent way to reach them.

The Hard Paywall Counterintuition

If you ask most founders whether to offer a free trial or require payment upfront, the instinct is almost always free trial. Let people experience the value first. Lower the friction. Earn the conversion.

Here's what I've seen in practice: hard paywalls often convert better than soft ones.

The logic is straightforward once you see it. A person who hands over their credit card before they've used the product has made a real commitment. They've decided it's worth paying for. That decision means they're far more likely to actually use it, get value from it, and stick around. A free trial user is in a fundamentally different psychological state. They're evaluating, not committed, and their default is to drift away.

More importantly for validation purposes: the only true signal that someone will pay is that they pay. Not that they said they would. Not that they clicked on an ad. Not that they filled out a survey. Actual money, from an actual human, who made a real decision.

This is why the manual-before-you-build approach is so powerful. Before Airbnb had a platform, the founders were manually listing properties and processing bookings. Before Uber had an app, the concept was tested with a much simpler version of the idea. The question they were answering wasn't "is this a good idea?" It was: will a stranger get into another stranger's car and pay for it? Will a stranger sleep in another stranger's house and pay for it?

Those were their riskiest assumptions, and they tested them with the minimum possible infrastructure, because the only thing that mattered was whether people would actually do the thing.

Identify Your Riskiest Assumption First

Every business is built on a stack of assumptions. Most of them are probably fine. But somewhere in that stack is one assumption that, if it's wrong, makes everything else irrelevant.

For Uber, the riskiest assumption was that strangers would trust each other enough to share a car. For Airbnb, it was that homeowners would let strangers sleep in their homes. Both assumptions seemed borderline insane at the time. One early Airbnb investor reportedly called the idea "madness."

Your job in the pre-build phase is to identify your version of that assumption and find the cheapest possible way to test it.

Ask yourself: what is the one thing that has to be true for this business to work, that I'm least sure about? Not "is there a market?" or "can we build it?" Those are real questions but they're rarely the riskiest ones. The riskiest assumption is usually something behavioral: will people actually change how they do something? Will they trust a platform with something they currently handle themselves? Will they pay for something they currently get for free?

Once you've named that assumption, design a test for it. Not a survey. Not a mockup walkthrough. A real test where someone has to make a real decision, ideally with real money.

Who You Talk To Matters as Much as What You Ask

In B2B, this is where a lot of validation falls apart silently.

You can do everything else right: identify the problem, find the right company size and industry, even get positive signals from the conversations, and still end up talking to the wrong person inside the organization.

Here's the distinction worth making explicit: the user of your product and the buyer of your product are often not the same person. A marketing manager might be your ideal user, the person whose daily life improves most with your product. But in most companies, a new software subscription needs sign-off from finance, or from a VP who has no idea what the product does day-to-day.

If the person who will actually use your product doesn't see the value, move on. That's a dead end regardless of who else you talk to. But getting a user excited isn't enough either. You need to understand the full buying chain: who uses it, who approves it, who pays for it, and what each of those people needs to hear.

Getting this wrong doesn't just slow down sales. It corrupts your validation data. You think you have a signal when you have noise from the wrong person.

Mixed Signals Don't Always Mean a Bad Idea

What do you do when some conversations go well and others don't? When half the people you talk to seem genuinely interested and the other half can't see the point?

The instinct is to average them out and make a judgment call. That's the wrong move.

Mixed signals are almost always a segmentation problem. You're talking to too many different types of people and grouping them together as if they're one market. The founder who goes to the gym five times a week and the founder who goes once have different relationships with fitness. They're not the same customer even if they share a job title.

When you get contradictory feedback, the question to ask is: what's different about the people who got it versus the people who didn't? Industry, company size, role, how frequently they encounter the problem, whether they've tried to solve it before. Somewhere in those variables is a real ICP hiding.

Timing also matters more than most people want to admit. Zoom existed before COVID. It wasn't new. But the conditions that made everyone suddenly desperate for exactly what Zoom offered didn't exist yet. Sometimes mixed signals mean your idea is sound but the market isn't ready. The question then becomes whether you can survive long enough for conditions to change, and whether you're making that bet consciously or by accident.

When to Get a Second Opinion

There's a point in every founder's journey where they've done the work: talked to users, gotten some paying customers, validated the core assumption, and still can't tell whether they have enough to go all-in.

At that point, the problem is usually not a lack of data. It's perspective. You've been so deep in the problem for so long that you've lost the ability to see it clearly. The details that feel important might be noise. The things you're discounting might be the real signal.

This is where a trusted cofounder, adviser, or peer group becomes invaluable. Not to make the decision for you, but to give you the bird's-eye view you can no longer give yourself. Someone who respects you enough to tell you what they actually think, not what you want to hear.

Choose that person carefully. The most useful second opinion comes from someone who has no stake in your excitement and no incentive to be polite about it.

The One Thing to Do This Week

If you take nothing else from this post, take this:

Find one person who fits your target customer, put something in front of them, and ask them to pay for it.

Not a survey. Not a "would you use this?" conversation. Not a waitlist signup. A real ask for real money.

It doesn't need to be a polished product. It doesn't even need to be a product at all. It can be a manual service, a one-page landing page with a checkout button, a prototype that barely works. What matters is that the other person has to make a real decision: yes or no, with actual consequences.

The worst that happens is they say no. And now you know something true.

The faster you can get to the moment where someone either hands you money or doesn't, the faster you'll know whether you're building something people will pay for, and the less time and runway you'll spend finding out the hard way.

Nobody likes being told their baby is ugly. But the founders who succeed are the ones who go looking for that feedback before they've spent a year building the baby.