Pain point

Definition
A pain point is a specific problem a customer already feels, costing them money, time or risk, that they would happily pay to make go away.

Why it matters

A message built on a real, quantified pain point stops a reader in a way "we save you time" never does, because the reader recognises their own situation. Pain also differs by role. A technical buyer worries about complexity, a finance buyer about return and a manager about the team's workload. One message aimed at everyone usually lands with nobody. The most common mistake in positioning is describing a feature instead of the pain it removes.

How to apply it

  • Ask open questions in customer interviews, such as "What is the biggest headache in this area?", not loaded ones such as "Do you struggle with X?".
  • Put a number on every pain, in hours, money or risk. An abstract complaint becomes a business case once it has a figure.
  • Keep a short list of pain points for each buyer persona, and rank them by how often they come up and how much they cost.
  • Check behaviour as well as speech. Session recordings and support tickets often show friction that interviewees forget to mention.

What it is

A pain point is a concrete frustration with a measurable cost, not a vague wish. "We want better reporting" is a wish. "Our finance team spends two weeks every month reconciling spreadsheets" is a pain point. It has a cost, a place in someone's week and a person who feels it.

Marketers often sort pain points into four types. Financial pain is paying too much. Productivity pain is wasting time. Process pain is a workflow that is slow or error-prone. Support pain is not getting help when it is needed.

Common mistakes

  • Treating a feature request as a pain point. "We need an export button" describes a wanted solution. Ask what problem the export would solve.
  • Assuming the pain without asking customers. Interview at least five before you write the message.
  • Naming a pain that exists but costs the buyer too little to act on. Rank pain points by cost and by how often they come up.
  • Writing for one pain when different roles feel different ones. A finance lead and an operations lead need different headlines.
  • Using your own jargon instead of the words customers used. Keep their phrases in the copy.
  • Never revisiting the list. Pain points shift as a market changes, so check it at least once a year.
Worked example

Say a small accounting firm with eight staff wants to sell a client-reporting service, but its founder only has guesses about what hurts. She books six interviews with bookkeepers at similar firms and records them with Fireflies.ai, which produces transcripts and summaries she can review. Across the calls, one phrase keeps coming back: month-end reconciliation takes about two working days per client. She then sends a short SurveyMonkey questionnaire to 120 contacts asking how many hours that step costs them each month. Forty-one replies put the median at nine hours. That number, not the feature list, becomes the opening line of her outreach.

Tools in the example

Some links are affiliate links: we may earn a commission at no cost to you. It never decides a ranking. How we work with partners

  1. Article

    Jobs to be done

    The progress a pain point stops someone making.

  2. Article

    Value proposition

    The promise that answers the pain.

  3. Article

    One-pager

    A document that often opens by naming a single pain point.

  4. Article

    Voice of customer

    The customer's own wording, a rich source of pain points.