Needs & Pain Points

First PublishedMay 24, 2026Last UpdatedMay 25, 2026ByAtif Alam

The decision this page enables: which customer needs are worth solving — and which to deliberately ignore.

What it is

Customer needs are the underlying gaps a person wants closed; pain points are the specific frictions they feel today as a result. A “need to ship code faster” is the need; “spending 40 minutes a day fixing CI flakes” is the pain point. The pain points are what people will pay you to remove.

Not all needs are equal. Some are urgent and frequent (you can build a product around them); some are real but mild (nice-to-haves that don’t convert); some are invented (people say they want them in interviews but never act on them).

Why it matters

This is the input to almost every Strategy and Marketing decision downstream:

The ICP is the segment whose pain is sharpest.
The positioning leads with the pain you remove and the alternatives you displace.
The Workbook → Audience & message section asks for “the pain, in the customer’s words” — this page is where you derive that line.

How to find needs and pain points

Three categories worth distinguishing — because the type of need drives the method you use to find it:

Functional needs — the practical job (“I need to deploy code”). Surfaced by direct observation, customer-discovery interviews, and looking at the workarounds people build today.
Emotional needs — how the person wants to feel (“I want to look competent in front of my team”). Surfaced by interview questions that probe behavior and word choice (“Tell me about the last time…”), not direct asks (“Do you feel anxious?”).
Social needs — how the person wants to be seen (“I want my team to think I’m pragmatic, not bleeding-edge”). Often the strongest driver in B2B buying, and almost never volunteered.

Then evaluate each candidate need on two dimensions:

Severity — how much does it hurt when this need isn’t met? (Mild annoyance vs. blocking their job.)
Frequency — how often does this need come up? (Once a year vs. daily.)

The matrix that follows is the single most useful lens for prioritizing what to build.

The severity × frequency matrix

	Low severity	High severity
High frequency	”papercuts” — small but constant; great for product-marketing copy, mediocre for category creation	the gold zone — frequent and painful. Build here.
Low frequency	ignore	”high-stakes rare” — niche but you can charge a lot per occurrence (e.g. audit prep tools)

The gold zone (top-right) is where you build a category. The other quadrants can be useful — but only after you’ve nailed the gold-zone need first.

Templates

Need statement

Customer [persona] needs to [outcome they want]
when [trigger / situation]
because [why this matters to them],
but today they [current workaround / friction].

Severity:  [1-5, where 5 = blocks their job]
Frequency: [daily / weekly / monthly / quarterly / rarely]
Evidence:  [how many distinct customers mentioned this, in what context]

Pain log

A simple table you maintain as you research:

| Pain                        | Said by             | Trigger              | Severity | Frequency |
| --------                    | --------            | --------             | --------     | --------     |
| 40-min/day fixing CI flakes | 6 of 8 interviewees | every PR             | 4        | daily     |
| One-off audit log exports   | 2 of 8              | annual SOC-2 prep    | 3        | yearly    |

The “Said by” column is the one most early-stage teams skip. Without it, you cannot distinguish a real pattern (6 of 8) from a strong opinion held by one loud customer.

Metrics to track

Distinct-customer count per pain — how many different people mentioned this pain. Floor: 3 distinct customers before treating it as real signal; below that, it’s anecdote.
Interview saturation point — the interview number at which no new pains appear in a session. Healthy products usually saturate at 5-7 interviews within a single segment.
% of cohort affected — what fraction of your target segment hits this pain at least monthly. Floor for “build it” candidates: ≥40% of the ICP cohort.
Workaround effort — how much time/money customers spend today on the workaround. Strong signal: any workaround that costs them >2 hours/week or >$50/month.
Stated willingness-to-pay — only directional; ask “what would you currently pay to make this go away?” Treat the number as ranked order, not absolute.

Examples

SaaS workspace (B2B through-line)

For the small-team SaaS workspace product:

Pain:        "I spend ~6 hours/week stitching outputs between 3 tools
              and the glue keeps breaking when one tool updates."
Said by:     6 of 8 interviewed team leads at <10-person SaaS teams
Trigger:     any change in the upstream tool's API or UI
Severity:    4  (not blocking, but recurringly painful)
Frequency:   weekly
Workaround:  hand-edited spreadsheets; a brittle Zapier
Need type:   functional (the workflow) + social (the team lead doesn't
             want to look like the person who can't stop the breakage)

This sits squarely in the gold zone (high severity × high frequency) and led to the product’s “unified workspace, no glue code” positioning.

Consumer fitness app (B2C contrast)

For a habit-tracking fitness app aimed at casual home exercisers, the equivalent research surfaces a very different pain:

Pain:        "I lose motivation by week 3 of any new routine."
Said by:     11 of 14 interviewed casual exercisers
Trigger:     missing 2-3 consecutive workout days
Severity:    3  (emotional, not blocking)
Frequency:   monthly, in cycles
Workaround:  starting a new app every 2 months
Need type:   emotional (consistency without guilt) + social (don't want
             to look like a quitter to themselves)

Note that the B2C pain skews emotional/social, while the B2B pain skews functional. The same matrix works for both, but the interview techniques and validation methods differ — see Customer Discovery Interviews.

Common pitfalls

Asking “what features do you want?” — features are solutions; you want the underlying pain. Ask about the last time the problem happened, not about hypothetical futures.
Treating one loud customer as a pattern. Three distinct customers is the floor for “this is a real need.”
Recording stated importance instead of revealed importance. What people say they want and what they actually pay to fix are routinely different. Weight behavior > words.
Skipping emotional and social needs. Especially in B2B, the buyer’s career-safety and team-perception needs often outweigh the functional ones — but they’re almost never volunteered.
Building for the “low severity, high frequency” quadrant thinking volume = market. Papercuts make great copy (“annoying, isn’t it?”) but not paying products. Build in the gold zone first.