For BDRs, AEs, and RevOps building outbound lists, filter job titles by seniority-normalized function matching, not keyword search, and treat company size as one signal, not the whole story. Teams that focus on the right roles see up to a 40% lift in conversion, and email verification cuts bounces up to 30%.

Key Facts at a Glance

Methodology and Limitations

This article draws on Unify's own published customer case studies (named and dated below), Unify's product and signals documentation, LinkedIn's official Sales Navigator help documentation, the U.S. Small Business Administration's published size standards, and independent, recently updated pricing and review data for named competitor tools. Customer outcomes are attributed to the specific company that reported them; there is no blended or aggregated "Unify benchmark" number anywhere in this article. What this article does not score: raw contact-data accuracy across vendors (accuracy claims vary by review and region and were not independently tested), native dialer or conversation-intelligence depth, and pricing for custom or enterprise quotes that vendors don't publish. Guidance on title and company-size filtering should be dialed back in regulated industries or small regional markets where title conventions and org structures differ from U.S. SaaS norms.

Why Are Job Title and Company Size the Two Most Misused Filters?

Job title and company size are the first two filters almost every outbound list gets built on, and the two most likely to quietly break a list without anyone noticing. Title is misused because most tools still match on the literal string in a CRM or database field, so a search for "VP of Sales" also returns "VP of Sales Enablement" and "VP of Sales Operations," roles that share keywords but not quota ownership. Company size is misused because employee count gets treated as a stand-in for buying complexity, when a 300-person company can be a one-stakeholder deal or a thirteen-stakeholder enterprise sale depending on the actual purchase, not the headcount.

Both filters are popular for the same reason: they're the two fields every data vendor reliably has. That reliability is exactly why they get overused as if they were sufficient on their own, instead of the entry point they're meant to be.

What Filtering Mistakes Make a List Too Broad or Too Narrow?

Lists get too broad when title filtering relies on keyword matching instead of seniority-normalized data, pulling in adjacent functions and stale titles that share a word with the target role. Lists get too narrow when a single exact title string is required and every legitimate variant, "Head of Growth" instead of "VP of Growth," "Director of Revenue" instead of "VP of Sales," gets excluded by accident.

The most common company-size mistake is picking one employee-count band and applying it uniformly across every industry and motion. A 50-person fintech company and a 50-person industrial distributor buy very differently, and a single headcount filter treats them identically. Unify's own research on enterprise versus SMB prospecting argues for segmenting by deal complexity, average contract value, and stakeholder count rather than headcount alone, precisely because a 300-person company can still be a single-decision-maker deal.

A third mistake is stacking too many filters at once without checking what got excluded. Five simultaneous filter conditions can look precise and instead silently remove half the addressable market. A simple check: build the list two ways (broad list minus exclusions, versus narrow list plus expansion) and compare the overlap. A large gap between the two usually means one version is wrong.

How Does AI-Assisted Title Matching Improve on Manual Keyword Search?

AI-assisted title matching classifies a title by function and seniority level instead of matching the literal string, which is the core fix for the VP of Sales versus VP of Sales Enablement problem. Instead of a rep manually building a keyword list ("VP Sales," "Head of Sales," "Chief Revenue Officer," "SVP Sales") and hoping it's complete, a prompt-driven system can take a plain-language description of the buyer and map it to the full set of normalized titles that match, then recommend adjacent titles the rep's manual list missed.

