How do you research a company before a sales call?

Start with the decision you need to make, not a data hunt. Confirm the official domain, capture how the company describes what it sells, map its products and connected websites, review the markets and customers it mentions, look for recent product or hiring changes, and corroborate important claims against an independent source. Then write down the specific reason the company might need your outcome — or disqualify it.

How long should you spend researching a prospect?

Depth should follow potential value and uncertainty. A simple company can take fifteen minutes; a complex group with several brands takes longer. Do not spend an hour on an account that fails the basic fit test in five minutes.

Is it legal to research a company before contacting them?

Reviewing publicly available business information — a company’s own website, its documentation, public registries, app listings, and public company accounts — is ordinary commercial research. What matters is staying within public sources, respecting the terms of the platforms you use, and following the marketing and privacy rules that apply to the outreach itself in your jurisdiction.

What should you look for when researching a potential customer?

What the company sells and who it says it sells to, its products and connected websites, the countries and markets it mentions, its pricing and go-to-market model, recent product, hiring, or positioning changes, and any public activity suggesting the situation your product addresses is present.

What is the difference between firmographics and company research?

Firmographics — industry, headcount, location, funding — are filters. They tell you a company belongs to a segment. Company research explains the situation: what the business actually does, how it is structured, what changed recently, and whether there is a credible reason for it to care right now.

Should research findings go into the outreach message?

Mostly no. The research stays behind the message. Reference one specific public observation, state the problem it may create without claiming certainty, connect it to an outcome, and ask one answerable question. The purpose of the research is relevance, not proof of effort.

How to Research a Company Before You Pitch: A Practical Guide for Founders

Most weak sales messages are written too early.

The founder finds a company name, glances at the homepage, and begins composing a pitch. Because the research is shallow, the message has nowhere useful to go. It falls back to generic claims about saving time, improving efficiency, or using AI.

A better sequence is: research the company, form a business hypothesis, then decide whether a pitch is justified.

This guide explains how to research a potential customer using publicly available business information. It is designed for founders, indie hackers, developers selling SaaS, and small agencies that cannot afford to waste limited outreach on accounts with no credible reason to buy.

If you are comparing the underlying concepts first, start with business intelligence vs. company intelligence: internal performance data and external company context solve different problems.

Start with a question, not a data hunt

Company research becomes endless when the objective is “find everything.” Before opening tabs, define the decision you need to make.

Useful research questions include:

Does this company fit our target customer situation?
Is there a visible operational problem our product may address?
Has something changed that makes the problem more relevant now?
Which part of the company would experience the outcome?
What evidence would make us decide not to contact it?

The last question is important. Good research is not a machine for justifying outreach. It should also help you disqualify companies quickly.

Write the question at the top of your notes. Every source you review should help answer it, qualify it, or reveal what you still do not know.

1. Confirm the official company domain

Begin with the official website and verify that you have the correct company. Similar names, acquired brands, regional entities, and abandoned domains can create confusion before the research has even started.

Review the homepage, product pages, pricing, about page, contact details, legal footer, careers, documentation, release notes, and status page when available.

Capture the company's own language:

What outcome does it sell?
Who does it say the product is for?
Which industries, countries, or use cases appear repeatedly?
Does it position itself as software, a service, a marketplace, or a combination?
Which objections does the website try to answer?

Do not rewrite the company into your preferred category. Preserve the words it uses, because those words will make your later questions more accurate.

2. Map products and connected websites

Many companies are larger or more fragmented than their primary homepage suggests. Look for product domains, documentation sites, support portals, status pages, app listings, sub-brands, regional sites, and domains linked from official profiles.

Connected websites can reveal:

Multiple products serving different customer groups
A shared infrastructure or operating layer
A recent acquisition or brand consolidation
Developer-facing products that receive little homepage attention
Geographic expansion through localized domains

Treat a link as evidence of a relationship, not necessarily ownership. Record why you believe two properties are connected and prefer official cross-links or corroborating independent sources.

3. Understand customers and markets

Now identify the commercial context. Review case studies, customer logos, solution pages, marketplace listings, partner directories, job descriptions, and public announcements.

Ask:

Is the company selling to consumers, businesses, governments, or several groups?
Does it focus on a narrow vertical or a horizontal workflow?
Which markets and languages does it support?
Does its pricing imply self-service, sales-led, usage-based, or enterprise procurement?
Are the named customers similar to the companies you already serve?

