Find Decision Makers by Company Domain: A Step-by-Step Method

To find decision makers by company domain, define the buying group first, then query a people data source with that domain plus seniority and department filters, and verify what comes back. The domain is the anchor: it identifies the company without the ambiguity of a name, which matters when several firms share one.

Why the domain is the right starting point

Company names collide. Dozens of businesses call themselves “Apex” or “Summit”. A domain is unique, machine-readable and already present in most CRMs and web forms. Every people search endpoint worth using accepts it as the key input. BusinessMCP’s search, documented on its People Data API page, requires only a domain of up to 253 characters, with seniority, department and title filters as options.

If your list has company names but no domains, resolve them first. A company-level lookup does that cheaply: BusinessMCP’s company data API takes a domain, URL or work email and returns the company behind it, and offers a search by industry, country and size for building a list from scratch.

Step 1: define the buying group

A decision maker is not a title; it is a role in a particular deal. Sketch the group before you query.

Role	What they do in the deal	Typical filter idea
Economic buyer	Owns budget and signs	Senior leadership, finance or the relevant function head
Champion	Wants the problem solved	Manager or director in the using team
Technical evaluator	Judges fit and integration	Senior engineer, architect or security
Blocker	Can stop the deal	Procurement, legal, security review
End user	Lives with the result	Individual contributors in the department

You rarely need all five. For a developer tool, you might want a technical evaluator and an economic buyer. For a finance product, the controller and the head of finance. Be explicit; the filters follow from the roles.

Step 2: translate roles into filters

Use the tightest filter that still returns someone. With a search endpoint that offers seniority (up to six values), department and title_contains, a role becomes a query.

1. Set seniority to the levels that match the role, not every level.
2. Set department to the function that owns the problem.
3. Use title_contains only when a keyword is distinctive, such as “security” or “payroll”.
4. Cap the limit so a large account does not return a surprise list.

Seniority labels vary by provider, and the BusinessMCP page does not enumerate the accepted values here, so check the developer docs for the exact strings. Our people search article covers the request fields in detail.

Key takeaway: the best list is short and specific. Two named people you can personalise for beat twenty names you cannot.

Step 3: check the results

Raw results are candidates. Before outreach, do three checks.

• Currency. Does the title look current? Spot-check a sample against the company site or a professional profile.
• Fit. Is the person actually in the buying group, or just a similar title in a different division?
• Status. If an email is returned, read its status. BusinessMCP labels stored addresses valid, catch_all or unknown, and marks addresses built from the company’s format as pattern, which are unverified.

Segment your outreach by that status. See catch-all email addresses for why the middle label needs extra care.

Step 4: fill gaps

Searches often return a name with no email, or an email with no title. Fill gaps with the other endpoints.

• Name and domain known, email missing: use the email finder.
• Email known, title missing: use person enrichment.

Keep calls efficient. All three BusinessMCP endpoints bill only on a found result, but per-item search charges still add up on large accounts.

Step 5: log and respect limits

Record where each contact came from, when you pulled it and why. The provider logs every people call with the declared purpose, and your records should match.

Remember what the source will not give you. BusinessMCP never returns people located in the EU, EEA, UK or Switzerland, nor people placed in California, Texas, Vermont or Oregon. A company headquartered elsewhere may therefore show fewer decision makers than you expect, because the exclusion applies to the person’s location. If a region matters to you, plan another route and check the rules that apply. The privacy article explains the background.

A worked example

Imagine you sell a monitoring tool and are targeting 50 mid-size software companies. Your buying group is a head of engineering (economic buyer) and a senior platform engineer (evaluator). For each domain, you search with engineering as the department and a senior seniority level, capped at three results. You review the lists, drop two accounts that return nobody in covered regions, enrich four contacts who lack titles, and find emails for six named people you met at a conference. You log the purpose as outbound prospecting. The numbers here are illustrative, not predictions; the shape of the workflow is the point.

Common mistakes

• Pulling everyone at the account and emailing them all.
• Using one filter set for every industry.
• Ignoring stale titles.
• Treating pattern emails as verified.
• Forgetting that excluded regions return nothing by design.
• Skipping the purpose log.

Pair this method with a periodic refresh, since roles change and old lists decay.

Prioritising accounts before you spend

Not every account deserves a search. Rank accounts first, using fit and timing signals you already have: industry, size, recent hiring, a product launch, a visit to your pricing page. Run people searches only for the top tier, and use cheaper account-level lookups for the rest.

BusinessMCP’s Data API overview lists company, IP, email and people tools under one key, which suits this staged approach: a company lookup at $0.02 per found call can confirm industry and size before a person-level search at $0.08 per item is justified. The saving comes from skipping accounts that would never have qualified, not from any discount. Re-rank every quarter, because the accounts worth the spend change as your product and market do.