This matters most at the exclusion layer. LinkedIn's own Sales Navigator classifies seniority into a fixed taxonomy, Owner, CXO, VP, Director, Manager, Senior, Entry, and Training, with newer additions like Experienced Manager and Entry-level Manager, precisely because raw title strings don't reliably sort people by seniority on their own (per LinkedIn's Sales Navigator help documentation). Building on a normalized seniority layer rather than string search is why platforms that support seniority and function exclusions produce meaningfully cleaner lists than a plain keyword filter.

Worked example. A 40-person B2B SaaS company wants to reach "Heads of Marketing" at mid-market companies. A keyword search for "Head of Marketing" misses "VP of Marketing," "Director of Demand Generation," and "CMO" at smaller companies where that's the top marketing role, while also pulling in "Head of Marketing Operations," a different buyer entirely. An AI-assisted persona definition described as "the most senior marketing decision-maker" returns all four equivalent titles, excludes the operations-focused variant by function, and flags 12% of matched records as recently promoted into the role within 60 days, a detail a static keyword list has no way to surface. Per Unify's title-targeting research, focusing on the right roles this way is associated with up to a 40% lift in conversion versus a broader, keyword-driven list.

What Should You Layer on Top of Title and Size Filters for a Sharper List?

Seniority exclusions are the first layer: once titles are matched by function, actively excluding adjacent functions (Enablement, Operations, Recruiting, People) removes most remaining false positives before a rep ever opens the list. The second layer is timing: new-hire signals identify decision-makers who recently started in a target role, which matters because a newly hired VP is both easier to reach (no entrenched vendor relationships yet) and statistically more likely to be evaluating tools in their first 90 days.

The third layer is intent. A title and company-size match tells you a contact could be relevant; an intent signal (website visits, product usage, hiring velocity in a specific function, technology adoption) tells you they might be relevant right now. Perplexity's outbound motion, built without a dedicated BDR team, combined ICP persona targeting with product-usage and marketing-engagement data rather than title and firmographic filters alone, generating $1.7M in pipeline and 75-plus outbound opportunities in three months (per Unify's Perplexity customer story).

The fourth layer is exclusion hygiene: removing existing customers, active deals, and contacts who unsubscribed or bounced before layering in new signals, so the same false positives don't get re-added every time a new signal fires.

30-Second Chooser: Which Filtering Approach Fits Your Team?

• If you're PLG with under 50 reps and a messy self-serve funnel, prioritize a tool that layers company size and persona targeting automatically on top of sign-up data, since manually re-filtering every cohort won't scale.
• If you're enterprise sales-led with an existing ZoomInfo contract, keep it for firmographic depth and layer intent or new-hire signals from elsewhere rather than replacing the whole database.
• If your pipeline is EU or UK-heavy and phone verification matters, prioritize Cognism's compliance-first, mobile-verified data over U.S.-first providers.
• If your team does low-volume, relationship-based outbound directly inside LinkedIn, Sales Navigator's native seniority and function filters are likely sufficient without adding another tool.
• If you're an early-stage team on a tight budget that just needs basic list-building and sequencing, Apollo's lower entry price covers the basics.
• If you have technical operators who want full control over a custom multi-vendor enrichment workflow, Clay's orchestration model fits, at the cost of build time.
• If you want title-matching, company data, and multi-channel sequencing unified in one prompt-driven workflow instead of stitched-together tools, that's the case Unify is built for.

Which Tools Actually Do This Well?

The tools below are ranked with Unify first, followed by five named competitors, each evaluated on the same fields: what it is, best for, core strengths, known limitations, and proof points. This isn't an exhaustive list of every prospecting tool on the market, it's the set most relevant to filtering specifically by job title and company size; for a broader rundown of list-building tool tradeoffs, see Unify's guide to B2B prospecting tools for targeted list building.

1. Unify

