How to Find Real Business Problems Before You Pitch

The problem with guessing a prospect's pain

Weak prospecting often starts with a service and works backward. A web agency sees an old-looking site and concludes that the company "needs a new website." An automation consultant sees a contact form and concludes that the company "needs automation." An SEO consultant sees a business with competitors and concludes that it "needs SEO." Those statements describe what the seller wants to sell, not necessarily what the buyer needs.

Good research reverses the logic. It starts with the company. What is changing? What appears difficult, manual, inconsistent, slow, risky or strategically important? Which of those observations are supported by a source? Only then should the researcher ask whether the seller's offer is relevant.

This matters because public information has limits. A careers page can show that a company is hiring customer-support staff. It does not prove that the existing support process is failing. Reviews can show repeated complaints about response times. They do not prove the root cause. A public filing can show a strategic priority or risk. It does not tell you that a specific vendor category has been budgeted.

Use Observation → Consequence → Offer relevance → Validation question

Noustiq uses a four-step editorial framework for turning public evidence into a useful sales hypothesis without overstating what the evidence proves.

The first step should be factual. The second and third are usually inference. The fourth keeps the outreach honest.

Example: an automation consultant

Observation: a clinic advertises multiple new front-desk roles, offers booking by phone, and has recent reviews mentioning slow callbacks.

Consequence: the clinic may be handling more enquiry volume than its current process comfortably supports.

Offer relevance: an automation consultant who builds missed-call follow-up and enquiry-routing workflows may have a relevant service.

Validation question: "How are you currently handling enquiries when the front desk is busy or the clinic is closed?"

The research does not claim that the clinic has a broken process. It creates a reason for a useful conversation.

Where useful problem evidence comes from

Different sources reveal different kinds of evidence. The most useful research combines a small number of strong sources rather than collecting every available fact.

1. The company's own website

Start with pages that describe what the business sells, who it serves, how customers buy, how it operates and what it is changing. Product pages, pricing pages, contact flows, location pages, leadership pages, case studies, careers pages and newsrooms can all matter.

Look for operational facts. Does the company require customers to call for something competitors handle online? Is a service offered across multiple locations with different processes? Is the company opening new offices, introducing a new service or hiring for a new function? These observations can reveal complexity or change without requiring speculation.

2. Job postings and hiring patterns

A job posting is direct evidence that the company is recruiting for a role and describing work it expects someone to perform. The U.S. Bureau of Labor Statistics defines a job opening as a position for which work exists, the job could start within 30 days, and the employer is actively recruiting externally. At the company level, a public job post can therefore be strong evidence about current work and capability needs.

It is not evidence that the company wants to outsource that work. Hiring a RevOps manager may indicate increasing operational complexity. It does not mean the company wants a RevOps consultant. Treat the posting as context for a hypothesis, not as proof of vendor demand.

3. Public company filings

For U.S. public companies, SEC EDGAR is a high-value primary source. A 10-K can describe strategy, material risks and operating results; a 10-Q updates financial and risk information; an 8-K can disclose material events between regular reports. These documents are especially useful when a seller's offer connects to a stated risk, investment priority or operating change.

Filings are detailed, but that does not make every sentence sales-relevant. Focus on facts that change your assessment of fit, urgency, ownership or risk.

4. Official company registers

In the UK, Companies House can help verify company status, officers and filing history. That is useful for identity and governance research, particularly when a small business has a limited public footprint. The register itself warns that Companies House does not check the accuracy of all information filed, so it should be treated as an official record of filings, not as independent verification of every business claim.

5. Reviews and customer feedback

Reviews can reveal repeated customer-facing themes: delays, communication gaps, booking difficulty, fulfilment problems, quality inconsistency or service strengths. One angry review is weak evidence. A repeated pattern across recent reviews is more useful, especially if the same theme appears on the company's own support or policy pages.

A review still represents the reviewer's experience. Do not convert "three customers complained about response time" into "the company has an understaffed support department." The first statement is observable. The second is a diagnosis.

6. Leadership changes, funding, expansion and other triggers

LinkedIn Sales Navigator currently highlights events such as leadership changes, hiring, company growth, funding and engagement as account signals. HubSpot similarly describes news, funding and topic research as signals that can help prioritize accounts. Signals matter because they can explain why a company deserves a fresh look now.

But a trigger is not the same as intent. Funding may create capacity to invest, or it may be earmarked for something unrelated. A new executive may reassess suppliers, or may keep everything unchanged. The strongest use of a trigger is to sharpen the question you ask, not to claim you know the buying decision.

