"Willingness to Pay Research: Reading the Signals"

People say they like your idea. Nobody pays. Willingness to pay is where most ideas quietly die, and it is also the part of research people skip, because it is the least comfortable question to ask.

What willingness to pay looks like in a thread

It rarely looks like “I would pay twenty dollars”. It looks like someone complaining about a bill, describing a workaround that costs them money, or asking for a cheaper option because the current one is too expensive.

That is why you search for behavior and cost, not for opinions. The strongest signal is a person already spending something — money, hours, or a contractor — on the problem you want to solve.

The useful detail is almost always attached to a complaint about something else. Someone grumbling about an accountant’s bill is telling you the accountant is the current solution. Someone describing a late-night spreadsheet ritual is telling you the ritual is the cost. Read for what the person already pays, in cash or in evenings, and ignore the wish list.

The signals that actually count

• They already pay for something adjacent. A spreadsheet plus a part-time bookkeeper is a budget, even if it is not a line item for your product.
• They describe a cost in time. “This takes me a full day every month” is a price tag in disguise.
• They ask for a cheaper option. “Is there anything cheaper than X” means X is being bought.
• They tried and abandoned tools. Churn complaints tell you the job is real and the last attempt missed.
• They mention a deadline or a penalty. Taxes, audits, and renewals create urgency, and urgency is what makes a price tolerable.

Notice that none of these require you to ask anyone directly. They are all visible in how people talk about the problem.

The signals that fool people

Not every excited comment is evidence. Be suspicious of these:

• “That would be cool.” Interest is cheap.
• “I would definitely use that.” Use is not pay.
• “Someone should build this.” This is a wish, not a purchase.
• A long compliment with no mention of the current cost.

If a thread contains only these, keep looking. Enthusiasm without an existing budget or time cost is the most common reason a product launches to silence.

How to search for paying behavior

Say you are exploring a tool that handles recurring client invoices. You want the threads where money is already moving.

1. Search the task in plain words: site:reddit.com "recurring invoices" "how do you".
2. Add a cost phrase: site:reddit.com "recurring invoices" "takes me hours".
3. Search for the cheaper-option question: site:reddit.com "anything cheaper than" invoices.
4. Search for switching pain: site:reddit.com invoices "switched from" -review.
5. Read the replies and note every mention of money, hours, or a tool they pay for.
6. Repeat in a customer community, such as a subreddit for bookkeepers rather than founders.

Each search is short on purpose. You are looking for a handful of threads that mention a real cost, not a hundred threads that mention the topic.

If a search returns nothing in one community, do not assume the problem is absent. Move to where the buyer works. Founders and buyers use different words for the same job, and the paying side is the one that matters here.

What to do with the signal

Write down, for each thread, what the person currently spends. Then group the threads by that spend. If most of your threads describe the same cost — say a bookkeeper charging for a few hours a month — you have a starting point for pricing, because you already know the number you have to beat.

You still have to test the price with real buyers. But you can enter that conversation with evidence, and “people in your position spend a few hours a month on this” lands differently than “I think this is a problem”.

One caution: a set of threads can show that a budget exists without telling you the number. A bookkeeper charging for a few hours a month sets a floor and a ceiling at once, because you have to come in under what they pay now while still covering your own cost. Write both numbers down. If they sit too close together, that is worth knowing before you write code, not after.

FAQ

Isn’t this just confirmation bias?

It can be if you only keep the threads that agree with you. Counter-evidence is why you also search for abandoned tools and cheaper options. If those threads are full of people who tried and left, that is a signal about the job, not proof that you will win it.

How much spend counts as a real signal?

Any recurring cost tied to the problem. A few hours a month of paid time is a signal. A one-off purchase of a template is weaker, because it is not a budget that repeats.

What if nobody in the threads ever mentions money?

Then you have a problem people talk about but do not pay to solve. That is not automatically a dead end, but it is a warning. Look for a downstream cost, such as a fine, a lost client, or a delayed payment, and search for that instead.

Where do I find budget talk for business tools?

Customer-facing communities are better than founder communities. The people doing the work describe the money. Founders describe the idea. Search where the work happens, and the cost shows up in the first few threads.

Payments are hard to judge from a single comment, and easy to judge from a set of threads read side by side. That set is exactly what MicroSaas Research groups and reads for you, pulling from a public Reddit archive plus Hacker News, Stack Overflow and GitHub and returning a report with quotes checked against the source text. It runs in two to four minutes for a one-time 2.99 EUR. Before you spend anything, run the searches yourself: Reddit search operators that surface complaints and competitor research for indie hackers both add context.