Find a company owner’s name, title, email and phone

Define the record you need

Decide whether you need the legal owner, a publicly identified founder, or a business decision-maker. A clinic's managing partner may handle a supplier proposal; a store manager may route it; a historical founder may have left.

For outreach research, keep the following fields separate:

Field	What to record	Evidence needed
Company	Trading name, location and domain	Matching business context
Person name	Name as published	A page linking the person to this business
Title	Exact role, including qualifications such as former	Nearby role text
Email	Address and recipient category	Public source plus person or business association
Phone	Number, location and extension if published	Contact context identifying whose line it is
Evidence	Short supporting wording and source URL per claim	The original page, not a search snippet
Checked date	Date of your observation	Your research log
Review state	Supported, missing, uncertain or conflicting	Reason for the state

These are worksheet fields; product exports vary. When role and contact evidence come from different pages, record both URLs.

Download the blank evidence worksheet CSV to record your own checks. It is a manual template, not product output.

Confirm the business and its website

Start with the company name and city, or its supplied website. Common names, old domains and franchise locations create mismatches. Open the site before searching for people.

Compare name, services, public phone and location. Two consistent signals are a practical research rule, without guaranteeing accuracy. For a renamed company, look for an announcement explaining the transition. A corporate domain can identify a brand without establishing a branch owner.

Follow redirects and record the final domain. A directory, social profile or booking service can identify a business, but it is a different source from the company's own website. If the site instead describes an unrelated company or a different city with no explanation, stop the person lookup and mark the match uncertain. Finding a valid email on the wrong website does not repair the company match.

Choose sources for each field

Choose the next source according to the field you still need.

Public source	Most useful for	Main limitation
About, leadership or team page	Names, roles and sometimes named email links	A founder story may describe the past
Contact page or footer	Business phone, location, shared inbox and routing	Company-wide contacts do not establish a person's direct channel
Individual biography	Connecting a named person, role and published contact	Check that the biography is still linked from the current site
News release or company announcement	Appointments, ownership changes and dated context	An older announcement is historical evidence
Public professional profile	Role history and company association	Self-reported roles may be stale or unavailable
Business registry	Entity identity, status and roles available in that jurisdiction	Coverage varies; an agent or officer is not automatically an owner
License or industry directory	Licensed person, entity and practice address	A license holder may work for the company without owning it
Chamber or business directory	Local identity and published business contact	Re-check the company website for changes
Domain registration lookup	Registration context for the domain	Registrant data may be redacted; a registrant is not necessarily the business owner

Read the registry's own description. California's records guidance lists available officer, director, member and manager information, while explicitly distinguishing ownership and personal email or phone information that it does not maintain. Do not advertise a state search as a guaranteed owner-contact database.

Oregon's privacy guidance distinguishes a registered office receiving legal papers from an assumed-business-name registrant who is an owner. It also explains that some sole proprietors need no state name registration. Role labels and missing-record meanings depend on jurisdiction.

For domain registration, ICANN identifies RDAP as the definitive gTLD registration-data source from January 28, 2025. Registration context is a secondary check, not a replacement for business and person evidence.

For a field-by-field decision about registries, profiles, directories and websites, use the public-source comparison guide. It explains which source can fill an identity gap and which can only provide a company contact route.

Research one company

Use a short, deliberate sequence:

1. Identify the business. Save the name, city, original website and final domain. Resolve obvious mismatches before collecting contacts.
2. Read leadership pages. Follow About, Team, Leadership, Our Story or individual biography links. Capture the person and published role together.
3. Read contact pages. Record the public business inbox, phone and form. Note location-specific numbers and any named recipients.
4. Look for person-specific channels. Open a named biography or email link. Confirm that its contact belongs to the same person rather than another employee or the page footer.
5. Fill a remaining evidence gap. Use a registry for entity context, a recent company announcement for a role change, or a relevant professional profile for role history.
6. Review the row. Open each source again and check whether it supports exactly what you entered. Preserve blanks, conflicting claims and dates.

