How to Score a Pain Point for Willingness to Pay

Most founders rank problems by gut feel. The problem that sounds biggest wins, and months later nobody pays for the fix. A pain point can be loud, common and still not worth building for, because the people who have it won't spend money on it.

This guide gives you a manual method to score a pain point on three things: intensity, frequency and willingness to pay. It is the same three-part idea behind the 0-100 scores in SaasNiche, but the weights and rubric below are my own simple version, so you can run it with a spreadsheet and a few hours on Reddit.

What you are actually scoring

A pain point is a specific complaint from a specific kind of person, not a topic. "Marketing is hard" is a topic. "I redo the same website audit for every new client" is a pain point.

Score each pain point on three dimensions:

• Intensity: how much it hurts when it happens.
• Frequency: how often it happens, and to how many people.
• Willingness to pay (WTP): whether there is evidence that people spend, or would spend, money or serious time to make it go away.

Intensity and frequency tell you the problem is real. WTP tells you whether it is a business. That is why I weight it the most.

Step 1: Collect verbatim evidence first

Don't score from memory or from a summary. Score from the exact words people used.

For each candidate pain point, save:

• The exact quote
• The username, subreddit and date
• The link to the thread
• Upvotes and the number of people agreeing in replies

Quotes keep you honest. A paraphrase tends to sound more painful than the original, and you will score it higher without noticing.

A useful side effect: every quote you save is also someone you can contact later for customer discovery.

Step 2: Score intensity (0-10)

Intensity is about consequences, not tone. People swear about small annoyances all the time. Look for what the problem costs them.

Signals that raise intensity:

• A concrete loss: money, clients, access, security, deadlines
• Time quantified ("hours every week")
• A workaround that is clearly painful, like manual copy-paste or a messy spreadsheet
• The problem is a risk to their job or business
• Escalation: it started small and got worse

Signals that lower intensity:

• "It would be nice if..."
• No consequence mentioned
• The person says they live with it fine

Rough scale:

Step 3: Score frequency (0-10)

Frequency has two parts: how often one person hits the problem, and how many different people hit it.

Per-person frequency. Look for words like "every time," "again," "each week," "over and over." A task someone does daily is worth more than something they hit once a year.

Across people. One post is an anecdote. Search the same subreddit and neighboring ones for the same complaint in different words. If five unrelated people describe it, frequency goes up. Different communities describing it also helps, because it suggests the problem isn't just one forum's habit.

Rough scale:

• 0-2: one post, one-off event
• 3-5: a few similar posts, or a recurring but occasional problem
• 6-8: many posts, or a repeated task for each client, project or week
• 9-10: constant, daily, multiple communities

Step 4: Score willingness to pay (0-10)

This is the hardest one, and the one most people skip. Complaining is free. Paying is not.

WTP evidence comes in layers. From strongest to weakest:

1. Direct statements: "I'd pay for this," "I'm paying $X for a tool that half-works," "I hired someone to do this."
2. Existing spend: they name a tool, agency or contractor they already pay for the same job.
3. Tool-seeking behavior: "Anyone know a tool for...?" or "What are the alternatives to...?" People asking for recommendations are shopping.
4. Money tied to the problem: the problem costs billable hours, client revenue or compliance risk, so a fix has a clear value.
5. Buyer context: the poster is a business owner, agency, IT lead or freelancer billing by the hour, not a hobbyist.

Signals that lower WTP:

• Pure venting with no interest in solutions
• Consumers or students with no budget and plenty of free alternatives
• People who say they'd just build it themselves
• A problem that is annoying but costs nothing measurable

Rough scale:

• 0-2: venting only, no buyer context
• 3-4: plausible buyer, but no spend or tool-seeking
• 5-6: business context or a money cost, but no stated spend
• 7-8: tool-seeking or existing spend
• 9-10: explicit "I'd pay" or confirmed current spend, repeated by several people

Be strict. If you are inferring willingness to pay from context rather than reading it in the quote, cap the score at 6 until you've talked to someone.

Step 5: Combine into a 0-100 score

Use a weighted total:

Score = (Intensity × 0.3 + Frequency × 0.3 + WTP × 0.4) × 10

That gives a number from 0 to 100. The weights are a judgment call, not a standard. WTP gets 40% because a painful, frequent problem with no budget behind it is a hobby project.

Add one gate: if WTP is 3 or below, cap the total at 50, however high the other two scores are. This stops loud, popular complaints from outranking quieter problems that people pay to fix.

Also write a confidence note next to each score: low (one quote), medium (several quotes), high (several quotes plus a conversation). A 70 built on one post is a lead, not a conclusion.

Worked examples from real Reddit posts

Here are three posts, scored by hand with the rubric above. I'm scoring each from one quote, so treat the numbers as provisional.

Example 1: Repetitive website audits

“Every time i took on a new client i was doing the same manual analysis over and over. Go through their website, check the SEO, read the copy, look at competitors, figure out where they're leaking money.”

