Where does a pain point sit among buying signals?
Buying signals follow the way people move toward a purchase. A pain point comes first: the person knows something hurts but has not decided what would fix it. The earlier the signal, the fewer vendors are in the conversation, and the more teaching your email has to do.
| Signal | What the person knows | What your email must do |
|---|---|---|
| Pain point post | Something costs time, money or sleep | Name the problem and show it is solvable |
| Recommendation request | A tool could fix it, but not which one | Explain the category and where you fit |
| Alternative search | Their current tool is not the answer | Prove you meet their requirements |
| Competitor complaint | A specific vendor is failing them | Make switching feel safe |
What does a pain point post sound like?
Pain shows up in professional subreddits, on X and in community threads indexed by search engines. The words give it away: time ("every month we spend"), manual work ("still copy-pasting"), risk ("almost missed", "before the audit") and growth ("since we doubled"). Two fictional examples:
- "Our two-person finance team spends the first week of every month chasing receipts from 40 field technicians. There has to be a better way."
- "We almost lost our biggest client because weekly reporting kept slipping. How do other agencies stop reporting from eating Fridays?"
How do you search for pain point signals?
Pain is easier to find by its words than by its topic. Start from the problem your best customers had before they found you, write down the phrases they used before they knew your category existed, and sort them by kind of pain. Then add a role or an industry to each phrase, never a vendor name: once a vendor is named, you are looking at a different signal, such as a competitor complaint.
| Kind of pain | Phrases people use | Example search |
|---|---|---|
| Time | "every month we spend", "takes us a full day", "eats our Fridays" | "takes us a full day" reconciliation |
| Manual work | "still copy-pasting", "by hand", "giant spreadsheet" | "by hand" invoices field technicians |
| Risk | "almost missed", "before the audit", "got flagged" | "before the audit" access reviews startup |
| Scale | "since we doubled", "can't keep up", "breaking at our size" | "can't keep up" support tickets agency |
| Cost | "bill went up", "paying for seats nobody uses" | "paying for seats nobody uses" small team |
| Ownership | "our only ops person left", "nobody owns this" | "nobody owns" client onboarding |
Where to run the searches
Search inside the professional communities where your buyers talk shop first, sorted by newest. Then use a search engine with the site: operator and quoted phrases to reach community threads it has indexed. Exclude words that pull in job seekers and students, such as "interview" or "homework".
How often
Weekly is enough for most pains, because a recurring problem stays true for weeks. Read each thread in full: the replies often say more about the poster's company than the post itself.
How Startories qualifies a pain point, and why many are dropped
Startories classifies posts that describe a problem without naming a solution as pain points, separately from requests and complaints. The hard part comes next: many of these posts are written under pseudonyms with no business attached. A signal is only kept when it can be tied to a real company from public business details, such as a company the poster names or a business website they link. When it cannot, the post is dropped rather than guessed.
The posts that remain are scored against your ICP with the reasons written out, and the decision-maker is identified. That is often not the poster: a technician describing a broken process is a user, while the operations or finance lead owns the budget. Only a verified business email is contacted.
Scoring a pain point: a worked example
Use two gates and three scores. A post that fails a gate is dropped, however strong the pain. The scale below is an example built for a firm that automates finance operations for field service companies of 20 to 200 people; the numbers are ours, not an industry standard.
- Gate 1, company: the post can be tied to a real business from public business details.
- Gate 2, owner: you can name the role that owns the budget for the fix.
- Recurrence, 0 to 3: one bad week scores 0; "every month" scores 3.
- Stated cost, 0 to 3: hours, money or a near miss, written in the post itself.
- Fit, 0 to 3: how much of the problem your offer actually removes.
| Post | Gates | Recurrence | Cost | Fit | Result |
|---|---|---|---|---|---|
| Finance lead at a 60-person HVAC services firm: two people lose the first week of every month to receipts | Pass | 3 | 3 | 3 | 9: write to the poster, who owns the process |
| Technician at a plumbing company: "I spend every Sunday on expense paperwork" | Pass; the owner is the operations manager | 3 | 1 | 2 | 6: write to the operations manager about the process, with no trace of the post |
| Anonymous account: "month-end is killing me" | Fails gate 1 | – | – | – | Dropped: no company can be identified |
| Owner of a 25-person landscaping firm: reconciling fuel cards took one whole weekend | Pass | 0 | 2 | 2 | 4: park; one bad weekend is not a process |
How do you write to someone who never asked for a vendor?
Carefully, and about the problem. Your email should read like a note from someone who has seen this problem at many companies, because that is the honest version of what happened. It should make sense even if the reader never saw the post.
A structure that fits this signal has four parts: the problem as something common in their industry, its cost in their terms, one concrete fix, and a question that is easy to answer, including with "no".
A complete email to a controller
Subject: month-end at field service companies
"Hi Marcus, at field service companies, month-end usually stalls on receipts from the field rather than on the books themselves. We set up receipt capture that technicians use from their phones, matched automatically to card transactions, so the close starts with the paperwork already in. Is month-end close something you are working on this quarter, or a known annoyance you have learned to live with?"
Why it works: a controller who never saw the post would still find it relevant, the fix fits in one sentence, and the question lets him say "not now" without effort, which is still useful to you.
Angles for other owners
- Agency owner, reporting pain: "If weekly client reporting eats your account managers' Fridays, we automate the data pull and leave the commentary to them."
- Head of support, volume pain: "When ticket volume doubles, routing breaks before the team does. We rebuild routing rules for support teams of five to fifteen in two weeks."
- Operations manager, handoff pain: "The handoff from sales to onboarding is a common place for B2B services firms to lose days. We map it and automate the steps that repeat."
- Founder, everything pain: "Not pitching yet: is month-end close something you're trying to fix this quarter, or a known annoyance you have learned to live with?"
The one follow-up
Two to three weeks later, send something useful with no ask: a short checklist, a template or a two-line tip. Then stop. If the problem gets worse, a stronger signal such as a recommendation request will tell you.
Reach companies with a reason to buy this week
Startories finds the buying signal, verifies the decision-maker and runs the outreach until they book a call.
Privacy and platform etiquette: where is the line?
Pain point posts are more personal than a launch or a job ad. Someone describing a stressful month is sharing it with peers, not with salespeople. Treat what you learn as context about a business problem, not as information about a person.
The platforms set rules as well. Reddit's Data API Terms govern programmatic access to its content, and X does the same through its Developer Policy. Many professional subreddits also restrict self-promotion in their own rules. Two practical consequences: do not answer the thread with a pitch, and do not message the poster on the platform. If you contact anyone, do it by business email, and write to the person who owns the problem.
If you write to people in the UK or the EU, you also need a lawful basis for processing their data. For B2B outreach that is usually legitimate interests, which means weighing your interest against the person's reasonable expectations; the ICO explains when you can rely on legitimate interests. A message about a business problem, sent to a business address, with an easy opt-out, fits those expectations far better than one built from personal details.
Startories contacts verified business emails only, includes an opt-out in every message, suppresses unsubscribed contacts across all campaigns and deletes personal data on request.
Is speed as important here as for other signals?
Less than for a complaint or a recommendation request. A recurring problem does not disappear in a day, and no shortlist is forming yet, so reaching out within a few days is fine. The exception is a post with a deadline ("before our audit next month"): treat it like any hot signal and act within 24 to 48 hours.
Because the pain is ongoing, one respectful follow-up a few weeks later is reasonable. Do not chain five emails to someone who never asked for help.
Objections you will hear, and honest answers
- "We're fine with the spreadsheet." Believe them, and ask what would make it stop being fine: a new hire, a bigger client, an audit. Offer to check back at that point, and do.
- "Not a priority this quarter." Ask which quarter it becomes one and put a single email on your calendar for then.
- "How did you find us?" Tell the truth, briefly: their company came up in public discussions of this problem, and you work on it with similar businesses. Offer to take them off your list. A vague answer costs more trust than the truth.
- "We built something internally." Ask what it does not cover yet. Internal fixes tend to handle the main case and leave the exceptions to someone's evenings.
- "Just send pricing." Send it, with one line on the scope it covers. Hiding the price from someone who was never shopping makes the whole email feel like a trap.
Who benefits from pain point signals, and the traps
This signal suits sellers who solve a process problem and can explain it plainly: consultants, AI and automation agencies that replace manual work, accounting firms for month-end and reporting pain, marketing agencies, and vertical SaaS built around one workflow. If your buyers vent on Reddit, see Reddit lead generation.
- Venting about an employer. An employee complaining about their own company's chaos is rarely in a position to buy.
- Engagement bait. Some "pain" posts are written by consultants to start a discussion and collect leads of their own.
- Problems you only half solve. If your product fixes part of it, say which part.
How do you measure pain point outreach?
Pain point emails teach as much as they sell, so measure both. Four numbers, kept per problem rather than per campaign:
| Number | How to compute it | How to read it |
|---|---|---|
| Problem-confirmation rate | Replies that confirm the problem, buying or not ÷ emails sent | Whether the pain is real and shared. Low means it is rarer than the posts suggested |
| Meeting rate | Meetings ÷ companies contacted | The business result. Compare it with your other signals before adding volume |
| Opt-out rate | Unsubscribes ÷ emails sent | Watch it closely here. If it rises, the email reads as intrusive: rewrite the opening first |
| Upgrade rate | Contacted companies that later show a stronger signal ÷ companies contacted | Pain can come back as a request or an alternative search: your warmest second touch |
Start with one problem
Pick one recurring problem your best customers had before they found you, and the words they used to describe it. That is a complete funnel brief. Starter ($99 a month, first project $1 for a 3-day trial) covers one funnel, one ICP and one intent source; see plans.
To see where pain points sit in the bigger picture, read signal-based outbound and our buying signals guide, and use the ideal customer profile template to define who should receive these emails.
Frequently asked questions
What is pain point prospecting?
Pain point prospecting means finding companies that describe a business problem in public, before they look for a product, and offering a solution to that problem. It reaches buyers earlier than most signals, with less competition and more need for a careful, helpful message.
Is it creepy to email someone about a problem they posted?
It can be, if you quote the post or mention where you saw it. Write to the decision-maker about the business problem, as something common in their industry, and include an easy opt-out. The email should make sense even to someone who never saw the post.
How is a pain point different from a recommendation request?
A recommendation request means the person has already decided a tool is the answer and is asking which one. A pain point post only describes the problem, so your email has to explain the solution before it can sell yours.
What happens to anonymous posts?
If a post cannot be tied to a real company from public business details, Startories does not turn it into a lead. Guessing who wrote an anonymous post is unreliable, and it is on the wrong side of the privacy line.
What should I say if a prospect asks how I found them?
The truth, briefly: their company came up in public discussions of a problem you solve, and you work on it with similar businesses. Offer to remove them from your list. Never pretend the email was random or that someone referred you.
How fast should I respond to a pain point signal?
Within a few days is usually fine, since the problem is ongoing and no shortlist exists yet. If the post mentions a deadline, such as an audit or a renewal, act within 24 to 48 hours.