Score the evidence before you score the prospect

Before deciding that a problem is commercially relevant, evaluate the evidence behind it. A useful qualitative test is:

The purpose is not to produce a mystical score. It is to make the reasoning visible. If the evidence is weak, the correct outcome may be hold rather than forcing the prospect into outreach.

Seven problem patterns worth researching

Many B2B services can be researched through recurring problem patterns. The useful pattern depends on the seller's offer.

1. Growth strain: new locations, rapid hiring, expanded service lines or higher operating complexity.
2. Customer friction: repeated complaints, unclear buying steps, slow response or confusing self-service.
3. Process fragmentation: visible handoffs between forms, email, phone and manual workflows.
4. Capability build-out: hiring for roles or functions the company previously did not appear to have.
5. Technology change: migration, integration, platform adoption or a visible need to connect systems.
6. Commercial change: new market, new audience, new pricing, new product or expansion.
7. Risk or compliance pressure: a stated regulatory, security, operational or reporting requirement relevant to your expertise.

None of these is automatically a sales opportunity. The research question is whether the pattern is both observable and meaningfully connected to your offer.

What not to call a business problem

Some findings sound specific but are commercially empty.

• "Their website looks old." Appearance is subjective unless you connect it to a measurable usability, accessibility, conversion or maintenance issue.
• "They are not using AI." Lack of a technology is not itself a problem.
• "Their competitors rank higher." That may matter to an SEO prospect, but only if organic acquisition is relevant to the business.
• "They have no chatbot." A missing feature does not prove a missing outcome.
• "They are growing." Growth is context. Research what the growth changes operationally.
• "They could save time." Almost every company could. The statement is too generic to justify outreach.

Turn the problem hypothesis into a first-conversation question

The strongest research often produces a better question rather than a more aggressive pitch. If you observed that a company is hiring multiple customer-service roles, you might ask how inbound volume is currently routed. If you saw expansion into a second location, ask how the company keeps the customer journey consistent across locations. If a public filing describes cybersecurity as a material risk, ask which part of the control environment is receiving the most attention this year.

This style has two advantages. First, it is harder to be embarrassingly wrong because you are not pretending to know the answer. Second, it gives the buyer room to correct your hypothesis, which is useful field feedback for future research.

A practical 15-minute problem-research workflow

1. Define your offer precisely. Write down the actual problem you solve, for whom and under what conditions.
2. Read the company's core pages. Understand business model, customer, offer and buying journey.
3. Look for recent change. Check news, careers, leadership, locations, product launches and public announcements.
4. Check one independent or official source. Use filings, registers, reviews or professional identity sources when relevant.
5. Record observations separately from interpretations. Do not blend them into one paragraph.
6. Test offer relevance. Ask whether your service directly connects to the likely consequence.
7. Identify the likely owner. Map the issue to a function before searching for a person.
8. Write one validation question. If you cannot write a useful question, the research may not be ready for outreach.

Fifteen minutes is a workflow suggestion, not an evidence-based optimum. Strategic accounts may deserve much more time. Low-value targets may deserve less.

How this maps to Noustiq Pro

Noustiq Pro is designed around the distinction between evidence and assumption. A target company should not become "ready for outreach" just because contact details exist. The research record should preserve the reason to contact, the source behind it, the likely decision-maker and what remains uncertain.

The practical goal is a short prospect brief a human can inspect. If the reason to contact the company cannot survive that review, the right outcome is to keep researching or reject the prospect, not to manufacture a stronger story.

Problem-research checklist

• Can I quote or point to the observation without interpretation?
• Is the source current enough for the claim?
• Do I know what is observed and what is inferred?
• Is the likely business consequence plausible without several hidden assumptions?
• Does my offer directly address that consequence?
• Can I identify the function likely to own it?
• Is there a reason this matters now?
• Can I phrase the first outreach as a question that can be proven wrong?

If several answers are no, you may have a company that fits your list but not a researched sales opportunity.

Sources and further reading

These sources were reviewed on 26 Aug 2026. They support the external facts, legal guidance and platform-specific details referenced in this article. Noustiq's frameworks, examples and decision rules are editorial synthesis unless a source is explicitly named.

• LinkedIn Sales Navigator: How to Prioritize the Right Accounts
• LinkedIn Sales Navigator: How to Use Sales Navigator
• HubSpot: Use intent signals
• U.S. SEC: Using EDGAR to Research Investments
• Companies House: Search the register
• U.S. Bureau of Labor Statistics: JOLTS