The purpose is not to collect every logo. It is to understand the operating environment into which your product would need to fit.

4. Look for current activity and change

A static company description is less valuable than a dated view of what is changing. Review official release notes, product announcements, pricing pages, developer documentation, repositories, package registries, job openings, and partner updates.

Potential changes include:

A new product or pricing model
Expansion into another country or customer segment
A growing integration ecosystem
Consolidation of previously separate products
New compliance or operational requirements
Reduced activity across previously maintained properties

No individual signal proves intent. A job opening can remain online after priorities change. A repository commit can be routine maintenance. A pricing page can be an experiment. Record dates and seek supporting signals before treating a change as strategically important.

5. Compare claims across independent sources

An official website is the starting point, not the entire research record. Compare material claims with sources such as legitimate public registries, official partner pages, app stores, developer platforms, industry publications, and the company's current public accounts.

The goal is corroboration. If several sources agree on the same product relationship, market, or recent change, your confidence increases. If they conflict, preserve the conflict as an open question.

IBM's explanation of sales intelligence emphasizes combining public information and other sources to understand prospects and tailor decisions. For a founder, source comparison also reduces a common outreach mistake: confidently referencing information that is outdated or belongs to a different company.

6. Separate observations from inferences

Use two columns in your notes.

Observed: The company links three product domains from its official group page. Its documentation added two integrations this quarter. Its careers page lists roles in a new country.

Inferred: The company may be consolidating product operations and expanding into that market.

The observation is source-backed. The inference is a hypothesis. Keeping them separate makes your pitch less presumptuous and your discovery questions more useful.

Avoid statements such as “I know you are struggling with...” when public information cannot support them. Prefer: “I noticed these changes and wondered whether they are creating...”

7. Identify the business reason to care

Only now should you connect the company's situation to your product.

Write one sentence for each part:

Situation: What appears to be happening in the company?
Problem: What operational difficulty could plausibly follow?
Outcome: What measurable or practical result does your product help produce?
Unknown: What must the company confirm before this becomes a real opportunity?

If the chain is weak, do not force it. A company can match your ideal customer profile and still have no visible reason to change. Recognizing that is a successful research outcome.

8. Write outreach around the hypothesis

Early-market sales is usually a founder responsibility because the conversation links customer context directly to product learning. Andreessen Horowitz's guidance on founder-led sales emphasizes finding strategically aligned customers, qualifying whether an opportunity is real, and understanding the target organization.

Your message should be short even when the research was thorough:

Mention the specific, public observation.
Explain the problem it may create without pretending certainty.
Connect that problem to an outcome—not a long feature list.
Ask one answerable question.

The research stays mostly behind the message. Its purpose is to improve relevance, not to overwhelm the recipient with everything you found.

A fictional before-and-after example

Before research:

We built an AI platform that helps teams automate operations and save time. Can I show you a demo?

After researching company.com:

I noticed that company.com now links three product sites through one partner program, and the shared documentation added several integrations recently. Has keeping partner information consistent across those product surfaces become more manual as the ecosystem grows? We help product groups centralize that workflow without replacing their existing portals.

The second message is still a hypothesis. It does not claim private knowledge or guaranteed need. It gives the recipient a specific reason to answer and an easy way to correct the founder's understanding.

A reusable company-research checklist

Before contacting a company, confirm that your notes cover:

This process can take fifteen minutes for a simple company or much longer for a complex group. Depth should follow potential value and uncertainty. Do not spend an hour researching an account that fails the basic fit test in five minutes.

Research improves the conversation—it does not replace it

Public company intelligence has limits. Sources become outdated. Legal entities do not always map neatly to brands. Public activity may not reflect internal priorities. The company itself remains the authoritative source for its current situation.

The purpose of research is to enter that conversation with better questions. It helps you prioritize accounts, avoid irrelevant messages, explain why you are reaching out, and recognize when there is no credible opportunity.

DefenceCore is evaluating a manually operated company intelligence service for founders. Submit a company website and, if the request is accepted, the team will prepare a source-backed review of its publicly available business footprint. It is not an automated instant scan, and it does not promise private, confidential, or restricted information.

The most useful pitch begins before the writing. It begins when a founder decides to understand the company first.