How to Find the Named Decision-Maker at a Company, Not a Generic Inbox

Published 2026-09-23 by Dale Taylor

Why a generic inbox wastes the outreach you've already done

A lot of what gets sold as "prospecting" is really just company-level targeting. You get a list of businesses that fit a profile, you find the general contact address, and you send. The company matched. The person didn't.

That matters because a generic inbox has no owner. It's usually checked by whoever drew the short straw, filtered by whatever spam rules the business has set up, or forwarded to three different people none of whom feel it's specifically theirs to answer. None of that is a decision-maker problem you can fix by writing a better subject line. It's a targeting problem, and it happens before the email is even written.

I run Aigentic through Claude Code, and the outbound I send myself goes through exactly this problem if I let it. A list of "companies that look like a fit" is easy to build. A list of "people at those companies who can actually say yes" is a different exercise, and it's the one that determines whether an email gets read by someone with the authority to act on it.

What "named decision-maker" actually requires

Two things have to be true for a contact to count as a named decision-maker rather than a guess:

**The role has to be right for what you're selling.** A generic "find me a contact" search returns whoever the data provider ranks highest, which is often someone in HR or admin because their profile is well filled-in, not because they buy anything. You have to search by the combination of company and title that actually matches your offer. If you're selling automation work, that's usually an owner, a director, or an ops lead, not a generic "manager" role picked because it was the first result.

**The email has to be verified, not inferred.** Most lead tools will happily generate <firstname.lastname@company.com> for anyone whose name and employer they know. That's a guess based on a common pattern, not a check that the mailbox exists. It's the difference between "this is probably their email" and "this address has been checked and responds." The first one bounces often enough to hurt your sender reputation. The second one doesn't, because it's actually been verified rather than assumed.

Aigentic Intelligence, the product I built and run our own outbound through, does both of these as one step rather than two separate tools bolted together: it identifies the company, resolves the named decision-maker for that company against the role you're targeting, and returns a verified work email rather than a pattern guess. It's built and live, and it's what our current outbound runs on. I'm not claiming it's flawless. I am saying that doing role-matching and verification properly, in one pass, is what separates a named contact from a guessed one.

The practical steps, if you're doing this yourself

You don't need a product to get this right, you need the discipline to do both steps rather than stopping at the first one. It's slower than pulling a company list and firing off to a shared inbox, but it's the difference between an email that gets read by someone who can act on it and one that sits in a folder nobody owns.

1. **Define the actual buying role before you search**, not after you get results. Write down the job function that would say yes to what you're selling, specifically enough that "manager" on its own doesn't qualify. For most small B2B sellers that's the owner or a named director, because that's who can act on a decision without checking with someone else.

2. **Search by company and role together**, not company alone. A tool that returns "the most senior contact we have on file" for a company is not the same as a tool that returns the person matching the role you specified. If your data source can't filter by title against a specific company, you're going to end up back at a generic contact with better presentation.

3. **Verify before you send, not after you get a bounce.** A bounced email doesn't just fail to land, it tells the receiving mail server something about your sending domain, and enough of them do damage. Verification isn't a nice-to-have step at the end. It's what makes the difference between a real send and an expensive guess.

4. **Check the result against a human read, not just a green tick.** A verified address confirms the mailbox exists. It doesn't confirm the person still works there or that the title is current. Company data goes stale, particularly at smaller businesses where nobody's updating a directory. A quick look at the person's current role, wherever you can see it, catches the cases where the data is technically valid but practically wrong.

5. **Treat a bounce as a data signal, not just a failed send.** If an address bounces, that's information about the source you got it from, not just a lost email. If a source bounces often, stop trusting its verification and start checking it against a second source before you send again.

Where this still goes wrong

None of this makes outreach guaranteed to land. A verified email that reaches an inbox still has to be read, and being read still depends on whether the message is worth fifteen seconds of that person's attention. Getting the right person's real address is the precondition for a good cold email working, not a substitute for writing one.

It's also worth being honest that "verified" is a claim about the mailbox, not a promise. A verified address can still belong to someone who's left the role, changed companies, or simply doesn't check email that day. Verification reduces the failure modes you can control. It doesn't remove the ones you can't.

The point of doing this properly isn't a bigger number of contacts. It's fewer wasted sends to addresses that were never going to work, and a better chance that the ones that do land reach someone who can actually say yes.

Start with the Sample Five, five leads in your niche with a named decision-maker and a verified work email.