Extract candidates before assigning them to a person

When your starting point is a company website, collect what it actually publishes before deciding who owns each contact. This applies to a manual check and to reviewing a tool's extracted candidates.

Website location	Candidate to extract	Association to review
Visible leadership card or biography	Published name and exact nearby role	Does the wording identify this person's relationship to this business?
Visible contact text	Email address or phone number	Is the contact labeled for a person, office, department or the whole company?
Email or call link	The mailto: address or tel: number in the link target	Does the target agree with the displayed text, and does the surrounding block identify the recipient?
JSON-LD Person record, when present	Its name, jobTitle and any published email or telephone	Does the record belong to the same person and company? Is the role explicit, and does the current page support the context?

For an email button, inspect its link target as well as its label. A mailto: link can also contain a subject or other query parameters; record the address separately. A tel: link may identify the business line even when it appears below an owner's biography. Preserve the published extension and location instead of converting it into a direct-person number.

JSON-LD is structured data embedded in a webpage, not an independent confirmation of identity or current ownership. A Person record labeled CEO or manager stays that role unless another explicit statement supports ownership. Names, role text and contacts must keep their page context; collecting every email on a domain and attaching it to the first name found creates an unsupported record.

Compare the visible page with the readable HTML when a tool misses information. Content rendered only after JavaScript runs, text inside an image or a linked PDF may not be in the HTML the tool inspected. Record a reading limit and review manually rather than treating the missing result as proof that the company publishes nothing. The worked record below shows how extracted candidates become separate person and business fields.

When navigation is incomplete, search the domain plus a role or page term. Try site:example.com owner, site:example.com founder, or site:example.com contact, substituting the real domain. Search the quoted company name with its city when the website lacks the information. These queries are discovery aids; a result snippet is not the final evidence.

Set a research budget. If it ends without an owner name, retain the business route and missing-evidence reason. Research further when a specific identity is essential to the decision.

Interpret names and titles

Keep the role the company publishes. Owner, co-owner and an explicit ownership statement support a public ownership claim. Founder identifies who started a business; CEO, president and general manager identify leadership roles. Neither category alone proves current shareholding.

California's official FAQ describes an agent for service of process as the designated recipient of court papers. This individual or corporate agent role does not establish ownership.

Some role words depend on context. Principal can identify a senior architect, a practice leader or an owner. A license qualifier or registered professional establishes a qualification, not a universal ownership relationship. A blog author establishes authorship. A review reply signed with a first name provides a lead for further research, not a complete identity record.

For a franchise or group, record which entity and location the claim concerns. Keep multiple owners as separate people when the source supports them. Selecting one contact for a campaign is your routing choice; it does not erase the others or make that person the sole owner.

If a Contact page lists an operations manager or a department contact, the owner-and-manager contact-page guide explains how to combine it with leadership evidence and choose the relevant business route.

When your goal is to reach the person who handles a specific purchase or operational issue, use the owner or operating manager contact workflow to check the location, responsibilities and approval route.

Three real public website examples

Manually checked on October 3, 2026, these examples establish published information, without verifying legal ownership, mailbox delivery, phone reachability or extraction coverage.

Website	Supported person and role	Contact conclusion
Zack de Vito team	Jim Zack, Owner / Managing Principal	His biography names an email recipient; the contact page labels phone numbers by office
LH & Associates team	Lynn Htut, Owner / Principal	Visible email text is person-linked, but the contact link points to a placeholder; mark the address needs_review
DesignLeveL team	Tracy Kameoka, Owner, Founder and Principal	The visible email and phone are general company contacts; no direct owner channel was established in this check

Zack de Vito publishes jim@zackdevito.com in Jim's biography. Its San Francisco office number, 415.495.7889, belongs in a business-phone field; the contact page does not label it Jim's direct line.

A filled four-field record from the published pages