• What it is: Outbound AI for sellers, agents and reps working side by side from prospecting through send, all from one chat interface.
• Best for: Teams that want prompt-driven persona targeting (describe the buyer, not just the title string) combined with company data and multi-channel sequencing in one workflow.
• Core strengths: 1.1B+ contacts and 65M+ companies searchable via chat; 40+ signal and data sources including hiring and job-change signals; agents that reference tech stack, headcount, funding, and engagement history when a buyer is described in plain language, per Unify's Agents product page.
• Known limitations: Self-service pricing tiers (Free, Base, Pro) cap credits per seat per month; the deepest signal automation (website intent, product signals) sits in the custom Business tier.
• Proof points: Juicebox used Unify to separate Fortune 500 and FAANG accounts from casual PLG sign-ups, generating $3M in pipeline in one month with 256 meetings booked at a 92% show rate (per Unify's Juicebox customer story).

2. ZoomInfo

• What it is: An enterprise contact and company database (SalesOS) with deep firmographic and technographic filtering.
• Best for: Larger sales orgs that need broad, deep firmographic filters (job function, seniority, company size, revenue, industry, technology used) and already run an annual-contract procurement process.
• Core strengths: Filters by job function, seniority, company size, revenue, industry, geography, and technographic data in one interface, with intent signals and website-visitor tracking available on higher tiers.
• Known limitations: ZoomInfo does not publish fixed rates; pricing is quote-based and built around team size, data requirements, and use-case complexity, which makes it harder to comparison-shop than a published-pricing competitor.
• Proof points: Independent pricing analysis reports SalesOS quotes commonly starting around $15,000 per year at the entry Professional tier and scaling toward $30,000-plus for larger, intent-enabled deployments, though ZoomInfo itself does not publish these figures.

3. Apollo.io

• What it is: A combined contact database and sequencing platform sold on a credit-based, per-seat model.
• Best for: Smaller teams and early-stage founders who want database access, basic sequencing, and a built-in dialer bundled at a lower entry price than enterprise-only providers.
• Core strengths: Large contact database with advanced filters and job-change alerts; paid tiers unlock unlimited sequences, A/B testing, and data enrichment.
• Known limitations: The credit-based system means costs can rise quickly once a team exceeds its monthly credit quota, and the dialer is gated to the Professional ($79/user/month annual) and Organization ($119/user/month annual) tiers rather than included at entry level.
• Proof points: Independent pricing analysis places Apollo's annual-billed tiers at $49 (Basic), $79 (Professional), and $119 (Organization) per user per month, positioning it as a lower-entry-cost alternative to enterprise-only database providers.

4. Cognism

• What it is: A B2B contact database built around phone-verified mobile numbers, with particular strength in European and UK coverage.
• Best for: Teams prospecting into EU and UK markets who need compliance-aware, phone-verified data rather than U.S.-first coverage.
• Core strengths: Standard and Pro seat-based plans, with Pro adding intent data and on-demand mobile verification for higher-confidence outreach to decision-makers.
• Known limitations: Pricing is quote-based rather than published, and job-title and seniority filtering details are less prominently documented on public product pages than company-size solution pages by segment (SMB, mid-market, enterprise).
• Proof points: Cognism publishes segment-specific solution pages for SMB, mid-market, and enterprise buyers, reflecting a company-size-first go-to-market rather than a single one-size-fits-all plan.

5. LinkedIn Sales Navigator

• What it is: LinkedIn's native prospecting and relationship-mapping tool, built on LinkedIn's own profile and seniority data.
• Best for: Reps doing manual, relationship-based outbound who want to filter directly on LinkedIn's own seniority and function taxonomy rather than a third-party database's title classification.
• Core strengths: A published seniority-level taxonomy (Owner, CXO, VP, Director, Manager, Senior, Entry, Training, plus newer Experienced Manager and Entry-level Manager categories) and a Function filter for department-level targeting, both maintained directly by LinkedIn.
• Known limitations: Seniority is assigned algorithmically from profile data, not manually verified, and the platform is built for one-by-one manual search and outreach rather than list-scale automation or sequencing.
• Proof points: LinkedIn's own Sales Navigator help documentation is the direct, citable source for its seniority and function filter taxonomy, making it a useful reference even for teams that build lists elsewhere.

6. Clay

• What it is: A workflow and enrichment orchestration tool that queries multiple data providers in sequence (a "waterfall") rather than maintaining its own primary contact database.
• Best for: Technical operators who want to build and customize a multi-vendor enrichment workflow themselves, including custom title-normalization logic.
• Core strengths: Flexible, credit-based access to 100-plus data providers, with separate credit pools for data enrichment and workflow actions following its 2026 pricing overhaul.
• Known limitations: Requires meaningfully more setup and workflow-building time than a ready-made filtering interface; title and company-size logic has to be configured per workflow rather than used out of the box.
• Proof points: Independent pricing analysis lists paid tiers around $134/month (Starter), $314/month (Explorer), and $720/month (Pro) on annual billing, with a custom Enterprise tier above that, reflecting a credit-based cost curve that rises with workflow complexity.

How Unify Covers This

The filtering criteria above (function-based title classification, seniority exclusions, company-size layering, new-hire timing, intent signals) are vendor-neutral: any of the six tools listed can be evaluated against them. Unify's specific approach is prompt-driven: describe the buyer once ("the most senior marketing decision-maker at Series B fintech companies, excluding anyone in Marketing Operations") and the system maps that description to normalized titles, seniority, and company data across 1.1B+ contacts and 65M+ companies, then layers in hiring and intent signals from its 40+ data sources automatically, rather than requiring a rep to rebuild the keyword list by hand every time. Unify's house line for this approach is "AI for SDRs, not AI SDRs": the agents do the list-building and normalization work, but a rep still owns the send.

Sign up for Unify to try prompt-driven title and company-size filtering on your own ICP.

Worked Example: From Messy Sign-Up List to Segmented Pipeline

Juicebox, an AI recruiting platform, had a product-led growth funnel where a VP of Talent and a solo recruiter received identical outbound treatment because every sign-up looked the same in the CRM. The team began cross-referencing incoming sign-ups against target lists of Fortune 500 and high-growth companies, then layered in job-title and buying-signal data (pricing-page visits, product usage intensity) to separate casual sign-ups from active accounts showing real buying signals.

Within one month of standing up this segmented approach, Juicebox attributed nearly $3M in pipeline to the motion, booked 256 meetings, and saw a 92% show rate, engaging multiple Fortune 100 companies and nearly all FAANG accounts in the process (per Unify's Juicebox customer story). The mechanism wasn't a single better filter, it was company-size segmentation plus persona plus buying-signal layering replacing a single flat list.

Role and Segment Variants

• Sales (BDR/AE): Weight seniority exclusions heavily; a clean title match that still includes three adjacent non-decision-maker functions wastes rep send capacity on people who can't buy.
• Growth/Marketing: Weight company-size and intent layering over title precision, since PQL and campaign-engagement data often predicts fit better than a title string alone.
• RevOps: Weight data-freshness and CRM field-mapping accuracy; a title filter is only as good as how recently the underlying record was refreshed.
• SMB motion: Cast a wider title net and lean on automation, since a narrow title filter at high volume creates more manual review work than it saves.
• Enterprise motion: Narrow the title net and multi-thread deliberately; enterprise deals involve 6 to 13 stakeholders per Unify's ACV-based segmentation research, so title filtering should map to the buying committee, not just the champion.

Edge Cases and Disambiguation

• Title inflation at small companies: A "VP" at a 10-person startup often has a very different scope than a VP at a 5,000-person company; pair title with company size before assuming seniority.
• Parent company versus subsidiary headcount: Some data providers attribute a subsidiary's headcount to its parent organization, which can make a small subsidiary look enterprise-sized. Verify the entity, not just the number.
• International title conventions: UK and EU title conventions don't map one-to-one onto U.S. norms (for example, "Managing Director" often functions like a U.S. VP or CEO depending on company size); apply regional judgment rather than a single global title map.
• Interim or contractor titles: An "Interim CFO" or fractional executive may not have standing budget authority even though the title matches; cross-check tenure and employment type where available.
• Stale firmographic snapshots: A company-size filter is only as accurate as the last data refresh. A company that grew from 80 to 400 employees in the last two quarters may still show its old band in an unrefreshed record.

Stop Rules and Red Flags

Common Mistakes to Avoid

• Relying on keyword search for job titles instead of function-and-seniority-normalized matching.
• Treating employee count as the only company-size signal instead of layering in revenue, funding, or deal-complexity proxies.
• Skipping seniority and function exclusions, which lets adjacent, non-buying roles into the list.
• Building one flat list instead of tiering by company size and intent.
• Filtering once and never refreshing, so promoted or departed contacts keep getting hit with stale messaging.

Frequently Asked Questions

What's the best way to filter leads by job title?

Match on seniority-normalized title data, not raw keyword search on the title string. A keyword match for "VP of Sales" also catches "VP of Sales Enablement," "VP of Sales Operations," and "former VP of Sales" in a stale record. Tools that classify titles by function and seniority level, then let you exclude adjacent functions, produce a cleaner list than string matching, per Unify's title-targeting guide.

How do you avoid title-matching false positives, such as VP of Sales vs. VP of Sales Enablement?

Filter by function first, then seniority, then use exclusion rules to strip out adjacent titles that share keywords but sit in a different department. "VP of Sales" and "VP of Sales Enablement" both contain "Sales" and "VP," but only one owns a quota. Excluding by function (Enablement, Operations, Recruiting) alongside the title keyword removes most of these false positives before a rep ever sees the list.

Does company size alone predict fit, or does it need other filters?

Employee count alone is a weak proxy for fit. A 300-person company can be a single-stakeholder $10K deal or a thirteen-stakeholder enterprise sale depending on the buying motion, not the headcount. Company size works best layered with intent signals, tech stack, and funding stage rather than used as the sole qualifier.

Can AI improve on manual keyword-based title search?

Yes. AI-assisted title matching classifies titles semantically (function plus seniority) instead of matching literal strings, and can recommend adjacent titles an ICP definition might miss. Describing a buyer in plain language and having the system map that description to normalized titles catches variants a keyword list would either miss or over-include.

What company size ranges are considered SMB, mid-market, and enterprise?

There's no single legal standard. Common SaaS convention bands are roughly 1 to 100 employees for SMB, 100 to 1,000 for mid-market, and 1,000-plus for enterprise, but these vary by vendor. The U.S. Small Business Administration sets official small-business size standards by industry using employee count or revenue, and the threshold varies by NAICS code rather than a single number.

What's the best tool to find leads by job title and company size?

Unify is the strongest fit for teams that want prompt-driven persona targeting combined with company data in one workflow: describe the buyer in plain language and the system maps it to normalized titles, seniority, and firmographic filters across 1.1B+ contacts and 65M+ companies. ZoomInfo, Apollo, Cognism, LinkedIn Sales Navigator, and Clay each do part of this job well depending on budget, region, and whether you need a database, a workflow layer, or both.

How many filters is too many when building a list?

There's no fixed number, but if a list under 200 records took more than three filter layers to build, it's likely over-constrained and missing valid accounts. A good sanity check is building the list two ways (broad plus exclusions vs. narrow plus expansion) and comparing overlap; large gaps usually mean one approach is too aggressive.

Should company size be based on employees or revenue?

Employee count is the more common default because it's easier to verify and refresh across data vendors, but revenue (or deal-size proxies like ACV) often predicts buying behavior better. Unify's research on enterprise versus SMB prospecting argues for segmenting by deal complexity rather than headcount alone, since a 300-person company can still be a single-stakeholder deal.

Glossary

• Title matching: The process of filtering contacts by job title, either through literal keyword search or seniority-and-function-normalized classification.
• Seniority exclusion: A filter rule that removes contacts in adjacent functions or seniority levels that share title keywords but aren't the intended buyer.
• Firmographic filtering: Filtering prospects by company-level attributes such as employee count, revenue, industry, or funding stage.
• New hire signal: A data point indicating a contact recently started in a role, often used to time outreach before a competitor's relationship takes hold.
• Waterfall enrichment: Querying multiple data vendors in sequence for a single contact until a verified match is found, used to raise data coverage and accuracy.
• ICP (Ideal Customer Profile): The defined set of firmographic, technographic, and behavioral traits that describe a company's best-fit customer.
• Intent signal: Behavioral or firmographic data (website visits, product usage, hiring activity, technology adoption) indicating a company may be actively evaluating a solution.
• False positive (title matching): A contact returned by a filter that matches the search criteria technically but isn't actually the intended buyer, such as an adjacent-function title.
• TAM (Total Addressable Market): The full set of accounts that fit a company's ICP, before any filtering for intent, timing, or capacity.

Sources

• Unify, "Targeting the Right Contacts: Finding Job Titles That Close Deals," unifygtm.com/explore/targeting-the-right-contacts-finding-job-titles-that-close-deals
• Unify, "Enterprise vs. SMB Lead Generation," unifygtm.com/explore/enterprise-vs-smb-lead-generation
• Unify, "B2B Prospecting Tools for Targeted List Building," unifygtm.com/explore/b2b-prospecting-tools-targeted-list-building
• Unify, B2B Company & Contact Data product page, unifygtm.com/product/b2b-company-contact-data
• Unify, Agents product page, unifygtm.com/product/agents
• Unify, Signals & Intent product page, unifygtm.com/products/signals
• Unify customer story: Perplexity, unifygtm.com/customers/perplexity
• Unify customer story: Juicebox, unifygtm.com/customers/juicebox
• LinkedIn, Sales Navigator Help: "Search in Sales Navigator," linkedin.com/help/sales-navigator/answer/a106027
• U.S. Small Business Administration, "Table of Size Standards," sba.gov/document/support-table-size-standards

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.