— u/W_E_B_D_E_V, r/Entrepreneur

• Intensity: 6. It's a time sink and a manual grind, but the quote doesn't describe a crisis.
• Frequency: 9. "Every time" and "over and over" point to a repeated task tied to each new client.
• WTP: 6. The poster runs client work, so time has a price. But the quote doesn't mention paying for a tool.

Score: (1.8 + 2.7 + 2.4) × 10 = 69. Confidence: low. To raise WTP, look for agency owners naming the tools they already pay for audits.

Example 2: Duplicate identities after an acquisition

“8 months post-acquisition and we still have 200 people with active accounts in both tenants. Some line-of-business apps were never migrated.”

— u/Prestigious-Fun-9680, r/sysadmin

• Intensity: 8. Eight months of unresolved duplicate accounts is a lingering security and admin problem.
• Frequency: 5. It's painful, but any one company goes through an acquisition rarely. You'd need to check how many IT teams face this across companies.
• WTP: 6. This is a business context where security gaps matter. But that is my inference. The quote doesn't mention budget.

Score: (2.4 + 1.5 + 2.4) × 10 = 63. Confidence: low. The next step is searching for people asking about tools or consultants for post-merger identity cleanup.

Example 3: Cascading cloud account suspensions

“one of my client had his payment delayed... it affected my personal account as well. Mine also got deactivated/suspended.”

— u/Future_Carpenter_910, r/webdev

• Intensity: 8. Losing access to accounts you depend on is a real consequence.
• Frequency: 4. One incident is described. You'd need more posts to know how common it is.
• WTP: 4. The poster is a freelancer who probably cares, but the quote shows no tool-seeking or spend. It reads more like a warning than a shopping request.

Score: (2.4 + 1.2 + 1.6) × 10 = 52. Confidence: low. This one needs more evidence before you'd spend time on it.

Notice what the exercise shows. All three feel like good problems at first read. The scores separate them once you ask what's actually proven about frequency and spending.

Turn the scores into a decision

Once you have 10 to 20 scored pain points, sort them and look at the top five.

1. Check confidence. Promote anything above 60 with low confidence into a research queue, not a build queue.
2. Hunt for WTP evidence. Search the same subreddits for phrases like "alternatives to," "anyone use a tool for," "I pay for," and "worth paying."
3. Talk to the posters. Message a few and ask what they do today, what they've tried and what it costs them. Ask about past behavior, not hypothetical interest.
4. Rescore. Update WTP and frequency with what you learned.

A good message is short, polite and clearly not a pitch. You're asking about their experience, not selling anything.

Common mistakes when scoring

• Scoring tone instead of consequence. Angry posts aren't always costly problems.
• Counting upvotes as WTP. Upvotes show agreement, not budget.
• Treating one thread as a trend. Score a single post, but label it low confidence.
• Ignoring who the poster is. The same complaint from a business owner and a student carries different weight.
• Letting existing free tools slide. If a free option already solves it well, WTP drops.
• Falling for your own idea. If you already love a solution, you'll score generously. Score before you brainstorm solutions.

Where a tool can save time

Doing this by hand is slow, and it gets slower as you add communities. SaasNiche scans Reddit communities and scores each pain point from 0 to 100 on intensity, frequency and willingness-to-pay signals, with the verbatim quotes, usernames and source links kept alongside so you can verify them. The manual method above is useful either way, because it teaches you what a strong signal looks like, and you can use it to sanity-check any score you see.

If you want to skip the first pass of collecting and scoring, you can browse scored pain points at saasniche.com and apply the checks above to the ones that interest you before you build anything.

FAQ

What is willingness to pay in a pain point?

It is the evidence that people would spend money, or serious time or effort, to solve a problem. Direct signs include saying they'd pay, naming a tool or service they already pay for, or asking for tool recommendations. Indirect signs include a measurable cost, like lost billable hours or compliance risk.

Can you measure willingness to pay from Reddit posts alone?

Not fully. Posts can show strong signals, like existing spend or requests for tools, but they rarely show exact price tolerance. Treat Reddit as a way to find and rank candidates, then confirm with direct conversations and, later, a test such as a pre-sale or a paid pilot.

How many quotes do I need before I trust a score?

There is no fixed number. One quote is a lead. Several unrelated posts describing the same problem give you more confidence, and a few direct conversations with affected people give you more still. It helps to record a confidence level next to every score.

Should intensity, frequency and willingness to pay be weighted equally?

Not necessarily. Weighting willingness to pay more heavily is one option, since a frequent, painful problem with no budget behind it is hard to turn into a business. The 30/30/40 split in this guide is a judgment call. Adjust it to your market and your own experience.

What is a good pain point score?

It depends on your scale and on how you gather evidence. With the rubric here, scores above roughly 70 with medium or high confidence deserve follow-up conversations. Anything with low willingness to pay should be capped, whatever its other scores.