This is a manual research example checked on October 3, 2026, not an OwnerClue task, export or mailbox-delivery test. It records one selected person; the team page also identifies another owner, so this is not a complete ownership roster.

Field	Recorded value	Evidence and scope
Company website	zackdevito.com	The company’s own team page and contact page
Person name	Jim Zack	Named person in the team page and biography
Published title	Owner / Managing Principal	Exact role published for this person on the team page
Person-associated email	jim@zackdevito.com	Address explicitly associated with Jim in his biography; delivery untested
Business phone	415.495.7889	San Francisco office number on the contact page
Direct owner phone	Blank	No number was explicitly labeled as Jim's direct line in these checked pages
Role and email source	https://www.zackdevito.com/team/	Person and email association come from the same source
Phone source	https://www.zackdevito.com/contact/	Keep the office context when combining the record
Checked date	2026-10-03	Observation date, not a claim that the company updated the pages that day

The name, title and person-associated email form a supported person record. The phone is a supported company route. A CRM may display them on one row, but that formatting does not make the office line a direct owner phone. Keep the distinctions in an evidence file even if the CRM import has fewer columns.

LH & Associates displays lynn@lynnhtut.com in Lynn's section, but its link target is mailto:mail@example.com. Two other staff links use that same placeholder. Preserve the visible address as a published candidate with needs_review status and confirm it through another business route before use. The placeholder is not a usable contact; another employee's Principal Architect role also stays separate from ownership.

DesignLeveL illustrates a useful incomplete record: keep the supported person and role, retain the company's public contact route, and leave direct owner email and phone unconfirmed. For detailed interpretation of team cards, biography links and repeated footers, see the team-page research guide.

Connect email and phone to the right recipient

An email on the same domain may be a shared inbox, another employee's contact or a service provider's address. Check its recipient association.

Prefer a link or address explicitly published in the person's own record. A personal-looking address elsewhere remains a candidate until its association is supported. If only a general inbox or contact form is available, record it as a business route. Ask the company to direct a relevant enquiry to the right person rather than claiming you have the owner's email.

Separate email source, recipient association and delivery status. A published address can be old. A verifier's result concerns mailbox checks; it does not identify the current owner. Hunter's verification FAQ explains that valid results can change, accept-all domains create uncertainty, and unknown results can occur when servers block checks. Preserve the provider, status and check time separately if you use such a service.

The public owner-email guide walks through person-linked addresses, shared inboxes, mismatched link targets and missing-email outcomes with additional company examples and a dedicated worksheet.

If you need only the name-email pair, the company owner name and email workflow starts from the company, separates identity from email association, and checks the pair before a CRM import.

Apply the same reasoning to phones. Main line, branch number, named extension and direct mobile are different fields. A mobile line classification does not prove whose phone it is or authorize texting. Keep the published contact purpose and honor requests to stop contact. Choose an appropriate business channel for the enquiry.

Handle missing and conflicting information

Use explicit outcomes instead of silently completing a row:

Situation	Record	Next action
Person named, no personal email	Person and exact role; direct email blank	Keep the public business inbox, form or phone
Email found, no owner named	Email as a business contact; owner blank	Look for supported leadership evidence only if needed
Older source names a founder	Historical role and source date	Check current leadership or a later announcement
Website and profile name different leaders	Both sources; conflicting state	Compare dates and ask the company if necessary
Site cannot be read	Research failure and affected URL	Revisit manually; do not conclude that no owner exists
Brand page covers several branches	Brand-level evidence	Seek location or franchisee evidence before naming a branch owner

A checked date records your observation, not a company update. Recently captured undated pages can still be stale. When sources disagree, preserve alternatives and explain the narrower conclusion you can support.

Stop at the level you can support. A direct-contact gap and an identity gap need different next steps. The first may be solved through a business routing channel; the second needs stronger person evidence.

Build a repeatable batch

