Who are the decision makers here?
Give a company domain or profile URL and get its curated decision-maker set back. This is the list build.
A curated set rather than a seniority filter — sourced beyond one network, cross-checked, and continuously monitored. Ask who the decision makers are at a company, or whether one person is one.
Platforms shipping their own products on these records today.












Most providers expose decision makers as a field you filter on. Two of these three are not lookups at all — they answer whether a specific person qualifies, which is a different job.
Give a company domain or profile URL and get its curated decision-maker set back. This is the list build.
Give one profile and get a yes or no, checked against the company they are at now rather than the one on an old record.
Give a profile and a company together, and confirm the status at that specific company. This is the check before you route, score or send.
A seniority filter over profiles is something anyone can run. The difference is the inclusion rule, where the names come from, and what happens to the wrong ones.
Someone who can decide for their department or at company level. In practice C-suite, or director and above.
Decision makers are also drawn from company websites and cross-checked, so the set does not inherit one network’s blind spots.
Detected and dropped, so what you get is a curated set rather than a scrape with a job title filter over it.
People move. The set tracks those moves rather than being cut once and redated.
Every one of these is the same set, asked a different way.
Vertex Labs · account score
Committee, not headcount78
Pull the set for a target account so a score reflects who actually decides, not headcount. For sales-intelligence platforms.
Inbound — before routing
Checked before it reaches a rep
Check one profile against one company before routing it to a rep or firing a sequence. For RevOps and lead routing.
One move, two signals
Re-check the committee on a cadence and catch the moves — a departure is churn risk, an arrival is a warm lead. For customer success.
who decides at Vertex Labs?
Answered from the set
Give a copilot the decision-maker set for an account so it reasons about the right people. For AI and agent teams.
Committee size by stage
A CFO appears at Series B
Aggregate the set across a segment to see how buying committees are shaped before you plan coverage. For strategy and analytics.
Account · Vertex Labs
Attached once, kept current
Attach the committee to an account in your own systems instead of researching it per deal. For data teams.
We resolve and validate our own graph rather than reselling someone else’s, and matching stays hashed — so the raw identifiers you send are never exposed.
Security & Trust CentreDepartment and seniority: someone who can decide for their department or at company level. In practice that is C-suite, or director and above.
A title filter inherits whatever the source says, including titles that are inflated, stale or invented. This is a maintained set — names are drawn from more than one place, cross-checked, and wrong ones are removed.
It is continuously monitored rather than cut and redated. 10M+ of the set sits across the top 250K companies.
Yes, and that is the part most providers cannot do. Give a profile on its own to check against their latest company, or a profile plus a company to confirm the status there.
Yes — Decision Makers is a segment of the People Dataset as well as a live product.
No. We resolve and validate our own graph across 18+ data sources.
Fifteen minutes, your own account list, and the committees we return for it.