TL;DR: Use a 6-step workflow to define buying roles, normalize titles, filter accounts, waterfall-enrich contact fields, verify records, and enforce suppression rules. For Sales, Growth, and RevOps teams, Unify searches 1.1B+ contacts and 65M+ companies, then checks 11+ email and phone vendors so more of the workflow runs in one place.

Methodology and limitations

This guide combines a vendor-neutral workflow with current Unify product data and one named customer case, verified in August 2026. It avoids universal match-rate or bounce-rate claims because results change by geography, persona, company size, and provider mix. Pylon's figures are individual results, not a benchmark. Compliance notes are operational guidance, not legal advice.

What is the best way to find decision-maker contact information at scale?

The best method is a governed pipeline that separates targeting, discovery, enrichment, verification, and permission checks. A larger database does not fix a vague persona, and a correct title does not prove that a person owns the decision.

• Step 1: Define the buying committee and each role's authority.
• Step 2: Build a qualified account universe before spending enrichment credits.
• Step 3: Normalize titles by function, seniority, region, and company context.
• Step 4: Waterfall-enrich email and phone fields across complementary sources.
• Step 5: Verify, deduplicate, and record field-level provenance before outreach.
• Step 6: Apply suppression, opt-out, and regional compliance rules.

Step 1: Define the buying committee before searching

Define decision-making roles as jobs in the purchase, not as a list of impressive titles. Most B2B purchases involve some combination of an economic buyer, operational owner, technical evaluator, user champion, and procurement or security reviewer.

For each role, document the problem owned, likely function, minimum seniority, disqualifying responsibilities, and evidence of authority. This prevents finding the right department but the wrong person.

Step 2: Build the account universe before enriching contacts

Filter companies before finding people so every enrichment request starts with a plausible account. Use firmographic fit, geography, business model, company size, and relevant technology, then add current signals such as hiring, website activity, product usage, or a leadership change.

Fit answers whether an account could buy. A signal suggests why it might act now. The guide to targeted B2B list building explains how to combine both layers.

Step 3: Normalize titles without flattening real authority

Title normalization should map every raw title to a function, seniority band, and likely buying role while preserving the original title for review. The same words can imply different authority at a startup, a regional subsidiary, and a global enterprise.

Use equivalence groups instead of exact-match strings, then verify scope through company size, geography, reporting line, and public role context.

Step 4: Waterfall-enrich each field across complementary sources

Waterfall enrichment queries another source when the first source cannot resolve a field with enough confidence. Email, mobile, company, and title data should have independent fallback logic because one provider may be accurate for one field and incomplete for another.

Sequence sources around the ICP. Test the same representative sample across providers, record field-level provenance, stop when confidence is sufficient, and measure each source's marginal gain. The guide to waterfall enrichment architecture covers the mechanics.

Step 5: Verify and deduplicate immediately before action

Verification belongs immediately before sequencing, not only when a record is first collected. A valid-looking email can become stale after a job change, and a returned phone number can belong to a previous role or employer.

Store the verification timestamp, provider, confidence state, and original source. Match against CRM records before creating a new person, and define which system owns each field.

Step 6: Apply suppression and regional rules before outreach

Compliance must be an execution gate, not a cleanup task. Check internal opt-outs, prior objections, customer and active-opportunity exclusions, account ownership, restricted regions, and any channel-specific do-not-contact status before a contact enters a sequence.

The FTC requires truthful sender information, a valid postal address, and a working opt-out mechanism for covered commercial email. California's current privacy regulations define notice and opt-out duties for covered businesses that sell or share personal information. GDPR also gives individuals the right to object to processing for direct marketing. Review the B2B data compliance guide with counsel before operationalizing a new region.

How should you evaluate tools for this workflow?

Evaluate tools against the job they perform and the evidence they return. A vendor-neutral test should reveal whether a system improves coverage without hiding source quality, creating duplicate records, or bypassing governance.

How Unify covers this

Unify is outbound AI for sellers, where AI agents and sellers work side by side from finding buyers already in market to reaching them with the right message. Reps can search 1.1B+ contacts and 65M+ companies, use 40+ signal and intent data sources, and waterfall 11+ email and phone vendors from the same chat-driven workflow, according to the live B2B Company & Contact Data page.

Unify connects list building, proprietary enrichment, research, and sequencing without removing seller judgment. The operating principle is AI for SDRs, not AI SDRs: agents handle repetitive discovery and drafting while the rep remains responsible for the conversation and send.

What does the workflow look like in practice?

Pylon provides a published example of the system operating at scale. Its team used CRM-enriched data, website intent, technology data, and new-hire signals to identify decision-makers and tailor outbound by company context.

Per the Pylon customer story, the team prospected and enriched 6.5K+ contacts and launched 10 automated Plays within 2 weeks. The same story reports a 3X increase in outbound meetings and 4.2X ROI, plus $300K in new pipeline within weeks. These are Pylon's results, not a general benchmark or guarantee.

Use this 30-second decision framework

Choose the lightest workflow that preserves targeting quality and governance.

• If the account is strategic: use automation for discovery, then require manual authority and contact validation.
• If the ICP spans several regions: prioritize source diversity, regional title mapping, and local compliance review.
• If reps export between tools: prioritize a connected enrichment, CRM, and sequencing workflow.
• If records conflict: prioritize field-level provenance and deterministic overwrite rules.
• If contact data is old: reverify at sequence entry instead of trusting the original collection date.
• If the segment is extremely niche: combine automated discovery with specialist manual research.