Before batch enrichment, preserve company, location, normalized domain and row identifier. Repeated domains may represent multiple branches. Decide whether the research unit is a location, company or person before deduplicating.

Test a sample including a clear owner, general inbox, chain location and missing evidence. Apply the full-list review rules. Complete-looking rows can still match the wrong business or another person's email.

Measure relevant businesses, correct website matches, supported people, public-email rows and explicitly person-linked emails separately. Define a usable record for your task before calculating coverage or cost. A hundred business emails do not equal a hundred owner emails. Keep website research and independent delivery checks as distinct stages.

Export an evidence file alongside a smaller CRM import. Preserve source URLs, checked dates and review reasons when a receiving template omits them. Import phone numbers as text to retain international prefixes. Re-check stale or conflicting records before important outreach, and keep a suppression list for contacts who ask not to hear from you again.

Use OwnerClue for website research

OwnerClue supports two starting points: an industry-and-location Maps search, or domain enrichment for websites you already have. Existing-domain batches accept up to 100 input rows; a 200-website list needs two batches.

Website inspection attempts up to five same-site URLs per business, starting with the homepage and following relevant contact, about, team or leadership links. Failed or unreadable attempts can leave fewer readable public HTML pages. The workflow does not execute browser JavaScript, read images or PDFs, or inspect every page on the site.

Automatic owner extraction starts with a supported JSON-LD Person record whose published role explicitly identifies an owner or founder. When that record is unavailable, an optional AI fallback can use explicit wording in inspected page text. The text fallback depends on availability and configuration; owner fields can remain blank when it is unavailable or disabled, even if a manual reader can see an owner's name. A manager or executive title alone does not populate the owner field. The result stores one supported owner/founder record, rather than automatically returning every co-owner or a general management directory.

A supported record retains the published role, wording, source URL and capture time. An email published in that supported structured person record can receive an owner-associated label; the AI text fallback supplies person evidence without promoting a separate email to an owner email. Other extracted addresses can remain public business contacts or contacts needing review. Review the recipient category instead of assuming the primary email belongs to the named owner.

The workflow does not automatically search registries or social sources, guess email formats, or verify delivery. Review uncertain associations using the state dictionary.

Maps full CSV uses owner_evidence for supporting wording; domain full CSV uses owner_quote. Both include owner_source_url and owner_captured_at. Keep the full file when preparing a CRM import. A successful readable-domain result can still have missing owner or email fields; billing documentation explains what is charged.

Enrich your existing websites or start a local search. Review a small list using these evidence rules before expanding it.

Frequently asked questions

How can I find a company owner for free?

Start with the website, then address gaps through public profiles, announcements or entity records. A free lookup may show officers or agents without proving ownership or providing direct contacts.

Can one page provide name, title, email and phone?

Yes, if it explicitly publishes them together. Often the person appears on a leadership page while the phone belongs to the company. Preserve separate sources and recipient categories.

Is an owner name plus info@ a complete owner contact?

It is an identified person with a general business contact route. It can support a routing enquiry, but it should not be labeled a direct owner email. Keep the personal-contact field blank unless stronger evidence supports it.

Does email verification prove who owns the mailbox?

No. Delivery checks and recipient attribution answer different questions. Keep the public page connecting the address to the person, and record independent verification status separately. Neither establishes the person's current legal ownership of the company.

What should I do when a founder has left?

Preserve the historical founder role and dated source. Look for current leadership or a company announcement before choosing a recipient. Do not keep using a former person's name simply because it makes personalization easier.

How do I research hundreds of company websites?

Normalize inputs, choose your company or location unit, test a varied sample, process batches, and review uncertain rows. Retain person evidence and contact sources in the full export. Use separate counts for business contacts and person-linked channels.

Can I always recover missing information with more searching?

No. A business may publish no owner's name or direct contact. Record what you inspected and use its public business route when appropriate. An honest incomplete record gives the next researcher a clear starting point.