How to tell if people will pay, not just say they like it

Someone said your idea is great. Another said they would definitely use it. A third asked you to “keep them posted.” None of that is a customer. In 2026 you can ship a clean product in a weekend. Polite feedback is even cheaper. Payment is the only signal that still costs the other person something.

This is how you tell a compliment from a sale before you burn another month on v2. Indiecity is for one person or a team under twenty. If you still need language from real conversations, start with customer interviews when you have zero users. If you already took money and the story is real, send it in.

Compliments are not proof

Rob Fitzpatrick wrote The Mom Test so founders would stop collecting praise and calling it research. People want to be kind. You want to hear that the work matters. That is how you get “That sounds amazing,” and walk away thinking the market said yes.

Fitzpatrick’s point is that compliments feel like learning and they are not. He also flags fluff: generics, hypotheticals, and anything about the future. “I would definitely buy that” is fluff. It costs them nothing to say. It costs you months if you believe it.

People stop lying when you ask them for money.

That is the whole method in one sentence. You do not need a survey about willingness to pay. You need a deposit, a pre-order, an invoice, or a clear no.

What “I like it” usually means

When someone says they like it, they often mean one of these:

• They do not want to hurt your feelings.
• The problem is real for someone else, not for them this month.
• They like the idea of the outcome, not the work of buying and switching.
• They are being social, not buying.

None of those are insults. They are just not revenue. End the chat with a commitment that costs time, reputation, or money. Fitzpatrick’s hierarchy is simple: a second meeting with a goal, an intro to the real buyer, a letter of intent, a deposit, a pre-order. One of those is a real signal. Two of those is stronger.

Stop asking if they would pay

“Would you pay $49 a month for this?” feels rigorous because it has a number. Fitzpatrick still calls it a bad question. People are optimistic about their future selves. They also want you to leave happy. So they say yes, or “probably,” or “if you add one more thing.”

Ask about the past instead. What did they do the last time this broke? What did they pay (tools, freelancers, overtime, a full-time hire)? How often does it hit? If they never searched for a fix and never paid anyone, they will not wake up ready for your product.

Last time [problem] hit, what did you do? Walk me through it. What did that cost you in time or money? What did you try that failed?

When you have something they can buy, skip the hypothetical. Put the price in the room and ask them to buy. If you skip that ask, you will collect the same pile of replies everyone is collecting this year.

2026 is full of curious people who do not pay

In August 2026, Harshit Tiwari wrote on Indie Hackers after shipping, doing manual outreach, and still sitting on zero revenue. He wrote that his reply rate on LinkedIn DMs was about 37 percent. People were curious, not paying. He also found checkout bugs that blocked people who tried to pay, so he could not tell if the zero was demand or a broken form. He said the thing most launch threads skip: he still did not have proof people would pay.

SkillIssue’s comment put the next step in plain words: take ten of those replies, run the work on their real problem, and ask for payment on the call. Replies measure curiosity. They do not measure payment. More content and another public v2 do not replace that ask.

You will see the same pattern this year. AI makes shipping cheap, so the feed fills with demos people clap for. Claps are free. Count paid yeses, not “sounds cool.”

Ask for the money on the same day

Once they have described a real problem and you have shown the one thing that removes it, say the price and stop talking. Do not end with “I will send something over.” Have the link, invoice, or transfer ready. The Collison brothers at Stripe set people up on the spot for a reason. Once they leave the call, the yes cools off.

If this takes [their words for the pain] off your week, it is [price]. I can start you today. Want to do that now?

Fair. What would you need to see to decide? Let’s book 15 minutes on [day] before you go. I will send the payment link either way so it is not blocked on me.

If you need [boss / partner / finance] for the full amount, can we lock a deposit of [smaller number] today so I hold the slot? If they kill it, we stop.

A deposit is not a trick. Fitzpatrick treats money in hand as the cleanest truth. If they will not put a small amount down, the big “yes later” was not real.

Charge a real number

A cheap price gets a cheap yes. Patrick McKenzie (patio11) has been saying for years that builders undervalue their own software and can often charge more. The essay is old. The habit is still everywhere in 2026: you pick a number that feels comfortable for you, not a number next to what the problem already costs them.

If you ask for pocket change, a yes still teaches you almost nothing about whether they will pay a real price. If you ask for a number next to what the problem already costs them, a yes is signal and a no is signal. Either way you learned. A free plan only teaches you about free users.

Pick a number you can say on a call without wincing. Put it on the page. Put it in the note. Watch what happens when the number is real.

Score the conversation, not the feeling

After every talk, mark one outcome. Not how warm it felt.

• Paid: money moved.
• Hard commitment: deposit, pre-order, signed intent, or a booked next step with the real buyer and a date.
• Soft yes: compliments, “keep me posted,” “when it is ready.”
• Clear no: wrong problem, no budget, not the buyer.
• No path to pay: they tried and checkout broke. Fix checkout before you decide nobody wants it.

Only the first two count toward proof. Soft yeses go in a list you do not brag about. If checkout failed for people who tried to buy, your zero does not mean no demand until you re-ask with a working link. Harshit’s thread is a public example of that trap.

A one-week test you can run now

1. Day 1. Write the offer in one paragraph. Put a price on it. Open a payment link or invoice template. Buy it yourself as a stranger would, and fix what breaks.
2. Days 2 to 4. Talk to ten people who already have the problem. First half of each call: their life and last attempt. No pitch yet.
3. Same calls, second half only if the pain is real: show the one fix, say the price, ask them to pay today.
4. Day 5. Write down every soft yes in one column and every paid or hard commitment in another. Do not mix them.
5. Days 6 to 7. Follow up only the soft yeses with one clear ask and a deadline. No new features. No longer deck.
6. End of week. Count money and hard commitments. That number is your signal. Compliments do not move it.

If you cannot name ten people with the problem, you are not ready to judge demand. You are still guessing the buyer. Find the room first, then run the week.

When they like it and still will not pay

Sometimes the product is fine and the person is wrong. They do not own the budget. The pain is mild. They already hacked a spreadsheet they can live with. That is useful. Change the buyer or the offer.

Sometimes the path to pay is broken. Test it. Pay yourself. Fix the error before you decide the offer is broken.

Sometimes you never asked. You demoed, you smiled, you said you would follow up, and both of you escaped. Ask on the call. Ask in the next message with a link and a date. If you will not ask, you will not learn.

What to stop counting

• “Love it” messages and launch applause.
• Waitlist size with no price and no charge date.
• Friends who signed up to be nice.
• Replies that never reach a payment ask.
• Survey scores about “interest.”
• Feature requests from people who never bought.

Then you know

You know people will pay when money moves. A real no is useful too: it tells you to change the offer or the buyer. Compliments tell you nothing. Building is easy this year. Separating praise from payment is still the work.

Once you can tell a compliment from a sale, go get the ten. Use the first 10 paying customers guide for the names, the notes, and the two-week plan. When someone pays and you will put your name on how it happened, write the story. You can join Indiecity while you run the week. That gives you people to talk to. It does not get you a paid yes. Until then, put a price in the next conversation and ask.