How should the workflow change by role and segment?

The six-step architecture stays consistent, but ownership and review depth should change with the motion.

• SDRs and AEs: optimize for fast discovery, visible context, and manual validation on priority accounts.
• RevOps: own source order, CRM field rules, deduplication, suppression, and auditability.
• Growth and marketing: connect account signals to persona discovery without bypassing ownership or exclusions.
• Enterprise sales: map a buying committee and verify authority instead of stopping at one senior contact.
• EU and regulated segments: increase legal review, provenance requirements, retention controls, and channel-specific suppression.

Handle these edge cases explicitly

Edge cases should enter a review queue rather than being forced through default automation.

• Founder-led companies: titles reveal little, so validate operating responsibility through current public context.
• Regional titles: translate meaning and scope, not just words.
• Consultants and fractional executives: confirm whether the person can buy for the target company.
• Recent job changes: keep the old record for history, but do not assume the old email or phone still belongs to the person.
• Shared or role-based inboxes: do not treat an address such as sales@ or info@ as a verified decision-maker contact.

Stop or adapt when a red flag appears

Pause the affected records immediately when identity, ownership, permission, or deliverability becomes uncertain.

What are the top five mistakes to avoid?

• Searching one executive title and calling the result a buying committee.
• Enriching an unqualified account list and mistaking coverage for relevance.
• Flattening international titles without checking local authority and scope.
• Writing provider data into the CRM without provenance, confidence, or deduplication rules.
• Treating compliance and suppression as manual checks that happen after enrollment.

Start using Unify to move from a prompt to a targeted, enriched list and a reviewed sequence in one workflow.

Frequently asked questions

What is the best way to find decision-maker contact information at scale?

Use a repeatable six-step workflow: define the buying committee, build the target-account universe, normalize titles, run multi-source enrichment, verify and deduplicate records, then apply suppression and regional compliance rules before outreach. Test the process on a representative sample from your own ICP before scaling it.

How many decision-makers should you find at each account?

Find enough contacts to cover the roles involved in the buying decision instead of relying on one senior title. The right number depends on company size, deal complexity, and whether users, champions, technical evaluators, and economic buyers are different people. Start with the smallest complete buying group for your motion.

What is title normalization in B2B prospecting?

Title normalization maps inconsistent job-title strings to a common function, seniority level, and likely buying role. It lets a search treat titles such as VP Sales, Head of Sales, and Commercial Director as possible equivalents without assuming they carry identical authority at every company.

Why use waterfall enrichment for contact data?

Waterfall enrichment sends an unresolved field to another provider when the first source cannot return a sufficiently confident result. This can improve coverage across different regions and segments while preserving field-level source attribution. Unify currently waterfalls more than 11 email and phone vendors.

When should contact information be reverified?

Reverify contact information immediately before it enters an outreach sequence, especially when it was collected earlier or the person may have changed roles. Reverification should also be triggered after a bounce, a job-change signal, or conflicting company and title data.

Can B2B teams use work contact data under GDPR and CCPA?

The answer depends on purpose, jurisdiction, collection method, and how the data is sold, shared, or used. GDPR gives people the right to object to direct marketing, while California rules include notice and opt-out obligations for covered businesses. This article is operational guidance, not legal advice, so counsel should review the final workflow.

When is manual research better than automated contact sourcing?

Manual research is most useful for strategic accounts, unusual regional titles, small private companies, regulated buying groups, and contacts whose authority cannot be inferred from a database record. Automation should handle repeatable discovery and verification, while a seller validates ambiguous or high-value cases.

Glossary

• Buying committee: The group of people who influence, evaluate, approve, use, or block a B2B purchase.
• Decision-maker: A person with meaningful authority over whether and how a purchase proceeds.
• Title normalization: Mapping a raw job title to a consistent function, seniority level, and likely buying role.
• Waterfall enrichment: Querying complementary data providers in sequence until a field is resolved with sufficient confidence.
• Verification: Checking whether a contact field is current and usable before it enters an action.
• Field-level provenance: The source, timestamp, and method attached to one specific data value.
• Suppression list: A governed set of contacts or accounts that must not receive specified outreach.
• Firmographic fit: Company characteristics used to judge whether an account belongs in the target market.

Sources

• Unify, B2B Company & Contact Data, 2026
• Unify customer story, Pylon, live 2026
• Unify, Waterfall Enrichment: The 2026 B2B Contact Data Architecture
• Unify, The Sales Leader's Guide to B2B Data Compliance, updated July 2026
• Federal Trade Commission, CAN-SPAM Act compliance guide
• California Privacy Protection Agency, CCPA regulations effective January 1, 2026
• EUR-Lex, General Data Protection Regulation, current official text

About the author

Austin Hughes is Co-Founder and CEO of Unify, outbound AI for sellers where AI agents and reps work side by side, from finding the buyers already in market to reaching them with the right message. Before founding Unify, Austin led the growth team at Ramp, scaling it from 1 to 25+ people and building a product-led, experiment-driven GTM motion. Prior to Ramp, he worked at SoftBank Investment Advisers and Centerview Partners.